<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Android &#8211; Manuel Bogner&#039;s Blog</title>
	<atom:link href="https://blog.mbo.dev/archives/category/android/feed" rel="self" type="application/rss+xml" />
	<link>https://blog.mbo.dev</link>
	<description>Solutions to everyday IT problems</description>
	<lastBuildDate>Wed, 30 Aug 2023 09:17:22 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://blog.mbo.dev/wp-content/uploads/2022/11/cropped-cropped-mbo-white_opt-32x32.png</url>
	<title>Android &#8211; Manuel Bogner&#039;s Blog</title>
	<link>https://blog.mbo.dev</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Revive Xiaomi Mi Mix 3 with Arrow OS 11.0</title>
		<link>https://blog.mbo.dev/archives/1789</link>
		
		<dc:creator><![CDATA[Manuel Bogner]]></dc:creator>
		<pubDate>Sun, 09 Jan 2022 19:53:48 +0000</pubDate>
				<category><![CDATA[Android]]></category>
		<guid isPermaLink="false">https://blog.coffeebeans.at/?p=1789</guid>

					<description><![CDATA[With a release date in 2018 I expected to have my Xiaomi Mi Mix 3 at least for a few years &#8211; 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 [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>With a release date in 2018 I expected to have my Xiaomi Mi Mix 3 at least for a few years &#8211; 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 motivation to follow the Xiaomi flagship in the future.</p>



<p>It took me until beginning of 2022 to decide that I don&#8217;t want to buy a new device just because of misssing updates. At least not if there are proper custom roms out there that are still maintained. I found that Arrow OS is maintaining a branch for my phone with an updated Android 11. So i wanted to give it a try.</p>



<h2 class="wp-block-heading">Unlock Bootloader</h2>



<p><strong>WARNING: Unlocking the bootloader removes all data from your device &#8211; it&#8217;s a factory reset!!</strong> So backup your data first!</p>



<p>The first big hurdle you need to take with Xiaomi is the bootloader. Under <a rel="noreferrer noopener" href="https://en.miui.com/unlock/download_en.html" target="_blank">https://en.miui.com/unlock/download_en.html</a> they provide a tool where you need to ask for permission to unlock your bootloader. The tool states theses steps to do:</p>



<ul class="wp-block-list">
<li>Download the Mi Unlock app to PC, and sign in with your Mi Account;</li>



<li>Shut down your phone manually, and hold Volume down key and Power button to enter Fastboot mode;</li>



<li>Connect your phone to PC using USB cable and click &#8220;Unlock&#8221;.</li>
</ul>



<p>Also make sure to have the developer mode incl. the usb debugging enabled.</p>



<p>For being able to use fastboot under Windows I had to install the USB drivers for my phone first. I took the file from <a rel="noreferrer noopener" href="https://droidfilehost.com/download/download-xiaomi-usb-driver-for-windows/" target="_blank">https://droidfilehost.com/download/download-xiaomi-usb-driver-for-windows/</a>. After the installation nothin was changed but I was able to select the driver for the &#8220;Android&#8221; device from the list of predefined devices &#8211; &#8220;Android Composite ADB Interface&#8221;.</p>



<p>It is important that you are logged in to the same Xiaomi account in the unlock tool as you are logged in in your phone. Otherwise it won&#8217;t work because Xiaomi asks you to wait for 14 days to rethink your decision to unlock the device.</p>



<p>With the driver in place and the phone in fastboot mode the unlock tool finally recognised the phone and allowed me to klick unlock after having waited for the cooldown phase.</p>



<h2 class="wp-block-heading">Install Arrow OS</h2>



<p>Adb and fastboot come with Android Studio which I had already installed. So I took these tools simply from there. Further I downloaded the latest official release from Arrow OS &#8211; <a rel="noreferrer noopener" href="https://arrowos.net/download" target="_blank">https://arrowos.net/download</a>. Vanilla + Gapps build. Next to this we need a new recovery. So I also fetched the latest TWRP from <a rel="noreferrer noopener" href="https://dl.twrp.me/perseus/" target="_blank">https://dl.twrp.me/perseus/</a>. The installation procedure is described under <a rel="noreferrer noopener" href="https://forum.xda-developers.com/t/rom-11-0-0-perseus-arrowos-11-0-official-weekly.4176405/#post-83706165" target="_blank">https://forum.xda-developers.com/t/rom-11-0-0-perseus-arrowos-11-0-official-weekly.4176405/#post-83706165</a> but that only gives directions and won&#8217;t help you if you don&#8217;t know the commands.</p>



<pre class="wp-block-code"><code>// start phone in fastboot mode (power + sound down = bootloader)

// install TWRP
fastboot flash recovery twrp.img

// reboot into recovery - (power + sound up = recovery)
fastboot reboot recovery

// wait until TWRP is started and allow it to do changes to the fs
// "Make FULL WIPE (system/vendor/data/dalvik/cache) and FORMAT DATA - YES" from within TWRP.

// copy downloaded files from my computer to the device
adb push vanilla.zip /sdcard/vanilla.zip
adb push gapps.zip /sdcard/gapps.zip

// install vanilla.zip via TWRP
// install gapps.zip via TWRP

// reboot device</code></pre>



<p>The device should now boot into Arrow OS and up to now I haven&#8217;t found any problems.</p>



<h2 class="wp-block-heading">Sidenote</h2>



<p>In general the installation procedure for a custom rom hasn&#8217;t really changed so my experience from experimenting with my old Nexus 3 helped a lot avoiding to brick my device.</p>



<hr class="wp-block-separator has-css-opacity"/>



<p><strong>Important:</strong> I wrote this post from memory because I didn&#8217;t want to start from scratch to document it. Please write me if I missed something important or something is wrong. If you decide to follow the steps described in this post you do so on your own risk.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Root android after OTA from 4.4 to 4.4.2</title>
		<link>https://blog.mbo.dev/archives/748</link>
					<comments>https://blog.mbo.dev/archives/748#respond</comments>
		
		<dc:creator><![CDATA[Manuel Bogner]]></dc:creator>
		<pubDate>Mon, 16 Dec 2013 19:34:26 +0000</pubDate>
				<category><![CDATA[Android]]></category>
		<guid isPermaLink="false">http://blog.coffeebeans.at/?p=748</guid>

					<description><![CDATA[After an OTA upgrade from 4.4 to 4.4.2 SuperSU told me that it can&#8217;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 [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>After an OTA upgrade from 4.4 to 4.4.2 SuperSU told me that it can&#8217;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 <a href="http://download.chainfire.eu/351/">http://download.chainfire.eu/351/</a> and laid it to my sdcard. After a reboot into the custom bootloader I installed the zip file from flash and rebooted into my rooted android 4.4.2.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.mbo.dev/archives/748/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Root Google Nexus 5</title>
		<link>https://blog.mbo.dev/archives/737</link>
					<comments>https://blog.mbo.dev/archives/737#respond</comments>
		
		<dc:creator><![CDATA[Manuel Bogner]]></dc:creator>
		<pubDate>Tue, 19 Nov 2013 01:39:02 +0000</pubDate>
				<category><![CDATA[Android]]></category>
		<guid isPermaLink="false">http://blog.coffeebeans.at/?p=737</guid>

					<description><![CDATA[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&#8217;ve rooted a nexus device before. With CWM my phone didn&#8217;t start anymore so I tried openrecovery which worked like a charme: Preparation [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><span style="color: #ff0000;">First of all I want to say that I take no responsibility if you brick your phone by following steps from my blog.</span></p>
<p>The whole process seems to be very familiar if you&#8217;ve rooted a nexus device before. With CWM my phone didn&#8217;t start anymore so I tried openrecovery which worked like a charme:</p>
<h2>Preparation</h2>
<ul>
<li>Download <strong>openrecovery</strong> from <a href="http://www.androidfilehost.com/?fid=23212708291678610" target="_blank" rel="noopener">http://www.androidfilehost.com/?fid=23212708291678610</a></li>
<li>If you haven&#8217;t already done that download and install the <strong>Android SDK tools</strong> for your system from <a href="http://developer.android.com/sdk/index.html" target="_blank" rel="noopener">http://developer.android.com/sdk/index.html</a>. You&#8217;ll need to have the Android Platform tools installed</li>
<li><strong>(Windows only)</strong> You may need device drivers for the Nexus 5 under windows &#8211; but as I only have ubuntu machines I stick to linux ;-)</li>
<li><strong>(optional)</strong> To be able to restore your phone if something goes wrong it is also advisable to download the factory image from google from <a href="https://developers.google.com/android/nexus/images#hammerheadkrt16m" target="_blank" rel="noopener">https://developers.google.com/android/nexus/images#hammerheadkrt16m</a>. There are lots of tutorials how to flash this so I&#8217;ll also leave this to you.</li>
</ul>
<h2><strong>Installation</strong></h2>
<ul>
<li>Copy the downloaded openrecovery-twrp-2.6.3.2-hammerhead.img to your android-sdk-linux/platform-tools folder and cd to that folder</li>
<li>Change to superuser with <em></em></li>
</ul>
<pre class="lang:sh decode:true">sudo su</pre>
<ul>
<li><strong>Reboot</strong> your phone <strong>to recovery mode</strong> (shut down the phone and hold volume down and power button to turn it on again)</li>
<li><strong>Check that your device is recogniced</strong> with</li>
</ul>
<pre class="lang:sh decode:true">./fastboot devices</pre>
<ul>
<li><strong>Unlock the bootloader</strong> (<span style="color: #ff0000;">This will erase all your data!!!</span>)</li>
</ul>
<pre class="lang:sh decode:true">./fastboot oem unlock
./fastboot reboot-bootloader
sleep 5</pre>
<ul>
<li><strong>Flash the recovery image</strong> with</li>
</ul>
<pre class="lang:sh decode:true crayon-selected">./fastboot flash recovery openrecovery-twrp-2.6.3.2-hammerhead.img
./fastboot reboot-bootloader
sleep 5</pre>
<ul>
<li>Go to <strong>recovery mode</strong> (change selection on phone with vol +/- and select with power button)</li>
<li>In recovery mode choose to <strong>reboot the phone</strong> from within recovery mode. The application will ask if you want to root the phone. Say yes ;-)</li>
<li>The phone boots after that. When finished start the SuperSU application which tells you that you haven&#8217;t finished yet. Choose TWRP when asked how to finish installation. The phone will reboot again and you are done.</li>
</ul>
<p>Feel free to post questions. For me it worked exactly as described here.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.mbo.dev/archives/737/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Cyanogenmod 10.1.2 (Android 4.2.2) on Nexus S</title>
		<link>https://blog.mbo.dev/archives/621</link>
					<comments>https://blog.mbo.dev/archives/621#respond</comments>
		
		<dc:creator><![CDATA[Manuel Bogner]]></dc:creator>
		<pubDate>Thu, 15 Aug 2013 11:07:29 +0000</pubDate>
				<category><![CDATA[Android]]></category>
		<guid isPermaLink="false">http://blog.coffeebeans.at/?p=621</guid>

					<description><![CDATA[Hi, I recently upgraded my Samsung Nexus S to Cyanogenmod 10.1.2 as there won&#8217;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 [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>Hi,</p>
<p>I recently upgraded my Samsung Nexus S to Cyanogenmod 10.1.2 as there won&#8217;t be factory images from google anymore. The phone has to be unlocked as described in previous posts in this category.</p>
<p>First I downloaded the following files:</p>
<ul>
<li><a title="clockworkmod recovery" href="http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.3.6-crespo.img" target="_blank" rel="noopener">Clockwork Recovery 6.0.3.6</a></li>
<li><a title="cyanogenmod" href="http://download.cyanogenmod.com/get/jenkins/34242/cm-10.1.2-crespo.zip" target="_blank" rel="noopener">Cyanogenmod 10.1.2</a></li>
<li><a title="gapps" href="http://goo.im/gapps/gapps-jb-20130301-signed.zip" target="_blank" rel="noopener">Google Apps for Jellybean</a></li>
</ul>
<p>Then I copied the two zip-file to the sdcard of the phone and bootet into the bootloader (Hold louder and on/off button to power on) to flash the recovery image from the connected notebook (you may need superuser rights on your local pc):</p>
<pre>./fastboot flash recovery recovery-clockwork-6.0.3.4-crespo.img</pre>
<p>After a reboot again into the bootloader I first made a factory reset, mounted the sdcard and flashed the two downloaded zip-archives beginning with cyanogenmod (the order is important). Then I rebootet my phone and it started nicely into my new cyanogenmod.</p>
<p><span style="color: #ff0000;">Notice! I&#8217;m not responsible if you brick your phone while following my instructions.</span></p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.mbo.dev/archives/621/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Android Jelly Bean 4.1.1 on Nexus S [I9023]</title>
		<link>https://blog.mbo.dev/archives/292</link>
					<comments>https://blog.mbo.dev/archives/292#respond</comments>
		
		<dc:creator><![CDATA[Manuel Bogner]]></dc:creator>
		<pubDate>Tue, 24 Jul 2012 23:43:33 +0000</pubDate>
				<category><![CDATA[Android]]></category>
		<guid isPermaLink="false">https://blog.coffeebeans.at/?p=292</guid>

					<description><![CDATA[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 [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>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. <span style="color: #ff0000;">Of course you follow my steps on your own risk.</span></p>
<p>I first downloaded all files I needed</p>
<ul>
<li><a href="http://download.clockworkmod.com/recoveries/recovery-clockwork-6.0.1.0-crespo.img">recovery-clockwork-6.0.1.0-crespo.img</a></li>
<li>On <a href="http://forum.xda-developers.com/showthread.php?t=1736645">http://forum.xda-developers.com/showthread.php?t=1736645</a> I found the link to the OTA package from google for my device (I9023).</li>
<li><a href="http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip">Superuser-3.1.3-arm-signed.zip</a></li>
</ul>
<p>Then I rebooted my phone into bootloader and flashed the recovery image to the actual version via</p>
<pre class="lang:sh decode:true">sudo ./fastboot flash recovery ~/recovery-clockwork-6.0.1.0-crespo.img</pre>
<p>Then i directly started recovery mode, mounted the sdcard and installed the OTA package followed by the SuperUser package. Then I mounted /system and moved the install recovery script as usual by</p>
<pre class="lang:sh decode:true crayon-selected">./adb shell
cd /system/etc
rm install-recovery.sh.old
mv install-recovery.sh install-recovery.sh.old</pre>
<p>Then just reboot the phone into the new 4.1.1 Jelly Bean which updates your apps at first boot and all your config and apps should stay in place and the recovery is still working after a boot of the system and is rooted. So my phone is working as expected and the upgrade took me about 30min including searching for the needed files.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.mbo.dev/archives/292/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Manual Android 4.0.3 to 4.0.4 Update</title>
		<link>https://blog.mbo.dev/archives/237</link>
					<comments>https://blog.mbo.dev/archives/237#respond</comments>
		
		<dc:creator><![CDATA[Manuel Bogner]]></dc:creator>
		<pubDate>Tue, 10 Apr 2012 17:39:28 +0000</pubDate>
				<category><![CDATA[Android]]></category>
		<guid isPermaLink="false">https://blog.coffeebeans.at/?p=237</guid>

					<description><![CDATA[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. [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>I already described my full rom upgrade to 4.0.3 in a former post <a href="/?p=208" target="_blank" rel="noopener">https://blog.coffeebeans.at/?p=208</a>. 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.</p>
<p><span style="color: #ff0000;">If you follow my steps you do this on your own risk and I&#8217;m not responsible if you brick your phone or loose warranty.</span></p>
<p>I found an officially signed update package under <a href="http://forum.xda-developers.com/showthread.php?t=1445635" target="_blank" rel="noopener">http://forum.xda-developers.com/showthread.php?t=1445635</a> (Android 4.0.3 (Build IML74K/XXKI1 Radio/KL1 Bootloader 4.0.3 -&gt; 4.0.4) and copied it over to my sdcard. I also copied the SuperUser-zip I used the last time. Then I rebooted into bootloader and started recovery mode. There I just installed the downloaded patch and the superuser package in this order.</p>
<p>Then I checked that there is no <strong>install-recovery.sh</strong> in /system/etc. I had to rename it again, as I did the last time. Then i booted my new 4.0.4 without any problems. Also the recovery mode is still working after a reboot.</p>
<p>&nbsp;</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.mbo.dev/archives/237/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Manually update Google Nexus S I9023 with Android 4.0.3 Ice Cream Sandwich and root it</title>
		<link>https://blog.mbo.dev/archives/208</link>
					<comments>https://blog.mbo.dev/archives/208#respond</comments>
		
		<dc:creator><![CDATA[Manuel Bogner]]></dc:creator>
		<pubDate>Thu, 23 Feb 2012 11:59:36 +0000</pubDate>
				<category><![CDATA[Android]]></category>
		<guid isPermaLink="false">https://blog.coffeebeans.at/?p=208</guid>

					<description><![CDATA[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 &#8211; of course you follow my steps on your own risk and I&#8217;m not [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>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 &#8211; <span style="color: #ff0000;">of course you follow my steps on your own risk and I&#8217;m not responsible for bricked phones or lost warranties</span>:</p>
<h2>ICS</h2>
<p>First I was waiting for an OTA update but nothing happened and after looking for a way to manually do it I found some links to Google full ROMs under http://forum.xda-developers.com/showthread.php?t=1445635 and decided to try the update. I chose the &#8220;Android 4.0.3/IML74K/XXKI1 Radio/KL1 Bootloader&#8221; full rom and downloaded the package.</p>
<p>With this image on the sdcard of my phone, copied over USB, I rebooted my phone into the bootloader by holding power and up button to power it on. As I&#8217;ve already unlocked (fastboot oem unlock) my bootloader before I skipped this step now and there are dozens of howtos for this &#8211; but mentioned that most of these forums told me unlocking the bootloader voids warranty. In the menu I chose recovery, mounted the sd card and installed the downloaded package. After a reboot i had ICS :-)</p>
<h2>Custom Recovery</h2>
<p>But trying to get back into recovery I had to find out that the upgrade broke my recovery image. So I looked for the latest recovery image for crespo under <a href="http://download.clockworkmod.com/recoveries/" target="_blank" rel="noopener">http://download.clockworkmod.com/recoveries/</a> which was <a href="http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-crespo.img" target="_blank" rel="noopener">recovery-clockwork-5.0.2.0-crespo.img</a>. I downloaded this file and flashed it with fastboot which only works if you are in the bootloader. I copied the image to my plattform-tools folder of the <a href="http://developer.android.com/sdk/index.html" target="_blank" rel="noopener">Android-SDK</a> before</p>
<pre class="lang:sh decode:true"># verify that phone is available
./fastboot devices
...
# flash new recovery
./fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img</pre>
<p>Now it was possible to get back into recovery. But only till next boot of the phone. There is a script installing the broken image on every boot. This can be stopped by renaming install-recovery.sh in /system/etc of the phone. I mounted /system in the recovery menu then run these commands:</p>
<pre class="lang:sh decode:true">./adb shell
cd /system/etc
mv install-recovery.sh install-recovery.sh.old</pre>
<p>Now the phone was running with stock ROM without root access.</p>
<p><strong>Root</strong></p>
<p>I downloaded <a href="http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip">Superuser-3.0.7-efghi-signed.zip</a> from <a href="http://androidsu.com/superuser/" target="_blank" rel="noopener">http://androidsu.com/superuser/</a>. There are different versions but only one for ICS. Icopied this file into the plattform-tools folder of my SDK, booted the phone into recovery, mounted the sdcard and then run this command to copy the file to the phone:</p>
<pre class="lang:sh decode:true crayon-selected"># copy the file to phone
./adb push Superuser-3.0.7-efghi-signed.zip /sdcard</pre>
<p>Then I installed the file over the recovery menu and rebooted it. Now I have a rooted Nexus S with Android 4.0.3 and custom recovery.</p>
<p><strong>Lessons learned</strong></p>
<p>I shouldn&#8217;t have booted ICS after every single step to see if it is still working and to appreciate my work. All steps should be combinable by copying all needed files mentioned above to the sdcard (no matter how) and then doing the following &#8211; every step is explained above:</p>
<ol>
<li>Boot into bootloader and choose recovery in the menu</li>
<li>Install new ROM</li>
<li>Reboot the phone into bootloader or get back to bootloader in another way</li>
<li>Flash recovery</li>
<li>Choose recovery in the menu</li>
<li>Rename install-recovery.sh</li>
<li>Install Superuser package</li>
<li>Reboot the phone normally</li>
</ol>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.mbo.dev/archives/208/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Android SDK under 64bit Ubuntu 11.10</title>
		<link>https://blog.mbo.dev/archives/56</link>
					<comments>https://blog.mbo.dev/archives/56#respond</comments>
		
		<dc:creator><![CDATA[Manuel Bogner]]></dc:creator>
		<pubDate>Wed, 07 Dec 2011 10:26:00 +0000</pubDate>
				<category><![CDATA[Android]]></category>
		<guid isPermaLink="false">https://blog.coffeebeans.at/?p=56</guid>

					<description><![CDATA[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 [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>today i had the problem under Ubuntu 11.10 64bit, that adb from the Android SDK failed to start with the output</p>
<p><strong><em>error while loading shared libraries: libncurses.so.5: wrong ELF class: ELFCLASS64</em></strong><br />
The solution is quite simple: The system has a 64bit environment, but the package from google is 32bit. So you have to install the 32bit libraries via</p>
<pre class="lang:sh decode:true crayon-selected">sudo apt-get install ia32-libs</pre>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.mbo.dev/archives/56/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
