[X]Assistant

[i81]

The material presented on the page is unofficial (with the exception of official firmware), in the event of unsuccessful firmware or destruction of the device, the author of the software and the Administration do not bear responsibility for the resource! All actions are performed at your own risk!

Flashing HTC HD2
HTC Leo, HTC T8585
General: Description | Discussion пїЅ | FAQ пїЅ | Purchase пїЅlAccessories пїЅ | Owner communication пїЅ | Marriage пїЅ | GPS пїЅ | Modification and refinement of the OEM software HTC пїЅ | Adaptation of OEM software for HTC пїЅ | Discussion on energy consumption пїЅ | General flashing questions пїЅ | Discussion of the original firmware пїЅ |

пїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ HTC HD2 download

пїЅ | HTC Leo - Firmware radio module пїЅ |
HTC Leo (HD2) - Android OS пїЅ | WP7 for HD2 пїЅ | Learning to build firmware пїЅ | HTC Leo - Flashing (Archive) |

This topic discusses the features of the original HTC firmware, updates to them, software compatibility.

In this topicnotis discussed:

• selection and installation of any modified firmware (custom and assemblies with region lock disabled)
  
• installation of Russian firmware on non-PCT devices (gray and purchased abroad)
  
• decorations, fashions and patches ("whistles and fakes")
  

Instructions for firmware official versions:

Before flashing, charge the phone by more than 30%!

Method 1- recommended.
1) Connect the included phone to the computer with a cable;
2) Make sure that an ActiveSync (or Windows Mobile Center) session is established;
3) Run the firmware file on the computer and follow the instructions on the screen.

Method 2 . Used when the phone does not load or is loaded incorrectly.
1) Connect the switched off phone to the computer;
2) Press the volume key down and, while holding it, turn on the phone. Boot bootloader, the so-called "mattress";
3) Run the firmware file on the computer and follow the instructions on the screen.

Method 3 - from microSD memory card. It is recommended only if you want to change the SPL version (and you know what it is and why), or when methods 1 and 2 are not available.
1) Unpack the firmware on the computer (if the exe file is just to run it, do not press anything, go to the TEMP directory and look there);
2) Write to the memory card RUU_Signed.nbh and rename it to LEOIMG.nbh. As a rule, it is not required to format the card;
3) Press the volume key down and, while holding it down, turn on the phone. Boot bootloader, the so-called "mattress". The firmware from the memory card will start automatically.

After flashing, some recommend immediately making a hard reset (seeFAQ), but the expediency of this is not proven by anyone.

Attention!
Official firmware without problems can be put on those phones for which they are released (Russian - in Russian, T-mobile on T-mobile, and etc.). To install official firmware on a phone for which it is not intended (for example, from another region) you may have to use HSPL - to install the entire firmware, or SSPL - to install the PART OF the firmware without a radio module. For details, see the cap in the topic.Flashing.

Tracker latest firmware
^{(relevance on 2010-10-22)}

RUS:
(firmware contains Region Lock!)
HD2 RUU Leo S HTC RUS3.14.411.2 Radio 15.42.50.11U 2.15.50.14 LEO S Ship.exe

PCT Archive:

HTC RUS 1.43.411.4 mirror
HTC RUS 1.48.411.1 mirror
HTC RUS 1.66.411.2 with radio 2.06.51.07 mirror
Official firmware, which is not on the NTS site has a new radio 2.07.51.22_2

For non-PCT firmware, use Russian firmware without regionalok from MagLite - to install a part of the firmware without a radio module. In this case, the radio module can be flashed in advance along with the official firmware for the phone, or you can download and flash separately. For details, see the cap in the topic.Flashing.

WWE (UK):
RUU_Leo_S_HTC_WWE_3.14.405.2 _Radio_15.42.50.11U_ 2.15.50.14 _LEO_S_Ship [mirror]

WWE firmware archive:

