Waze Social GPS Maps & Traffic 3.7.7.0 Apk

Waze is a fun, community based mapping, traffic & navigation app, 50
million strong. Join forces with other drivers nearby to outsmart
traffic, save time & gas money, and improve everyone’s daily
commute.By simply driving around with Waze open, you’re already
contributing tons of real-time traffic & road info to your local
driving community. You can also actively report accidents, hazards

How to: manually install an OTA update on your HTC device

Sometimes it turns out that your device for some reason can't find the most recent OTA (Over The Air) update. However, there is a solution to apply OTA update manually, without being forced to wait for the update being downloaded and installed by your device.

Facts you need to know before continuing:

1. This method has nothing to do with the "adb sideload" feature available on Android devices since Jelly Bean. It should work on every Android HTC device.
2. Read about different software versions for the HTC devices here. Keep in mind that the OTA update must match the software version on your device. Each original OTA update.zip package has 2 different software versions in its name - the version of the software that must be currently installed on your device and the version of the software that your device will run after the update. For example:

OTA_M7_UL_JB43_SENSE55_MR_HTC_Europe_3.62.401.1-2.24.401.8_release_338160gxmo5sd9337kadux.zip

As you can see, 2.24.401.8 is the software version you must currently have installed to be able to run the OTA and 3.62.401.1 is the version of the software expected after the update. You can't flash an OTA update on a different software version to that expected by the OTA update for two main reasons:

1. Formal reason - the OTA update.zip package checks if your system is running the expected software version before it starts to install the update:

   assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "htc/htc_europe/m7:4.2.2/JDQ39/235216.8:user/release-keys");

   This must match the following build fingerprint from the build.prop. If the versions don't match, the installation of the OTA package will be cancelled.
   

   ro.build.fingerprint=htc/htc_europe/m7:4.2.2/JDQ39/235216.8:user/release-keys

2. Technical reason - OTA update.zip packages usually contain patches for the target files. This way OTA update doesn't have to be 1GB size, even if it is supposed to update the whole OS to the newer version. Patch files have an *.apk.p extension (f.g. Camera.apk.p) and each patch file must match the target file (f.g. Camera.apk). To make it possible, OTA update.zip package checks the MD5 checksum of each file on the system partition on your device:

   assert(apply_patch_check("/system/app/Camera.apk",

   "b3b79e40bad0b1bec5fb949ac5f8662f91bee714",

   "5a5bf63e3d7c9de52a7d8d7a292e158263783844"));

   And finally, if the MD5 is correct it applies the patch. All these commands are stored in META-INF\com\google\android\updater-script of each OTA update.zip package. If the MD5 is incorrect, or at least one file is missing, the installation of the OTA package will be cancelled.
   

   assert(apply_patch("/system/app/Camera.apk", "-",
   b3b79e40bad0b1bec5fb949ac5f8662f91bee714, 4229394, 
   5a5bf63e3d7c9de52a7d8d7a292e158263783844,
   package_extract_file("patch/system/app/Camera.apk.p")));

Now you are ready to manually apply the OTA update on your device. The method you'll use is based on Android stock recovery.

1. Make sure you have the stock (original) recovery flashed on your device
2. Make sure you're running a completely unmodified operating system. Additional files like Superuser.apk or su binary are allowed, you just can't have any system files changed or removed (due to the MD5 check)
3. Make sure you have a reasonable amount of battery charge remaining
4. Make sure the OTA update you're about to install matches the software version on your device
5. Copy the OTA update.zip package to your device (internal storage preferred)
6. Turn OFF the device (make sure fastboot mode is disabled in settings)
7. Hold your volume down and power keys until the bootloader starts up
8. Using the volume keys, navigate down to RECOVERY and press power
9. You are now in stock recovery mode. You should see nothing more than a (sometimes spinning) Android with the red exclamation mark above it (an empty black screen is also possible). Wait for a few seconds
10. First hold volume up, then (with volume up held down) press power button to enter the main recovery menu. This keys combination may vary from device to device. Try different keys combination if the above one doesn't work (might be all three keys all together too)
11. Navigate down to "apply from phone storage" text and press power to confirm
12. Navigate to the location where you copied the OTA update.zip package and press power to confirm
13. Wait (sometimes you might need to follow further instructions on the screen) until the update process is finished
14. Once system is booted you should see a confirmation about the successfully flashed update.

Have any questions or comments? Feel free to share! Also, if you like this article, please use media sharing buttons (Twitter, G+, Facebook) below this post!

HTC ROM Update Utility (RUU) variants explanation

Owners of HTC devices might be a little confused when it comes to understanding the current method of numbering used by HTC to mark their software updates. Here you can find a short explanation of this matter.

