... GSM version (Maguro) with Android 4.3 from GNU/Linux

I found so many incomplete tutorials written in bad English that I decided to write one myself and keep it simple. You must have your phone’s bootloader unlocked; doing so will wipe your device!

1. Watch this tutorial video.
2. Download the fastboot and adb binaries, e.g. from the Universal Nexus Linux Toolkit. Extract the archive on your machine. Find the binaries.
   The problem with this toolkit is that the bundled zips are rather old and didn’t work for me, so:
3. Download the ClockworkMod recovery image from here.
4. Download the SuperSU zip file from here.
5. Connect your phone to your PC via USB.
6. Boot your phone into bootloader mode: Power it off, push both the volume rocker up+down and then press the power button, i.e., press all three at once for about two seconds.
7. ./fastboot oem unlock if you haven’t ever done it. This will wipe your device, reset it to factory settings and delete all your data. Yes, really.
8. ./fastboot flash recovery /path/to/recovery-clockwork-6.0.4.7-maguro.img
9. Now load the recovery: Volume button down twice to choose Recovery mode, power button to select.
10. Navigate using the volume rocker: “install update from zip”, press power button to select, choose “install zip from sideload”, press power button.
11. ./adb sideload /path/to/UPDATE-SuperSU-v1.93.zip
12. Navigate back and reboot normally. Your installed apps should now show SuperSU installed.

Have fun!

My boot partition was so small that I couldn’t do any initramfs-updates any more, so I backed it up, deleted /dev/md0 (boot) and /dev/md1 (swap) to recreate both with new sizes, restored my backup, and after a reboot grub couldn’t find anything due to the new UUIDs of the partitions.

Before I rebooted, I should have merged the output of `mdadm -Es` into /etc/mdadm/mdadm.conf, followed by

Instead, I had to go through this:

At grub rescue prompt:

... bringing me to a BusyBox/initramfs emergency prompt:

... bringing me to a simple bash prompt in my system:

... as well as:

... to be able to run:

You wouldn’t learn much if you weren’t forced to fix things once in a while. — myself

Quote of myself from four years ago:

I had to do the migration to a parallel machine and had only one week to accomplish this. I’ll never do it this way again, however, rather pay for two servers for a short time and decide when to finally switch.

This is exactly how I did it this time.

Although Debian 5 lenny had been released in Feb 2009, it didn’t yet make it into Host Europe’s 4.0 line of virtual servers; instead, that virtual machine was still based on 2007’s Debian 4 etch, which received its last kernel update, still 2.6.18, by the provider in Aug 2011. I upgraded it to Debian 6 squeeze nonetheless. I noticed that this year’s Debian 7 wheezy does not run under an etch kernel (especially libc6, rkhunter and aide), and as squeeze is already oldstable since May and will no longer be maintained by next May, it was time to perform an upgrade.

Now I run an instance of their 7.0 line with the same price, but RAM and disk space were both doubled (to 2 GB and 100 GB, respectively). It is still based on squeeze with a 2.6.32 kernel; based on my experience, I expect it to run wheezy and jessie before I have to switch again (in about another four years).

Like previously (and like seven years ago), I did the TCP forwarding using rinetd, except for Postfix, for which I set up relaying again.

Some quotes of myself from four years ago:

“Cheap” should mean here that you don’t need to spend money on extra hardware like a remote timer or on extra software like Windoze [...]

My hope is that I can use gphoto2 with an Android smartphone.

Somehow this is still a Linux-post, as Android simply is the most popular Linux distribution to date. Btw, PC and smartphone don’t count as dedicated extra hardware. But you might need to purchase an app and a USB adapter:

Meanwhile I use the awesome DSLR Controller on my Android smartphone in USB host-mode to create time-lapse picture sequences on my aging Canon EOS 40D—a thing that wouldn’t work with a diePhone, I guess. This app can do a lot more, of course. Up to now, you have to rely on USB. However, as Wi-Fi enabled DSLRs are appearing, there is some hope to get rid of that cable and adapter one day; Canon’s own EOS Remote app doesn’t support time-lapse shooting yet. [Update: To equip your camera with Wi-Fi, you could hack an Android TV stick!]

