Android

With a release date in 2018 I expected to have my Xiaomi Mi Mix 3 at least for a few years – if I manage not to crush it like its predecessor. Already in 2020 I had to learn that Xiaomi stopped support for the former flagship device. Really very disappointing and not a big […]

After an OTA upgrade from 4.4 to 4.4.2 SuperSU told me that it can’t root my device and I should consult internet. My recovery was overwritten by the update. So I reflashed my openrecovery image I used in my last post in this category and downloaded SuperSU from http://download.chainfire.eu/351/ and laid it to my sdcard. After a

First of all I want to say that I take no responsibility if you brick your phone by following steps from my blog. The whole process seems to be very familiar if you’ve rooted a nexus device before. With CWM my phone didn’t start anymore so I tried openrecovery which worked like a charme: Preparation

Hi, I recently upgraded my Samsung Nexus S to Cyanogenmod 10.1.2 as there won’t be factory images from google anymore. The phone has to be unlocked as described in previous posts in this category. First I downloaded the following files: Clockwork Recovery 6.0.3.6 Cyanogenmod 10.1.2 Google Apps for Jellybean Then I copied the two zip-file

OTA asked me to upgrade to 4.1.1 Jelly Bean today but as in all previous attempts to upgrade via OTA it failed again. So here is the manual way to upgrade from 4.0.4 to 4.1.1. How to get there can be found in previous posts in this blog. Of course you follow my steps on

I already described my full rom upgrade to 4.0.3 in a former post https://blog.coffeebeans.at/?p=208. This time I chose not to loose my apps+configuration and downloaded an official 4.0.3 to 4.0.4 patch from google as the OTA-update failed without an error message and the hourly message that there is an update available was a bit annoying.

There are lots of forums explaining how to upgrade or root a Nexus S but it took me hours to find all needed parts and get it running with ICS and rooting it afterwards. So I decided to summarize my experience – of course you follow my steps on your own risk and I’m not

today i had the problem under Ubuntu 11.10 64bit, that adb from the Android SDK failed to start with the output error while loading shared libraries: libncurses.so.5: wrong ELF class: ELFCLASS64 The solution is quite simple: The system has a 64bit environment, but the package from google is 32bit. So you have to install the