<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Upgrade on Nico Maas</title>
        <link>https://www.nico-maas.de/tags/upgrade/</link>
        <description>Recent content in Upgrade on Nico Maas</description>
        <generator>Hugo -- gohugo.io</generator>
        <language>en-us</language>
        <lastBuildDate>Mon, 31 Jul 2017 13:00:42 +0000</lastBuildDate><atom:link href="https://www.nico-maas.de/tags/upgrade/index.xml" rel="self" type="application/rss+xml" /><item>
            <title>[Gigabyte] BIOS Upgrade on old Gigabyte Motherboards</title>
            <link>https://www.nico-maas.de/posts/2017-07-31-gigabyte-bios-upgrade-on-old-gigabyte-motherboards/</link>
            <pubDate>Mon, 31 Jul 2017 13:00:42 +0000</pubDate>
            <guid>https://www.nico-maas.de/posts/2017-07-31-gigabyte-bios-upgrade-on-old-gigabyte-motherboards/</guid>
            <description>&lt;p&gt;There are several old Gigabyte Motherboards like the GA-MA Series which uses their BIOS Included Q-Flash Utility for upgrading. This tool tries to access an attached USB Device in a file browser way to give you the choice on which file to flash. Most of the time, you won&amp;rsquo;t be able to access your drive, as it will only be shown as &amp;ldquo;Floppy B&amp;rdquo;. In truth, this means your USB drive is formated the wrong way: You should have only one partition on that stick, with size LESS than 128 MB and FAT as file system. Yeah, I figured that out the hard way ^^&amp;rsquo;. It will then be shown as &amp;ldquo;HDD 0-0&amp;rdquo; in Q-Flash and will provide your files for easy upgrading 🙂&lt;/p&gt;</description>
        </item><item>
            <title>[Docker] Upgrade Sonarqube from 5.6 to 6.2</title>
            <link>https://www.nico-maas.de/posts/2017-01-20-docker-upgrade-sonarqube-from-5-6-to-6-2/</link>
            <pubDate>Fri, 20 Jan 2017 21:57:36 +0000</pubDate>
            <guid>https://www.nico-maas.de/posts/2017-01-20-docker-upgrade-sonarqube-from-5-6-to-6-2/</guid>
            <description>&lt;p&gt;I just updated Sonarqube from 5.6 (LTS) to 6.2. Before that, I upgraded all my plugins in Sonarqube itself and made an backup of my installation and database.&#xA;Then, I replaced image: &lt;code&gt;sonarqube:lts-alpine&lt;/code&gt; in my docker-compose.yaml with image: &lt;code&gt;sonarqube:6.2-alpine&lt;/code&gt;.&#xA;I did an docker-compose up and it started, however, I had some errors so it just kept on restarting.&#xA;Following &lt;a class=&#34;link&#34; href=&#34;https://stackoverflow.com/questions/37781951/elasticsearch-bulk-index-error-on-sonar-startup&#34;  target=&#34;_blank&#34; rel=&#34;noopener&#34;&#xA;    &gt;this advice&lt;/a&gt; I then proceded to delete &lt;code&gt;$SONAR_HOME/data/es/&lt;/code&gt;. I then restarted Sonarqube, which worked. I then pointed my Webbrowser to the URL of my Sonarqube Instance and added an &lt;code&gt;/setup&lt;/code&gt; and allowed the Database Upgrade. After that, I had a working new Sonarqube instance :).&lt;/p&gt;</description>
        </item><item>
            <title>[Win7] Upgrade Error in Android SDK for Windows</title>
            <link>https://www.nico-maas.de/posts/2013-11-04-win7-upgrade-error-in-android-sdk-for-windows/</link>
            <pubDate>Mon, 04 Nov 2013 13:21:34 +0000</pubDate>
            <guid>https://www.nico-maas.de/posts/2013-11-04-win7-upgrade-error-in-android-sdk-for-windows/</guid>
            <description>&lt;p&gt;Recently I got an error on trying to upgrade my Android SDK, claming that I would not be able to access an URL. I was looking around the Internet and got the information that I should first upgrade the Eclipse Plugin. OK!&lt;/p&gt;&#xA;&lt;p&gt;Upgrading AVT:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;In Eclipse go to Help&lt;/li&gt;&#xA;&lt;li&gt;Install New Software - Add&lt;/li&gt;&#xA;&lt;li&gt;inside Add Repository write the Name: ADT and Location: &lt;a class=&#34;link&#34; href=&#34;https://dl-ssl.google.com/android/eclipse/&#34;  target=&#34;_blank&#34; rel=&#34;noopener&#34;&#xA;    &gt;https://dl-ssl.google.com/android/eclipse/&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;after loading you should get Developer Tools and NDK Plugins&lt;/li&gt;&#xA;&lt;li&gt;check both if you want to use the Native Developer Kit (NDK) in the future or check Developer Tool only&lt;/li&gt;&#xA;&lt;li&gt;click Next&lt;/li&gt;&#xA;&lt;li&gt;Finish and Restart Eclipse&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;p&gt;Source: http://stackoverflow.com/questions/14869929/update-android-sdk-tool-to-22-0-4latest-version-from-22-0-1&lt;/p&gt;</description>
        </item><item>
            <title>HTC Universal</title>
            <link>https://www.nico-maas.de/posts/2011-04-01-htc-universal/</link>
            <pubDate>Fri, 01 Apr 2011 09:00:53 +0000</pubDate>
            <guid>https://www.nico-maas.de/posts/2011-04-01-htc-universal/</guid>
            <description>&lt;p&gt;I found a &amp;ldquo;bricked&amp;rdquo; HTC Universal without - everything.&lt;br&gt;&#xA;So I decided to piece it back together.&lt;br&gt;&#xA;First thing to find was an USB Cable to recharge the battery.&lt;br&gt;&#xA;Working is an normal Mini USB Cable, even tough the connector looks different.&lt;/p&gt;&#xA;&lt;p&gt;After that, I found out that the HTC was a brick.&lt;br&gt;&#xA;So to unbrick:&lt;/p&gt;&#xA;&lt;p&gt;get mtty1.42.exe, enter bootloader mode , (Power + Light Bulb + Reset)&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;Stop Activesync USB connection&lt;/li&gt;&#xA;&lt;li&gt;Uni : Reboot Bootloader then Connect USB&lt;/li&gt;&#xA;&lt;li&gt;PC : Run mtty1.42.exe&lt;/li&gt;&#xA;&lt;li&gt;Choose USB in &amp;ldquo;Port&amp;rdquo; (Reconnect if can&amp;rsquo;t find/reconglize USB and try remove sim and sd card)&lt;/li&gt;&#xA;&lt;li&gt;type : task 28 55aa&lt;/li&gt;&#xA;&lt;li&gt;Press Enter&lt;/li&gt;&#xA;&lt;li&gt;Cause DOC reformatted, so there&amp;rsquo;s no rom in DOC ,try reflash any rom that you like .&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;p&gt;For task 28 55aa in mtty success , will show the message (attachment )&lt;/p&gt;</description>
        </item></channel>
</rss>