The most elegant solution would of course be located within the camera itself. Canon is still sleeping in this regard, but at least there’s the third-party Magic Lantern firmware add-on for some newer models, also sporting an intervalometer. My 40D is not (yet, but I guess won’t ever be) supported.

You should still set the camera to a resolution at or slightly above the HD 1080p resolution, which in my case is 1936×1288. You should fix the aperture and ISO values, and probably also the exposure time. [Update: In addition, fix the white balance. Also, don’t forget to cover the viewfinder with the eyepiece cover on your strap, as otherwise you might get different exposures that result in flickering!]

After getting the images to your Linux machine, you need to crop the pictures from 3:2 to 16:9 (in my case 1936×1089) or crop a 1920×1080 patch directly. You can do this with a simple script using ImageMagick:

(GNU Parallel didn’t work for me.) You can then issue

to render an HD video into a format that’s also recognized by your smartphone.

Finally, you could use OpenShot to edit your videos and add background music. (You could of course compose that music yourself using FOSS as well...)

Almost three years ago I migrated to a virtual server at HostEurope.de. It was a real relief to not care for any hardware anymore, and I’m really satisfied with their service which includes monitoring and restoreable snapshots. The only major problem I had was when I once tried to upgrade the C-library on an incompatible kernel version—I learned to use Debian Stable on servers. Minor problems however arose once in a while when I hit the privvmpages (private memory) limit. As only 256 MB RAM were guaranteed for my package in their 2.0 line at €15/month, I upgraded to the 512 MB package for €20/month a few months ago, which was a smooth single-click task. As they now already introduced their 4.0 line, I upgraded to 1024 MB for only €13/month. But I had to do the migration to a parallel machine and had only one week to accomplish this. I’ll never do it this way again, however, rather pay for two servers for a short time and decide when to finally switch. And as the monthly fee has now decreased, I had to pay €10 for this “downgrade” anyway.

I had planned to simply sync /etc, /usr, /var and /home to the new system to have a nonetheless smooth migration. But the new system turned out to be on 64-bit. So it took me more time to do a migration by hand, although I had asked their service in advance if that were possible. A further drawback was that I couldn’t keep the system’s RRD-files, as they seem to be platform-specific as well; that meant that all system log counters were starting freshly, as I was too lazy to export/import their data.

A WTF-situation arose when I noticed that the system had various server packages installed but was missing their symlinks in /etc/rc*.d and cron tabs in /etc/cron.*. I had to compare those with my old system.

phpMyAdmin wasn’t working anymore as it suddenly needed a localhost directive for MySQL in the config. That took me some time to find out.

Finally, ajaxterm didn’t launch in --daemon mode. That took me some time as well. As a quick hack I now start it without --daemon but with /usr/bin/nohup to the background.

I also had to take care that /etc/hosts is now dynamically created/overwritten at boot time. In my /etc/init.d/hostname_vps I now copy it from /etc/my.hosts.

For TCP forwarding I used rinetd and set up Postfix relaying like previously.

An interesting detail is that I moved from a 2×1500 MHz machine to one with 16×141 MHz.

“Cheap” should mean here that you don’t need to spend money on extra hardware like a remote timer or on extra software like Windoze (which Canon’s EOS Utility depends on). With a GNU/Linux system, just install gphoto2—in Debian, take version 2.4.5 from ‘squeeze’. After attaching your e.g. Canon EOS camera via USB, you can issue the command

to automatically shoot and download images for a time lapse, in this example every 10 seconds for one hour. You should keep all exposure values constant and switch to a lower resolution in advance. You can render an HD video e.g. with

If you make it bad, it might look boring like my very first try:

If you make it good, it should look like this.

My hope is that I can use gphoto2 with an Android smartphone.