Nex-5n here.
UART0 shows the following just after the camera is reset for a firmware update, haven't gone further as it won't be possible to revert to older firmware once I do:
relevant FirmwareUpdater.logCode:E Uncompressing Linux.......................................................... done, booting the kernel.
Haven't looked at UART1 or JTAG yet (crash course welcome on JTAG, have not used it before)
Also booting with BOOT_MODE_1 high results in no serial output and the SD card light flashing on and off at about one second intervals. Not sure what it's waiting for here.
Thread: Sony NEX/Axx Firmware hacking
Results 21 to 30 of 158
-
Junior Member
- Join Date
- Jan 2012
- Posts
- 7
05-15-2012 11:05 AM
-
Junior Member
- Join Date
- May 2012
- Posts
- 1
05-21-2012 02:11 AM
I have been doing some research couple of months ago and i want to continue when i have the time (~mid june).
I backed up all of the fw version so if anyone is interested pm me
-
Senior Member
- Join Date
- Feb 2012
- Posts
- 233
05-27-2012 12:46 PM
A comparison of the VG-20 and other NEX camera FW's would be handy i'm sure in adding clean hdmi to the nex 5n, and nex 7. VG-20 allows clean HDMI and shares very few tecnical differences apart from case size. hardware is near identical
-
-
06-01-2012 08:53 AM
Just clean live view HDMI in Nex5n is my only real request, that, and a Sound Devices PIX 220 can make the NEx5n a little great FS100 ;) at $2500, obviously this will kill the VG20 for good.
Ahhhh.. dreaming..www.cajitacreativa.com
Sony Nex FS100 | Sony Alpha 77 | Sony Nex 5n
MacPro 8-Core | Led Cinema 24" | 4TB | 32GB
Cinema 4D R13 | Creative suite CS6 | ZBrush4r3
-
Junior Member
- Join Date
- Jan 2012
- Posts
- 7
06-04-2012 12:31 PM
Did the firmware update, no other output on UART0 unfortunately.
Seems to just send the entire .dat file through in chunks, not much more. Full FirmwareUpdater.log can be found at http://www.4shared.com/archive/du-Kt...l?refurl=d1url
Not sure where to go from here.
-
Member
- Join Date
- Jul 2012
- Posts
- 36
07-13-2012 09:41 AM
Just want to heat up the thread.
The firmware is a single tar in ustar format with standard initrd.img, vmlinux.bin, rootfs.img, standalone libraries and something that manufacturer calls scenarios. The last one are probably UI description. They are gzipped. Files starts with ESFf and has esf extension.
-
Junior Member
- Join Date
- Jan 2012
- Posts
- 7
07-15-2012 10:26 AM
I can't find the ustar/gzip header anywhere in the FirmwareData*.dat. How are you extracting these files?
-
Junior Member
- Join Date
- Apr 2012
- Posts
- 2
-
Member
- Join Date
- Jul 2012
- Posts
- 36
07-15-2012 11:11 AM
I don't say anything about gzip headers or even it's signature in firmware. And it's not a secret that FirmwareData_user_xxxxxxx_loader.dat is not a firmware itself. Its a container and even encrypted firmware file lay inside it not in a simple way. And sure you will not find any plain text in crypted firmware.
About encryption. I cannot tall anything about it at this moment.






