ultramango / gear360reveng Goto Github PK

Hey there!
I noticed that the source code for the Gear 360 is not longer avaible for download on the Samsung website.

Since I want to build an long-exposure mode, it would be really helpful to have some of the source code.
Can someone privide me the "bundle" directly?

Thank you all in advance!

I finally could get a shell on the camera it was a 2 step process.

• First step to get a shell with camera in recovery mode:
  created info.tg and nx_cs.adj as in nx500 modding on the sdcard.
  added on the sdcard telnetd (copy of busybox) and wpa_supplicant.conf (in order to connect to my home wifi)
  test.sh has been modified in order to set up networking and start telnet as follows:
  wlan.sh start
  ifconfig wlan0 up
  wpa_supplicant /mnt/mmc/wpa_supplicant.conf
  #then I set up a fixed IP address and the default route
  telnetd

• Second step is a little bit more tricky since the camera always restarts from hibernate and first attempt to change root filesystems resulted in filesystem corruption.

In the end since there's a lot of free space under /opt/usr I created a folder /opt/usr/bin with busybox (telnetd) on the device
and made a small change in /usr/lib/systemd/system/factory_check.sh to start telnetd

It is mandatory to shut the device forcing the full restart and a rebuild of the hibernate image otherwise when camera reboots the hibernate state and the filesystem state will be not consistent
Not writing the details here since this step is quite risky....

New firmare it seems
https://www.samsungimaging.com/file/download?XmlIdx=291&file=C200GLU0AQK1_171121_1257_REV00_user.bin
Sorry, I can not add the link as PR right now

Described it here https://github.com/ottokiksmaler/gear360_modding/tree/master
TLDR version - it's exactly the same camera internally (OS wise) as NX1/500.

Hi @ultramango
did you come accross anything in the camera app, that suggests we could allow longer shutter times?
That would be an excellent hack to have with iso400+tripod
Thanks

Something I was wondering about:
Do you think there is factory calibration data written into the EXIF, about how lenses are assembled?
The app does a really good and quick job stitching with minimal "borders" where image content does not match, tbh I'd be surprised if it could do so quick and well on a phone CPU, without getting some calibration data how images line up

Is there a way we could do a "large scale comparison", which binary sections of the jpg beginning match between all images taken with a single camera, and then another one which of these parts also differ with all other cameras, to find out if there is camera specific data in the images?

Can not reached https://www.samsungimaging.com
Do you have firmware file or link to download

Thxs

I have a SM-C200 and after loading, it has entered an infinite restart loop. I read the post but did not find a way to reset via the card in the SD card. If you can help me, I'm happy. Or if you have a way to make it come back to life.

Hi,

first of all thanks for the work! I am trying to make timelapse photo mode for Gear 360 (gen.1) which only has video timelapse mode (half reso of photo mode and output format is video). Obviously custom firmware is out of question, since nobody decrypted it yet (all we know it's linux based).

Other option if to use generic bt dongle to emulate official bt remote (which connects to cam in remote mode). Have you tried to hack it maybe? I do not have official bt remote (comes in expensive samsung value bundle), but i got mac address from it. From the log seems it connects, but then camera asks for some unkown service which other side (Kali Linux with bt dongle) doesn't have and disconnects. Could that service be in Samsung Accessory service for android?

any help would be great!

Hi,

I got a Gear360 (2016) a few days ago, and also own a few NX cameras, and I wanted to improve the existing documentation.

I've created a wiki page on the SLP bin file format used by Gear360 and NX cameras over at samsung-nx-hacks and wanted to say thanks for your reverse-engineering efforts!

Also I'm interested in documenting the bootloader / startup process for DRIMe5 devices, as well as looking for something similar to the fw_generator that Samsung dropped in their DRIMe4 dumps.