wz_mini_hacks
wz_mini_hacks copied to clipboard
gtxaspec
V2 installation proposed changes
current method:
- Run compile script
- script downloads firmware
- extracts firmware
- replace kernel
- repack firmware
- flash demo.bin
- boot wz_mini
The downside to this, is the need to modify the onboard flash with a new kernel image
proposed method:
- 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.
- download the stock firmware from the vendor
- flash stock firmware demo.bin ( we need this step since step 1 erases the onboard system, root, and driver partitions )
- 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.
I have successfully flashed four v2 devices using this method. If anyone would like to test, let me know!
Here are the new provisional installation directions for T20 devices which does not require compiling the firmware:
EXPERIMENTAL, MAY DAMAGE YOUR DEVICE. PROCEED AT YOUR OWN RISK. report back results if possible!
Installation ( for PanV1/V2 ONLY )
- This step only needs to be done ONCE, ever, for t20 based devices
- Format memory card, FAT32, DOS Partition type
- extract the file named
demo_uboot.bin.gz, and then copy the file nameddemo_uboot.binto root of memory card, and make sure it is the only file on the memory card - rename the file named
demo_uboot.binthat you copied in the previous step, todemo.binin the root of the memory card, again making sure it is the only file on the memory card - insert memory card into device. hold the setup button while inserting the power cable. the LED should light up purple, then you can let go of the button ( standard firmware flashing procedure )
- once the flashing is complete, the camera will reboot, and the LED will start rapidly flashing, once the rapid flashing stops, the camera will reboot.
- remove the memory card, insert it back into your computer, delete file named
demo.binon the memory card - download the stock firmware for the device. follow the standard flashing procedures.
- once the camera has been successfully flashed with the stock firmware, you may now proceed to install wz_mini
- you may now copy the contents of SD_ROOT to the memory card
- extract
factory_ZMC6tiIDQN.gzand copy it to the root of the memory card - you may now boot wz_mini on the t20 device.
after flashing, you may check the logs located at <memory card root>/wz_mini_u_boot_initramfs.log for debug info about the flashing result.
if you believe these directions can be simplified, please let me know!
Outstanding. I'm game. And I just figured out how to run the other script after getting Ubuntu loaded onto a stick and shaking off over ten years of Linux cobwebs! LOL At least I have the platform to try this now.
And my version of demo.bin actually worked..., albeit on one of three cams only. That does have me slightly concerned about those two cams. Multiple cards across all three cams only seem to work with one of the cameras. The other two take the latest OEM firmware and the latest (last) Wyze RTSP firmware without issue, but won't cooperate with wz_mini.
Is 7-Zip and acceptable alternative to enabling special permissions on the Windows folder and getting Samba running right on the Ubuntu thumb drive -- just to unzip and transfer 2 files back and forth? The tar command line utility in Windows 10 is not cooperating, either.
Too anxious to wait for an answer on the 7-Zip question. It works fine for the tasks and essentially makes the V2 process almost as easy as the V3 process for Windows users -- just a couple of extra steps and no Linux intimidation involved.
The process as described worked perfectly for me -- again, on one of three of my V2s. All three took the wipe down and the OEM recovery without a hitch. The same two problem children simply will not play nice with wz_mini no matter what I've tried so far. No logs generated from that process to analyze.
They did take the latest version of Wyze RTSP firmware with no problem..., which raises a question about flashing other firmware now since doing the wipe down and recovery. Any considerations there?
A couple of minor questions about the instruction list:
"once the camera has been successfully flashed with the stock firmware, you may now proceed to install wz_mini...."
"Install" had me confused enough to actually try flashing it to one of my trouble cams. Silly me. Perhaps 'prepare' or 'stage' wz_mini' would be a more accurate and less confusing instruction there? I also wondered if the original demo.bin file may somehow still be required.
Copying the contents of SD_ROOT to the memory card would include the T31 factory file and may be confusing to some who may wonder if both factory files are necessary. Are they? (I included both.)
There has also been a question of whether just copying the wz_mini folder is sufficient, or if the files themselves need to be copied individually. I believe just copying the folder contents actually gave me an error in the log when I tried it indicating the wz_mini folder itself could not be found and may have aborted the process as a result? (The memory is a little hazy after trying so many things with my two troublesome cams.)
All in all I personally think this is a great idea and applaud the effort, sir. Well done. And thank you!
both files can be included, only one is used depending on the device.
the folder wz_mini must be copied to the root, not the subfolders inside wz_mini.
after the stock firmware is flashed, the demo.bin files are no longer needed
< both files can be included, only one is used depending on the device.>
Some browsing elsewhere seems to suggest that an additional one may be required for the problem V2s that provides what the base u-boot is looking for on the SD card for these particular devices -- if I'm sorta understanding this sorta correctly.
@Bob-AOL
If you could try some things on the camera's that don't work with wz_mini:
- download the .860 firmware for your v2. flash your v2 with it
- verify via the mobile app that your camera is running on the .860 firmware
- if it is, proceed to download the .1002 firmware for your v2. flash your v2 with it.
- verify via the mobile app that you are on the .1002 firmware
- if it is, proceed to follow the new instructions to flash and install wz_mini
- report back if you can with results.
The new instructions procedure is what I originally followed as detailed previously. Doing it all over again starting at .860 instead of .1002 made no difference. Rather pointless since the uboot_demo.bin wiped the flash for a clean .1002 anyway, didn't it? At least the uboot_demo.bin version generated the attached log file that may shed some light. The SD card is still not recognized to generate a wz_mini initramfs.log file after flashing the new .1002 image and the camera just boots to the onboard firmware normally -- which is progress in one respect since the endless loop seems to have been somehow remedied. Just still no recognition of wz_mini on this hardware..
So I've gone back through all available layers of V2 firmware to 2020 and tried the conventional installation approach with each one. Still no joy
The one cooperative V2 is still cruising along nicely.
@Bob-AOL thanks for the valuable info and logs. Let me analyze and I'll get back to you.
@Bob-AOL I may have a solution, would you be willing to flash a test bootloader? I won't say it's without risk of bricking the camera. Let me know!
If it's no less dangerous than the other 'enhanced' method, sure. Have you tried it with success?
I'm also trying to establish a Linux platform that allows me to do everything in the Linux environment -- thinking there may be some degree of sensitivity by the problem cam flash to how I'm compiling and transferring the .sh file for use with the conventional method.
I know you're spread pretty thin and development can take time. Was just curious if there was any progress. I'd be willing to send you one of the cams if it would be at all helpful (or practical).
Again, your efforts in all of this are greatly appreciated!
can confirm this worked for me on two v2's and one pan v1. ultimately makes life 10 times easier in the long run. Would be wonderful to automate the process even more but I understand the limitations.
just did another v2. I was going to try to combine steps 7-10 but i accidentally copied the factory_ZMC6tiIDQN file for v3 and decided to just continue on. but it did flash the stock firmware with the SD_ROOT contents in the card. so odds are its safe to condense at least a little.
One minor issue. Looks like I cant open the rtsp streams from any of these now. tried VLC and motioneye. Edit: I take it back, It works if I only enable a single stream. probably resource related.
I tried this today on one of my V2s, and it seems to be working great! (I didn't even both trying to current official method first, so I can't compare to that.)
Could it be the cards or maybe the PC you're using to write to the cards? Maybe even the download is corrupted? Just spit balling.
On Sun, Sep 11, 2022, 5:40 PM Bob-AOL @.***> wrote:
Still only one for three here.
— Reply to this email directly, view it on GitHub https://github.com/gtxaspec/wz_mini_hacks/issues/241#issuecomment-1243057627, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKDOF46EBIJ5PQTVFMO3XQTV5ZNVPANCNFSM56O6U7OA . You are receiving this because you commented.Message ID: @.***>
Thanks. Been there. Done that..., multiple times. It's all pretty well covered above (and elsewhere). Our host is still working on it as is also covered above.
@gtxaspec
Just checking back in on this. I've re-visited everything again from scratch with the same results.
Success, I've taken the plunge and used this latest method to install wz_mini_hacks on my Wyze Cam 2.
I now have wz_mini_hacks operational on 7 Wyze Cam 3 and 1 Wyze Cam 2.
Thanks You!!!
@gtxaspec -- hey Bob, I'll have an update this weekend for ya!
Any update on this?
@Bob-AOL sorry for the delay, still need to test some things before I can get you a test image. My test setup is offline at the moment. I haven't given up on it yet!