Thanks for looking into this,
Not sure how I made these mistakes I did over 15 of them, maybe files got mixed up.
I ran the brick fix again, got the mini system into the cam. Then I extracted the cam data using putty, moved all these files extracted to a new backup folder,
I took the mod files I posted here and put them in the cam upload folder ready to upload into the cam, I then loaded the hex editor opened up the mt6_mod and
made the edit on 0x05 and changed this value to 0D (this is what I interpreted) it was 0c before.
uploaded the mod file into the cam (the exact same files i posted here with 0x05 changed to 0D) into the cam, uploaded the new FW into the cam reboot it hoping to see in sadp 192.168.1.64 but no detection.
I then decided to do everything from scratch.
back to mini system, extract files mod the needed areas including 0x05 save and upload I took a screen shot of the mod I did before I saved it so you can see what I changed in red.
Still nothing,
Is there anything evident that I did incorrectly?
After all this, I dont' see it in sadp I cant' login in via 192.168.1.64, I can't batch config it,
I CAN PING IT.
ordered the parts they were cheap! thanks under 3$ for everything
No, it's still able to be recovered.
The 'bootpara data' that's held in mtd6ro and is modified to convert the camera also has another copy in mtd5ro.
I'd guess that your problem camera still has telnet access - is that correct?
With either telnet access, or the serial console access, mtd5ro can be extracted and used to recover any data that was in mtd6ro which can then be fixed up and applied to the camera.
Looking at the files that you supplied, from the problem camera :
The checksum value in 0x05 is not correct.
The value in the file is 0x0C03 when it should be 0x0D03
On the newer firmware, that will cause a 'bricked' camera.
But easily fixed.