Open falkien opened 3 years ago
@falkien that "ip=192.168.1.99" is not representative of anything on your network -- it is a "fixed" value defined in the firmware that honestly means nothing unless your device has an ethernet port (which I am pretty sure it does not).
Your firmware version has been patched before so we know the process can work on it.
If you're following the steps correctly and you're not getting the "- ip=30 ..." portion to show up (step 6) then the possible reasons are: 1-Wrong format of the SD card (it has to be FAT32) -- some people have mentioned that partitioning and formatting it in Linux helps, so you can try that or different format tools if you don't have a linux machine. OR 2-Incompatible SD card -- the SD card may work fine in the device after it's booted up but the bootloader support for SD card is more limited and may not read some types of SD card (so I suggest trying as many as you can). I usually have had success with Samsung EVO 32gb but have had issues with ATP Industrial Grade MLC (8GB). OR 3-There could be an issue with your reset button -- try to use it 'normally' (to reset the device after it's booted up) to verify it works, and if it doesn't work there's not much we can do on your device without opening and using a hardware programmer.
If you've checked the above you're welcome to post a ZIP of your SD card files (except for the SDT folder/directory) so I can take a look and make sure everything looks good.
I have tried 4 different cards. All formatted fat32. I have not tried it on a Linux box. I also only have 8gb cards. I will try the Linux format. if that doesn't work. I will get a 32gb card. The reset does work properly.
Ok, I got another SDcard and I am getting the same results. After going through this a few times I was going to attach the zip of the SD card. That is what caused me to pause before I did it. You said to post a ZIP of my SDCard except for the SDT folder/directory. I don't have a SDT folder/directory. Now I feel like I am missing a vital step. I have attached the ZIP file JIC. I did remove the ppsFactoryTool.txt because it had my wifi info. Thanks for the help. SDCARD.zip
@falkien Here's what's wrong: -ppsMmcTool.txt downloaded incorrectly has HTML data in it instead of correct contents.Please download the file correctly (do not create it from scratch as you may create it with an incorrect format) -- you can use this link to donwload it (right-click and Save As...): https://raw.githubusercontent.com/guino/Merkury1080P/main/mmc/ppsMmcTool.txt -initrun.sh downloaded incorrectly has HTML data in it instead of correct contents. Please download the file correctly (do not create it from scratch as you may create it with an incorrect format) -- you can use this link to donwload it (right-click and Save As...): https://raw.githubusercontent.com/guino/Merkury1080P/main/mmc/initrun.sh -incorrect env file (for wrong device) -- you also have a env.html which is also wrong (but isn't used so you can delete it). Please download the file correctly (do not create it from scratch as you may create it with an incorrect format) -- you can use this link to donwload it (right-click and Save As...): https://github.com/guino/Merkury1080P/raw/main/mmc/env
Once you correct the issues you should be able to root it. Also the SDT directory is only created on the SD card if you enable recording in the app (and also if the card format isn't wrong).
@guino Successfully rooted! Thanks! I am now at step 8 (RTSP) and there is no matching MD5 or Version on the ppsapp-rtsp page. Looks like the highest patch is for ppstrong-a3-tuya2_merkury-4.0.2.20200929 Mine is ppstrong-a3-tuya2_merkury-4.0.6.20210207. My CRC32 is a221d69c and my MD5 is e5e559715d01cf8060d56ba97ce4a79c. Do I need to go through the manual way with Ghidra and a HEX editor? I wanted to check to see if there might be an easier way, but I am up to the challenge. Thanks again for your help.
@falkien please look at the list closer and press the ‘load more’ to load it completely. https://github.com/guino/ppsapp-rtsp/issues/1#issuecomment-781001017
@guino WOW, I feel like a turd at this point. I followed the instructions and added the modified ppsapp file to the root of the SDCard and booted. I got the 2 beeps per the instructions. Now no matter what URL I use in VLC, I can't get the feed to come up.
rtsp://admin:admin@192.168.1.158:8554//Streaming/Channels/102 rtsp://admin:admin@192.168.1.158:8554//Streaming/Channels/101 rtsp://admin:admin@192.168.1.158:8554 rtsp://192.168.1.158:8554
I feel like I am wasting your time at this point. I am going to try and figure this out. Again, thank you so much for your quick responses and help. They have certainly got me this far.
These are the errors that I am getting in VLC live555 error: Failed to connect with rtsp://192.168.1.158:8554//Streaming/Channels/101 satip error: Failed to setup RTSP session
@falkien Can you confirm that you previously setup the camera with the app and that you can view the video feed in the app after patching?
did you try mjpeg/snap to see if it works?
I realize the instructions show an extra “/“ in the URL that should not be there I have updated the instructions to remove it - can you try without the extra “/“?
If you can please try any phone app that supports RTSP/ONVIF to see if it works.
I have tried this 20 times. I have the 1080p version and I have followed the instructions. The one thing that keeps happening is the part that is supposed to say ip=30 I get an address from my octoptint server, even if it's off.
Results from /proc/cmdline setenv bootargs mem=64M console=ttySAK0,115200n8 loglevel=10 mtdparts=spi0.0:256k(bld),64k(env),64k(enc),64k(sysflg),3m(sys),4032k(app),640k(cfg) ppsAppParts=5 ip=192.168.1.99:::255.255.255.0 eth=00:55:7b:b5:7d:f7
Here is the device info. {"devname":"Smart Home Camera", "model":"Mini 11S", "serialno":"064024936", "softwareversion":"4.0.6", "hardwareversion":"M11S_A2_V10_F37", "firmwareversion":"ppstrong-a3-tuya2_merkury-4.0.6.20210207", "identity":"MR2010162501419890", "authkey":"5lj3hUKLMxi0gshH0fx2qTgSfbWVtTJA", "deviceid":"pp019c6fcfe07f2e7863", "pid":"aaa", "WiFi MAC":"b4:fb:e3:29:83:cd", "ETH MAC":"00:00:00:00:00:00"}