Android SDK Three update failures and how to solve them _android

Recently on the Internet to see the picture of Moto 360, really handsome, handsome and handsome, more handsome than handsome. So want to study the Android Wear.

Updated the Android SDK and failed three times.

1. Failure for the first time

Failed to fetch URL error message appears

Failed to fetch URL Https://dl-ssl.google.com/android/repository/repository-6.xml, reason:connection to https:// Dl-ssl.google.com refused Failed to fetch URL http://dl-ssl.google.com/android/repository/addons_list-1.xml, Reason: Connection to Http://dl-ssl.google.com refused Failed to fetch URL https://dl-ssl.google.com/android/repository/addons _list-1.xml, reason:hostname in certificate didn ' t match: != cannot be resolved when updating ADT Ndroid/eclipse

Solutions

Open the C:\Windows\System32\drivers\etc folder, copy the Hosts file to the desktop, and open the Hosts file with text editing software (such as Subline Text2). Add one line:74.125.237.1 dl-ssl.google.coms

-->

After the modification, the Hosts file modified will be replaced by the hosts file under the C:\Windows\System32\drivers\etc folder.

2. Second failure

After modifying the Hosts file, I was delighted to find a new API, the legendary Android L. Install updates, also have speed. But there are the following error prompts on the download:

Download interrupted:unexpected HTTP status:500

Download interrupted, unexpected HTTP status: 500. Google a bit, and found that the problem is server-side.

Solution :

First download Zym, this is a proxy server software. For example, the proxy address is 127.0.0.1, and the port number is 8580.

Then click on the Android SDK Manager's Tools option to select Settings. Set the HTTP proxy server address to the 127.0.0.1of the above software, and the proxy port is set to 8580. Check to force the use of https://instead of http://.

Finally, it's done.

3. Third failure

Unexpectedly failed again, although the SDK can be downloaded, but the last package is not installed successfully. See the figure below.

The pit dad, Google a bit, on the StackOverflow saw the same problem.

Solutions

Similarly, the Android SDK Manager, click Tools,settings,clear Cache in turn. As follows

Oh yes! Successfully updated!!!