First of all, we all know that HTC sells their devices all over the world. Every carrier and region of the world has some more or less different "local settings". By "local settings" I mean things like: emergency call numbers, languages, time-zone settings, network settings, carriers branding, GPS settings and more. Because of that each software for even the same device must be different.

Secondly, even the same device might use different hardware related to the region of the world. For example, HTC One is available in at least 6 different hardware configurations. One of the main difference is modem version. GSM version of the HTC One uses MDM8215 chip and LTE variant has MDM9215. Verizon (US) is known to have MDM9615. So that's already 3 different versions of the same device.

Every HTC update has the following numbering structure:

a.bb.ccc.d

a - the first number of the software. Normally it doesn't increase very often, but when it does, it usually means newer Android version.

bb - this number is also a software number. Increasing bb number means some more or less major update based on the same Android version, but sometimes it might even bring newer version of the HTC Sense.

ccc (also cc or cccc) - this is the number of the region/carrier. It has nothing to do with the software itself being newer or older. More details below.

d (sometimes dd) - the third part of the software version (the fourth one in the RUU name). Usually indicates some minor update with some hot fixes.

Example: 3.20.401.3

So basically, when you are interested in the software version, you should look at a.bb.d (3.20.ccc.3) because ccc (401) means only the region/carrier variant of the software.

Here is the list I was able to gather of possible RUU variants:

a.bb.61.d - Orange UK (United Kingdom)

a.bb.65.d - Orange CH (Switzerland)

a.bb.69.d - Orange PL (Poland)

a.bb.73.d - Orange FR (France)

a.bb.75.d - Orange ES (Spain)

a.bb.110.d - T-Mobile UK (United Kingdom)

a.bb.111.d - T-Mobile DE (Germany)

a.bb.112.d - T-Mobile AT (Austria)

a.bb.113.d - T-Mobile CZ (Czech Republic)

a.bb.118.d - T-Mobile PL (Poland)

a.bb.161.d - Vodafone UK (United Kingdom)

a.bb.163.d - Vodafone FR (France)

a.bb.165.d - Vodafone IT (Italy)

a.bb.166.d - Vodafone CH-DE (Switzerland - Germany)

a.bb.168.d - Vodafone GR (Greece)

a.bb.169.d - Vodafone AT (Austria)

a.bb.206.d - O2 UK (United Kingdom)

a.bb.207.d - O2 DE (Germany)

a.bb.401.d - World Wide English (WWE)

a.bb.415.d - Arabic (UAE/Middle East)

a.bb.468.d - Turkey

a.bb.497.d - Morocco

a.bb.498.d - WWE Brightpoint US (United States)

a.bb.502.d - Cingular US (United States)

a.bb.531.d - T-Mobile US (United States)

a.bb.631.d - Rogers Canada (WWE)

a.bb.651.d - Sprint US (United States)

a.bb.661.d - Telus WWE (Canada)

a.bb.666.d - Bell Canada

a.bb.707.d - Asia (WWE)

a.bb.708.d - Asia HK (Hong Kong)

a.bb.709.d - Asia TW (Taiwan)

a.bb.720.d - Asia (India)

a.bb.728.d - Virgin AU (Australia)

a.bb.751.d - Chunghwa Telecom (Taiwan)

a.bb.771.d - Hutchison 3G UK (United Kingdom)

a.bb.777.d - ?

a.bb.841.d - Telsra WWE (World Wide English)

a.bb.862.d - Voda-Hutch AU (Australia)

a.bb.901.d - TIM IT (Italy)

a.bb.911.d - SK Telecom (South Korea)

a.bb.980.d - Optus AU (Australia)

a.bb.999.d - HTC Test RUU

a.bb.1400.d - China

a.bb.1401.d - ?

a.bb.1403.d - HTC China CMCC (China Mobile Communications Corporation)

a.bb.1540.d - HTC One U.S. Developer Edition

a.bb.1600.d - ?

a.bb.1700.d - HTC One Google Edition

The list is quite long, and I'm sure there are still some some missing. If you know more variants, please let me know in the comments section.

The 401 and the 707 devices are usually the first ones that HTC prepare updates for. Carrier branded software is usually months after the WWE updates.

Finally, keep in mind that each software version is connected with the CID (Carrier ID) and MID (Model ID) of your device. That means you can't use whichever version you want, unless you have S-OFF on your device. Each ROM Update Utility.exe package will check your device details (bootloader version, MID and CID) before starting the update process.

Have any questions or comments? Feel free to share! Also, if you like this article, please use media sharing buttons (Twitter, G+, Facebook) below this post!