^{(2 versions of the same firmware with different versions of the radio; only the first one is officially released)}
1) RUU_Leo_HTC_WWE_1.66.405.2 _Radio_Signed_15.30.50.07U_ 2.06.51.07 _Ship
2) RUU_Leo_HTC_WWE_1.66.405.2 _Radio_CRC_Signed_15.32.50.07U_ 2.07.51.22_2 _Ship

WWE (HK):
^{(WWE version for Hong Kong)}
RUU_Leo_HKCSL_WWE_1.72.831.1 _Radio_CRC_Signed_15.32.50.07U_ 2.07.51.22_2 _Ship

T-Mobile US HD2:
^{(firmware American version HD2 chardware1GB ROM and 576 RAM - for ordinary HD2 it is practically useless!)}
RUU_Leo_1_5_TMOUS_2.10.531.0 _Radio_Signed_15.34.50.07U_ 2.08.50.08_2 _Ship [part1] + [part2] .

Firmware collections:
http://forum.xda-developers.com/showthread.php?t=577717
http://www.4shared.com/dir/22189940/b8552f...d_Leo_ROMs.html
http://shipped-roms.com/shipped/Leo/

Patches and updates:
^{(relevance on 2010-03-31)}

Update for HTC HD2 Java Message Pop up
^{This is your phone’s Facebook profile.}

Update for HTC HD2 Facebook Albums
^{This is an update for HTC HD2. This will prevent your phone from opening.}

A pack called HTC_RUS_applications_package_v1.0 which includes several programs: Kommersant, SPB TV, Yandex.Maps and Classmates.
HTC_RUS_applications_package_v1.0.exe(6.24 MB)

Post has been editedDaymon - 19.07.11, 16:14

Reason for editing: Corrected the cap.

[Progmanit]

Hurray, finally I'm in a long-awaited separate topic on off. firmware!
I post my previously published topic with observations on the PCT 1.66 v2 Cradio 2.07, supplemented by weekly testing:

In general, I finally installed the RUU_Leo_HTC_RUS_1.66.411.2_Radio_CRC_Signed_15.32.50.07U_2.07.51.22_2_Ship firmware, after the official base 1.43 RUS (from the official fixes - only a patch of pink spot), now I share my first impressions:

At first about pluses:(compared to 1.43)
Camera:
- the recollection of closely located objects was fixed when the flash was fired - Hurray !!! (at 1.43 photography in the dark was almost impossible)
- GPS-Photo mode has appeared - it is PLEASANT! (no need to climb registries and settings / cut tweaks)

Power usage:
- in the auto-backlight mode (30% brightness) in the absence of running applications, it hears ~ 56 mA,
in the minimum backlight mode (10% brightness) in the absence of running applications ~ 33 mA hamsters - Hurray !!! (at 1.43 in similar modes, the values ​​were ~ 125 mA and ~ 95 mA, respectively) Simply fantastic !!!

Speed:
- the shell and the OEM software works so far clearly faster (perhaps the feeling is subjective due to the comparison with the software of the previous firmware overloaded with all sorts) - NICE!

Built-in memory:
- not exactly measured, but it turned out more than 10-12 megabytes - it is PLEASANT!

Phone:
- volume drops have become more moderate, the connection is more stable, it has become less likely to kick out the Packet Internet (Beeline operator Moscow time)
- the automatic activation of the speakerphone is activated when the device is flipped - NICE! (no need to climb registries and settings / cut tweaks)

SMS:
- now when uploading long stories of correspondence in a dialogue with specific contacts (I tried on contact with correspondence in 180 messages), there are practically no brakes and most importantly, now you don’t need to wait up to a minute to respond to such a contact - Hurray!
- auto-transfer of words to the next line adequately works - PLEASANT!

