Recent content by domb84

Annoyingly getting it to dump the CA_DUMP.RAW config seems to have been a fluke as I cannot recreate it. If I flatten the config .BIN file completely it will accept it as long as it prefixes and suffixed with ANEKA001. I just need to work out what the 160 remaining values do I think!

More success! I've been playing with the UnCamHD online config generator that creates a DCTCONFIG.bin. I placed this on the SDCard with the uengmode file to engage engineering mode and received an error "Cfg file error: Check Magic Err!" I looked at the bin file and noticed it started and ended...

Apparently ls1 is some kind of serial interface. Plus I'm guessing the little image of a laptop around them shows they are some kind of serial/debugging interface? https://libre.solar/hardware/ls-one.html

These look promising to get a serial connection running on the m127. If i manage to get a console up and running will have a go at resolving the issues in that firmware.

That's amazingly detailed thanks @0dan0. I've not setup a serial port. I'm not sure if there is one on the M127 so I'll take a look. Sadly my C knowledge is zero and I'm not a developer. I could hack around with it if it was something simple like Python but my brain isn't cut out for proper...

Thanks. Did you decompile the firmware in ghidra or some such? I'm a complete novice at C and hacking firmware!

@0dan0 do you have any details on how you fixed the low res capture and scaling and altered the white balance? I've now got working flashable firmware for the m127 and would like to replicate those fixes if possible. https://mega.nz/folder/oLpkFQrS#fRa0Oag6eX_jlMZdxlqo6Q If you have any...

Success at last! I've managed to modify and flash back the firmware for the M127 machine while increasing the bitrate to 30Mbps. Put the FWDV180N.BIN file from the link on an sdcard, boot the machine and it will have a red light flash slowly around 5 times, then it will flash very quickly...

I seem to have made some kind of progress with the M127 firmware. I've been struggling to open the firmware in any of the tools were supposed to be able to work with it (JNovatekDec.jar and Novatek-FW-info). I managed to find the string FW96650A.bin in the firmware dump. A quick google of this...

I've had another crack at this and copied the first 2296 bytes to the merged modified firmware and recalculated the checksum. .\ntkcalc.exe -cw .\final_firmware.bin Sadly still doesn't boot. My modified firmware still ends up being 1,706,556 bytes rather than 4MB which is still confusing me...

I should have a bit of time this week to look at the M127 firmware again and seeing if I can get a modded one booting. Do you know if any of the fixes you've applied would work on the one I uploaded? i.e. are there any matching code across the firmwares? Perhaps you have a list of hex codes that...

Great work on the firmware adjustments. I have an m127 machine which appears to be much the same as the kodak etc but runs different firmware. I managed to take a dump of it but have struggled to get a bootable image flashed back. As you seem rather skilled with messing with firmware I don't...

Thanks i’ll take a look into it. I’m a complete novice with this so it’s a bit slow trying to reflash the chip with each change. My main concern is that the compressed rom is actually around 1-2MB/s smaller than the original, so something seems very wrong! Not just the 2k bytes.

I cannot seem to create a modified ROM that will boot. I believe it's down to the partition scheme but I'm out of ideas a this point. I can create an image where the offsets match, but after it's been compressed it's ~2.5MB so when it's flashed the rest is filled with 0's. When it's decompressed...

Hi Joe, yes I tried all of those. I have managed to get a better SOP8 clip and I flashed my modified firmware back and it didn't boot. Luckily I flashed the original dump back and it came back to life. I'm going to have another play with it, but hopefully someone who is cleverer than i can...