Now for the MINUSES:(compared to 1.43)
Phone:
- the spasmodic noise did not disappear against the background of conversations, although it began to appear less frequently and became less intense - BAD! :(
- the overwhelming frequencies during a conversation (as it seems to me mostly soft jamb due to the incorrect setting of the internal "equalizer" for telephone conversations), leading to wheezing and rattling even at a low volume, also remained - FULL SAKS! :(
- the spontaneous activation of an overestimated volume at a previously set lower level is also not completely eliminated, although it began to jump out much less often (the same situation with the use of a BT headset) - BAD! :(

Power usage:
- in the standby mode, it may have increased slightly and is 3-7 mA (at 1.43 it was 2-3 mA)

SMS:
- remained unchanged "I" instead of the desired "I" - BAD! :((do not tell me what to do with this?)
- some SMS in the history of correspondence with a specific contact is crawled to the bottom lines with the date and time of sending / receiving - it is BAD! Sad )

Problems not solved by firmware 1.66:
HTC Music (Manny Player):
- loads songs for infinitely long if not a particular album or artist is selected for playback, but all the songs from your music folder on the memory card - but for now it loads, Leo is in complete dependence :(

The topic will be supplemented with fresh observations.
I hope someone will come in handy.

Post has been editedProgmanit - 20.03.10, 01:43

[Progmanit]

During the week I installed the necessary software and then a terrible thing happened - the power consumption at first surprised me with such a thing:
- when the bluetooth is off, the backlight is at a minimum without running programs - 35 mA, and under the same conditions, but with the Enabled Turnover and a hamster paired with a BT headset, 95 mA! This is despite the fact that in sleep mode, the above modes consume: the first ~ 3-4 mA, and the second ~ 4-5 mA. The question is why when a device is taken out of sleep mode, a paired headset (which is paired and active both in sleep mode and in work mode) starts to eat 60 mA more ???

and then struck down with such a thing - power consumption returned to the firmware 1.43, only worse:
- Without running programs and turning off all modules except the phone, it began to eat on auto-backlight (30%) 125-145 mA, at the minimum of the backlight (10%) 98-110 mA (whereas on the freshly downloaded 1.66 it was in the same modes 56 and 33 mA, respectively ). Now I think that it could lead to this - the only thing I changed in the phone in the period between power consumption at the minimum of the backlight between 35 mA and 105 mA is the installation of the new 10th opera, but how it could affect it even in background processes not?!

[sergwrk]

Weekly observation of 1.66 RU: power consumption is on average clearly higher than with firmware 1.48 RU (it did not measure currents, and by eye approximately 20-30%)

[i81]

djet @ 20.3.10, 1:16

I just thought how easy and good it would be to read a topic without rubbish and screaming.

Hope there is no garbage. If possible, I will clean everything at once. A little later I will add a cap that it is allowed to write only positive feedback about the whistles + screen + file itself.

Progmanit @ 20.3.10, 3:36

hopping noise amid conversations did not disappear

I do not have this ... 3G you have included?

Progmanit @ 20.3.10, 3:58

power consumption returned to firmware 1.43, only worse

key phrase in your post

Progmanit @ 20.3.10, 3:58

installed the necessary software

I advise you to stretch the installation for a longer period and check ... Although I had an example in my life on the X900, I haven’t yet found a solution to this problem:
I put at that moment the last SPB Mobile Shell (2.5 chtol version) I put SPB Vader with a template for gismeteo, integrating Vader into Shell and EVERYTHING! - Akum dies after half a day, right before your eyes. Removing a bunch does not help. I go to the engineering menu, do a battery calibration and then it helps. 10 times set - always the same result ...

Ps

Progmanit ProgmanitWhat and how do you measure the current in sleep mode?

[Progmanit]

i81 @ 20.3.10, 6:45

Progmanit, what and how do you measure the current in sleep mode?

Well, either classically using the Power Info utility, but a much more visual and operational way is to install BatteryClock and enable the option to display the current power consumption in addition to the time and charge of the battery - then everything becomes clear!

The only trouble is the power consumption sensor on HD2 (from which all the programs that show power consumption read information) only updates information every 30 seconds.

[i81]

Progmanit @ 20.3.10, 11:24

Well either classically utility Power Info

in my question the key phrase "in sleep mode" i.e. All processes except the phone and the main system slow down ... And the display is turned off ... I repeat the question: how?

[stm555]

i81,
You can read the sensor readings at any time, but the sensor updates them every 30 seconds. If you turn on the device and do not get into the time of measurement, you can see the readings during sleep

[ergardt]

Hello again!!! ;) I congratulate everyone on the topic I finally need ...: D
And now essentially: There is a problem on RUU_Leo_HTC_RUS_1.66.411.2 with radio 2.06, constantly at night or after a long hibernation a message flies out that it was not possible to connect, the connection with the server was terminated, etc. It is a pity that I can not lay out the screen for the time being, but once I catch it, I will post it. So the question is how to win it? There is a hunch that this breaks the GPRS connection, since I have no limit and is constantly turned on for all sorts of updates .. But during the day this does not happen ...: sveta:

[Progmanit]

ergardt @ 20.3.10, 11:04

that it was not possible to connect, the connection with the server was terminated, etc.

Well, once in the daytime this does not happen to you, I can only envy your operator! This happens on me several times a day on bee (Msk), and if you rummage around in the internet for a long time, then several times during a session. And it does not depend not only on the firmware, but also on the communicator itself - this has stably happened on other KMCs and even on phones. So IMHO - nothing terrible happened to you - just the most likely minor failures in the packet data of the operator.


Posted 03/20/2010 13:14:

i81 @ 20.3.10, 6:45

Do you have 3G included?

Well, I have a choice of automatic, and the areas where I live 3G connection is not covered, so the GSM \ EDGE mode is active, I suppose.

[ergardt]

Progmanit @ 20.3.10, 13:14

just the most likely minor failures in the operator's packet data.

It turned out to take pictures, the screen does not work ...

Post has been editedDaymon - 15.02.11, 15:49

[djet]

ergardt @ 20.3.10, 21:45

I can add only the following, practice shows that whistles better get along on official firmware ... (this is my practice and I do not impose on anyone)

Not surprisingly, this is an argument in favor of the lack of whistles. In the custom, the concentration of the whistles often exceeds all reasonable norms, which is why the "incapacity" and glitches arise.

ergardt @ 21.3.10, 12:33

It turned out to take pictures, the screen does not work ...

These are problems of the biline and their overloaded network.

[djet]

Release
RUU_Leo_HKCSL_WWE_1.72.831.1_Radio_CRC_Signed_15.32.50.07U_2.07.51.22_2_Ship
ROM Version: 1.72.831.1
Serial Number: HT9BXNW01232

[i81]

djet @ 21.3.10, 18:01

Release

and she has a binding to the region?
What is HSPL in it?

[djet]

i81,
Not.
1.66.0000

[Football]

The current is there, the clave is Chinese: lol:

[i81]

djet @ 21.3.10, 18:38

1.66.0000

Something at these NTS is seven Fridays for weeks ... then 1.66 SPL then again the old one ... nothing to do with it! Is it really impossible to create one version of the patch for all devices? And then sit reptile that is better ...

[djet]

Football @ 21.3.10, 16:47

Current there it is, Klava Chinese laugh.gif

your keyboard patch no longer works, by the way, and leads to WSOD.

[orc12]

Do you have a normal Wi-fi network catches HD2? Something on my latest firmware has become a very weak signal level.

[kosh12]

For the same hardware, a microcircuit with a large amount of rom is not a particularly serious difference.

[Progmanit]

Progmanit @ 23.3.10, 0:39

I'll check tomorrow

In general, did Wi-Fi work worse (in the sense of the signal level) failed to identify (although there is a suspicion that it became worse), but the fact that it did not become better is for sure. It’s just that the shift has a separate office at work, so there, for example, is far from the top-end Glukofish X500, although on the brink of shutdown, it still caught the network — that is, it was possible to work, it was just sometimes reconnected once a minute. So, HD2 on the previous 1.43 network there only detected, but when authorizing it flew in a couple of seconds. Those. not one site to go was not possible. Now at 1.66 the situation is similar, only now the authorization is not even going to pass - it jumps immediately to the neighboring foreign network with a more decent signal.