HTC HD2 - Android NAND + MAGLDR + cLK | Discussion of Android firmware and MAGLDR loaders and cLK
The material presented on the page is unofficial, in case of unsuccessful firmware or loss of the device the author of the software and the Administration do not bear the responsibility of the resource!All actions are performed at your own risk!
HTC HD2 Android NAND + MAGLDR + cLK
HTC Leo, HTC T8585
HD2 guide. General information:
Description | HD2 FAQ | HD2 talk пїЅ | Purchase пїЅlAccessories пїЅ | Marriage пїЅ | HD2 owners chat пїЅ
Flashing пїЅlRe-flashing of American HD2 from T-Mobile пїЅlFlashing radio module пїЅ
Porting Android OS:
Android NAND + MAGLDR пїЅ | HTC HD2 - Android FAQ | Android SD пїЅ | Android SD - build directory | Embellishments пїЅ | Ubuntu пїЅ
Creating your own Android firmware пїЅ | HyperGBXMod firmware пїЅ | Firmware from Krendelrus пїЅ | Firmware from alexdoux25 пїЅ | Firmware from Lost_Angel пїЅ | Firmware from De11 пїЅ | Firmware from mikhei777 пїЅ | Firmware TyphooN CyanogenMod 7 пїЅ | Dorimanx firmware пїЅ | Pure CyanogenMod 7 пїЅ | NDT Ginger MIUI Firmware пїЅ | Android 4 firmware пїЅ
Porting Windows Phone 7:
HD2 WPh7 talk | WPh7 HD2 FAQ | WPh7 firmware from DFT | Firmware from gres-197
Android NAND + MAGLDR Theme Archive
--------------------------------------------------------------------------------------------------------------
There is no curator in the subject. If there is a user in the subject who wants to become a Curator and the correspondingRequirements for candidates, he can apply in the topicI want to be curator(after having studied the topic header and all materials for curators).
Prior to the appointment of the curator, on filling caps, please contactmoderatorssection through a button
under the messages to which you want to add links.
Post has been editedvaalf - 08.03.17, 19:59
HTC HD2 Android NAND + MAGLDR + cLK
HTC Leo, HTC T8585HD2 guide. General information:
Description | HD2 FAQ | HD2 talk пїЅ | Purchase пїЅlAccessories пїЅ | Marriage пїЅ | HD2 owners chat пїЅ
Flashing пїЅlRe-flashing of American HD2 from T-Mobile пїЅlFlashing radio module пїЅ
Porting Android OS:
Android NAND + MAGLDR пїЅ | HTC HD2 - Android FAQ | Android SD пїЅ | Android SD - build directory | Embellishments пїЅ | Ubuntu пїЅ
Creating your own Android firmware пїЅ | HyperGBXMod firmware пїЅ | Firmware from Krendelrus пїЅ | Firmware from alexdoux25 пїЅ | Firmware from Lost_Angel пїЅ | Firmware from De11 пїЅ | Firmware from mikhei777 пїЅ | Firmware TyphooN CyanogenMod 7 пїЅ | Dorimanx firmware пїЅ | Pure CyanogenMod 7 пїЅ | NDT Ginger MIUI Firmware пїЅ | Android 4 firmware пїЅ
Porting Windows Phone 7:
HD2 WPh7 talk | WPh7 HD2 FAQ | WPh7 firmware from DFT | Firmware from gres-197
Android NAND + MAGLDR Theme Archive
All about firmwareAndroid OSloaderMAGLDRandClockworkMod recovery
This firmware manual is suitable for any HD2 in any good condition. It does not matter if you have TMOUS or a European, it does not matter what OS it is, what bootloader is stitching, what kind of radio, just got a device from the factory or passes a third party. It doesn't matter what version of Windows you have on your PC, 32-bit or 64-bit.
Mandatory requirements for Android firmware on HD2:
1. A modified SPL loader version 2.08.HSPL must be flashed, with other versions of the Android SPL loader it will not be downloaded.
Check it out. Why go to the SPL bootloader ("mattress"): on the switched off communicator, hold down the volume down key and briefly press the power button. After the color bars appear on the screen, the volume down button can be released. The inscription "SPL-2.08.HSPL" should be present in the upper lane of the mattress; if it is absent, follow the instructions in the next spoiler
2. firmware radio module must be version 2.10 and higherThe firmware of the radio module and the SPL loader has nothing to do with Android and is NOT discussed in this topic.
3. additional Android loader must be flashed - MAGLDR
- Download archiveleoimg.zipand unpack it
- Fileleoimg.nbh(it contains MAGLDR 1.13) from the archive copy to the root of the memory card
- Go to the SPL bootloader (mattress): on the fully switched off communicator, hold down the volume down key and briefly press the power key. After the color bars appear on the screen, the volume down button can be released.
- After a few seconds, the SPL will automatically detect the file and offer to install it.
If the SPL loader does not offer to install the * .nbh file (after the appearance of color bars, the process stops) or the installation fails, try to copy the leoimg.nbh file to the memory card again, making sure that the operation was successful. Make sure there are no other * .nbh files on the memory card. Try to format the memory card. The same file may not be flashed from a large memory card.
- Download the flasher with the installation file MAGLDR to the PC -MAGLDR version 1.13
- Unpack the archive with the MAGLDR bootloader in any folder on the PC
- Go to the SPL bootloader (mattress): on the fully switched off communicator, hold down the volume down key and briefly press the power key. After the color bars appear on the screen, the volume down button can be released.
- Connect your smartphone to PC via USB.
- USB will appear in the lower strip of the mattress. If the inscription did not appear (the PC did not detect HD2, the drivers were not automatically installed), install the following driver on the PC manually (through the device manager)USB drivers. This is a driver from the Windows Mobile Device Center for Windows 7 or from Microsoft ActiveSync for Windows XP. The driver is also installed with the program.
- After the inscription has appeared, install the MAGLDR bootloader: run from the folder with the flash driverROMUpdateUtility.exeand follow the instructions on the PC screen, at the end the device will reboot and the USB cable can be disconnected.
- MAGLDR bootloader flashedAfter the MAGLDR firmware, any Windows Mobile firmware will be removed from the device.
- If all 3 mandatory requirements are met, you can proceed to install Android.
This method involves a clean installation of the firmware: from the old firmware no data and tails remain. Before using this instruction read it completely. When performing each item, keep in mind the following. You can install any of the available recovery, but the instruction is given only for the version with CWM recovery.If you do not understand something, do not skip this item.
P.1. Decide on the firmware in the " Firmware "of this message. Download the firmware of interest to your PC; mini dictionary .
A.2. Determine what type of firmware has been downloaded: DAF or zip (CWM). Distinctive features of zip firmware: the installation file is an archive of the * .zip format, inside of which, among other things, is the folder "META-INF". Usually in firmware catalog and the author's topic indicates the type of firmware.
If you downloaded a DAF firmware (which is rare now) go toInstructions for installing DAF firmware at the end of this instruction. If the firmware type is zip, then go to step 3.
P.3. Installing ClockworkMod recovery and creating on the built-in storage device necessary for flashing logical partitionsP.4. Preparing a memory card and installing firmware
- If required, create an ext partition on the memory card (20 point inFAQ), for some firmware this item is mandatory.
- Delete all files and folders remaining from the previous firmware on the memory card. User data can be left.
- Copy the installation zip with the firmware to the memory card without unarchiving it. This can be done either through a card reader by pulling the memory card out of the device. Or through CWM recovery (if it is already flashed).- A memory card must be inserted in the machine.
- On the memory card must be an installation zip firmware.
- We go in MAGLDR: on the switched off communicator, hold down the power button and DO NOT release it until the menu appears.
- Use the volume change keys to select an item.AD recovery.
- Press the "Call" key, CWM recovery will load.
- Choose itemwipe data / factory reset(however, all the data in the ext section, if it exists, will disappear).
- We perform wipe, waiting for the end of the operation.
- Choose iteminstall zip from sdcard ->choose zip from sdcard ->choose * .zip (file with the firmware you need)
- Press the "back" button to return to the main menu of CWM recovery.
- Choose itemreboot system now.
- The device will reboot and within 5-10 minutes will load Android.
- After the first launch, it is recommended to reboot once (and preferably several times). If the system starts to produce a bunch of errors and it does not work normally to reboot, turn the battery around. Most likely, the second time the firmware is loaded normally.
What is the difference between DAF and zip firmware? - The firmware itself is no different, only the way they are installed differs. zip firmware can not be installed without a memory card. Also, almost all DAF firmware do not support ClockworkMod recovery.
Mandatory requirements for Android firmware on HD2:
1. A modified SPL loader version 2.08.HSPL must be flashed, with other versions of the Android SPL loader it will not be downloaded.
Check it out. Why go to the SPL bootloader ("mattress"): on the switched off communicator, hold down the volume down key and briefly press the power button. After the color bars appear on the screen, the volume down button can be released. The inscription "SPL-2.08.HSPL" should be present in the upper lane of the mattress; if it is absent, follow the instructions in the next spoiler
Instructions for firmware boot SPL version 2.08.HSPL
- Download the following archive to PCHSPL4.zip- This is the fourth version of the SPL flasher, which allows you to flash the SPL loader of any version, both the official (OSPL) and modified versions.
- Unzip it to any convenient place on the PC.
- The communicator battery must be charged at least 50%.
- Go to the SPL loader ("mattress"): on the switched off communicator, hold down the volume down key and briefly press the power button. After the color bars appear on the screen, the volume down button can be released.
- We connect the smartphone to the PC via USB.
- In the lower lane of the mattress appearsUSB. If the inscription did not appear (the PC did not detect HD2, the drivers were not automatically installed), then install the following driver on the PC manually (through the device manager)USB drivers. This is a driver fromWindows Mobile Device Centerfor Windows 7 or fromMicrosoft ActiveSyncfor Windows XP. The driver is also installed with the program.
- After the caption appears, run HSPL4.exe on the PC and follow all the instructions on the PC screen. At one point, the flash driver will ask you exactly which version of the SPL bootloader to install, select2.08.HSPL(patched bootloader)
- At the end, the device will reboot, on the PC an inscription about successful completion will appear and the USB cable can be disconnected.
- Check if the SPL boot loader was correctly installed. We go in the mattress: on the switched off communicator, hold down the volume down key and briefly press the power button. The upper line should contain the inscription SPL-2.08.HSPL, it means that the patched bootloader needed for the Android OS firmware is stitched.
- Unzip it to any convenient place on the PC.
- The communicator battery must be charged at least 50%.
- Go to the SPL loader ("mattress"): on the switched off communicator, hold down the volume down key and briefly press the power button. After the color bars appear on the screen, the volume down button can be released.
- We connect the smartphone to the PC via USB.
- In the lower lane of the mattress appearsUSB. If the inscription did not appear (the PC did not detect HD2, the drivers were not automatically installed), then install the following driver on the PC manually (through the device manager)USB drivers. This is a driver fromWindows Mobile Device Centerfor Windows 7 or fromMicrosoft ActiveSyncfor Windows XP. The driver is also installed with the program.
- After the caption appears, run HSPL4.exe on the PC and follow all the instructions on the PC screen. At one point, the flash driver will ask you exactly which version of the SPL bootloader to install, select2.08.HSPL(patched bootloader)
- At the end, the device will reboot, on the PC an inscription about successful completion will appear and the USB cable can be disconnected.
- Check if the SPL boot loader was correctly installed. We go in the mattress: on the switched off communicator, hold down the volume down key and briefly press the power button. The upper line should contain the inscription SPL-2.08.HSPL, it means that the patched bootloader needed for the Android OS firmware is stitched.
About support for different versions of "HSPL"
This information is recommended for reading only by experienced users.
HSPL2, HSPL3, HSPL4 - is flashers (Windows program) SPL bootloader. A 2.08.HSPL - this version is very loader SPL. So the boot loader can flash and HSPL2, and HSPL3, and HSPL4. And following differences: HSPL2 not support TMOUS HD2 and it should not be used if your HD2 stitched SPL bootloader version 3.03.0000 (part of the official firmware 3.14), HSPL3 supports TMOUS HD2, but it also can not be used if your HD2 stitched loader SPL version 3.03.0000. HSPL4 can be used with the loader SPL version 3.03.0000, and thus it is possible to flash the patched SPL bootloader version 3.03.HSPL - so he does not support the MAGLDR. But at the same time he supports HSPL4 MAGLDR because with it you can flash the desired SPL version 2.08.HSPL
HSPL2, HSPL3, HSPL4 - is flashers (Windows program) SPL bootloader. A 2.08.HSPL - this version is very loader SPL. So the boot loader can flash and HSPL2, and HSPL3, and HSPL4. And following differences: HSPL2 not support TMOUS HD2 and it should not be used if your HD2 stitched SPL bootloader version 3.03.0000 (part of the official firmware 3.14), HSPL3 supports TMOUS HD2, but it also can not be used if your HD2 stitched loader SPL version 3.03.0000. HSPL4 can be used with the loader SPL version 3.03.0000, and thus it is possible to flash the patched SPL bootloader version 3.03.HSPL - so he does not support the MAGLDR. But at the same time he supports HSPL4 MAGLDR because with it you can flash the desired SPL version 2.08.HSPL
Instructions for the latest firmware Radio
- Download the following archive to PC Radio 2.15.50.14.rar and unzip it to any convenient folder. This is the archive with the flasher of the radio module version 2.15.50.14.
- Go to the SPL loader ("mattress"): on the switched off communicator, hold down the volume down key and briefly press the power button. After the color bars appear on the screen, the volume down button can be released.
- Connect your device to a PC via USB.
- After the computer correctly recognizes HD2 (USB appears in the lower band of the mattress), launch the file on the PCCustomRUU.exefrom the folder with the unzipped firmware of the radio module.
- Follow all the instructions of the flasher on the PC screen
- Go to the SPL loader ("mattress"): on the switched off communicator, hold down the volume down key and briefly press the power button. After the color bars appear on the screen, the volume down button can be released.
- Connect your device to a PC via USB.
- After the computer correctly recognizes HD2 (USB appears in the lower band of the mattress), launch the file on the PCCustomRUU.exefrom the folder with the unzipped firmware of the radio module.
- Follow all the instructions of the flasher on the PC screen
3. additional Android loader must be flashed - MAGLDR
WhatMAGLDR bootloader
DFT (Dark forces team - a group of developers working on HD2) led byCotulla developed the MAGLDR bootloader - an Android OS bootloader that allows you to flash and use Android or WPh7 on HD2 (support added since version 1.12).
Loader MAGLDR - is part of the firmware, which allows you to work with the HTC HD2 Android OS. In addition MAGLDR allows access to the memory card without loading the operating system. Android allows you to load both the built-in storage (NAND flash) and Android'a assembly memory card. And also it allows you to perform a number of other functions. MAGLDR stitched to the firmware of the Android'a. MAGLDR not replace vindovyh SPL bootloader. He runs after him. So that it can be easy to install and remove, without the risk of brick.
You can read about how the firmware is arranged in the following place:HTC Leo - FAQ. MAGLDR in this hierarchy occupies an intermediate place. The SPL loader (which used to load WM) now initializes MAGLDR, which in turn loads Android.
MAGLDR with Windows Mobile is not compatible, the firmware of one of them is due to the removal of the other.
MAGLDR stitched, how to enter it? - on the fully turned off communicator, hold down the power button and DO NOT release it until the menu appears.
If no operating system is not yet flashed, then when you turn on the HD2 screen, the main menu of the MAGLDR bootloader is displayed (boot menu), it can also be opened using the method described above.
How to find out what is my version of MAGLDR? - go into it, there will be written on top
Boot menu
1. "Boot WPH"- downloads Windows Phone 7 firmware (need to flash WPh7 first)
2. "Boot AD SD"- loads Android from a memory card. To start, you need to place the Android assembly on the memory card and specify the path to the kernel (zImage) and initrd.gz, this is done in the "AD SD Dir" item.
3. "Boot AD NAND"- downloads the Android firmware from the built-in drive (NAND). Requires pre-flash Android.
zImage and initrd.gz are loaded from the boot partition on the HD2 internal storage.
4. "USB MassStg"- the function of a removable drive allows you to connect to a PC via USB to access the memory card without booting the OS.
5. "USB Flasher"- mode to work with DAF flasher when connected to a PC via USB. Used to install DAF-firmware Android'a, Windows Phone 7, as well as to install ClockworkMod recovery. In order for the PC to correctly recognize the communicator in this mode, you must install (usually automatically installed) the driver from the Windows Mobile Device Center (Microsoft ActiveSync).
6. "USB TTY"- the function of executing commands (such as task 2a, task29, etc.) from a PC via USB via the MTTY program. Requires installation on a PC of the same driver as to support MTTY access to SPL.
7. "AD HardReset"- deletes the Android partition with the" hr "flag. It is usually used to remove Android along with user settings.
8. "AD Recovery"- starts recovery. Requires pre-flash ClockworkMod recovery.
9. "Tetris"- game Tetris. Score 111111 points to activate hidden menu items MAGLDR
10. "Services"- when you click on this item, a menu with service settings opens (Services menu)
12. "Powerdown"- off HD2
Button assignment:
- volume control buttons perform the navigation function;
- The "Call" key is responsible for selecting the item;
- key "Home" returns to the previous submenu;
- key "Windows" returns to the main menu (boot menu);
- the "Call on / off call" key is used to enter the main menu (boot menu) during autoloading of the device
Change Log:
- Version 1.10 was released on December 30, 2010 and became the first public version.
- In version 1.11, a bug was fixed when the firmware download stopped on the inscription "GoGoGo"
- Version 1.12 adds support for Windows Phone 7
- Version 1.13 adds support for Android recovery (ClockworkMod recovery must be installed separately); the charging problem was gracefully corrected (it wasn’t charged in the off state); now, when connected to power, the device automatically turns on, it cannot be charged in the off state; Fixed a problem with MassStorage mode (removable disk mode), but still often hangs when copying files to your device.
The latest version was released on February 1, 2011.
Maybe in the next version will appear
- it is planned to add support for startup.txt from Haret, only for Android assemblies for a memory card
- it is planned to add support for boot images, as in the native Android, the boot partition will be stitched not in a folder, but in the .img format in raw format. This is already implemented in the CLK loader.
- support for fastboot, already implemented in the alternative loader cLK
- support for fixed partition layout, with the ability to resize each partition separately, already implemented in the alternative cLK loader
- ability to work with any existing WM firmware
- ability to work with special firmware WM
Loader MAGLDR - is part of the firmware, which allows you to work with the HTC HD2 Android OS. In addition MAGLDR allows access to the memory card without loading the operating system. Android allows you to load both the built-in storage (NAND flash) and Android'a assembly memory card. And also it allows you to perform a number of other functions. MAGLDR stitched to the firmware of the Android'a. MAGLDR not replace vindovyh SPL bootloader. He runs after him. So that it can be easy to install and remove, without the risk of brick.
You can read about how the firmware is arranged in the following place:HTC Leo - FAQ. MAGLDR in this hierarchy occupies an intermediate place. The SPL loader (which used to load WM) now initializes MAGLDR, which in turn loads Android.
MAGLDR with Windows Mobile is not compatible, the firmware of one of them is due to the removal of the other.
MAGLDR stitched, how to enter it? - on the fully turned off communicator, hold down the power button and DO NOT release it until the menu appears.
If no operating system is not yet flashed, then when you turn on the HD2 screen, the main menu of the MAGLDR bootloader is displayed (boot menu), it can also be opened using the method described above.
How to find out what is my version of MAGLDR? - go into it, there will be written on top
Value of menu items
Boot menu
1. "Boot WPH"- downloads Windows Phone 7 firmware (need to flash WPh7 first)
2. "Boot AD SD"- loads Android from a memory card. To start, you need to place the Android assembly on the memory card and specify the path to the kernel (zImage) and initrd.gz, this is done in the "AD SD Dir" item.
3. "Boot AD NAND"- downloads the Android firmware from the built-in drive (NAND). Requires pre-flash Android.
zImage and initrd.gz are loaded from the boot partition on the HD2 internal storage.
4. "USB MassStg"- the function of a removable drive allows you to connect to a PC via USB to access the memory card without booting the OS.
5. "USB Flasher"- mode to work with DAF flasher when connected to a PC via USB. Used to install DAF-firmware Android'a, Windows Phone 7, as well as to install ClockworkMod recovery. In order for the PC to correctly recognize the communicator in this mode, you must install (usually automatically installed) the driver from the Windows Mobile Device Center (Microsoft ActiveSync).
6. "USB TTY"- the function of executing commands (such as task 2a, task29, etc.) from a PC via USB via the MTTY program. Requires installation on a PC of the same driver as to support MTTY access to SPL.
7. "AD HardReset"- deletes the Android partition with the" hr "flag. It is usually used to remove Android along with user settings.
8. "AD Recovery"- starts recovery. Requires pre-flash ClockworkMod recovery.
9. "Tetris"- game Tetris. Score 111111 points to activate hidden menu items MAGLDR
10. "Services"- when you click on this item, a menu with service settings opens (Services menu)
- Services menu
1. "Boot Settings"- when you click on this item, the "Autoboot" menu opens, in which the startup parameters are configured
- Autoboot
1. "Boot source"- in this menu it is selected that it will be loaded automatically when the device is turned on:"Android from SD"- build Android'a memory card,"Android from NAND"- Android'a firmware,"WPH from NAND"- Windows Phone 7 firmware.
2. "Always Menu"- when setting this parameter when booting, the device will automatically load the menu of the MAGLDR loader regardless of whether you have any OS installed and any OS installed.
3. "AD SD Dir"(short for Android directory on SD-card) - this item indicates the folder on the memory card from which the Android assembly will be loaded.
3. "DumpUDtoSD"- writes "asize" partition to the memory card. Experimental function. Buggy, slow running and not tested to the end. Do not use.
4. "UseLast24NAND"- allows you to use the backup 24 MB of internal drive, ie, increase the drive capacity available to the user. Be careful not to lose your data. When updating MAGLDR through the RUU flasher, when flashing the radio module, data from these 24 MB is erased. This means that will be damaged or the device will stop loading. By default, this area of ​​the drive is not enabled (OFF).
5. "ClearSD MBR"- deletes the partition table created when flashing Windows Phone 7, it allows you to format the memory card after using WPh7. When performing this item, all data from the memory card will be lost.
Cotulla
erase MBR, wifi boot ("200 Mb problem")
12. "Powerdown"- off HD2
Button assignment:
- volume control buttons perform the navigation function;
- The "Call" key is responsible for selecting the item;
- key "Home" returns to the previous submenu;
- key "Windows" returns to the main menu (boot menu);
- the "Call on / off call" key is used to enter the main menu (boot menu) during autoloading of the device
In tetris
Outside the game, you can return to the main menu with the "Home" button. You can start the game with the volume up button. At the same time, the "Call" key shifts the shape to the left, the "Windows" key moves the shape to the right, the "Home" key moves down, the "Start / end call" key rotates the shape.
Change Log:
- Version 1.10 was released on December 30, 2010 and became the first public version.
- In version 1.11, a bug was fixed when the firmware download stopped on the inscription "GoGoGo"
- Version 1.12 adds support for Windows Phone 7
- Version 1.13 adds support for Android recovery (ClockworkMod recovery must be installed separately); the charging problem was gracefully corrected (it wasn’t charged in the off state); now, when connected to power, the device automatically turns on, it cannot be charged in the off state; Fixed a problem with MassStorage mode (removable disk mode), but still often hangs when copying files to your device.
The latest version was released on February 1, 2011.
Maybe in the next version will appear
- it is planned to add support for startup.txt from Haret, only for Android assemblies for a memory card
- it is planned to add support for boot images, as in the native Android, the boot partition will be stitched not in a folder, but in the .img format in raw format. This is already implemented in the CLK loader.
- support for fastboot, already implemented in the alternative loader cLK
- support for fixed partition layout, with the ability to resize each partition separately, already implemented in the alternative cLK loader
- ability to work with any existing WM firmware
- ability to work with special firmware WM
MAGLDR firmware instructions
Method number 1 . Firmware without PC from a memory card.
- Download archiveleoimg.zipand unpack it
- Fileleoimg.nbh(it contains MAGLDR 1.13) from the archive copy to the root of the memory card
- Go to the SPL bootloader (mattress): on the fully switched off communicator, hold down the volume down key and briefly press the power key. After the color bars appear on the screen, the volume down button can be released.
- After a few seconds, the SPL will automatically detect the file and offer to install it.
If the SPL loader does not offer to install the * .nbh file (after the appearance of color bars, the process stops) or the installation fails, try to copy the leoimg.nbh file to the memory card again, making sure that the operation was successful. Make sure there are no other * .nbh files on the memory card. Try to format the memory card. The same file may not be flashed from a large memory card.
Method number 2 . Firmware without a memory card using a PC.
- Download the flasher with the installation file MAGLDR to the PC -MAGLDR version 1.13
- Unpack the archive with the MAGLDR bootloader in any folder on the PC
- Go to the SPL bootloader (mattress): on the fully switched off communicator, hold down the volume down key and briefly press the power key. After the color bars appear on the screen, the volume down button can be released.
- Connect your smartphone to PC via USB.
- USB will appear in the lower strip of the mattress. If the inscription did not appear (the PC did not detect HD2, the drivers were not automatically installed), install the following driver on the PC manually (through the device manager)USB drivers. This is a driver from the Windows Mobile Device Center for Windows 7 or from Microsoft ActiveSync for Windows XP. The driver is also installed with the program.
- After the inscription has appeared, install the MAGLDR bootloader: run from the folder with the flash driverROMUpdateUtility.exeand follow the instructions on the PC screen, at the end the device will reboot and the USB cable can be disconnected.
- MAGLDR bootloader flashed
- If all 3 mandatory requirements are met, you can proceed to install Android.
Instructions for firmware Android OS
This method involves a clean installation of the firmware: from the old firmware no data and tails remain. Before using this instruction read it completely. When performing each item, keep in mind the following. You can install any of the available recovery, but the instruction is given only for the version with CWM recovery.If you do not understand something, do not skip this item.
P.1. Decide on the firmware in the " Firmware "of this message. Download the firmware of interest to your PC; mini dictionary .
A.2. Determine what type of firmware has been downloaded: DAF or zip (CWM). Distinctive features of zip firmware: the installation file is an archive of the * .zip format, inside of which, among other things, is the folder "META-INF". Usually in firmware catalog and the author's topic indicates the type of firmware.
If you downloaded a DAF firmware (which is rare now) go toInstructions for installing DAF firmware at the end of this instruction. If the firmware type is zip, then go to step 3.
P.3. Installing ClockworkMod recovery and creating on the built-in storage device necessary for flashing logical partitions
What CWM recovery ?
Discussion CWM recovery for HD2 on xda-developers. The latest stable HD2 version is 5.0.2.6. dropbox - from here you can always download the image of the latest CWM recovery. Stable versions for HD2, laid out on XDA-developers, are distinguished by the fact that they fixed a bug that did not restore sd-ext when restoring a backup copy of the firmware, as well as included YES / NO fixes that remove all unnecessary items no "from the confirmation menu and the" yes "item is the first item.
What is ClockworkMod recovery (CWR / DVR or CWM)? - This is an enhanced version of recovery (HD2 does not have normal recovery, MAGLDR performs its functions), which allows you to make a full backup of the firmware, replace system files, install firmware without a PC, easily install patches and add-ons, perform wipe, reset to factory defaults settings and create an ext3 partition on the memory card. Recovery - advanced boot menu for Android OS.
How do I know which version of ClockworkMod recovery is stitched from me? - Go to the CWM recovery, there will be a version written on top.
How to log in to CWM recovery? - for MAGLDR: on the switched off smartphone, hold down and DO NOT press the power key until the loader menu appears on the screen, then select the item AD recovery ; for the cLK bootloader: on the switched off smartphone, hold down the "Back" button and briefly press the power key.
How to update CWM recovery without data loss? - Install the following zip via CWM recovery -
recovery_v5.0.2.6_leo_CWR.zip (4.25 MB)
After the update, the Android firmware will not fly off and all data will be saved, the version of the new CWM recovery 5.0.2.6. But you can put in an installation zip image with any recovery. Before updating, make a backup copy so that in case of unsuccessful firmware, you can restore the previous firmware. Also, recovery can be updated from under Android itself.instructions from the FAK.
Why is my CWM recovery not being updated? - this happens when a new recovery is more than the old one, we read about solving the problem here .
Navigation
• volume up button - up
• volume down button - down
• "Call" button - select item
• on / off button - back
• volume down button - down
• "Call" button - select item
• on / off button - back
menu item values
• Reboot system - reboot of the communicator
• apply sdcard: update.zip - install the firmware from the update.zip file located in the "/ sdcard /" directory
• wipe data / factory reset - cleansing data (user data), cache (temporary files) on the built-in storage device and ext section on the memory card (if it exists), as well as the ".android secure" folders on the memory card, folders, In which are the applications installed on the memory card.
• wipe cache partition - clearing the cache partition
• install zip from sdcard - install a zip firmware with a random name from a memory card (from any folder)
• apply sdcard: update.zip - install the firmware from the update.zip file located in the "/ sdcard /" directory
• wipe data / factory reset - cleansing data (user data), cache (temporary files) on the built-in storage device and ext section on the memory card (if it exists), as well as the ".android secure" folders on the memory card, folders, In which are the applications installed on the memory card.
• wipe cache partition - clearing the cache partition
• install zip from sdcard - install a zip firmware with a random name from a memory card (from any folder)
- в—¦ apply sdcard: update.zip - install the firmware from the update.zip file located in the "/ sdcard /" directory
в—¦ chooze zip from sdcard - select zip (firmware, fix, etc.) on the memory card for installation
в—¦ toggle signature verification - on / off. verification of firmware signature
в—¦ toggle script assert - on / off. approval script
- в—¦ backup - full backup of the firmware on the memory card
в—¦ restore - restore the backup created by the itembackup
в—¦ Advanced Restore - recovery mode with advanced settings, selective recovery
- в—¦ mount / system - mount system partition
в—¦ unmount / data - unmounting data section
в—¦ unmount / cache unmounting the cache partition
в—¦ mount / sdcard - mount memory card
в—¦ mount / sd-ext - mount ext partition of memory card (ext partition must be created on the memory card)
в—¦ format boot - format the boot partition
в—¦ format system - formatting the system partition (where the Android OS firmware itself is located)
в—¦ format data - formatting data section - user data section
в—¦ format cache - cache partition formatting
в—¦ format sdcard - formatting the memory card (all data from the memory card will be deleted)
в—¦ format sd-ext - formatting an ext partition on a memory card
в—¦ mount USB storage - connect to PC in removable disk mode
- в—¦ Reboot Recovery - restart recovery
в—¦ Wipe Dalvik Cache - cleaning Dalvik cache
в—¦ Wipe Battery Stat - reset battery statistics
в—¦ Report Error - report an error
в—¦ Key Test - Key Verification
в—¦ Restart adbd - reboot the ADB server
в—¦ Process dump - firmware dump
What is ClockworkMod recovery (CWR / DVR or CWM)? - This is an enhanced version of recovery (HD2 does not have normal recovery, MAGLDR performs its functions), which allows you to make a full backup of the firmware, replace system files, install firmware without a PC, easily install patches and add-ons, perform wipe, reset to factory defaults settings and create an ext3 partition on the memory card. Recovery - advanced boot menu for Android OS.
How do I know which version of ClockworkMod recovery is stitched from me? - Go to the CWM recovery, there will be a version written on top.
How to log in to CWM recovery? - for MAGLDR: on the switched off smartphone, hold down and DO NOT press the power key until the loader menu appears on the screen, then select the item AD recovery ; for the cLK bootloader: on the switched off smartphone, hold down the "Back" button and briefly press the power key.
How to update CWM recovery without data loss? - Install the following zip via CWM recovery -
recovery_v5.0.2.6_leo_CWR.zip (4.25 MB) After the update, the Android firmware will not fly off and all data will be saved, the version of the new CWM recovery 5.0.2.6. But you can put in an installation zip image with any recovery. Before updating, make a backup copy so that in case of unsuccessful firmware, you can restore the previous firmware. Also, recovery can be updated from under Android itself.instructions from the FAK.
Why is my CWM recovery not being updated? - this happens when a new recovery is more than the old one, we read about solving the problem here .
CWM recovery installation instructions
When installing recovery in this way, the current system will be deleted (if installed), all user data on the built-in storage device will be lost.
- Download archive with CWM recovery to PC:Flasher_for_CWM_recovery_v5.0.2.6.rar(4.36 MB)
and unpack it into any empty folder on the PC.
- Determine what size the system partition is required for the firmware: unpack the archive with the firmware downloaded in the first paragraph and determine the volume of the system folder. The system partition should be slightly larger (5-10 MB). The volume of the system partition can be from 50 to 400 MB (for European HD2), its size should be chosen so that the firmware fit there, but it must be remembered that the larger its size, the less memory remains for user data (the volume of the partition decreases data).
The cache partition size can vary from 5 to 50 MB, but for most firmware, a cache partition is required with a volume of no more than 5 MB.
- In the folder with the CWM recovery flash driver, we find the flash.cfg file (instructions for the DAF flash driver) of approximately the following content:
misc ya 1M
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya150 M
cache ya 5M
userdata ya | asize | hr allsize
In it: the fourth line - the size of the created system partition, the fifth - the size of the cache partition, "150M" - the size of the partition in megabytes.
Open the flash.cfg file in any text editor, for example, notepad, and change the number highlighted in red to the desired value. The dimensions of the remaining sections for almost all firmware are chosen as indicated in the example above.
- We go in MAGLDR: on the switched off deviceto clamppower key and do not release it until the menu appears.
- Use the volume change keys to select an item.USB flasher.
- Press the "Call".
- An inscription appears.usb wait ...Connect with USB cable to PC.
- An inscription appears.usb wait ... usb.
- If the inscription does not appear and the computer did not automatically install the driver on the USB device (installed incorrectly) install the driver manually from the archiveUSB_drivers.zip.
- Run DAF.exe on the PC from the folder with the CWM recovery flash driver on behalf of the Administrator and follow all the instructions on the PC screen, at the end the smartphone will reboot and the USB cable can be disconnected (only on the PC screen the end is displayed).
- After launch, the DAF flasher will create the sections specified in the configuration on the built-in storage device, recovery will be flashed to the same section, while the previous android firmware (if it was flashed) will be deleted.
- Download archive with CWM recovery to PC:
Flasher_for_CWM_recovery_v5.0.2.6.rar(4.36 MB)and unpack it into any empty folder on the PC.
- Determine what size the system partition is required for the firmware: unpack the archive with the firmware downloaded in the first paragraph and determine the volume of the system folder. The system partition should be slightly larger (5-10 MB). The volume of the system partition can be from 50 to 400 MB (for European HD2), its size should be chosen so that the firmware fit there, but it must be remembered that the larger its size, the less memory remains for user data (the volume of the partition decreases data).
The cache partition size can vary from 5 to 50 MB, but for most firmware, a cache partition is required with a volume of no more than 5 MB.
- In the folder with the CWM recovery flash driver, we find the flash.cfg file (instructions for the DAF flash driver) of approximately the following content:
misc ya 1M
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya150 M
cache ya 5M
userdata ya | asize | hr allsize
In it: the fourth line - the size of the created system partition, the fifth - the size of the cache partition, "150M" - the size of the partition in megabytes.
Open the flash.cfg file in any text editor, for example, notepad, and change the number highlighted in red to the desired value. The dimensions of the remaining sections for almost all firmware are chosen as indicated in the example above.
- We go in MAGLDR: on the switched off deviceto clamppower key and do not release it until the menu appears.
- Use the volume change keys to select an item.USB flasher.
- Press the "Call".
- An inscription appears.usb wait ...Connect with USB cable to PC.
- An inscription appears.usb wait ... usb.
- If the inscription does not appear and the computer did not automatically install the driver on the USB device (installed incorrectly) install the driver manually from the archiveUSB_drivers.zip.
- Run DAF.exe on the PC from the folder with the CWM recovery flash driver on behalf of the Administrator and follow all the instructions on the PC screen, at the end the smartphone will reboot and the USB cable can be disconnected (only on the PC screen the end is displayed).
- After launch, the DAF flasher will create the sections specified in the configuration on the built-in storage device, recovery will be flashed to the same section, while the previous android firmware (if it was flashed) will be deleted.
- If required, create an ext partition on the memory card (20 point inFAQ), for some firmware this item is mandatory.
- Delete all files and folders remaining from the previous firmware on the memory card. User data can be left.
- Copy the installation zip with the firmware to the memory card without unarchiving it. This can be done either through a card reader by pulling the memory card out of the device. Or through CWM recovery (if it is already flashed).
Copying files using CWM recovery
- We go in MAGLDR: on the switched off communicator, hold down the power key and DO NOT release it until the menu appears.
- Use the volume change keys to select an item.AD recovery.
- Press the "Call" key, CWM recovery will load.
- In the CWM recovery menu, select ”mounts and storage”
- In the opened submenu, select the item ”mount USB storage”
- If the USB cable is not connected, connect it to the PC.
- A removable disk will appear on the PC, if it does not appear, disconnect the USB cable and connect it again.
- Copy the zip firmware to the memory card without unarchiving it.
- On the communicator screen, select “Unmount”.
- Use the volume change keys to select an item.AD recovery.
- Press the "Call" key, CWM recovery will load.
- In the CWM recovery menu, select ”mounts and storage”
- In the opened submenu, select the item ”mount USB storage”
- If the USB cable is not connected, connect it to the PC.
- A removable disk will appear on the PC, if it does not appear, disconnect the USB cable and connect it again.
- Copy the zip firmware to the memory card without unarchiving it.
- On the communicator screen, select “Unmount”.
- On the memory card must be an installation zip firmware.
- We go in MAGLDR: on the switched off communicator, hold down the power button and DO NOT release it until the menu appears.
- Use the volume change keys to select an item.AD recovery.
- Press the "Call" key, CWM recovery will load.
- Choose itemwipe data / factory reset(however, all the data in the ext section, if it exists, will disappear).
- We perform wipe, waiting for the end of the operation.
- Choose iteminstall zip from sdcard ->choose zip from sdcard ->choose * .zip (file with the firmware you need)
- Press the "back" button to return to the main menu of CWM recovery.
- Choose itemreboot system now.
- The device will reboot and within 5-10 minutes will load Android.
- After the first launch, it is recommended to reboot once (and preferably several times). If the system starts to produce a bunch of errors and it does not work normally to reboot, turn the battery around. Most likely, the second time the firmware is loaded normally.
Instructions for installing DAF firmware
- If required, create a partition on the ext memory card (item 20FAQ), for some firmware this item is mandatory;
- unzip the archive with DAF firmware to any folder on the PC;
- we go in MAGLDR: on the switched off communicator, hold down the power key and DO NOT release it until the menu appears;
- use the volume change keys to select USB Flasher;
- press the "Call";
- appearsusb wait ...Connect the USB cable to the PC;
- appearsusb wait ... usb;
- If the inscription does not appear and the computer did not automatically install the driver on the USB device (installed incorrectly) install the driver manually from the archiveUSB_drivers.zip;
- we run DAF.exe (Install.exe) on the PC from the folder with the firmware on behalf of the Administrator and follow all the instructions on the PC screen, after the smartphone is restarted and the USB cable can be disconnected (only after the completion message appears on the PC screen) ). At this point in the built-in storage device, the creation of android-sections (system, data, etc.) is performed. In this case, all previously installed firmware and recovery will be erased.
- After the restart, Android will start loading. After the first start, it is recommended to restart the system 1 or several times.
Comment . DAF firmware is not compatible with CWM recovery. Installing one of them is due to the removal of the other. However, there are DAF firmware, when installed, CWM recovery is immediately installed, i.e. They are installed as DAF firmware, but at the same time they have all the advantages of zip firmware.
- unzip the archive with DAF firmware to any folder on the PC;
- we go in MAGLDR: on the switched off communicator, hold down the power key and DO NOT release it until the menu appears;
- use the volume change keys to select USB Flasher;
- press the "Call";
- appearsusb wait ...Connect the USB cable to the PC;
- appearsusb wait ... usb;
- If the inscription does not appear and the computer did not automatically install the driver on the USB device (installed incorrectly) install the driver manually from the archiveUSB_drivers.zip;
- we run DAF.exe (Install.exe) on the PC from the folder with the firmware on behalf of the Administrator and follow all the instructions on the PC screen, after the smartphone is restarted and the USB cable can be disconnected (only after the completion message appears on the PC screen) ). At this point in the built-in storage device, the creation of android-sections (system, data, etc.) is performed. In this case, all previously installed firmware and recovery will be erased.
- After the restart, Android will start loading. After the first start, it is recommended to restart the system 1 or several times.
Comment . DAF firmware is not compatible with CWM recovery. Installing one of them is due to the removal of the other. However, there are DAF firmware, when installed, CWM recovery is immediately installed, i.e. They are installed as DAF firmware, but at the same time they have all the advantages of zip firmware.
What is the difference between DAF and zip firmware? - The firmware itself is no different, only the way they are installed differs. zip firmware can not be installed without a memory card. Also, almost all DAF firmware do not support ClockworkMod recovery.
CLK loader , Installation instructions
cLK ( C edesmith's L ittle K ernel bootloader) is an alternative Android operating system loader. It is stitched instead of MAGLDR and performs similar functions. You can also find the names LK or HBOOT, in order to avoid confusion, the bootloader will always be called cLK. The loader was designed by xda -cedesmith . March 15, 2011, he released the latest version 1.3.3. Then he stopped developing the loader and at different times he developed it. arif-ali , dan1j3l , xdmcdmc and Rick_1995 . The latter is engaged in cLK at the moment. Now this bootloader is discussed in his topic on xda . The latest versions are laid out by the user. kokotas based on joint development. The following description and installation instructions are devoted to version 1.5.1.6 of 11/23/2012. The original description in English can be found in author's message on xda There is also a list of changes.
Differences between cLK and MAGLDR:
- Allows you to charge the device in the off state. The smartphone is activated with the call accept button. In addition, it allows you to change the battery voltage threshold when charging in the off state.
- Loader menu is not displayed at boot (reboot HD2). No running lines (logs) at boot.
- Supports reboot into recovery mode, allows you to go directly from the switched off device to CWM recovery.
- Supports reboot into bootloader mode
For these advantages, CLK firmwares are called natural (native), i.e. Android works like on real Android devices.
- The structure of the zip firmware is different. Therefore, adapted for cLK firmware versions are required. zip'y for replacing the kernels also require special versions for cLK (since zip for CWM recovery in the case of the cLK bootloader does not contain the boot partition as a folder, but as an image). All other fixes and patches can be installed from MAGLDR.
- Supports only internet connection using ppp protocol. MAGLDR, in addition, supports a newer way - the rmnet protocol.
- At the moment, the Internet with the cLK loader is less stable for some users.
- Allows in most cases to do with the firmware without connecting to a computer. In the loader menu there is a built-in function for resizing logical partitions on the built-in storage device and their order.
- Has a means of checking the damaged blocks of the built-in flash drive.
- Has open source and everyone can improve this bootloader. Due to this, unlike MAGLDR, the CLK loader is regularly updated and at the same time its development does not depend on the DFT development team.
- Supports SysAlarm alarm, which is triggered when HD2 is off.
- cLK reads the CID, IMEI, MAC address of Bluetooth and the MAC address of the Wi-Fi device (getting the MAC address of Wi-Fi does not work correctly)
- In the cLK bootloader, the ability to connect to a PC in fastboot mode is implemented. But there is no possibility of connecting to a PC to use the DFT flasher from DAF.
- The cLK loader can be updated (flashed) not only through the mattress (from a computer or a memory card), but also via fastboot (it needs to be flashed with cLK), via recovery or from Android.
- Does not know how to work with a memory card (there are no drivers for FAT32), therefore Android’s standard assemblies for MAGLDR for a memory card will not work. The kernel (zImage) and initrd.gz should be flashed into the built-in drive, in the "sboot" section.
- In the CLK, there are no MAGLDR functions such as the launch of WPh7, the function of connecting to a PC in removable disk mode and tetris. CLK also does not allow installing the so-called DAF firmware (which is now almost gone), although experienced users can find in our FAQ’s instructions for converting DAF to zip and zip-MAGLDR to zip-cLK.
At the same time recovery (CWM, TWRP) that for cLK, that for MAGLDR is used the same and work with it is no different.
When installing cLK firmware, it should be taken into account that the partitioning of the built-in HD2 drive into logical partitions, i.e. Creating a system (system), boot (boot), cache (cache) and other sections occurs after cLK firmware and regardless of recovery. Because in cLK, you can change the order of partitions and their sizes without reinstalling recovery.
The CLM recovery version of stable version 5.0.2.6 with touch control support (Touch Beta 8 RC1) is already built into the installation file cLK, there is also a version cLK with TWRP recovery v2.2.2.0. This allows you to install Android firmware even to those users who have a broken USB port (only if the modified SPL is already flashed), because the recovery is installed with the cLK from the memory card in the mattress mode.
CLK loader management .
To access the menus on cLK off your device, hold "Back" button and briefly press the power key. To download Android'a assembly memory card, hold down the "menu" (windows) when you turn on the device. To enter the CWM recovery on the unit is turned off, hold down the "Home" and briefly press the power button. Connects to your PC in fastboot mode, open the main boot menu cLK and connect the USB cable. In cLK management boot menu is similar MAGLDR the following buttons:
- volume control buttons perform the navigation function;
- The "Call" key is responsible for selecting the item;
- the "Windows" key duplicates the "call" key (for those whose button is broken);
- key "Back" returns to the previous menu;
- key "Home" returns to the main menu.
Commands to control cLK via fastboot (from PC) can be viewedhere. As well as the users of our forum have written a program with a friendly interface, which, without knowing the commands for fastboot and generally understanding what it is, makes it easy to control the bootloader from a PC. Further, in order to distinguish it from others, this program will be called a script.
For inexperienced users should first understand the process of setting MAGLDR firmware and then install CLK. Below method involves installing a clean firmware from the old firmware no data and tails are left. The instructions given to the links and to CWM recovery, and on the TWRP, but the instructions are for the use of CWM, as the most widespread. Before using this manual read it all. Perform each item, keep in mind the following.
Required installation requirements for cLK firmware:
- A modified boot loader version 2.08.HSPL or 3.03.HSPL must be flashed. Check it out. Why go to the SPL loader ("mattress"): on the switched off communicator, hold down the volume down key and briefly press the power button. After the color bars appear on the screen, the volume down button can be released. The inscription "SPL-2.08.HSPL" or "SPL-3.03.HSPL" should be present in the upper mattress strip.
- Firmware versionradio modulemust be 2.10 or higher.
P.1. Downloading firmware and determining the parameters required to install it.
- We are determined with the firmware in the section "Firmware "of this message. There are also voting results. Downloading the firmware of interest to the PC; mini dictionary .
- Make sure that you downloaded exactly the version for the CLK loader. If the author releases a separate version for cLK, then the firmware will go in a zip-file, which, among other things, contains the file "boot.img". If the author releases the cLK firmware in the form of a patch, then you must first install a zip for MAGLDR, and then install the patch to the cLK version. Here in the patch will be the same "boot.img". For details, see the description of each firmware in our firmware catalog, as well as in the themes of the authors of the firmware.
- We determine the size of the partitions that will need to be created in the internal HD2 memory before installing the Android firmware.
A.2. Install additional boot loader cLK and recovery
- Download to PCLeoAdvancedRUU.exe- custom flasher.
- Download the archive with the installation file CLK loader of the required version onto your PC:
cLK v1.5.1.6 with integrated CWM recoveryblack_lk_20121123-TouchRec_b8.7z(4.36 MB)
cLK v1.5.1.6 with integrated TWRP recoveryblack_lk_20121123-TWRP_b2_2_2_0.7z(4.53 MB)
- Create the XXX folder on the PC and copy the file "LeoAdvancedRUU.exe" and the file "LEOIMG.nbh" from the archive "black_lk_20121123-TouchRec_b8.7z" into it.
- Go to the SPL loader ("mattress"): on the switched off device, hold down the volume down key and briefly press the power button. After the color bars appear on the screen, the volume down button can be released.
- We connect the smartphone to the PC with a USB cable.
- The inscription "USB" will appear in the lower strip of the mattress. If the inscription did not appear (the PC did not detect HD2, the drivers were not automatically installed), then install the following driver on the PC manually (through the device manager)USB drivers. This is a driver from the Windows Mobile Device Center for Windows 7 or from Microsoft ActiveSync for Windows XP. The driver is installed with the program.
- After the inscription has appeared, we run on the computer "LeoAdvancedRUU.exe" from the XXX folder.
- In the window that opens, change the language to Russian, select the item "Regular RUU" and click the "Next" button.
- The installer will open, follow the instructions on the PC screen.
- Download the archive with the installation file CLK loader of the required version onto your PC:
cLK v1.5.1.6 with integrated CWM recoveryblack_lk_20121123-TouchRec_b8.7z(4.36 MB)
cLK v1.5.1.6 with integrated TWRP recoveryblack_lk_20121123-TWRP_b2_2_2_0.7z(4.53 MB)
- Copy the file "LEOIMG.nbh" from the archive "black_lk_20121123-TouchRec_b8.7z" to the root of the memory card.
- Make sure that in the root of the memory card there are no other files with the extension .nbh.
- Turn off HD2 and insert a memory card into it.
- Go to the SPL loader (mattress): on the device completely turned off, hold down the volume down button and briefly press the power button.
- After a few seconds, SPL will automatically detect the file and offer to install it.
If SPL does not offer to install the file (after the appearance of color bars, the process stops) or the installation fails, try again to copy the file "LEOIMG.nbh" to the memory card, making sure that the operation was successful. Try to format the memory card. The same file may not be flashed from a large memory card. If cLK still fails to flash, try this procedure using a PC.
P.3. Splitting HD2 Internal Memory into Android Sections
With the cLK firmware, in the previous paragraph, besides the installation of the cLK itself, the following actions occurred: in the internal memory of HD2, the configuration of the default sections was created and recovery was installed in the same section.
- Go to cLK: on the switched off device, hold down the "Back" button and briefly press the power button. After loading the cLK menu (cLK 1.5.1.6 appears in the upper left corner), you can release the back button.
- Use the volume buttons to select "INFO".
- Click the "Call" button, a submenu with information will open.
- Select the "PRINT PARTITION TABLE" item, the device displays information about existing sections in the HD2 internal memory.
- If this configuration is suitable for the chosen firmware and suits you, then go to step 4.
- If the size of the sections you want to change, then press the "Home" button, select "SETTINGS" ->"RESIZE PARTITIONS".
In the menu that opens, select the section whose size you want to change. A menu will open.when you select each item size change occurs in the section corresponding to the number of megabytes. Another pressing of a few items, change the partition size to the desired value. Remember that if you increase the size of a section at the N MB, total size of the other sections should be at the N MB decrease. The size of one of the sections can be set samovychislyaemym, reducing its size to 0. The size of such a section is automatically calculated based on the available memory and the total volume of the remaining sections.
When you finish configuring the partition configuration, select "COMMIT CHANGES". A table with the sizes of the sections will appear on the communicator screen, make sure that the selected configuration is correct.
- Select the item "APPLY" - to apply, in two seconds the memory will be redistributed and the main menu cLK will open.
- If you want to change the order of sections, use the menu REARRANGE PARTITIONS
- If you need to delete or create a partition, change the order of partitions, reinstall recovery, this can be easily done using a computer using a script
CLKScript_v8.1.exe(1.72 MB)
If this is not required, go to step 4.
P.4. Preparing a memory card and copying the firmware installation file there
- If required, create a partition on the ext memory card (20 point inFAQ), for some firmware this item is mandatory.
- Delete all files and folders remaining from the previous firmware on the memory card. User data can be left.
- Copy the installation zip with the firmware to the memory card without unzipping it. This can be done either through a card reader (card reader), by pulling out a memory card, or through CWM recovery.P.5. Installing firmware
- A memory card must be inserted in the communicator.
- On the memory card must be an installation zip firmware.
- If the communicator is not in the CWM recovery menu, then you need to go there: on the switched off device, hold down the "Home" button and briefly press the power button.
- Select itemwipe data / factory reset.
- Run wipe.
- After the end of the operation. Select iteminstall zip from sdcard ->choose zip from sdcard ->select * .zip (file with the firmware you need).
- Press the “back” button to return to the CWM recovery main menu.
- select itemreboot system now.
- The communicator will reboot and within 5-10 minutes will load Android.
- After the first start it is recommended to reboot the system.
Differences between cLK and MAGLDR:
- Allows you to charge the device in the off state. The smartphone is activated with the call accept button. In addition, it allows you to change the battery voltage threshold when charging in the off state.
- Loader menu is not displayed at boot (reboot HD2). No running lines (logs) at boot.
- Supports reboot into recovery mode, allows you to go directly from the switched off device to CWM recovery.
- Supports reboot into bootloader mode
For these advantages, CLK firmwares are called natural (native), i.e. Android works like on real Android devices.
- The structure of the zip firmware is different. Therefore, adapted for cLK firmware versions are required. zip'y for replacing the kernels also require special versions for cLK (since zip for CWM recovery in the case of the cLK bootloader does not contain the boot partition as a folder, but as an image). All other fixes and patches can be installed from MAGLDR.
- Supports only internet connection using ppp protocol. MAGLDR, in addition, supports a newer way - the rmnet protocol.
- At the moment, the Internet with the cLK loader is less stable for some users.
- Allows in most cases to do with the firmware without connecting to a computer. In the loader menu there is a built-in function for resizing logical partitions on the built-in storage device and their order.
- Has a means of checking the damaged blocks of the built-in flash drive.
- Has open source and everyone can improve this bootloader. Due to this, unlike MAGLDR, the CLK loader is regularly updated and at the same time its development does not depend on the DFT development team.
- Supports SysAlarm alarm, which is triggered when HD2 is off.
- cLK reads the CID, IMEI, MAC address of Bluetooth and the MAC address of the Wi-Fi device (getting the MAC address of Wi-Fi does not work correctly)
- In the cLK bootloader, the ability to connect to a PC in fastboot mode is implemented. But there is no possibility of connecting to a PC to use the DFT flasher from DAF.
- The cLK loader can be updated (flashed) not only through the mattress (from a computer or a memory card), but also via fastboot (it needs to be flashed with cLK), via recovery or from Android.
- Does not know how to work with a memory card (there are no drivers for FAT32), therefore Android’s standard assemblies for MAGLDR for a memory card will not work. The kernel (zImage) and initrd.gz should be flashed into the built-in drive, in the "sboot" section.
- In the CLK, there are no MAGLDR functions such as the launch of WPh7, the function of connecting to a PC in removable disk mode and tetris. CLK also does not allow installing the so-called DAF firmware (which is now almost gone), although experienced users can find in our FAQ’s instructions for converting DAF to zip and zip-MAGLDR to zip-cLK.
At the same time recovery (CWM, TWRP) that for cLK, that for MAGLDR is used the same and work with it is no different.
When installing cLK firmware, it should be taken into account that the partitioning of the built-in HD2 drive into logical partitions, i.e. Creating a system (system), boot (boot), cache (cache) and other sections occurs after cLK firmware and regardless of recovery. Because in cLK, you can change the order of partitions and their sizes without reinstalling recovery.
The CLM recovery version of stable version 5.0.2.6 with touch control support (Touch Beta 8 RC1) is already built into the installation file cLK, there is also a version cLK with TWRP recovery v2.2.2.0. This allows you to install Android firmware even to those users who have a broken USB port (only if the modified SPL is already flashed), because the recovery is installed with the cLK from the memory card in the mattress mode.
CLK loader management .
To access the menus on cLK off your device, hold "Back" button and briefly press the power key. To download Android'a assembly memory card, hold down the "menu" (windows) when you turn on the device. To enter the CWM recovery on the unit is turned off, hold down the "Home" and briefly press the power button. Connects to your PC in fastboot mode, open the main boot menu cLK and connect the USB cable. In cLK management boot menu is similar MAGLDR the following buttons:
- volume control buttons perform the navigation function;
- The "Call" key is responsible for selecting the item;
- the "Windows" key duplicates the "call" key (for those whose button is broken);
- key "Back" returns to the previous menu;
- key "Home" returns to the main menu.
Menu structure
Kernel @ boot [NAND]- downloads Android’s firmware
RECOVERY- downloads recovery
FLASHLIGHT- turns on the flash diodes (turn off by pressing the "back" key)
SETTINGS- opens the cLK bootloader settings menu
REBOOT cLK- reboot of the cLK loader, differs from the previous point in that after switching on, the cLK will load again
Powerdown- turns off HD2
RECOVERY- downloads recovery
FLASHLIGHT- turns on the flash diodes (turn off by pressing the "back" key)
SETTINGS- opens the cLK bootloader settings menu
- RESIZE PARTITIONS- menu in which resizing of sections is performed
- lk
recovery
boot
misc
system
userdata
cache
PRINT PARTITION TABLE- display the created partition table
COMMIT CHANGES- accept changes
- APPLY- to apply, in two seconds the memory will be redistributed and the main menu will open
- CANCEL- cancel
- lk
recovery
misc
boot
system
userdata
cache
PRINT PARTITION TABLE- display the created partition table
- COMMIT CHANGES- accept changes
- APPLY- to apply, in two seconds the memory will be redistributed and the main menu will open
CANCEL- cancel
SHOW STARTUP INFO- show information when loading cLK
SHOW MULTIBOOT MENU- show multiboot menu
SET DEFAULT KERNEL- set the default kernel
SET DEFAULT SCREEN BRIGHTNESS- set the screen brightness
SET DEFAULT UDC SETTINGS
SET DEFAULT OFF-MODE CHARGING- set the charging mode to off
SET DEFAULT CHARGING VOLTAGE THRESHOLD- set the charging threshold
SET DEFAULT CPU FREQ- set the frequency of the CPU in the bootloader
ENABLE ExtROMorDISABLE ExtROM- enable or disable backup 24 MB. When enabled, the automatic change of partitions occurs so that the cache partition becomes the last and 24 MB is allocated for it. When you turn off from use, the backup area of ​​the drive (24 MB) is displayed.
ENABLE FILLING BBT @ STARTUP- enable filling the table of bad-blocks when loading cLK (necessary for performing PRINT BAD BLOCK TABLE)
INVERT SCREEN COLORS- inverts the colors on the screen
FORMAT NAND- formats sections misc, boot, system, userdata, cache
RESET SETTINGS- reset the settings to the default state
- PRINT PARTITION TABLE- shows the logical partition table on the HD2 built-in storage device
PRINT BAD BLOCK TABLE- displays a table of damaged flash drive blocks (for this you need to enable FILLING BBT in the SETTINGS section)
PRINT NAND INFO- shows information about the built-in drive
CREDITS- thanks to the developers
HELP- displays a list of commands for fastboot with explanations
REBOOT cLK- reboot of the cLK loader, differs from the previous point in that after switching on, the cLK will load again
Powerdown- turns off HD2
How to run an Android assembly for a memory card
- Find the firmware you want to run from the memory card, it should be for the MAGLDR bootloader
- zip'a system folder with firmware renamed to "Android" and placed in the root of the memory card
- Files "zImage" and "initrd.gz" from zip with firmware put in the root of drive C
- Open a command prompt and run the command
cd C: / " - on the communicator, download the cLK main menu, connect to the PC and execute the command (the easiest way to do this is through a script)
fastboot -c "rel_path = Android nand_boot = 0" -b 0x11800000 flash: raw sboot zImage initrd.gz - turn off HD2
- Hold down the "menu" button (windows) and briefly press the power button
Commands to control cLK via fastboot (from PC) can be viewedhere. As well as the users of our forum have written a program with a friendly interface, which, without knowing the commands for fastboot and generally understanding what it is, makes it easy to control the bootloader from a PC. Further, in order to distinguish it from others, this program will be called a script.
Description of the script to work with cLK
Script - a program for PC (for Windows), designed to work with the loader CLK, when connected to a PC in fastboot mode. To do this, just go to the main menu cLK and connect the USB cable to the PC. For the computer to correctly detect the device, it is required to install the driver for USB from the Google of the Android SDK. Then, when you connect in fastboot mode, the HD2 will be defined as "Android". For the script any other additions except the driver is not required. The script laid out its developer (xGetsx ) in the next message HTC HD2 - Android NAND + MAGLDR (Post # 9719867) . The original author of the script is ~ Nops ~ . The latest version of the script is 8.1 (released April 10, 2012), the author’s file is originally called CLKScript_125_.exe. The script is old, with the latest versions of cLK works correctly, but does not support all commands.
This script allows you to perform the following operations:
- creation (in arbitrary order), deletion and resizing of android-partitions on the built-in storage device;
- firmware recovery (any of the available);
- cleaning the built-in drive;
- reboot the device;
- execute arbitrary commands for fastboot.
In this material, only the tab "Working with sections" and "Other" will be considered, since They allow you to perform all the manipulations required for firmware. The remaining 2 tabs allow you to download the necessary files that are better to download from the forum, because here they are always the latest version.
The screenshot shows that the script is launched using the file "CLKScript_v8.1.exe". In order for the script to flash recovery, the image must be called "recovery.img" and be in the same folder as the CLKScript_v8.1.exe file, although the latest version of the script allows you to choose which particular recovery image you need to flash and where it is located.
Paragraphs 2-6 in "Working with sections" tab allows you to set the configuration partition. The "Show partition information" displays the current configuration of the smartphone after setting it is necessary to select "confirm changes", then your smartphone will restart and boot loader to create internal storage configuration you have selected. When manipulating with sections in the cLK reboot is not required, but the script is designed for older versions, so there is still a reboot occurs. When you specify the partition size - 0, its size is automatically calculated (based on the available storage volume and volume nezadeystvovannoogo under other sections), this section should only be one.
The item "Create partitions by default" creates the following configuration:
misc = 1 MB
recovery = 5 MB
boot = 5 MB
sboot = 5 MB
system = 150 MB
cache = 10 MB
userdata = the size of this section is calculated automatically, based on the amount of available memory and the total volume of the previous sections.
Sections on the drive are arranged in the same order as in the list.
 |
This script allows you to perform the following operations:
- creation (in arbitrary order), deletion and resizing of android-partitions on the built-in storage device;
- firmware recovery (any of the available);
- cleaning the built-in drive;
- reboot the device;
- execute arbitrary commands for fastboot.
In this material, only the tab "Working with sections" and "Other" will be considered, since They allow you to perform all the manipulations required for firmware. The remaining 2 tabs allow you to download the necessary files that are better to download from the forum, because here they are always the latest version.
The screenshot shows that the script is launched using the file "CLKScript_v8.1.exe". In order for the script to flash recovery, the image must be called "recovery.img" and be in the same folder as the CLKScript_v8.1.exe file, although the latest version of the script allows you to choose which particular recovery image you need to flash and where it is located.
Paragraphs 2-6 in "Working with sections" tab allows you to set the configuration partition. The "Show partition information" displays the current configuration of the smartphone after setting it is necessary to select "confirm changes", then your smartphone will restart and boot loader to create internal storage configuration you have selected. When manipulating with sections in the cLK reboot is not required, but the script is designed for older versions, so there is still a reboot occurs. When you specify the partition size - 0, its size is automatically calculated (based on the available storage volume and volume nezadeystvovannoogo under other sections), this section should only be one.
The item "Create partitions by default" creates the following configuration:
misc = 1 MB
recovery = 5 MB
boot = 5 MB
sboot = 5 MB
system = 150 MB
cache = 10 MB
userdata = the size of this section is calculated automatically, based on the amount of available memory and the total volume of the previous sections.
Sections on the drive are arranged in the same order as in the list.
Instructions for installing the firmware on the cLK bootloader
For inexperienced users should first understand the process of setting MAGLDR firmware and then install CLK. Below method involves installing a clean firmware from the old firmware no data and tails are left. The instructions given to the links and to CWM recovery, and on the TWRP, but the instructions are for the use of CWM, as the most widespread. Before using this manual read it all. Perform each item, keep in mind the following.
Required installation requirements for cLK firmware:
- A modified boot loader version 2.08.HSPL or 3.03.HSPL must be flashed. Check it out. Why go to the SPL loader ("mattress"): on the switched off communicator, hold down the volume down key and briefly press the power button. After the color bars appear on the screen, the volume down button can be released. The inscription "SPL-2.08.HSPL" or "SPL-3.03.HSPL" should be present in the upper mattress strip.
- Firmware versionradio modulemust be 2.10 or higher.
P.1. Downloading firmware and determining the parameters required to install it.
- We are determined with the firmware in the section "Firmware "of this message. There are also voting results. Downloading the firmware of interest to the PC; mini dictionary .
- Make sure that you downloaded exactly the version for the CLK loader. If the author releases a separate version for cLK, then the firmware will go in a zip-file, which, among other things, contains the file "boot.img". If the author releases the cLK firmware in the form of a patch, then you must first install a zip for MAGLDR, and then install the patch to the cLK version. Here in the patch will be the same "boot.img". For details, see the description of each firmware in our firmware catalog, as well as in the themes of the authors of the firmware.
- We determine the size of the partitions that will need to be created in the internal HD2 memory before installing the Android firmware.
What sections are needed for the firmware and how to choose their size
Any Android zip firmware for HD2 (and not only for HD2) requires that 6 sections be created in the internal memory of the device before installing it:
пїЅ misc (other) - a service partition used by CWM recovery during zip installation. For all firmware it is necessary to choose equal to 1 MB.
пїЅ boot - boot partition. It installs the kernel of the Android operating system (zImage) and initrd.gz. For all firmware this section is required to create a size of 5 MB. Its size is calculated based on the size of the core plus 1-2 MB. Remember that if you change the kernel to a non-standard, it may not be installed due to the fact that the partition is too small. But in any case, creating a boot partition of more than 10 MB does not make sense.
пїЅ recovery - section where recovery is installed. Its size is calculated based on the size of the recovery.img image. Because if all currently existing recovery versions do not exceed five megabytes, then this section should be set to 5 MB for any firmware.
пїЅ system (system) - the partition into which the main part of the firmware is copied, directly Android OS. In order to determine the size of this section, unpack the archive with the firmware. Weigh the system folder. The size of the section of the same name should be 5-10 MB larger.
пїЅ cache (Cache) - the partition for the temporary files is used exclusively to speed up the system. Section is used by some programs Market'om and Android, as well as a number of other tasks. Its size can vary 2-50 MB. But for most of the firmware you need to install its size to 5 MB. In fact, the cache partition is not required, and depending on its configuration, the system can not create (which is not recommended for inexperienced users). In this case, the cache will be written directly to the section of data in the cache directory. But it does not know where it may lead.
� data (or userdata) - user data section. Its size determines the amount of available internal memory that Android will show. This section installs all applications (if the installation location is “internal memory”), data, and system settings. If the sizes of all other sections are already set, then the size of the data section can be calculated automatically. To do this, when specifying the volume of the section, you must specify "0".
From the stated material it follows that the sizes of the misc, boot and recovery sections are the same for all firmware. The sizes of the remaining sections should be calculated according to the specified recommendations.
Also, the required section sizes are partially or fully indicated by some authors of the firmware (see their topics), and you can also see ourfirmware directory.
To install Android on the cLK bootloader, as well as on the MAGLDR bootloader, the user has 420 MB of internal flash memory. When creating partitions, you need to focus on this figure. When using backup 24 MB of memory (initially they are not involved), 444 MB will be available for all 6 sections.
When flashing the cLK itself in the internal HD2 memory, the following partition configuration is created
пїЅ misc (other) - a service partition used by CWM recovery during zip installation. For all firmware it is necessary to choose equal to 1 MB.
пїЅ boot - boot partition. It installs the kernel of the Android operating system (zImage) and initrd.gz. For all firmware this section is required to create a size of 5 MB. Its size is calculated based on the size of the core plus 1-2 MB. Remember that if you change the kernel to a non-standard, it may not be installed due to the fact that the partition is too small. But in any case, creating a boot partition of more than 10 MB does not make sense.
пїЅ recovery - section where recovery is installed. Its size is calculated based on the size of the recovery.img image. Because if all currently existing recovery versions do not exceed five megabytes, then this section should be set to 5 MB for any firmware.
пїЅ system (system) - the partition into which the main part of the firmware is copied, directly Android OS. In order to determine the size of this section, unpack the archive with the firmware. Weigh the system folder. The size of the section of the same name should be 5-10 MB larger.
пїЅ cache (Cache) - the partition for the temporary files is used exclusively to speed up the system. Section is used by some programs Market'om and Android, as well as a number of other tasks. Its size can vary 2-50 MB. But for most of the firmware you need to install its size to 5 MB. In fact, the cache partition is not required, and depending on its configuration, the system can not create (which is not recommended for inexperienced users). In this case, the cache will be written directly to the section of data in the cache directory. But it does not know where it may lead.
� data (or userdata) - user data section. Its size determines the amount of available internal memory that Android will show. This section installs all applications (if the installation location is “internal memory”), data, and system settings. If the sizes of all other sections are already set, then the size of the data section can be calculated automatically. To do this, when specifying the volume of the section, you must specify "0".
From the stated material it follows that the sizes of the misc, boot and recovery sections are the same for all firmware. The sizes of the remaining sections should be calculated according to the specified recommendations.
Also, the required section sizes are partially or fully indicated by some authors of the firmware (see their topics), and you can also see ourfirmware directory.
To install Android on the cLK bootloader, as well as on the MAGLDR bootloader, the user has 420 MB of internal flash memory. When creating partitions, you need to focus on this figure. When using backup 24 MB of memory (initially they are not involved), 444 MB will be available for all 6 sections.
When flashing the cLK itself in the internal HD2 memory, the following partition configuration is created
recovery = 6 MB
boot = 5 MB
misc = 1 MB
system = 150 MB
userdata = 0 (partition size is calculated automatically)
cache = 5 MB
boot = 5 MB
misc = 1 MB
system = 150 MB
userdata = 0 (partition size is calculated automatically)
cache = 5 MB
A.2. Install additional boot loader cLK and recovery
Instructions for firmware cLK
Method number 1 . Firmware from a computer, without the need for a memory card
- Download to PCLeoAdvancedRUU.exe- custom flasher.
- Download the archive with the installation file CLK loader of the required version onto your PC:
cLK v1.5.1.6 with integrated CWM recovery
black_lk_20121123-TouchRec_b8.7z(4.36 MB)cLK v1.5.1.6 with integrated TWRP recovery
black_lk_20121123-TWRP_b2_2_2_0.7z(4.53 MB)- Create the XXX folder on the PC and copy the file "LeoAdvancedRUU.exe" and the file "LEOIMG.nbh" from the archive "black_lk_20121123-TouchRec_b8.7z" into it.
- Go to the SPL loader ("mattress"): on the switched off device, hold down the volume down key and briefly press the power button. After the color bars appear on the screen, the volume down button can be released.
- We connect the smartphone to the PC with a USB cable.
- The inscription "USB" will appear in the lower strip of the mattress. If the inscription did not appear (the PC did not detect HD2, the drivers were not automatically installed), then install the following driver on the PC manually (through the device manager)USB drivers. This is a driver from the Windows Mobile Device Center for Windows 7 or from Microsoft ActiveSync for Windows XP. The driver is installed with the program.
- After the inscription has appeared, we run on the computer "LeoAdvancedRUU.exe" from the XXX folder.
- In the window that opens, change the language to Russian, select the item "Regular RUU" and click the "Next" button.
- The installer will open, follow the instructions on the PC screen.
Method number 2 . Firmware from memory card, without PC
- Download the archive with the installation file CLK loader of the required version onto your PC:
cLK v1.5.1.6 with integrated CWM recovery
black_lk_20121123-TouchRec_b8.7z(4.36 MB)cLK v1.5.1.6 with integrated TWRP recovery
black_lk_20121123-TWRP_b2_2_2_0.7z(4.53 MB)- Copy the file "LEOIMG.nbh" from the archive "black_lk_20121123-TouchRec_b8.7z" to the root of the memory card.
- Make sure that in the root of the memory card there are no other files with the extension .nbh.
- Turn off HD2 and insert a memory card into it.
- Go to the SPL loader (mattress): on the device completely turned off, hold down the volume down button and briefly press the power button.
- After a few seconds, SPL will automatically detect the file and offer to install it.
If SPL does not offer to install the file (after the appearance of color bars, the process stops) or the installation fails, try again to copy the file "LEOIMG.nbh" to the memory card, making sure that the operation was successful. Try to format the memory card. The same file may not be flashed from a large memory card. If cLK still fails to flash, try this procedure using a PC.
P.3. Splitting HD2 Internal Memory into Android Sections
With the cLK firmware, in the previous paragraph, besides the installation of the cLK itself, the following actions occurred: in the internal memory of HD2, the configuration of the default sections was created and recovery was installed in the same section.
- Go to cLK: on the switched off device, hold down the "Back" button and briefly press the power button. After loading the cLK menu (cLK 1.5.1.6 appears in the upper left corner), you can release the back button.
- Use the volume buttons to select "INFO".
- Click the "Call" button, a submenu with information will open.
- Select the "PRINT PARTITION TABLE" item, the device displays information about existing sections in the HD2 internal memory.
- If this configuration is suitable for the chosen firmware and suits you, then go to step 4.
- If the size of the sections you want to change, then press the "Home" button, select "SETTINGS" ->"RESIZE PARTITIONS".
In the menu that opens, select the section whose size you want to change. A menu will open.
+25
+10
+5
+1
-1
-5
-10
-25
+10
+5
+1
-1
-5
-10
-25
When you finish configuring the partition configuration, select "COMMIT CHANGES". A table with the sizes of the sections will appear on the communicator screen, make sure that the selected configuration is correct.
- Select the item "APPLY" - to apply, in two seconds the memory will be redistributed and the main menu cLK will open.
- If you want to change the order of sections, use the menu REARRANGE PARTITIONS
- If you need to delete or create a partition, change the order of partitions, reinstall recovery, this can be easily done using a computer using a script
CLKScript_v8.1.exe(1.72 MB)If this is not required, go to step 4.
Work with partitions and firmware recovery using a script
- Open the main menu of the CLK loader.
- Connect your device to a PC with a USB cable.
- Download a stable version of ClockworkMod recovery 5.0.2.6 -recovery.img(4.12 MB)
- Place the file "recovery.img" next to the script "CLKScript_v8.1.exe".
- On the PC, run the file "CLKScript_v8.1.exe".
- In the program window that opens, select the "Work with sections" tab.
- Select the item "Show information about partitions" and press the "OK" key at the bottom of the window.
- If the partition information in the HD2 internal memory is displayed on the communicator screen, then the driver needed for the program is installed automatically. If the communicator does not respond to the commands sent by the program, then you need to install the driver on the PC. Download the archiveGoogle Driver r4.zipand unpack it. This is the Google driver for USB from the Android SDK (in everyday life is called the ADB driver). The archive version 2 for the 32-bit and 64-bit versions of Windows. Install the driver through the device manager from the "Google_Driver_r4" folder, the system will automatically detect the driver and select the correct version. Download the latest driver, as well as learn more atofficial website.
- After installing the driver, select the "Show partition information" item again and press the "OK" key from the bottom of the window.
- If the display of the device displays information about the sections in the internal memory of HD2, then you can start working with sections. In the appropriate tab, create the desired partition configuration. Then select "Approve changes" and press the "OK" key.
- If the communicator does not restart automatically, restart it manually.
- After the reboot, the partition configuration you specified is created in the internal memory.
- When you change the order of partitions, as well as when you delete the recovery partition, recovery is deleted, which is installed with cLK. If this happens, install recovery again. To do this, go to the "Other" tab in the script, select the "Flash recovery" item and click the "OK" button. Next, select the file "recovery.img" and click the "open" button. After this, firmware recovery will occur.
- Connect your device to a PC with a USB cable.
- Download a stable version of ClockworkMod recovery 5.0.2.6 -
recovery.img(4.12 MB)- Place the file "recovery.img" next to the script "CLKScript_v8.1.exe".
- On the PC, run the file "CLKScript_v8.1.exe".
- In the program window that opens, select the "Work with sections" tab.
- Select the item "Show information about partitions" and press the "OK" key at the bottom of the window.
- If the partition information in the HD2 internal memory is displayed on the communicator screen, then the driver needed for the program is installed automatically. If the communicator does not respond to the commands sent by the program, then you need to install the driver on the PC. Download the archiveGoogle Driver r4.zipand unpack it. This is the Google driver for USB from the Android SDK (in everyday life is called the ADB driver). The archive version 2 for the 32-bit and 64-bit versions of Windows. Install the driver through the device manager from the "Google_Driver_r4" folder, the system will automatically detect the driver and select the correct version. Download the latest driver, as well as learn more atofficial website.
How to install driver on PC
When the device is connected to USB, the computer will detect the device, try to install the driver, in your case it could not find the driver
- go "start ->Control Panel ->device Manager";
- find there an unknown USB device;
- click on this device with the right mouse button and select "properties"
- open the "driver" tab in the opened dialog box and press the "update" button;
- another dialog box opens, in it choose "perform a search for drivers on this computer";
- another dialog box opens, in which you press the "browse" button and specify the folder where you have the driver, naturally you need to unpack the archive downloaded from the forum into a folder - this is what you need to specify in this item.
- go "start ->Control Panel ->device Manager";
- find there an unknown USB device;
- click on this device with the right mouse button and select "properties"
- open the "driver" tab in the opened dialog box and press the "update" button;
- another dialog box opens, in it choose "perform a search for drivers on this computer";
- another dialog box opens, in which you press the "browse" button and specify the folder where you have the driver, naturally you need to unpack the archive downloaded from the forum into a folder - this is what you need to specify in this item.
- After installing the driver, select the "Show partition information" item again and press the "OK" key from the bottom of the window.
- If the display of the device displays information about the sections in the internal memory of HD2, then you can start working with sections. In the appropriate tab, create the desired partition configuration. Then select "Approve changes" and press the "OK" key.
- If the communicator does not restart automatically, restart it manually.
- After the reboot, the partition configuration you specified is created in the internal memory.
- When you change the order of partitions, as well as when you delete the recovery partition, recovery is deleted, which is installed with cLK. If this happens, install recovery again. To do this, go to the "Other" tab in the script, select the "Flash recovery" item and click the "OK" button. Next, select the file "recovery.img" and click the "open" button. After this, firmware recovery will occur.
P.4. Preparing a memory card and copying the firmware installation file there
- If required, create a partition on the ext memory card (20 point inFAQ), for some firmware this item is mandatory.
- Delete all files and folders remaining from the previous firmware on the memory card. User data can be left.
- Copy the installation zip with the firmware to the memory card without unzipping it. This can be done either through a card reader (card reader), by pulling out a memory card, or through CWM recovery.
Copying files using CWM recovery
- In the CWM recovery menu, select ”mounts and storage”.
- In the opened submenu, select the item “mount USB storage”.
- If the USB cable is not connected, connect it to the PC.
- A removable disk will appear on the PC, if it does not appear, disconnect the USB cable and connect it again.
- Delete all files and folders remaining from the previous firmware. User data can be left.
- Copy the zip firmware to the memory card without unarchiving it.
- On the KVM screen, select the item “Unmount”.
- In the opened submenu, select the item “mount USB storage”.
- If the USB cable is not connected, connect it to the PC.
- A removable disk will appear on the PC, if it does not appear, disconnect the USB cable and connect it again.
- Delete all files and folders remaining from the previous firmware. User data can be left.
- Copy the zip firmware to the memory card without unarchiving it.
- On the KVM screen, select the item “Unmount”.
- A memory card must be inserted in the communicator.
- On the memory card must be an installation zip firmware.
- If the communicator is not in the CWM recovery menu, then you need to go there: on the switched off device, hold down the "Home" button and briefly press the power button.
- Select itemwipe data / factory reset.
- Run wipe.
- After the end of the operation. Select iteminstall zip from sdcard ->choose zip from sdcard ->select * .zip (file with the firmware you need).
- Press the “back” button to return to the CWM recovery main menu.
- select itemreboot system now.
- The communicator will reboot and within 5-10 minutes will load Android.
- After the first start it is recommended to reboot the system.
Firmware
A list of all Android firmware for HD2 (English site)
All firmwares that are suitable for regular HD2 (512 MB ROM) are also suitable for TMOUS (1024 MB ROM). Some firmware come in two versions: for TMOUS HD2 and for European HD2. Be careful when downloading the firmware.
Firmware catalogwith brief descriptions in our topic is divided into 3 parts (the most current firmware are marked in red):
Lightweight Android 2.3 firmware- firmware based on Google Nexus, CyanogenMod, MIUI
HTC Sense based firmware- firmware based on HTC Desire, Desire HD, Desire Z, Incredible S ROM
Android 2.3 based firmware with new Sense
Android 4.0 firmware
Not sure which firmware you are interested in? See what others use.
What is the axis on your LEO?
All firmwares that are suitable for regular HD2 (512 MB ROM) are also suitable for TMOUS (1024 MB ROM). Some firmware come in two versions: for TMOUS HD2 and for European HD2. Be careful when downloading the firmware.
Firmware catalogwith brief descriptions in our topic is divided into 3 parts (the most current firmware are marked in red):
Lightweight Android 2.3 firmware- firmware based on Google Nexus, CyanogenMod, MIUI
HTC Sense based firmware- firmware based on HTC Desire, Desire HD, Desire Z, Incredible S ROM
Android 2.3 based firmware with new Sense
Android 4.0 firmware
Not sure which firmware you are interested in? See what others use.
What is the axis on your LEO?
Results of previous surveys
Voting from April 22 to May 4, 2012
Voting from April 13 to April 22, 2012
Voting from November 22 to December 10, 2011
Voting from September 24 to October 4, 2011
Voting from September 23 to September 24, 2011
Voting from June 3 to July 12, 2011
Voting from June 27 to July 5, 2011
Voting from June 5 to June 12, 2011
 |
Voting from April 13 to April 22, 2012
 |
Voting from November 22 to December 10, 2011
 |
Voting from September 24 to October 4, 2011
 |
Voting from September 23 to September 24, 2011
 |
Voting from June 3 to July 12, 2011
 |
Voting from June 27 to July 5, 2011
 |
Voting from June 5 to June 12, 2011
 |
Kernels
Core - basic and mandatory part of any operating system. The main part of any firmware - an operating system, so the core part of any firmware. The operating system consists of a kernel, applications and drivers. Just like you can change drivers and applications, you can change the kernel to optimize the system. It affects the power consumption, performance and functionality of the firmware options. For example it is the core determines the maximum and minimum frequency of the processor. For HD2, there are several branches of the nuclei. Most of them are compatible with a variety of firmware. Therefore, empirically, you can pick up with your favorite firmware most optimal kernel. In most cases firmware author knows best what her work. The core of the current firmware can be replaced by another without changing other parts of the firmware, and without loss of data and system availability, but not always. Most often, you can replace the kernel installation zip'a through ClockworkMod recovery.
Not all kernels are compatible with all firmware. Check compatibility is possible only at random.
You can replace the core in the installed firmware in two ways, presented below. In this case, it is necessary to replace not only the kernel itself (the zImage file), but also the modules (drivers) going to it. When installing via CWM, the process is fully automated, you just need to install zip.
Under installation, kernel firmware, etc. understand the process of replacing the kernel in the firmware.
Before replacing the kernel, make a backup copy of the firmware via CWM recovery. How to do this read HERE . If, after replacing the kernel, the system stops loading, you can restore the data and operability of the device by restoring the backup.
Some kernels can always be downloaded from the following link.http://cyanogenmod.arif-ali.co.uk/kernels/
Not all kernels are compatible with all firmware. Check compatibility is possible only at random.
You can replace the core in the installed firmware in two ways, presented below. In this case, it is necessary to replace not only the kernel itself (the zImage file), but also the modules (drivers) going to it. When installing via CWM, the process is fully automated, you just need to install zip.
Under installation, kernel firmware, etc. understand the process of replacing the kernel in the firmware.
Before replacing the kernel, make a backup copy of the firmware via CWM recovery. How to do this read HERE . If, after replacing the kernel, the system stops loading, you can restore the data and operability of the device by restoring the backup.
Replacing the kernel with CWM recovery
If the kernel installation file is an archive of the * .zip format, inside which, among other things, is the folder "META-INF", then the replacement of the kernel is as follows.
Make sure that the installation zip is designed to install the kernel under the boot loader you are using (cLK, MAGLDR). Kernel installers manufactured since the second half of 2012 are universal, i.e. they themselves determine what you are using the bootloader and flash the correct version of the kernel.
- reset the installation zip to the memory card without unarchiving it;
- insert a memory card in HD2;
- enter MAGLDR: on the switched off device, hold down the power key and DO NOT release it until the menu appears;
- use the volume keys to select the item "AD recovery";
- press the call accept button, CWM recovery will be loaded;
- select "install zip from sdcard" ->"choose zip from sdcard" ->select * .zip (installation zip with the correct kernel);
- after the end of the firmware, return to the main menu of CWM recovery, select the item "reboot system now";
- the communicator will reboot and load your Android firmware with a new kernel.
- reset the installation zip to the memory card without unarchiving it;
- insert a memory card in HD2;
- go to CWM recovery: on the switched off device, hold down the "Home" button and briefly press the power button;
- select "install zip from sdcard" ->"choose zip from sdcard" ->select * .zip (installation zip with the correct kernel);
- after the end of the firmware, return to the main menu of CWM recovery, select the item "reboot system now";
- the communicator will reboot and load your Android firmware with a new kernel.
Make sure that the installation zip is designed to install the kernel under the boot loader you are using (cLK, MAGLDR). Kernel installers manufactured since the second half of 2012 are universal, i.e. they themselves determine what you are using the bootloader and flash the correct version of the kernel.
Instructions for users of the MAGLDR loader
- reset the installation zip to the memory card without unarchiving it;
- insert a memory card in HD2;
- enter MAGLDR: on the switched off device, hold down the power key and DO NOT release it until the menu appears;
- use the volume keys to select the item "AD recovery";
- press the call accept button, CWM recovery will be loaded;
- select "install zip from sdcard" ->"choose zip from sdcard" ->select * .zip (installation zip with the correct kernel);
- after the end of the firmware, return to the main menu of CWM recovery, select the item "reboot system now";
- the communicator will reboot and load your Android firmware with a new kernel.
Instructions for users of the CLK loader
- reset the installation zip to the memory card without unarchiving it;
- insert a memory card in HD2;
- go to CWM recovery: on the switched off device, hold down the "Home" button and briefly press the power button;
- select "install zip from sdcard" ->"choose zip from sdcard" ->select * .zip (installation zip with the correct kernel);
- after the end of the firmware, return to the main menu of CWM recovery, select the item "reboot system now";
- the communicator will reboot and load your Android firmware with a new kernel.
Replacing the kernel with a PC - AutoCorrect
- Turn on the device and download Android;
- enable USB debugging: Settings ->Applications ->Development ->put a checkmark in front of the item "Debug USB";
- connect your device to a PC with a USB cable;
- unzip the archive with the kernel and run INSTALL.bat;
- Wait for the automatic restart of the communicator.
If the kernel is not installed, write "device not found", - install the driverHTC Driver. Install manually through the device manager.
- enable USB debugging: Settings ->Applications ->Development ->put a checkmark in front of the item "Debug USB";
- connect your device to a PC with a USB cable;
- unzip the archive with the kernel and run INSTALL.bat;
- Wait for the automatic restart of the communicator.
If the kernel is not installed, write "device not found", - install the driverHTC Driver. Install manually through the device manager.
The list of cores for HD2
Some kernels can always be downloaded from the following link.http://cyanogenmod.arif-ali.co.uk/kernels/
Kernels fromTytung
Author's topic on xda-developers
automatic frequency scaling mode by default - Interactive, the operating frequencies of the CPU Default: 245-998 MHz. Available Frequency: 128-1190 MHz. Working voltage processor: 800-1350 mV (voltage change supported interface). Built correction for fast spill screen. Integrated correction that improves the sound during a conversation (eliminates the high sensitivity microphone and "hands-free" mode). Full support cLK loader. Recording telephone conversations with the line. T-Mobile Wi-Fi Calling. Distribution of the Internet by USB, Wi-Fi access point. Real MAC-address of the Wi-Fi. Unique MAC-address for each HD2. Real (unique) MAC-address for each Bluetooth HD2. Support for high-capacity batteries official (HTC 2300 mA / h). Supported file system: Yaffs, Ext2 / 3/4, CIFS, NILFS, ReiserFS, BTRFS. Enabled sound driver ALSA. Quick charge and other
[23.11.12] Update for Android 2.3. Added fix for working with the alarm application, triggered from the off state. Universal installer (MAGLDR, cLK):tytung_gb_r16_with_off_alarm.zip(3.21 MB)
[08.11.12] Update for Android 2.3. Kernels for Android 4 look in the relevant topic. Universal installer:HTCLEO-Kernel_2.6.32_tytung_gb_r16-update.zip(3.21 MB)
The following automatic processor frequency scaling modes have been added: InteractiveX and Smartass2; added real MAC addresses for Bluetooth and Wi-Fi; fast charge; and other.
[15.01.12] Update for ICS only (Android 4). Version for loader cLK2.6.32.15_tytung_ics_r1_cLK.zip, version for bootloader MAGLDR -2.6.32.15_tytung_ics_r1_MAGLDR.zip[10.11.11] The correction of step gradients is enabled. R14 versionfor loader MAGLDR, for the MAGLDR loader with recording from tel. talk; for cLK bootloader, for the cLK bootloader with tel. talk.
[05.11.11] Added driver calibration auto white balance. To improve the sound quality of music added audio driver ALSA. The version with the recording of telephone conversations is returned (it can cause a complete loss of sound until the next reboot). Version r13for loader MAGLDR, for cLK bootloader
[30.09.11] version r12.3 is released only for Android 2.3.4 and higher. The audio driver (libaudio.so) fromdrizztje Up to version 5, as well as line recording is off . Version for bootloader MAGLDR - kernel_tytung_r12.3_update.zip , version for boot loader cLK - cLK_ppp_tytung_r12.3_update.zip
[12.09.11] For Android 2.3 Gignerbread:kernel_tytung_r12- version for bootloader MAGLDR;cLK_ppp_tytung_r12- version for loader cLK.
For Android 2.2 FroYo:kernel_tytung_r12_oldcam- version for bootloader MAGLDR;cLK_ppp_tytung_r12_oldcam- version for loader cLK.
[08.22.11] For Android 2.3 Gignerbread:kernel_tytung_r11- version for bootloader MAGLDR;cLK_ppp_tytung_r11- version for loader cLK.
For Android 2.2 FroYo:kernel_tytung_r11_oldcam- version for bootloader MAGLDR;cLK_ppp_tytung_r11_oldcam- version for loader cLK.
[4.05.11] Versions for the MAGLDR bootloader:kernel_tytung_r10_oldcam_update.zip- for Sense firmware,kernel_tytung_r10_update.zip- Only for firmware based on Android 2.3.4. Versions for the cLK bootloader:cLK_ppp_tytung_r10_oldcam_update.zip- for Sense firmware,cLK_ppp_tytung_r10_update.zip- Only for firmware based on Android 2.3.4.
[12.04.11] Versions for the CLK bootloader (with the new PPP driver):cLK ppp tytung r9 oldcam, clk ppp tytung r9. Versions for MAGLDR:kernel tytung r9 oldcam, kernel tytung r9[27.03.11] r8.3_oldcam_update.zip + r8.3_update.zip- updated bluetooth stack and returned old video recording driver
[25.03.11] r8.2_oldcam_update.zip + r8.2_update.zip- fixed a high power consumption bug after turning on bluetooth
[24.03.11] r8.1_oldcam_update.zip + r8.1_update.zip
automatic frequency scaling mode by default - Interactive, the operating frequencies of the CPU Default: 245-998 MHz. Available Frequency: 128-1190 MHz. Working voltage processor: 800-1350 mV (voltage change supported interface). Built correction for fast spill screen. Integrated correction that improves the sound during a conversation (eliminates the high sensitivity microphone and "hands-free" mode). Full support cLK loader. Recording telephone conversations with the line. T-Mobile Wi-Fi Calling. Distribution of the Internet by USB, Wi-Fi access point. Real MAC-address of the Wi-Fi. Unique MAC-address for each HD2. Real (unique) MAC-address for each Bluetooth HD2. Support for high-capacity batteries official (HTC 2300 mA / h). Supported file system: Yaffs, Ext2 / 3/4, CIFS, NILFS, ReiserFS, BTRFS. Enabled sound driver ALSA. Quick charge and other
[23.11.12] Update for Android 2.3. Added fix for working with the alarm application, triggered from the off state. Universal installer (MAGLDR, cLK):
tytung_gb_r16_with_off_alarm.zip(3.21 MB)[08.11.12] Update for Android 2.3. Kernels for Android 4 look in the relevant topic. Universal installer:
HTCLEO-Kernel_2.6.32_tytung_gb_r16-update.zip(3.21 MB)The following automatic processor frequency scaling modes have been added: InteractiveX and Smartass2; added real MAC addresses for Bluetooth and Wi-Fi; fast charge; and other.
[15.01.12] Update for ICS only (Android 4). Version for loader cLK2.6.32.15_tytung_ics_r1_cLK.zip, version for bootloader MAGLDR -2.6.32.15_tytung_ics_r1_MAGLDR.zip
List of major changes since r14
- included a fix that allows the wired headset to work on the ICS
- the value of the VM_MAX_READAHEAD parameter is changed to 1024 kilobits
- ported xt_qtaguid and xt_quota2 (allows you to correct the error with the standard traffic calculation tool)
- Wi-Fi driver ported from 3.x Linux kernel (bcm4329)
- improved flash compatibility with ICS
- Added automatic scaling of the frequency of the CPU InteractiveX and smartAssV2
- video accelerator driver (kgsl) is ported from msm-3.0 Linux kernel
- almost 2 times increased data transfer rate of the memory card
- the value of the VM_MAX_READAHEAD parameter is changed to 1024 kilobits
- ported xt_qtaguid and xt_quota2 (allows you to correct the error with the standard traffic calculation tool)
- Wi-Fi driver ported from 3.x Linux kernel (bcm4329)
- improved flash compatibility with ICS
- Added automatic scaling of the frequency of the CPU InteractiveX and smartAssV2
- video accelerator driver (kgsl) is ported from msm-3.0 Linux kernel
- almost 2 times increased data transfer rate of the memory card
[05.11.11] Added driver calibration auto white balance. To improve the sound quality of music added audio driver ALSA. The version with the recording of telephone conversations is returned (it can cause a complete loss of sound until the next reboot). Version r13for loader MAGLDR, for cLK bootloader
[30.09.11] version r12.3 is released only for Android 2.3.4 and higher. The audio driver (libaudio.so) fromdrizztje Up to version 5, as well as line recording is off . Version for bootloader MAGLDR - kernel_tytung_r12.3_update.zip , version for boot loader cLK - cLK_ppp_tytung_r12.3_update.zip
[12.09.11] For Android 2.3 Gignerbread:kernel_tytung_r12- version for bootloader MAGLDR;cLK_ppp_tytung_r12- version for loader cLK.
For Android 2.2 FroYo:kernel_tytung_r12_oldcam- version for bootloader MAGLDR;cLK_ppp_tytung_r12_oldcam- version for loader cLK.
[08.22.11] For Android 2.3 Gignerbread:kernel_tytung_r11- version for bootloader MAGLDR;cLK_ppp_tytung_r11- version for loader cLK.
For Android 2.2 FroYo:kernel_tytung_r11_oldcam- version for bootloader MAGLDR;cLK_ppp_tytung_r11_oldcam- version for loader cLK.
List of changes in the 11th version
- initrd.gz is now the same for cLK and MAGLDR (only for versions without the signature of oldcam)
- added RNDIS (Remote Network Driver Interface Specification) driver to support USB Tethering
- Added a fix that speeds up the screen waking (helps only those who had problems)
- Fixed the error that occurred when opening the camera
- changed MAC address to IEEE standard 00: 23: 76: XX: XX: XX for HTC
- added RNDIS (Remote Network Driver Interface Specification) driver to support USB Tethering
- Added a fix that speeds up the screen waking (helps only those who had problems)
- Fixed the error that occurred when opening the camera
- changed MAC address to IEEE standard 00: 23: 76: XX: XX: XX for HTC
[12.04.11] Versions for the CLK bootloader (with the new PPP driver):cLK ppp tytung r9 oldcam, clk ppp tytung r9. Versions for MAGLDR:kernel tytung r9 oldcam, kernel tytung r9
version 9 description
Only 4 kernel versions released. oldcam - means that the kernel is intended for firmware with the old camera driver, without this label - the kernel is intended for firmware with the new camera driver (sense). All versions support high capacity battery.
Features of the ninth version:
- when working with a bluetooth headset, the sound in the phone on both speakers may be muted, the problem is known, there is no solution yet, but the sound returns after a reboot
- support two-way recording of conversations
- support for a unique Bluetooth MAC address
- support Bluetooth PAN (Personal Area Network)
- used by the author-modified initrd.gz (modified init.htcleo.rc to support the unique Bluetooth MAC address)
- added sound enhancement (it seems that the sound quality during a call in the BT headset is better)
Features of the ninth version:
- when working with a bluetooth headset, the sound in the phone on both speakers may be muted, the problem is known, there is no solution yet, but the sound returns after a reboot
- support two-way recording of conversations
- support for a unique Bluetooth MAC address
- support Bluetooth PAN (Personal Area Network)
- used by the author-modified initrd.gz (modified init.htcleo.rc to support the unique Bluetooth MAC address)
- added sound enhancement (it seems that the sound quality during a call in the BT headset is better)
[25.03.11] r8.2_oldcam_update.zip + r8.2_update.zip- fixed a high power consumption bug after turning on bluetooth
[24.03.11] r8.1_oldcam_update.zip + r8.1_update.zip
Kernels fromseadersn
Author's topic on XDA-developers
The latest version was released November 18, 2011
for the cLK bootloader:
with recording telephone conversations from the lineR9 HD2 CLK CALLREC.zipwithout recordingR9 HD2 CLK STANDARD.zip
for MAGLDR bootloader:
with recording telephone conversations from the lineR9 HD2 MAGLDR CALLREC.zipwithout recordingR9 HD2 MAGLDR STANDARD.zip
The latest version was released November 18, 2011
for the cLK bootloader:
with recording telephone conversations from the lineR9 HD2 CLK CALLREC.zipwithout recordingR9 HD2 CLK STANDARD.zip
for MAGLDR bootloader:
with recording telephone conversations from the lineR9 HD2 MAGLDR CALLREC.zipwithout recordingR9 HD2 MAGLDR STANDARD.zip
Kernels fromfikret
Author's topic on XDA-developers
The kernel is compiled from the official sources of the 2.6.35.14 kernel from HTC Desire.
CPU available frequencies from 96 MHz to 1.5 GHz, Default CPU operating frequencies 245-998 MHz. automatic frequency scaling mode by default - ondemand (also available interactive, conservative, userspace, powersave, ondemand, performance, smartassV2, InteractiveX, Smartass, Smoothass, Savagedzen, Virtuous, Scary, Superbad, Lagfree, Skywalker, HYPER). Full support cLK loader. Unique MAC-address of the Wi-Fi and Bluetooth for each HD2. Support for high-capacity batteries official (HTC 2300 mA / h). Supported file system Yaffs, Ext2 / 3/4, CIFS, FUSE. Including patches for quick sifting screen. Audio driver ALSA (as additional modules). Support for Wi-Fi access point.
To change the working frequencies of the processor, the author does not recommend using the setCPU utility, instead it is suggestedВ® No-frills CPU Control.
[14.02.12] The kernel r2.16 (Linux kernel based 2.6.35.14) Versions for Android 2.3:cLK HD.zip, MAGLDR HD.zip; versions for Android 4.0cLK ICS.zip, MAGLDR ICS.zip
The kernel is compiled from the official sources of the 2.6.35.14 kernel from HTC Desire.
CPU available frequencies from 96 MHz to 1.5 GHz, Default CPU operating frequencies 245-998 MHz. automatic frequency scaling mode by default - ondemand (also available interactive, conservative, userspace, powersave, ondemand, performance, smartassV2, InteractiveX, Smartass, Smoothass, Savagedzen, Virtuous, Scary, Superbad, Lagfree, Skywalker, HYPER). Full support cLK loader. Unique MAC-address of the Wi-Fi and Bluetooth for each HD2. Support for high-capacity batteries official (HTC 2300 mA / h). Supported file system Yaffs, Ext2 / 3/4, CIFS, FUSE. Including patches for quick sifting screen. Audio driver ALSA (as additional modules). Support for Wi-Fi access point.
To change the working frequencies of the processor, the author does not recommend using the setCPU utility, instead it is suggestedВ® No-frills CPU Control.
[14.02.12] The kernel r2.16 (Linux kernel based 2.6.35.14) Versions for Android 2.3:cLK HD.zip, MAGLDR HD.zip; versions for Android 4.0cLK ICS.zip, MAGLDR ICS.zip
Kernels frommarc1706
Author's topic on XDA-developers . Kernel for Sense firmware. Based on HTC Desire kernel version 2.6.35.14
automatic frequency scaling mode by default - ondemand (also available interactive, conservative, userspace, powersave, ondemand, performance, smartassV2, Lagfree, Lazy, SavagedZen, scary, smartass, smoothass, superbad, virtuous, interactiveX, ondemandX). Operating frequencies default CPU: 245-998 MHz. Available Frequency: 96-1536 Mhz. Built correction for fast spill screen. Full support cLK loader. Recording telephone conversations with the line. Unique MAC-address of the Wi-Fi for each HD2. Unique MAC-address for each Bluetooth HD2. Support for high-capacity batteries official (HTC 2300 mA / h). Enabled sound driver ALSA. Driver integrated auto white balance from HTC.
[07.24.12] v0.2.3marc1706_desire_0_2_3.zip(3.94 MB)
[13.03.12] v0.2.0marc1706_desire_0_2_0.zip(3.94 MB)
automatic frequency scaling mode by default - ondemand (also available interactive, conservative, userspace, powersave, ondemand, performance, smartassV2, Lagfree, Lazy, SavagedZen, scary, smartass, smoothass, superbad, virtuous, interactiveX, ondemandX). Operating frequencies default CPU: 245-998 MHz. Available Frequency: 96-1536 Mhz. Built correction for fast spill screen. Full support cLK loader. Recording telephone conversations with the line. Unique MAC-address of the Wi-Fi for each HD2. Unique MAC-address for each Bluetooth HD2. Support for high-capacity batteries official (HTC 2300 mA / h). Enabled sound driver ALSA. Driver integrated auto white balance from HTC.
[07.24.12] v0.2.3
marc1706_desire_0_2_3.zip(3.94 MB)[13.03.12] v0.2.0
marc1706_desire_0_2_0.zip(3.94 MB)Kernels fromDorimanx
Author's topic on XDA-developers . The core is based on a kernel of Tytung for ICS. Version of the Linux kernel 2.6.32.59. Available frequency from the CPU 96 to 1612 MHz, Default CPU operating frequencies 245-998 MHz. Added several modes of automatic scaling of the CPU frequency, the default mode is enabled HYPER. Available change in voltage to the CPU via interface sysfs interface (as Titunga). Built correction for fast spill screen. Full support cLK loader. Recording telephone conversations with the line. T-Mobile Wi-Fi Calling. Distribution of the Internet by USB, Wi-Fi access point. Real MAC-address of the Wi-Fi. Unique MAC-address of the Wi-Fi for each HD2. Unique MAC-address for each Bluetooth HD2. Support for high-capacity batteries official (HTC 2300 mA / h). Supported file system: Yaffs2, Ext2 / 3/4, ReiserFS. Enabled sound driver ALSA. Included correction step gradients. And much more.
Frequent updates, but newer versions are not always stable. When installing a zip with a kernel, several different kernel options are offered, a description of the installation points can be foundHEREorHERE. The author releases the kernel in a single installation file. It is universal for all firmware, including bootloaders. When installing it, you need to select the desired version.
ALSA kernel driver is disabled by default -instructions for its inclusion.
The kernel is suitable for any firmware, but if you have Android 2.3.3 (or below), Sense, or HyperDROID, you should add the initrd.gz file from the installation zip of your firmware to the kernel installation zip, the "initrd Custom" folder.
The latest kernel versions can always be downloaded from the developer’s site.http://www.dorimanx.com/kernels/
[21.06.12] v7.3: Kernel for CM7 and ICS onlyKernel-Dorimanx-V7.3-ULTRA-HD2-MAG-CLK-MULTI.zip(9.02 MB)
[07.04.12] v6.4D:Kernel_Dorimanx_V6.4_ULTRA_HD2_MAG_CLK_MULTI.zip
[04/04/12] v6.4:Kernel_Dorimanx_V6.4_ULTRA_HD2_MAG_CLK_MULTI.zip
[03/29/12] v6.3:Kernel_Dorimanx_V6.3_ULTRA_HD2_MAG_CLK_MULTI.zip
[25.03.12] v6.2:Kernel_Dorimanx_V6.2_ULTRA_HD2_MAG_CLK_MULTI.zip
[13.03.12] v5.7:Kernel_Dorimanx_V5.7_ULTRA_HD2_MAG_CLK_MULTI.zip(7.18 MB)
[02.19.12] v4.7:Kernel_Dorimanx_V4.7_FOR_All_in_One_ROM_MAG_CLK.zip(5.29 MB)
[01.25.12] v3.9:Kernel_Dorimanx_V3.9_FOR_All_in_One_ROM_MAG_CLK.zip(5.59 MB)
[01/23/12] v3.8:Kernel_Dorimanx_V3.8_FOR_All_in_One_ROM_MAG_CLK.zip(5.5 MB)
[01/07/12] v3.6:Kernel-Dorimanx-V3.6-ULTIMATE-HD2-MAG-CLK.zip
[12/26/11] v3.2:Kernel_Dorimanx_V3.2_FOR_All_in_One_ROM_MAG_CLK.zip(5.18 MB)
[10.12.11] v2.7:Kernel-Dorimanx-V2.7-ULTIMATE-HD2-MAG-CLK.zip
[11/20/11] v2.4:Kernel-Dorimanx-V2.4-ULTIMATE-HD2-MAG-CLK.zip
Frequent updates, but newer versions are not always stable. When installing a zip with a kernel, several different kernel options are offered, a description of the installation points can be foundHEREorHERE. The author releases the kernel in a single installation file. It is universal for all firmware, including bootloaders. When installing it, you need to select the desired version.
ALSA kernel driver is disabled by default -instructions for its inclusion.
The kernel is suitable for any firmware, but if you have Android 2.3.3 (or below), Sense, or HyperDROID, you should add the initrd.gz file from the installation zip of your firmware to the kernel installation zip, the "initrd Custom" folder.
The latest kernel versions can always be downloaded from the developer’s site.http://www.dorimanx.com/kernels/
[21.06.12] v7.3: Kernel for CM7 and ICS only
Kernel-Dorimanx-V7.3-ULTRA-HD2-MAG-CLK-MULTI.zip(9.02 MB)[07.04.12] v6.4D:Kernel_Dorimanx_V6.4_ULTRA_HD2_MAG_CLK_MULTI.zip
[04/04/12] v6.4:Kernel_Dorimanx_V6.4_ULTRA_HD2_MAG_CLK_MULTI.zip
[03/29/12] v6.3:Kernel_Dorimanx_V6.3_ULTRA_HD2_MAG_CLK_MULTI.zip
[25.03.12] v6.2:Kernel_Dorimanx_V6.2_ULTRA_HD2_MAG_CLK_MULTI.zip
[13.03.12] v5.7:
Kernel_Dorimanx_V5.7_ULTRA_HD2_MAG_CLK_MULTI.zip(7.18 MB)[02.19.12] v4.7:
Kernel_Dorimanx_V4.7_FOR_All_in_One_ROM_MAG_CLK.zip(5.29 MB)[01.25.12] v3.9:
Kernel_Dorimanx_V3.9_FOR_All_in_One_ROM_MAG_CLK.zip(5.59 MB)[01/23/12] v3.8:
Kernel_Dorimanx_V3.8_FOR_All_in_One_ROM_MAG_CLK.zip(5.5 MB)[01/07/12] v3.6:Kernel-Dorimanx-V3.6-ULTIMATE-HD2-MAG-CLK.zip
[12/26/11] v3.2:
Kernel_Dorimanx_V3.2_FOR_All_in_One_ROM_MAG_CLK.zip(5.18 MB)[10.12.11] v2.7:Kernel-Dorimanx-V2.7-ULTIMATE-HD2-MAG-CLK.zip
[11/20/11] v2.4:Kernel-Dorimanx-V2.4-ULTIMATE-HD2-MAG-CLK.zip
Kernels fromKefi.N
Discussion topic on XDA-developers . The kernel is based on Tytung r12. Features: updated sources to the latest (Linux kernel version 2.6.32.39), CPU operating frequencies from 128 to 1536 MHz, added a new automatic CPU frequency scaling mode - SmartassV2 (by default interactive), the minimum voltage on the CPU is 925 mV. Support for btrfs, squashfs file systems has been removed from the kernel (almost no one uses them), the network protocol has also been removed cifs It allows you to watch video from a PC via Wi-Fi without downloading it.
[25.09.11] v0.9.7.3: the version for the MAGLDR bootloader -2.6.32.43 Kefir.net 0.9.7.4.zip, version for boot loader cLK only for AOSP firmware -cLK AOSP 2.6.32.43 0.9.7.4.zip, version for bootloader cLK only for CyanogenMod firmware -cLK CM7 2.6.32.43 0.9.7.4.zip.
[09.24.11] v0.9.7: the version for the MAGLDR bootloader -Kefir.net_v0.9.7.zip, version for boot loader cLK only for AOSP firmware and CyanogenMod -cLK_AOSP_v0.9.7.zip, version for boot loader cLK specifically for Typhoon CM7 firmware -cLK_CM7Ty_v0.9.7.zip
[21.09.11] version for the MAGLDR bootloaderKefir.net v0.9.6.1.zip, version for the cLK loader only for AOSP and CyanogenMod 7 firmwarecLK AOSP 2.6.32.39 v0.9.6.1.zip, version for boot loader cLK only for Sense firmware on Android 2.3cLK GBSense 2.6.32.39 v0.9.6.1.zip
[25.09.11] v0.9.7.3: the version for the MAGLDR bootloader -2.6.32.43 Kefir.net 0.9.7.4.zip, version for boot loader cLK only for AOSP firmware -cLK AOSP 2.6.32.43 0.9.7.4.zip, version for bootloader cLK only for CyanogenMod firmware -cLK CM7 2.6.32.43 0.9.7.4.zip.
[09.24.11] v0.9.7: the version for the MAGLDR bootloader -Kefir.net_v0.9.7.zip, version for boot loader cLK only for AOSP firmware and CyanogenMod -cLK_AOSP_v0.9.7.zip, version for boot loader cLK specifically for Typhoon CM7 firmware -cLK_CM7Ty_v0.9.7.zip
[21.09.11] version for the MAGLDR bootloaderKefir.net v0.9.6.1.zip, version for the cLK loader only for AOSP and CyanogenMod 7 firmwarecLK AOSP 2.6.32.39 v0.9.6.1.zip, version for boot loader cLK only for Sense firmware on Android 2.3cLK GBSense 2.6.32.39 v0.9.6.1.zip
Kernels fromHieros
Author's topic on XDA-developers . Kernels based on the Rafpigna 1.9 OC GB kernel have all the advantages of this kernel. The kernels are designed for firmware Sense + Android 2.3, but most likely will work with other Android 2.3 firmware.
[30.10.11] For the MAGLDR bootloader:kernel_magldr_1.8.5_btfix_2wcr.zip; kernel_magldr_1.8.5_btfix_no2wcr.zip;kernel_magldr_1.8.5_nobtfix_2wcr.zip;kernel_magldr_1.8.5_nobtfix_no2wcr.zip.
For the clk loader:kernel_clk_1.8.5_btfix_2wcr.zip; kernel_clk_1.8.5_btfix_no2wcr.zip; kernel_clk_1.8.5_nobtfix_2wcr.zip; kernel_clk_1.8.5_nobtfix_no2wcr.zip
[13.09.11] For the MAGLDR bootloader:v1.7.5 with bluetooth fix, v1.7.5 without fix bluetooth
[23.08.11] v1.7.4 for MAGLDR bootloader
[19.08.11] kernel_hieros_v1.7.2_magldr.zip, kernel_hieros_v1.7.2_clk.zip + description
[18.08.11] kernel hieros v1.7 + description
kernel hieros v1.5 MAGLDR.zip, kernel hieros v1.5 cLK.zip + description
[30.10.11] For the MAGLDR bootloader:kernel_magldr_1.8.5_btfix_2wcr.zip; kernel_magldr_1.8.5_btfix_no2wcr.zip;kernel_magldr_1.8.5_nobtfix_2wcr.zip;kernel_magldr_1.8.5_nobtfix_no2wcr.zip.
For the clk loader:kernel_clk_1.8.5_btfix_2wcr.zip; kernel_clk_1.8.5_btfix_no2wcr.zip; kernel_clk_1.8.5_nobtfix_2wcr.zip; kernel_clk_1.8.5_nobtfix_no2wcr.zip
[13.09.11] For the MAGLDR bootloader:v1.7.5 with bluetooth fix, v1.7.5 without fix bluetooth
[23.08.11] v1.7.4 for MAGLDR bootloader
[19.08.11] kernel_hieros_v1.7.2_magldr.zip, kernel_hieros_v1.7.2_clk.zip + description
[18.08.11] kernel hieros v1.7 + description
kernel hieros v1.5 MAGLDR.zip, kernel hieros v1.5 cLK.zip + description
Kernels fromRafpigna
Topic of discussion on xda-developers
[7.08.11] 2r0 GB- Android 2.3 version only,2r0 OC. There was a record of conversations from the line. In the GB version, a bug was removed with an increased battery zhory when turning on bluetooth.
[20.03.11] 1.9 OC(core for all firmware) +version for autochange; 1.9 OC GB(special kernel only for Gingerbread firmware). From version 1.9 appeared support for high-capacity batteries.
[3.03.11] ver 1.8 OC + version for autochange
[8.02.11] ver 1.7
[7.08.11] 2r0 GB- Android 2.3 version only,2r0 OC. There was a record of conversations from the line. In the GB version, a bug was removed with an increased battery zhory when turning on bluetooth.
[20.03.11] 1.9 OC(core for all firmware) +version for autochange; 1.9 OC GB(special kernel only for Gingerbread firmware). From version 1.9 appeared support for high-capacity batteries.
[3.03.11] ver 1.8 OC + version for autochange
[8.02.11] ver 1.7
Utility and Supplementfor Android on HD2
- Acceleration of firmware due to disabling CPU rendering
- Task 2a- command for the SPL loader that performs full low-level formatting of the built-in flash drive
- TWRP recovery- alternative recovery
- Solving the problem of auto brightnessHTC HD2 - Android NAND + MAGLDR (Post # 11574503), download from the forum:_ClockWorkMod_Light_Library_Fix_by_Milap.zip(165.86 KB)
- SGS Touchscreen Booster- the program for setting the sensor on the screen
- Touch recovery Beta8 RC1- CWM version with touch screen support (controlled by soft keys).Author's topic on XDA-developers
- Multifunctional Androbot by xGETSx- a program for assembling / disassembling images and other manipulations of firmware.
- Tweak to control the backlight keys- allows you to adjust the backlight of the keys so that it works while the screen is on
- Script to optimize the memory (RAM)- should speed up the system.
- Daemon oc- A script that optimizes the control of the processor, allows you to increase the responsiveness of the system without increasing power consumption.As in the script Daemon OC adjust max. CPU frequency?. DaemonController- A program to adjust the frequency of the processor in the script Daemon OC.Latest version.
- Adding A2SD + to any firmware with CWM. After installing the firmware, it is enough to install the following zip:MDJ_A2SD + .ziporthis
- Saturator- PC software that makes colors more saturated, so that the step gradients are almost absent. The program automatically converts apk. With the release of corrected step gradients, the program is not relevant. All recent kernel versions (December 2011) include this fix.
- Universal Flash Driver for HD2- PC program with user-friendly interface for installing and updating CWM, Radio, ROM, MAGLDR, partitioning (system, cache, etc.), supports full installation of both MAGLDR and cLK firmware.Russified version. Author's topic on XDA-developers.
- SwkeyorВ® Button Savior- soft emulated hardcore programs are useful for those who want to keep buttons and a loop located under the power button
- To improve the sound quality in the firmware (especially the sound of the telephone part), you can usesound driver from Coredroid firmware
- Patch to increase the speed of reading / writing from the memory card, carefully bourgeois language. For "acceleration" you need to install one of the zip'ov SDCardSpeedFix offered in the topic. And you can also use another way - the programSD Speed ​​Increase.
- Patch to support ad hoc networks
- Patch to improve work with ext partitions
- How to reduce the power consumption of the device?
- Morelocale- Russification of any firmware, about the Russification of MIUI firmware readhere
- setCPU- a program to view the current frequency of the processor, its changes, overclocking.
- CurrentWidget- application widget to monitor energy consumption.
- Titanium backup- A program for backup applications. Allows you to save applications and their data in order to restore them after flashing. Also allows you to delete system applications.
- What system applications can be removed? - Everything about this is written in the topic. Android stock program
- ADB - what is it, simply and in Russian
- Task 29- PC program for cleaning internal memory (NAND), in this topic its discussion is prohibited. This utility in bootloader mode allows you to clear the internal HD2 memory. In this case, Radio, the bootloader (bootloader or mattress), Splash and boot screen it does not remove, but it can help to clean the tails of old firmware.
- MAGLDR112.7z(397 KB)DFT_LEO_MAGLDR111.rar(456.56 KB)
There is no curator in the subject. If there is a user in the subject who wants to become a Curator and the correspondingRequirements for candidates, he can apply in the topicI want to be curator(after having studied the topic header and all materials for curators).
Prior to the appointment of the curator, on filling caps, please contactmoderatorssection through a button
under the messages to which you want to add links. Post has been editedvaalf - 08.03.17, 19:59
List of changes in the header and the second message
Here is a complete list of all the changes in the header and the second message (FAQ) in the subject, since June 2011. Particularly important changes in the firmware catalog are also indicated. Before the change comes the nickname of him.
15.04.13 - Semen: a link to the Task 2a instructions has been added to the "Usefulness and Add-ons"
07.01.13 - Semyon: the 96th question about getting rid of a short-term impulse in dynamics has been added to the FAQ
21.12.12 - Semen: a link to TWRP recovery has been added to the "Utility and Add-ons"
16.12.12 - Semyon: a new Tithung core has been added with an alarm clock fixed. The 95th question has been added to the FAQ about the alarm from the off state. The section cLK was changed, the instruction and description were altered for a new cLK 1.5.1.6. Added latest kernels marc1706 v0.2.3 and Dorimanx v7.3
15.12.12 - Semyon: corrected link to the latest version of cLK
19.11.12 - Semen: new kernel Tytung_gb_r16 added to kernel section
24.07.12 - Semyon: added a solution (question 94) of inadequate work of the OS in FAQ
25.06.12 - Semen: fixed instruction on firmware loader cLK from computer
01.06.12 - Semyon: another link on the topic of Android 4.0 has been added to the curator tag
27.05.12 - Semen: updated the 49 question in the FAQ, there is support for USB-host.
04.05.12 - Semen: the results of the last vote on the firmware added to the header in the section "Firmware".
26.04.12 - Semen: In connection with the April update of the script for cLK and cLK itself, the section "cLK bootloader, Installation Instructions" has been completely updated in the header.
22.04.12 - Semen: a spoiler "Kernels from seadersn" has been added to the kernel section. The survey on the types of firmware is completed, its results can be found in the "Firmware" section, a link to the Android 4.0 firmware has also been added there.
17.04.12 - Semen: in accordance with FAK, some of the questions in the FAQ are updated.
14.04.12 - Semen: Kernels from fikret and Tytung ics r1 are added to the kernel section.
13.04.12 - Semen: launched a survey on the types of firmware. On the basis of it, a survey on the popularity of specific firmware will be created.
8.04.12 - Semen: added the Dorimanx v6.4D kernel, added a link to the description of how to enable the ALSA driver in the description.
8.04.12 - Semen: in the "FAQ on Cyanogen mod" updated link to the list of changes. The bootloader survey is closed, its results can be found in the topic. HTC HD2 - Android NAND + MAGLDR (Post # 12491119) . In the "Utility and add-ons" added a fix that fixes the problem of auto-brightness. In the header, wherever it occurred, the requirement to install ActiveSync is replaced by the installation of the driver from ActiveSync. In the kernel section, the spoiler "Kernels from Dorimanx" is updated, the latest and older versions of the kernel are added.
6.04.12 - Semen: fixed non-working link in the kernel section for loading the Rafpigna 1.9 OC GB kernel. Link to download Script.folder_v7.exe (in cLK spoiler) fixed, new version released (eighth), after testing everything will be transferred to the new version.
3.04.12 - Semen: in the kernel section, the spoiler “Kernels from Tytung” was updated, as well as a new kernel was added under the spoiler “Kernels from marc1706”
1.04.12 - Semen: this list of changes moved to the second message. Fixed all links in the FAQ.
31.03.12 - Simon: The theme added a poll "cLK vs MAGLDR". The FAQ 94th issue merged with the 64th (at the boot MAGLDR mode "USB Flasher" is no device connection to the PC). In the FAQ, the answer to this question as amended. Fully updated "HTC HD2 - FAQ for All Android", and also added "How to start Android'a from a memory card using cLK loader", "How to start Android'a from a memory card using MAGLDR loader", "In the process of firmware recovery startup DAF.exe error "," Instructions for firmware recovery from under Android'a without a PC and without data loss. "
30.03.12 - Semen: The 94th question has been added to the FAQ (about the problem of connecting HD2 to a PC in the USB Flasher mode of the MAGLDR bootloader). Updated guide.
29.03.12 - Semen: the "Kernels" section is returned to the header, the section itself has been completely rewritten, information on specific cores will be updated later.
21.03.12 - Semen: the link to Cotulla's wallet (shown below) has been removed, over the past 13 months, other people have done much more.
The gigantic work on porting Android did a respectedCotulla . If you want to thank him financially, support his work through the PayPal service by clicking on the link https://www.paypal.com/cgi-bin/webscr?cmd=_...d=3C7JC3YZYBU2U
20.03.12 - Semyon: information added to the installation instructions for the MAGLDR bootloader and that the USB flasher mode requires a driver from Activesync from the PC (thanks Victor_Sinitca ). The distinctive features of ZIP firmware are reduced to the contents of the META-INF folder.
03.02.12 - Semen: in the section "Goodies and Additions" Touch recovery updated to version Beta8 RC1
24.01.12 - Semen: a link to the Touch version of CWM recovery, as well as a program for calibrating the on-screen sensor, has been added to the "Usefulness and Additions" section.
23.01.12 - Semen: Updated loader cLK to version 1.5.0.1. Completely rewritten the entire description and installation instructions under the spoiler "cLK loader, installation instructions"
22.01.12 - Semen: in connection with the release of the new version of cLK, the primary information was updated, the instruction will be rewritten later. Added information about support for Android bootloader cLK bootloader version 3.03.HSPL
21.01.12 - Semen: Updated information about MAGLDR under the spoiler "What is MAGLDR bootloader". Updated CWM recovery, wherever met. Minor changes in the "Add-ons" section.
09.01.12 - tryfic: the kernels are moved to post 6 of this topic, presumably the recovery will be there, the catalog will be updated. Added links to other topics.
16.12.11 - Semen: a theme archive has been created, a link to the archive has been added to the guidebook
14.12.11 - Semen: updated links to Mobile Device Center and ActiveSync
10.12.11 - tryfic: updated dorimanx kernel, removed vote
21.11.11 - tryfic: updated kernels
11.11.11 - Semen: added Tweak to the controls for backlighting of keys, a program for working with cLK and a program for assembling / disassembling images
4.10.11 - Semen: added voting results in the firmware section
27.9.11 - Semen: Tytung core updated to version r12.3
27.9.11 - Semyon: in connection with the advent of the FAQ on Android on HD2, a new note number 1 appeared in the curator tag. And also added this link to the guide.
27.9.11 - Semen: kernel from Kefi.N updated to version 0.9.7.4
26.9.11 - Semyon: the 83rd and 87th questions were updated in the FAQ (wrong encoding in the music player and too sensitive microphone)
25.9.11 - Semen: kernel from Kefi.N updated to version 0.9.7.3
24.9.11 - Semen: The program Saturator has been added to the utility and add-ons. The results of the last vote were added to the "Firmware" section.
22.9.11 - Semen: kernel from Kefi.N updated to version 0.9.6.1
21.9.11 - Semen: added Tytung r12 core, added HierOS v1.7.5 core, added Kefi.N core
9.9.11 - xGETSx: Added firmware from Mikhey777 to the directory.
6.9.11 - Semyon: modified the 19th question in the FAQ
4.9.11 - Semen: upgraded description of MAGLDR (spoiler content "What is MAGLDR bootloader"), added a description of menu items, explained previously unknown functions, wrote a description in terms of the current firmware position. In the 32nd question (about re-registration of Navitel) in the FAK a remark was added
2.9.11 - xGETSx: instructions for installing cLK firmware have been changed (a new script has been applied)
1.9.11 - Semen completely redesigned the "cLK loader" section. The instruction has become even more detailed. Combined both branches of CLK. Expanded description, fixed several bugs. Changed the 85th question in FAK (FATAL HIT error). Added 93rd question in FAQ (about resetting to factory settings). xGETSx: Changed instructions for changing sections cLK.
31.8.11 - Added 92nd question in the FAQ (about charging a fully discharged battery). Semyon: a new section appeared in the kernel section jan-willem3 . The section itself is slightly altered. Updated GPS driver (45th FAQ), decorative changes.
25.8.11 - Semyon: updated the 44th question in FAK (about the volume of conversational dynamics), updated the core from HierOS
22.8.11 - Semen: added a new r11 core from Tithung
20.8.11 - Semen: in the kernel section, updated the HierOS kernel to version 1.7.2.
18.8.11 - Semen: a new core from HierOS has appeared in the kernel section. xGETSx: Temporarily added the 4th item of the Curator tag about BAD blocks.
15.8.11 - Semen: In the cLK section added "Instructions for installing the firmware on the cLK 1.6.5 DE loader"
12.8.11 - xGETSx: Added new version cLK 1.6.5 DE. Because it is very different from the main one, in the section "cLK bootloader, Installation Instructions" this version of the bootloader is described separately. Semen: a survey on the firmware went to the archive (the results were added to the "Firmware" section). Created a new survey about loaders
11.8.11 - Semen: A reference to a theme with Lost_Angel firmware has been added to the guide. Changed the 19th question in the FAQ (change boot images), added information about replacing the third boot image. In the "Utility and add-ons" added a link to the program DaemonController.
8.8.11 - xGETSx: The item "fix permissions" has been removed from the CLK firmware installation point. Semen: from the "Instructions on Android OS firmware" removed the item "fix permissions". Updated the 53rd question in the FAQ (recording telephone conversations from the line), it also updated the Call recorder program. In the description of CWM in the instructions for the firmware added a solution to the problem with the update recovery.
7.8.11 - Simon: updated the GPS driver (45th FAQ question). Added new rafpigna kernels. In the "utility and add-ons" added a patch to optimize the RAM. Fully updated "Instructions for Android OS firmware" (MAGLDR version) under the spoiler "Everything about Android OS firmware, MAGLDR loader and ClockworkMod recovery"
6.8.11 - Semen: Daemon OC is added to the "Utility and Add-ons" - script that optimizes processor control
5.8.11 - Semyon: fixed the 64th question in FAK, changed guide.
4.8.11 - Semen: Added a large section "cLK loader". The section is designed for advanced users. But it has complete and detailed instructions for installing cLK firmware.
3.8.11 - Semen: removed the fourth remark in the curator tag as useless and rewrote everything. Cut the guide. Removed test versions of firmware, because they are outdated, they still do not develop, there is a Sense3 section. Link to Task 29 fixed
2.8.11 - Semen: in additions, the description for Task 29 was changed. In FAQ, the question about GPS was changed (45th): Method 2 took the final form, all patches were updated to the latest versions. The 3rd section "Firmware based on Android 2.3 with Sense 3" has been added to the firmware catalog.
1.8.11 - Semen: Changed the 45th question in the FAQ, added the 91st question (backup firmware).
31.07.11 - Semen: a utility has been added to the utility for saving buttons - SWkey. Updated GPS driver (45th FAQ). Added a new way of flashing MAGLDR (from a memory card). Added 90th FAQ question. Added instructions for increasing the available HD2 internal memory (91st FAQ question). Changed the 5th question in the FAQ.
Simon: A general guide to replace the boot image. Created by combining the 19th, 62nd questions from the FAQ and information from utilities. The instruction itself is placed in the 19th question. All other issues are removed. That does not move the former numbering newly created 90th question (about the format ext) moved to place 62. Accordingly, the number of questions was 90. After that, the engine will not stand it, FAC moved into the second message in the subject line. In this regard, there was a restructuring and redesign of the cap. Removed the fourth warning tag curatorial because of meaninglessness. The utility added a patch to support the Ad-hoc networks.
30.07.11 - Semen: Under spoiler "Everything about Android OS firmware, MAGLDR bootloader and ClockworkMod recovery" added the first paragraph (not everyone knows this until now). A pair of color changes under the same spoiler. In the miniFAQ section, the "unsolved problems" inscription finally disappeared, because problems inherent in all the firmware at the moment is not revealed. Added the 88th and 89th questions in the FAQ.
29.07.11 - xGETSx: 5th item of the Curator tag, 87 FAQ question
23.07.11 - Semen: xGETSx has been appointed curator. xGETSx: 4th item of the "Curator Tag"
20.07.11 - Semen: GPS driver updated (45th FAQ question)
17.07.11 - Semen: under the spoiler with additions to the item "increasing the speed of reading / writing from the memory card" the second method was added using the SD Speed ​​Increase program, thanks ds123
16.07.11 - Simon: a fully working GPS driver is filled up, the 45th question FAQ is altered. Changed the 17th and 18th questions in the FAQ. Modified the 31st question. Added solution of excessive microphone sensitivity.
15.07.11 - Semen: updated program to record conversations from the line, FAQ 53 question.
9.07.11 - Simon: added 86 FAQ question (about charging).
7.07.11 - tryfic: added link to post to create splash screens (utility and addons).
6.07.11 - Semen: GPS driver from Tytung updated to version 1.6 (45th FAQ question). A link to the dropbox is added to the CWM description (under the spoiler "what is CWM recovery?" In the "Android OS Firmware Instructions")
Earlier changes:
Semen:
simplified the 4th question in the FAQ, combined the 8th and 84th questions in the FAQ, added. Added 85th question in FAQ. In the firmware section added the results of the weekly vote.
Added a small Android. Added kernels fromHieros (domestic development). Added this spoiler. Added cLK firmware versions to the firmware catalog imilka . In the firmware catalog the description is unified, now it will be like this:
[firmware release date in dd.mm.yy format] [supported bootloaders, may be absent if only MAGLDR is supported] [CWM or DAF firmware type] memory] [built-in core]
Added latest kernels from Tithung - r10.
Added 81-84 questions in the FAQ
Changed 47 questions in FAQ
The CWM description has been changed in the Android OS Firmware Manual, as well as many other changes in this manual and in the whole spoiler. Everything about Android OS firmware, MAGLDR loader and ClockworkMod recovery
Reloads archives with CWM flashers, fixed names, deleted extra files
15.04.13 - Semen: a link to the Task 2a instructions has been added to the "Usefulness and Add-ons"
07.01.13 - Semyon: the 96th question about getting rid of a short-term impulse in dynamics has been added to the FAQ
21.12.12 - Semen: a link to TWRP recovery has been added to the "Utility and Add-ons"
16.12.12 - Semyon: a new Tithung core has been added with an alarm clock fixed. The 95th question has been added to the FAQ about the alarm from the off state. The section cLK was changed, the instruction and description were altered for a new cLK 1.5.1.6. Added latest kernels marc1706 v0.2.3 and Dorimanx v7.3
15.12.12 - Semyon: corrected link to the latest version of cLK
19.11.12 - Semen: new kernel Tytung_gb_r16 added to kernel section
24.07.12 - Semyon: added a solution (question 94) of inadequate work of the OS in FAQ
25.06.12 - Semen: fixed instruction on firmware loader cLK from computer
01.06.12 - Semyon: another link on the topic of Android 4.0 has been added to the curator tag
27.05.12 - Semen: updated the 49 question in the FAQ, there is support for USB-host.
04.05.12 - Semen: the results of the last vote on the firmware added to the header in the section "Firmware".
26.04.12 - Semen: In connection with the April update of the script for cLK and cLK itself, the section "cLK bootloader, Installation Instructions" has been completely updated in the header.
22.04.12 - Semen: a spoiler "Kernels from seadersn" has been added to the kernel section. The survey on the types of firmware is completed, its results can be found in the "Firmware" section, a link to the Android 4.0 firmware has also been added there.
17.04.12 - Semen: in accordance with FAK, some of the questions in the FAQ are updated.
14.04.12 - Semen: Kernels from fikret and Tytung ics r1 are added to the kernel section.
13.04.12 - Semen: launched a survey on the types of firmware. On the basis of it, a survey on the popularity of specific firmware will be created.
8.04.12 - Semen: added the Dorimanx v6.4D kernel, added a link to the description of how to enable the ALSA driver in the description.
8.04.12 - Semen: in the "FAQ on Cyanogen mod" updated link to the list of changes. The bootloader survey is closed, its results can be found in the topic. HTC HD2 - Android NAND + MAGLDR (Post # 12491119) . In the "Utility and add-ons" added a fix that fixes the problem of auto-brightness. In the header, wherever it occurred, the requirement to install ActiveSync is replaced by the installation of the driver from ActiveSync. In the kernel section, the spoiler "Kernels from Dorimanx" is updated, the latest and older versions of the kernel are added.
6.04.12 - Semen: fixed non-working link in the kernel section for loading the Rafpigna 1.9 OC GB kernel. Link to download Script.folder_v7.exe (in cLK spoiler) fixed, new version released (eighth), after testing everything will be transferred to the new version.
3.04.12 - Semen: in the kernel section, the spoiler “Kernels from Tytung” was updated, as well as a new kernel was added under the spoiler “Kernels from marc1706”
1.04.12 - Semen: this list of changes moved to the second message. Fixed all links in the FAQ.
31.03.12 - Simon: The theme added a poll "cLK vs MAGLDR". The FAQ 94th issue merged with the 64th (at the boot MAGLDR mode "USB Flasher" is no device connection to the PC). In the FAQ, the answer to this question as amended. Fully updated "HTC HD2 - FAQ for All Android", and also added "How to start Android'a from a memory card using cLK loader", "How to start Android'a from a memory card using MAGLDR loader", "In the process of firmware recovery startup DAF.exe error "," Instructions for firmware recovery from under Android'a without a PC and without data loss. "
30.03.12 - Semen: The 94th question has been added to the FAQ (about the problem of connecting HD2 to a PC in the USB Flasher mode of the MAGLDR bootloader). Updated guide.
29.03.12 - Semen: the "Kernels" section is returned to the header, the section itself has been completely rewritten, information on specific cores will be updated later.
21.03.12 - Semen: the link to Cotulla's wallet (shown below) has been removed, over the past 13 months, other people have done much more.
The gigantic work on porting Android did a respectedCotulla . If you want to thank him financially, support his work through the PayPal service by clicking on the link https://www.paypal.com/cgi-bin/webscr?cmd=_...d=3C7JC3YZYBU2U
20.03.12 - Semyon: information added to the installation instructions for the MAGLDR bootloader and that the USB flasher mode requires a driver from Activesync from the PC (thanks Victor_Sinitca ). The distinctive features of ZIP firmware are reduced to the contents of the META-INF folder.
03.02.12 - Semen: in the section "Goodies and Additions" Touch recovery updated to version Beta8 RC1
24.01.12 - Semen: a link to the Touch version of CWM recovery, as well as a program for calibrating the on-screen sensor, has been added to the "Usefulness and Additions" section.
23.01.12 - Semen: Updated loader cLK to version 1.5.0.1. Completely rewritten the entire description and installation instructions under the spoiler "cLK loader, installation instructions"
22.01.12 - Semen: in connection with the release of the new version of cLK, the primary information was updated, the instruction will be rewritten later. Added information about support for Android bootloader cLK bootloader version 3.03.HSPL
21.01.12 - Semen: Updated information about MAGLDR under the spoiler "What is MAGLDR bootloader". Updated CWM recovery, wherever met. Minor changes in the "Add-ons" section.
09.01.12 - tryfic: the kernels are moved to post 6 of this topic, presumably the recovery will be there, the catalog will be updated. Added links to other topics.
16.12.11 - Semen: a theme archive has been created, a link to the archive has been added to the guidebook
14.12.11 - Semen: updated links to Mobile Device Center and ActiveSync
10.12.11 - tryfic: updated dorimanx kernel, removed vote
21.11.11 - tryfic: updated kernels
11.11.11 - Semen: added Tweak to the controls for backlighting of keys, a program for working with cLK and a program for assembling / disassembling images
4.10.11 - Semen: added voting results in the firmware section
27.9.11 - Semen: Tytung core updated to version r12.3
27.9.11 - Semyon: in connection with the advent of the FAQ on Android on HD2, a new note number 1 appeared in the curator tag. And also added this link to the guide.
27.9.11 - Semen: kernel from Kefi.N updated to version 0.9.7.4
26.9.11 - Semyon: the 83rd and 87th questions were updated in the FAQ (wrong encoding in the music player and too sensitive microphone)
25.9.11 - Semen: kernel from Kefi.N updated to version 0.9.7.3
24.9.11 - Semen: The program Saturator has been added to the utility and add-ons. The results of the last vote were added to the "Firmware" section.
22.9.11 - Semen: kernel from Kefi.N updated to version 0.9.6.1
21.9.11 - Semen: added Tytung r12 core, added HierOS v1.7.5 core, added Kefi.N core
9.9.11 - xGETSx: Added firmware from Mikhey777 to the directory.
6.9.11 - Semyon: modified the 19th question in the FAQ
4.9.11 - Semen: upgraded description of MAGLDR (spoiler content "What is MAGLDR bootloader"), added a description of menu items, explained previously unknown functions, wrote a description in terms of the current firmware position. In the 32nd question (about re-registration of Navitel) in the FAK a remark was added
2.9.11 - xGETSx: instructions for installing cLK firmware have been changed (a new script has been applied)
1.9.11 - Semen completely redesigned the "cLK loader" section. The instruction has become even more detailed. Combined both branches of CLK. Expanded description, fixed several bugs. Changed the 85th question in FAK (FATAL HIT error). Added 93rd question in FAQ (about resetting to factory settings). xGETSx: Changed instructions for changing sections cLK.
31.8.11 - Added 92nd question in the FAQ (about charging a fully discharged battery). Semyon: a new section appeared in the kernel section jan-willem3 . The section itself is slightly altered. Updated GPS driver (45th FAQ), decorative changes.
25.8.11 - Semyon: updated the 44th question in FAK (about the volume of conversational dynamics), updated the core from HierOS
22.8.11 - Semen: added a new r11 core from Tithung
20.8.11 - Semen: in the kernel section, updated the HierOS kernel to version 1.7.2.
18.8.11 - Semen: a new core from HierOS has appeared in the kernel section. xGETSx: Temporarily added the 4th item of the Curator tag about BAD blocks.
15.8.11 - Semen: In the cLK section added "Instructions for installing the firmware on the cLK 1.6.5 DE loader"
12.8.11 - xGETSx: Added new version cLK 1.6.5 DE. Because it is very different from the main one, in the section "cLK bootloader, Installation Instructions" this version of the bootloader is described separately. Semen: a survey on the firmware went to the archive (the results were added to the "Firmware" section). Created a new survey about loaders
11.8.11 - Semen: A reference to a theme with Lost_Angel firmware has been added to the guide. Changed the 19th question in the FAQ (change boot images), added information about replacing the third boot image. In the "Utility and add-ons" added a link to the program DaemonController.
8.8.11 - xGETSx: The item "fix permissions" has been removed from the CLK firmware installation point. Semen: from the "Instructions on Android OS firmware" removed the item "fix permissions". Updated the 53rd question in the FAQ (recording telephone conversations from the line), it also updated the Call recorder program. In the description of CWM in the instructions for the firmware added a solution to the problem with the update recovery.
7.8.11 - Simon: updated the GPS driver (45th FAQ question). Added new rafpigna kernels. In the "utility and add-ons" added a patch to optimize the RAM. Fully updated "Instructions for Android OS firmware" (MAGLDR version) under the spoiler "Everything about Android OS firmware, MAGLDR loader and ClockworkMod recovery"
6.8.11 - Semen: Daemon OC is added to the "Utility and Add-ons" - script that optimizes processor control
5.8.11 - Semyon: fixed the 64th question in FAK, changed guide.
4.8.11 - Semen: Added a large section "cLK loader". The section is designed for advanced users. But it has complete and detailed instructions for installing cLK firmware.
3.8.11 - Semen: removed the fourth remark in the curator tag as useless and rewrote everything. Cut the guide. Removed test versions of firmware, because they are outdated, they still do not develop, there is a Sense3 section. Link to Task 29 fixed
2.8.11 - Semen: in additions, the description for Task 29 was changed. In FAQ, the question about GPS was changed (45th): Method 2 took the final form, all patches were updated to the latest versions. The 3rd section "Firmware based on Android 2.3 with Sense 3" has been added to the firmware catalog.
1.8.11 - Semen: Changed the 45th question in the FAQ, added the 91st question (backup firmware).
31.07.11 - Semen: a utility has been added to the utility for saving buttons - SWkey. Updated GPS driver (45th FAQ). Added a new way of flashing MAGLDR (from a memory card). Added 90th FAQ question. Added instructions for increasing the available HD2 internal memory (91st FAQ question). Changed the 5th question in the FAQ.
Simon: A general guide to replace the boot image. Created by combining the 19th, 62nd questions from the FAQ and information from utilities. The instruction itself is placed in the 19th question. All other issues are removed. That does not move the former numbering newly created 90th question (about the format ext) moved to place 62. Accordingly, the number of questions was 90. After that, the engine will not stand it, FAC moved into the second message in the subject line. In this regard, there was a restructuring and redesign of the cap. Removed the fourth warning tag curatorial because of meaninglessness. The utility added a patch to support the Ad-hoc networks.
30.07.11 - Semen: Under spoiler "Everything about Android OS firmware, MAGLDR bootloader and ClockworkMod recovery" added the first paragraph (not everyone knows this until now). A pair of color changes under the same spoiler. In the miniFAQ section, the "unsolved problems" inscription finally disappeared, because problems inherent in all the firmware at the moment is not revealed. Added the 88th and 89th questions in the FAQ.
29.07.11 - xGETSx: 5th item of the Curator tag, 87 FAQ question
23.07.11 - Semen: xGETSx has been appointed curator. xGETSx: 4th item of the "Curator Tag"
20.07.11 - Semen: GPS driver updated (45th FAQ question)
17.07.11 - Semen: under the spoiler with additions to the item "increasing the speed of reading / writing from the memory card" the second method was added using the SD Speed ​​Increase program, thanks ds123
16.07.11 - Simon: a fully working GPS driver is filled up, the 45th question FAQ is altered. Changed the 17th and 18th questions in the FAQ. Modified the 31st question. Added solution of excessive microphone sensitivity.
15.07.11 - Semen: updated program to record conversations from the line, FAQ 53 question.
9.07.11 - Simon: added 86 FAQ question (about charging).
7.07.11 - tryfic: added link to post to create splash screens (utility and addons).
6.07.11 - Semen: GPS driver from Tytung updated to version 1.6 (45th FAQ question). A link to the dropbox is added to the CWM description (under the spoiler "what is CWM recovery?" In the "Android OS Firmware Instructions")
Earlier changes:
Semen:
simplified the 4th question in the FAQ, combined the 8th and 84th questions in the FAQ, added. Added 85th question in FAQ. In the firmware section added the results of the weekly vote.
Added a small Android. Added kernels fromHieros (domestic development). Added this spoiler. Added cLK firmware versions to the firmware catalog imilka . In the firmware catalog the description is unified, now it will be like this:
[firmware release date in dd.mm.yy format] [supported bootloaders, may be absent if only MAGLDR is supported] [CWM or DAF firmware type] memory] [built-in core]
Added latest kernels from Tithung - r10.
Added 81-84 questions in the FAQ
Changed 47 questions in FAQ
The CWM description has been changed in the Android OS Firmware Manual, as well as many other changes in this manual and in the whole spoiler. Everything about Android OS firmware, MAGLDR loader and ClockworkMod recovery
Reloads archives with CWM flashers, fixed names, deleted extra files
The terminology of Android on HD2 has the following concepts: the assembly is the type of Android OS that runs from a memory card from WM, the Android firmware is the version that starts from internal memory (replaces WM). In order to avoid confusion, I ask you to use this unofficial (like everything else here), but historically established terminology.
The main knowledge base is the cap of this topic and FAK -Android FAQ on HD2 . For those who are used to the FAQ left in the form of this message. But do not forget to look into the FAK, there is more relevant information, as well as in a more complete form.
FAQ- frequently asked questions and answers to them
1. How does the Android port work on HD2 (performance, games), can it be considered stable? - Android works no worse than, for example, on HTC Desire and Google Nexus one. But a lot depends on the specific firmware.
2. I have flashed MAGLDR, I want to return everything back (run WM), how to do it? - It's simple, just flash any WM firmware, incl. unofficial. Sew through Bootloader! At the moment (MAGLDR 1.13), either WM or MAGLDR can exist in the internal memory. The firmware of one of them is due to the removal of the other.
3. When starting the flash driver gives an errorError Description: USB init failedor others - Run the flash driver on behalf of the Administrator or use corrected flash driver
4. The firmware after installation at the first start hangs ongo go go - Install the last MAGLDR.
5. Was the video recording in 720p? - no, the only driver that was never completed can be downloaded from here but the video is very poor quality.
6. How to reset MAGLDR settings? HTC HD2 - Android NAND + MAGLDR (archive) (Post # 6210157)
7. There is a robot voice. How to treat? - Fixed reboot. It can also help mute keystrokes. If it does not work - decision from Mikmik .
8. I already have an Android flashing, how can I change the firmware to another Android firmware? - just flash the new firmware using "Instructions on Android OS firmware" from the header. In this case, HSPL, Radio, and MAGLDR do not need to reinstall. The following is described in detail.The described method involves the installation of a new firmware clean, the update of the firmware version is described in the 15th paragraph.
9. How to update MAGLDR? - Install the new version, like the old one. Data will not be lost.
10. How to configure the installation of applications on the SD card?
1) useSparePartsfromxGETSx
2) use applications for transfer to a memory card such asВ® Move2SD EnablerandSDMove
3a) For firmware with Cyanogen Mod - Go to "Settings" ->"CyaogenMOD" ->"Applications" ->"Allow moving", put a check mark; you can experiment with the installation site in the same place.
3b) Settings ->Applications ->Application Management ->Next, select the program and click "Move to SD card"
11. How to get ROOT on firmware? - On all new firmware, superuser rights (root rights, administrator rights) are available initially and you do not need to receive them again. For "Stock" - immediately after the firmware is rebooted and in the MAGLDR menu select the item "AD Hard reset", after that the ROOT works. You can also try to get root using the program z4root + one more program SuperOneClick
12. Where can I additionally read about porting progress? - xda-developers branch (English forum)
13. Convenient work with the terminal and ADB - download and unpack, following the necessary instructions, no need to install.
14. I can not charge the communicator in the off state - In MAGLDR this can not be done. This is a known bug MAGLDR - HD2 not charging in the off state. Therefore, the MAGLDR version 1.13 has an automatic switch-on when the power is connected. In previous versions, if you have a problem, you need to wrap the battery.
As an alternative to MAGLDR, you can use the CLK bootloader, it allows you to charge the HD2 in the off state.
15. Is it possible to update the firmware without losing data? - Only in firmware versions for CWM recovery. Go to the CWM recovery execute item wipe dalvik cache as well as point wipe cache (paragraph wipe data Do not touch) and install the ZIP of the new firmware version via CWM recovery. At the same time, all settings and applications will remain in place.
16. Build / disassemble system.img and boot.img - in windows , in linux
17. When downloading files to a memory card via MAGLDR in "MassStg USB" mode, the transfer often hangs - this is a problem of MAGLDR 1.13, especially manifested when there is an ext partition. Use the removable disk mode in CWM recovery (while charging via USB) or copy files through a card reader.
18. On the support of high-capacity batteries - in all the latest (at the end of March) cores (and therefore the firmware), there was full support for official high-capacity batteries. Informal batteries also work, but there may be problems with charging and displaying the current charge. It is best to charge until the current becomes zero, you can check it with the program Current widget . When changing the battery, it is desirable to reset the battery statistics, i.e. perform Wipe Battery Stat in CWM before downloading the firmware. If a “big” battery sits as fast as a small one, a charge is probably incorrectly displayed, a reboot can help.
19. How to change the images that appear when loading HD2? - when booting HD2 can appear up to four different images. The first 3 of them are static, the last is dynamic (animation). The first image is called Boot Screen, the second is Splash Screen.
20. I do not have enough internal memory. How to create an ext4 partition on a memory card? - Instruction , Paragon Hard Drive Manager 2010 pro download A problem with creating a partition on Kingston maps has been noticed.
21. Can I create an ext partition after I installed the firmware? - You can create an ext partition on a memory card at any time. But if your firmware supports automatic data transfer to the ext partition (there is support for A2SD +, Data2ext, Data2SD scripts), then it is likely that after this the system will not work correctly. And still have to reinstall.
22. Accelerometer (G-sensor) is calibrated only with the screen down, how to fix it? - decision
23. How to make streaming video work? - CIFS protocol is responsible for this, which supports most of the cores. Those. All modern firmware support streaming video playback. If this function does not work on your firmware, replace the kernel.
24. What is config.txt and where is it located? It lies in the root of the memory card in the FAT section (if you have others).
25. When you click on the ad recovery item in MAGLDR, it writes "No boot sources"? - It is required to flash ClockworkMod recovery. MAGLDR 1.13 initially supports recovery, but it is not built in.
26. Replace files in app and framework folders in SQUASHED firmware - instruction + instructions for replacing files in SquashFS firmware
27. Have you fixedglitch with multitouch(on WM there were problems)? - the problem was not fixed, just like on Windows Mobile, on Android, the points close to the coordinate stick together. This is a hardware disadvantage of HD2, it can not be fixed by software. It appears absolutely on all Android OS, Windows Mobile and Windows Phone 7 firmwares. But there are very rare HD2 samples that do not have this glitch.
28. I can not understand what the abbreviations in the names of the firmware and what they mean? - mini dictionary
29. WhyQuadrantgives such bad results? - Quadrant is a synthetic test and does not display the real performance of the firmware and the device as a whole. In this topic, it is not recommended to use this program to measure the speed of the firmware, since The actual results are very often very different.
30. What is ClockworkMod recovery (CWR / DVR or CWM)? This is an enhanced recovery version (HD2 does not have the usual recovery), which allows you to make a full backup of the firmware, replace system files, install firmware without a PC, easily install fixes and patches, do wipe and create an ext3 partition on a memory card. Supported in MAGLDR version 1.13 and higher, but not originally installed. CWM installs only ZIP firmware. You can learn more about CWM for HD2 and download it in the Android OS firmware manual.
31. All kind of small. How to change the "resolution" of the screen and what to do if the applications do not run in full screen -32. How to deal with the license for Navitel when changing firmware? - 33. I asked for Android 2.3, I can not run Navitel - Navitel supports the latest version of android only starting with version 5.0.0.778.
34. I only have 412MB of RAM, is this normal? - appears set to 412 MB, 512 MB, in some in some Android firmware amount of available memory. Regardless of this, in all the Android firmware only ~ 412 MB of memory available to the operating system. Volume "available memory", which is displayed in the settings Android'a registered in the operating system kernel, it has registered to HTC (kernel for HD2 is based on the original nuclei of Android devices from HTC), our developers could not use more. But this does not mean that the remaining 150 MB are doing nothing, they just can not use the operating system and therefore the user.
HTC allocates the remaining memory for the video accelerator. And do not forget that the bootloader (SPL) and the radio module also use RAM. And 412 MB is the amount of RAM available for the Android operating system, i.e. all that remains of the above modules.
35. Where to see the kernel version? - download Android ->go to Settings ->About phone ->Kernel version
36. The kernel is not installed, writesdevice not found - decision
37. The application is installed, but does not start - transfer the application to the internal memory in the settings.
38. I can not synchronize my smartphone with a computer, HTC Sync does not work in my XXX firmware - HTC Sync is intended only for firmware with Sense. As an analogue for other firmware you can use DroidExplorer or MyPhoneEXplorer
39. How to make the screen turn on only by pressing a buttonpower? - edit all files / system / usr / keylayout / * kl by deleting the inscriptions WAKE and WAKE_DROPPED in the lines from HOME, BACK, CALL, MENU. After that, the screen will light up only by pressing a button. power However, the key illumination still lights up and does not go out. The method is not perfect, but the other has not yet been found.
40. I upgraded to another firmware, I connected to the android Market and all programs from the previous firmware start to automatically load, how to remove it? - you need to set up synchronization with Google. When logging in to your phone account, you need to remove the checkmark from the “Backing up data using a Google Account” item.
41. After installing a new firmware application miraculously appeared again? - if you use the ext partition and have not formatted it, the applications installed on the previous firmware will be restored. It can also happen through htcsense.com (to get rid of this you just need to disable synchronization with the htcsense.com service).
42. There is no Russian in the dialer, how to add it? - In the standard call from Google there is no Russian language and you can’t add it there. You can use third-party dialers, for example, Dialer one or Fast dialer . To search for other dialers use Software catalog - Android OS and topic SEARCH software for Android OS .
For those who do not know what a standard dialer from Google looks like, it goes by default in Cyanogen mod firmware (there is Russification in assemblies in 2012), AOSP and Nexus firmware.
43. When flashing through DAF.exe, it constantly gives an errorUSB init failed - most likely before the firmware you used MassStg USB, reboot the device.
44. When you call, regardless of the selected volume level - the volume is always at the maximum.45. GPS does not work, does not catch satellites badly or does not catch at all - help solve the following problem46. What is Cyanogen mod (CM, cyan)? - this is a tweaker. Modification of Android, which allows you to change the interface (top panel, lock screen, etc.) and system settings. It also allows you to change the frequency of the processor, including overclocking it, and more.
47. On my XXX firmware there are very noticeable stepped gradients, how to fix it?48. What is WI-FI (USB) Tethering? - This is Internet distribution via Wi-Fi (HD2 with EDGE or 3G is used as a modem). USB Tethering (Internet Pass-Through) is a feature that allows you to use your phone’s Internet from a PC via USB.
49. Is there USB host support on HD2? - On May 26, a support core appeared, but USB charging and connecting to a computer does not work, read more here
50. Can I turn off USB charging? - not.
51. Can I add Cyanogen mod to my XXX firmware? - not. If this mod is not built in immediately, then you can’t add it.
52. In Sense firmware there is a mode "turned the phone over - the sound is turned off", how to implement it in other firmware? - use third-party applications, such as Starksoft G-App and RD Mute
53. Is it possible to record telephone conversations from the line on HD2? - Yes54. Is it possible to flash several OS on HD2 at once, so that when the device is loaded, there is a choice what to load? - not.
55. Photos of contacts are constantly blurred, how to fix? - disable synchronization of contacts with Google.
56. Is it possible to add programs and widgets from HTC Sense such as a clock, calendar, camera, album, etc. to the firmware without Sense? - no, these widgets and applications use the proprietary HTC framework, which is not in the firmware without Sense. But for many applications there are almost complete counterparts.
57. What is a CWM recovery ZIP and how can I replace system files with them? - small FAQ so the issue from xGETSx
58. Convert DAF to ZIP and vice versa - instruction from xGETSx
59. How to change the size of the system and cache? - these partitions are created with the CWM firmware and can be changed only by flashing the CWM (the internal memory is formatted and your old firmware is erased).60. What is a system partition? - a logical disk (partition) in the internal memory HD2, in which the Android OS is stored (the firmware itself). More on this. .
61. How to delete ext partition? - use the program on your PC SDFormatter , when formatting in the program menu, select "format size adjustment". If you do not have a device for reading memory cards, then this can be done through MAGLDR in mass storage mode.
62. How to format an ext partition?
Method number 1.Go to ClockworkMod recovery and run "mounts and storage ->format sd-ext "
Method number 2.Format with PC. To do this, you need to either connect to the PC in removable disk mode (it is supported by the MAGLDR bootloader - "USB MassStg" and CWM recovery - "mount USB storage"). Or remove the memory card and connect it to the computer through a card reader. Next, you need to format the ext partition with a PC. Under Linux, this can be done with built-in tools. And in Windwos you have to install a third-party program, for example, Paragon Hard Drive Manager.
63. How to change font type and size in firmware? - use programs В® Font Changer and В® Font Size .
64. In the MAGLDR bootloader in USB Flasher mode, the communicator does not connect to the PC - In order for the computer to correctly recognize the connected device, you need to install the driver (usually installed automatically) from the Windows Mobile Device Center (Microsoft ActiveSync) on the PC, or you can install the mobile device center itself, the driver will be installed with it.
65. I have Windows XP and when I try to install firmware via MAGLDR, I get errors all the time - decision
66. Android does not see the memory card (writes that it is damaged), although it works fine on other devices and on the PC - format the memory card using the program panasonic SDFormatter , when formatting in the program menu, select format size adjustment
67. How to access the Internet of a PDA on a PC via USB? - for firmware without Sense: solution for windows 7 , solution for windows xp . For firmware with Sense 2: install HTC sync on the PC (it is not necessary to synchronize) and when connecting the PDA to the PC, select "pass-through connection".
68. The phone sees the Wi-Fi network, but does not connect to it. - decision
69. How to improve the quality of the video? - will require a third-party application LG camera (paid), set the following settings in it: video format - mpeg4, codec - mpeg4, resolution 800 * 480, 3 MB bitrate, 30 frames per second, iso 800. Thanks for the advice tweakos
70. It was stitched on Android and the sensor stopped working on the screen - Android has nothing to do with it. In HD2, there is a loop under the power button that goes to the screen, it is subject to heavy wear, especially in TMOUS HD2. If the firmware WM tezhe symptoms, it will only help the service. Mechanical buttons - a weak point HD2
71. Calibration of the accelerometer (G-sensor) in firmware without Sense - decision from eastic
72. Convert MAGLDR ZIP firmware to cLK ZIP - instruction
73. I install widgets, but I can not install them on the desktop, they do not even appear in the list of available widgets - Widgets must be in the internal memory of the device, then they will be in the list of adding widgets.
74. In my XXX firmware sound is very quiet, how to increase? - the volume can be increased with the help of the DSP manager program built into most of the firmware; for the rest, an alternative variant is suitable: Volume +
75. When an incoming call instead of the interlocutor heard a crash, how to fix it? - root explorer delete the file /etc/firmware/default.acdb . A side effect may be a voice vote.
76. Accelerometer (G-sensor) does not work on Android, although WM is fine -77. Installed the firmware, and the device does not boot beyond the boot animation - Most likely with the CWM recovery firmware, you indicated the wrong size of the system partition. Recheck CWM, specifying the desired size, and reinstall the firmware. If the author of the firmware does not have this parameter, see the description in our firmware catalog .
78. The battery is very quickly discharged, the consumption in standby mode does not fall below 60 mA, how to calibrate it? - Thanks for the solution found Nutthell :79. How to disable unnecessary languages? - Thanks for the way De11 . You need to edit the XML files in \ system \ customize (applicable only to Sense firmware)
- yes
- yes
- Russian
- Handwriting; ZuhYin; CangJie; PinYin; Stroke;
- no
- no
- no
- no
- no
-
-
-
-
-
-
-
- / system / customize / resource /
81. My device wakes up for a long time when I press the power button, it wakes up from standby for a long time, what should I do? - install the latest firmware or update the kernel in your firmware, there will already be included a patch so that the screen turns on quickly.
82. I have an ext partition, how to change the memory card without losing data? - you need to create an ext partition on the new map (better than the same size), and then copy the contents of the ext section into it from the old map. The same should be done with the rest of the contents of the memory card. The problem is that windows can't work with ext partitions. But the data can be transferred using Paragon Hard Drive Manager.
83. The player displays Russian tags incorrectly, how to fix it? -84. The phone does not see the Wi-Fi network - in the Wi-fi settings, in the additional functions set the frequency range - 14. And you can also try another solution .
85. When you click in the MAGLDR itemAD Recoverygives an error message1E FATAL HITand flashing does not help - Only flashing to the official Windows Mobile firmware will help. In this case, MAGLDR is removed and it will have to be reinstalled.
86. The current when charging all the time changes, before it was 300 mA, and now 50 - this is normal. When charging the battery, the current constantly decreases until it reaches zero - the battery is charged. The current varies exponentially from 900 mA (or more) to zero. At the same time, the current decreases very quickly, and at the end very slowly, the last percentages charge for a very long time - this is also normal.
87. The microphone when talking is too sensitive, the interlocutor can hear all the people around -88. Do the phone identification codes (serial, IMEI) change during firmware? - No, neither with Android firmware, nor with WM, Radio, MAGLDR or bootloader firmware.
89. How to change the maximum and minimum frequency of the processor? - In the Cyanogen mod settings, as well as in the setCPU program, these frequencies are automatically detected and read from the core. You can change the CPU operating frequency limits only by replacing the core. Rafpigna cores support overclock up to 1.5 GHz.
90. Increasing the available internal memory, how to use the backup 24 MB? - small FAK from delphin73 .
91. How to make a full backup of the firmware, so that you can always return the firmware to its previous state? - The DAF firmware in any way. The ZIP firmware: it is necessary to go to the CWM recovery, to find there the item "backup and restore" and there choose "backup" - in this case on the memory card will create a full backup of firmware, including a copy ext section. If you save the backup folder, then later through the same CWM, you can restore that backup point "restore". And most importantly, a system partition size of the internal memory and HD2 ext partition on the memory card at the time of recovery backup should not be less than the size of the sections at the time of the backup firmware.
92. What should I do if the battery is completely discharged and the communicator does not even turn on? - the problem occurs only for MAGLDR users (the CLK allows charging in the off state). You can solve it by connecting the charging clock by 8. If this does not help, it will help93. How to reset to factory settings? - go to CWM recovery and execute wipe data / factory reset . This will remove all installed applications and restore the default settings. Do not forget to delete the data from the memory card.
94. The operating system is unstable (constant reboots, processes crash), the OS or recovery is not loaded at all - if there were no errors in the firmware process, repeated firmware does not give anything, then most likely the problem is in the memory. In order to mark the broken memory cells install the official firmware WM. After that, repeat the installation of all components of Android. When installing recovery in the configuration of partitions in the internal memory, remove all the "ro" flags. Read more here .
95. How to make the alarm go off? - Update the android loader cLK to version 1.5.1.4 or higher, install the kernel with the built-in alarm clock fix (Tytung kernels support it from version r3.6 for Android 4 and from version 11.11.12 for Android 2.3), to the system section in the internal HD2 memory in the app folder, add the application SysAlarm.apk , set permissions as adjacent files and reboot the machine. After that, SysAlarm will appear in the application menu, with which you can set the alarm. Note: the alarm clock is triggered along with the loading of the operating system and it takes quite a long time, 2-3 minutes after the desired time has arrived.
96. Solving the problem of spontaneous short-term activation of the speakerphone when an incoming call - Install the following fix through recovery - Sound_fix.zip , it will replace the audio drivers in the firmware. Fix may not work on your firmware before using it be sure to do a full backup firmware . After installing the fix (audio driver replacement), the pulsed sound that sometimes appears in the speaker disappears. It occurs when an incoming call and in rare cases when working with multimedia applications. In addition, the bug will go away when, with an incoming call, the sound level is forced to the maximum regardless of the previous settings. Solution found Anton22 .
2. I have flashed MAGLDR, I want to return everything back (run WM), how to do it? - It's simple, just flash any WM firmware, incl. unofficial. Sew through Bootloader! At the moment (MAGLDR 1.13), either WM or MAGLDR can exist in the internal memory. The firmware of one of them is due to the removal of the other.
3. When starting the flash driver gives an errorError Description: USB init failedor others - Run the flash driver on behalf of the Administrator or use corrected flash driver
4. The firmware after installation at the first start hangs ongo go go - Install the last MAGLDR.
5. Was the video recording in 720p? - no, the only driver that was never completed can be downloaded from here but the video is very poor quality.
6. How to reset MAGLDR settings? HTC HD2 - Android NAND + MAGLDR (archive) (Post # 6210157)
7. There is a robot voice. How to treat? - Fixed reboot. It can also help mute keystrokes. If it does not work - decision from Mikmik .
8. I already have an Android flashing, how can I change the firmware to another Android firmware? - just flash the new firmware using "Instructions on Android OS firmware" from the header. In this case, HSPL, Radio, and MAGLDR do not need to reinstall. The following is described in detail.
ZIP firmware change method:
If the new firmware requires a system partition of approximately the same size (the same or slightly smaller), then it is enough to install the zip of the new firmware via CWM, having previously performed the same CWM wipe data / factory reset . If a larger partition is required for a new firmware, then first you need to reflash the CWM with the parameters (size of the system partition) required for the firmware, and then install the zip of the new firmware. You can determine the size of the system partition using the program root explorer , for this you need to go into it in the / system folder and look at the amount of available memory in the top panel - this will be the size of the system partition that you have created on the current firmware. The way to install CWM firmware and install zip firmware through it is described in the "Android OS Firmware Manual".
The size of the system partition required for a specific firmware can be specified in ourfirmware catalog.
The size of the system partition required for a specific firmware can be specified in ourfirmware catalog.
9. How to update MAGLDR? - Install the new version, like the old one. Data will not be lost.
10. How to configure the installation of applications on the SD card?
1) useSparePartsfromxGETSx
2) use applications for transfer to a memory card such asВ® Move2SD EnablerandSDMove
3a) For firmware with Cyanogen Mod - Go to "Settings" ->"CyaogenMOD" ->"Applications" ->"Allow moving", put a check mark; you can experiment with the installation site in the same place.
3b) Settings ->Applications ->Application Management ->Next, select the program and click "Move to SD card"
11. How to get ROOT on firmware? - On all new firmware, superuser rights (root rights, administrator rights) are available initially and you do not need to receive them again. For "Stock" - immediately after the firmware is rebooted and in the MAGLDR menu select the item "AD Hard reset", after that the ROOT works. You can also try to get root using the program z4root + one more program SuperOneClick
12. Where can I additionally read about porting progress? - xda-developers branch (English forum)
13. Convenient work with the terminal and ADB - download and unpack, following the necessary instructions, no need to install.
14. I can not charge the communicator in the off state - In MAGLDR this can not be done. This is a known bug MAGLDR - HD2 not charging in the off state. Therefore, the MAGLDR version 1.13 has an automatic switch-on when the power is connected. In previous versions, if you have a problem, you need to wrap the battery.
As an alternative to MAGLDR, you can use the CLK bootloader, it allows you to charge the HD2 in the off state.
15. Is it possible to update the firmware without losing data? - Only in firmware versions for CWM recovery. Go to the CWM recovery execute item wipe dalvik cache as well as point wipe cache (paragraph wipe data Do not touch) and install the ZIP of the new firmware version via CWM recovery. At the same time, all settings and applications will remain in place.
16. Build / disassemble system.img and boot.img - in windows , in linux
17. When downloading files to a memory card via MAGLDR in "MassStg USB" mode, the transfer often hangs - this is a problem of MAGLDR 1.13, especially manifested when there is an ext partition. Use the removable disk mode in CWM recovery (while charging via USB) or copy files through a card reader.
18. On the support of high-capacity batteries - in all the latest (at the end of March) cores (and therefore the firmware), there was full support for official high-capacity batteries. Informal batteries also work, but there may be problems with charging and displaying the current charge. It is best to charge until the current becomes zero, you can check it with the program Current widget . When changing the battery, it is desirable to reset the battery statistics, i.e. perform Wipe Battery Stat in CWM before downloading the firmware. If a “big” battery sits as fast as a small one, a charge is probably incorrectly displayed, a reboot can help.
19. How to change the images that appear when loading HD2? - when booting HD2 can appear up to four different images. The first 3 of them are static, the last is dynamic (animation). The first image is called Boot Screen, the second is Splash Screen.
Instructions for replacing images
When HD2 is loaded may not appear all 4 images, if some of them are missing or damaged, the system just skips it without any indication. The third and fourth images are usually present. If you have a load only 3 images, then, most likely, there is no Boot Screen or Splash Screen. To determine which of them is missing, you can ask them the following instructions. If there is no third image, the boot device instead of displaying images will show MAGLDR long menu with the last line "Go Go Go". For replacement Boot Splash screen and say thank youStanislav ( his original message ).
1. Download archive to PCBMP2NBH.zip. Create an empty folder on the PC with any name, put 3 files in it: "nbimg.exe", "BMP2NBH 1st Boot.exe" and "1boot.bmp". The first can be obtained from the archive. The third is to get it yourself. Getting1boot.bmp:2. Run the file "BMP2NBH 1st Boot.exe".
3. Two files will appear next to each other: "1boot.bmp.nb" and "1boot.bmp.nbh"
The file "1boot.bmp.nb" can be deleted, it is not needed, but does not interfere.
4. In the downloaded BMP2NBH.zip archive, find the ROMUpdateUtility.zip file (Russified custom flash driver) and unzip it to any folder on the PC.
5. Copy the 1boot.bmp.nbh file to the same folder.
6. Go to the SPL (bootloader, bootloader, mattress): on the device completely turned off, hold down the volume down key and briefly press the power key.
7. After the color bars (mattress) appear on the screen, we connect the KVM to the PC (USB will appear in the bottom bar).
8. Flash Boot Screen: from the folder with the custom flash driver, launch the ROMUpdateUtility.exe file and follow the instructions on the PC screen.
1. Download archive to PCBMP2NBH.zip. Create an empty folder on the PC with any name, place 3 files in it: "nbimg.exe", "BMP2NBH 2nd Splash.exe" and "2splash.bmp". The first can be obtained from the archive. The third is to get it yourself. Getting2splash.bmp:2. Run the file "BMP2NBH 2nd Splash.exe".
3. Two files will appear next to you: "2splash.bmp.nb" and "2splash.bmp.nbh".
The file "2splash.bmp.nb" can be deleted, it is not needed, but does not interfere.
4. In the downloaded BMP2NBH.zip archive, find the ROMUpdateUtility.zip file (Russified custom flash driver) and unzip it to any folder on the PC.
5. Copy the file "2splash.bmp.nbh" to the same folder.
6. Go to the SPL (bootloader, bootloader, mattress): on the device completely turned off, hold down the volume down key and briefly press the power key.
7. After the color bars (mattress) appear on the screen, we connect the KVM to the PC (USB will appear in the bottom bar).
8. Flash Splash Screen: from the folder with the custom flash driver, launch the ROMUpdateUtility.exe file and follow the instructions on the PC screen.
Several pre-made Splash Screen:
This animation is an archive with special content. To change the boot animation is enough withRoot explorer'a (or using any other file manager with root access, for example, usingEStrongs File Explorer, in the settings you need to remember to enable root access) file/system/media/bootanimation.zip(if it is not there, then the filesystem / customize / resource / bootanimation.zip) replace with any other. Various bootanimation.zip animations can be found on the Internet, as well as simply pulled out of any other ZIP firmware, simply unzip it, the file will be in the folder/system/media/bootanimation.ziporsystem / customize / resource / bootanimation.zip.
If you want to take the animation from another device, then the main thing to remember is that its resolution should coincide with that of HD2, namely 480x800.
It is a very complicated procedure and can be replaced only under Linux OS. The image itself is located in the initrd.gz file, which is part of the firmware and is in the boot (boot) partition along with the kernel. The file is called logo.rle - this is a graphical format for Linux. Detailshere. Instructions for changing the image.
Boot Screen Replacement
1. Download archive to PCBMP2NBH.zip. Create an empty folder on the PC with any name, put 3 files in it: "nbimg.exe", "BMP2NBH 1st Boot.exe" and "1boot.bmp". The first can be obtained from the archive. The third is to get it yourself. Getting1boot.bmp:
1. Method. Download the desired image from the Internet.
At the same time the choice is limited, but no effort is needed. Simply upload any image you like, located at the following link:google search "HTC HD2 Splash Screen" with parameters 480x800, BMP. Before using the image, do not forget to rename the image to "1boot.bmp" (you must enablefile extension display function).
2. The way. Find any image you like and bring it in the desired format yourself.
Any image with the following parameters will be suitable for the boot image:
- the name "1boot" (without quotes);
- BMP format;
- 480x800 resolution;
- color depth 24 bits.
To convert an image to this type, you can use most graphic editors for PC, for example, Photoshop.
At the same time the choice is limited, but no effort is needed. Simply upload any image you like, located at the following link:google search "HTC HD2 Splash Screen" with parameters 480x800, BMP. Before using the image, do not forget to rename the image to "1boot.bmp" (you must enablefile extension display function).
2. The way. Find any image you like and bring it in the desired format yourself.
Any image with the following parameters will be suitable for the boot image:
- the name "1boot" (without quotes);
- BMP format;
- 480x800 resolution;
- color depth 24 bits.
To convert an image to this type, you can use most graphic editors for PC, for example, Photoshop.
3. Two files will appear next to each other: "1boot.bmp.nb" and "1boot.bmp.nbh"
The file "1boot.bmp.nb" can be deleted, it is not needed, but does not interfere.
4. In the downloaded BMP2NBH.zip archive, find the ROMUpdateUtility.zip file (Russified custom flash driver) and unzip it to any folder on the PC.
5. Copy the 1boot.bmp.nbh file to the same folder.
6. Go to the SPL (bootloader, bootloader, mattress): on the device completely turned off, hold down the volume down key and briefly press the power key.
7. After the color bars (mattress) appear on the screen, we connect the KVM to the PC (USB will appear in the bottom bar).
8. Flash Boot Screen: from the folder with the custom flash driver, launch the ROMUpdateUtility.exe file and follow the instructions on the PC screen.
Splash Screen Replacement
1. Download archive to PCBMP2NBH.zip. Create an empty folder on the PC with any name, place 3 files in it: "nbimg.exe", "BMP2NBH 2nd Splash.exe" and "2splash.bmp". The first can be obtained from the archive. The third is to get it yourself. Getting2splash.bmp:
1. Method. Download the desired image from the Internet.
At the same time the choice is limited, but no effort is needed. Simply upload any image you like, located at the following link:google search "HTC HD2 Splash Screen" with parameters 480x800, BMP. Before using the image, do not forget to rename the image to "2splash.bmp" (you need to enablefile extension display function).
2. The way. Find any image you like and bring it in the desired format yourself.
Any image with the following parameters will be suitable for the boot image:
- the name "2splash" (without quotes);
- BMP format;
- 480x800 resolution;
- color depth 24 bits.
To convert an image to this type, you can use most graphic editors for PC, for example, Photoshop.
At the same time the choice is limited, but no effort is needed. Simply upload any image you like, located at the following link:google search "HTC HD2 Splash Screen" with parameters 480x800, BMP. Before using the image, do not forget to rename the image to "2splash.bmp" (you need to enablefile extension display function).
2. The way. Find any image you like and bring it in the desired format yourself.
Any image with the following parameters will be suitable for the boot image:
- the name "2splash" (without quotes);
- BMP format;
- 480x800 resolution;
- color depth 24 bits.
To convert an image to this type, you can use most graphic editors for PC, for example, Photoshop.
3. Two files will appear next to you: "2splash.bmp.nb" and "2splash.bmp.nbh".
The file "2splash.bmp.nb" can be deleted, it is not needed, but does not interfere.
4. In the downloaded BMP2NBH.zip archive, find the ROMUpdateUtility.zip file (Russified custom flash driver) and unzip it to any folder on the PC.
5. Copy the file "2splash.bmp.nbh" to the same folder.
6. Go to the SPL (bootloader, bootloader, mattress): on the device completely turned off, hold down the volume down key and briefly press the power key.
7. After the color bars (mattress) appear on the screen, we connect the KVM to the PC (USB will appear in the bottom bar).
8. Flash Splash Screen: from the folder with the custom flash driver, launch the ROMUpdateUtility.exe file and follow the instructions on the PC screen.
Several pre-made Splash Screen:
To flash the Splash Screen data, you need to transfer the HD2 to the mattress (download the bootloader), connect the USB cable to your PC and run the CustomRUU.exe file on the PC.WinDroid, HTC_Campaign_YOU_Leo, Energystar, Girl, Moscow, their screenshots can be viewedhere. Also, boot images can be found on the English-speaking forum XDA-developershereorhere.
Replacing boot animation
This animation is an archive with special content. To change the boot animation is enough withRoot explorer'a (or using any other file manager with root access, for example, usingEStrongs File Explorer, in the settings you need to remember to enable root access) file/system/media/bootanimation.zip(if it is not there, then the filesystem / customize / resource / bootanimation.zip) replace with any other. Various bootanimation.zip animations can be found on the Internet, as well as simply pulled out of any other ZIP firmware, simply unzip it, the file will be in the folder/system/media/bootanimation.ziporsystem / customize / resource / bootanimation.zip.
If you want to take the animation from another device, then the main thing to remember is that its resolution should coincide with that of HD2, namely 480x800.
Replacing the third boot image
It is a very complicated procedure and can be replaced only under Linux OS. The image itself is located in the initrd.gz file, which is part of the firmware and is in the boot (boot) partition along with the kernel. The file is called logo.rle - this is a graphical format for Linux. Detailshere. Instructions for changing the image.
Instructions for creating an ext partition without a PC through CWM recovery
- On the communicator should be installed ClockworkMod recovery.
- The memory card must be installed in the communicator.
- Login to CWM recovery.
For MAGLDR: on the switched off communicator, hold down the power key and DO NOT release it until the menu appears, use the volume keys to select "AD recovery", press the call accept key.
For cLK: on the switched off communicator, briefly press the power key and hold down the "Home" key until the cLK menu appears. Next, it will automatically download CWM recovery.
- CWM recovery will boot.
- Go to the "advanced" menu.
- Select "Partition SD card".
- Select in the first window 1024M and in the second 0M (First - the size of the EXT3 partition created on the memory card, the second - the size of the Swap partition, if you install 0 MB, the partition will not be created).
- While creating partitions, in no case do not take any action with the communicator.
- The section is created, we return to the main menu with the "Back" button.
- To exit CWM recovery, click "reboot system now".
- The memory card must be installed in the communicator.
- Login to CWM recovery.
For MAGLDR: on the switched off communicator, hold down the power key and DO NOT release it until the menu appears, use the volume keys to select "AD recovery", press the call accept key.
For cLK: on the switched off communicator, briefly press the power key and hold down the "Home" key until the cLK menu appears. Next, it will automatically download CWM recovery.
- CWM recovery will boot.
- Go to the "advanced" menu.
- Select "Partition SD card".
- Select in the first window 1024M and in the second 0M (First - the size of the EXT3 partition created on the memory card, the second - the size of the Swap partition, if you install 0 MB, the partition will not be created).
- While creating partitions, in no case do not take any action with the communicator.
- The section is created, we return to the main menu with the "Back" button.
- To exit CWM recovery, click "reboot system now".
What are Data2ext, A2SD + and how do they differ
ext-partition - a section specially created on the memory card that is used to install programs and user data in it on firmware supporting A2SD +, A2SD, Data2ext methods
A2SD is a function (script) that allows you to automatically install applications on a memory card in a specially created ext-partition (formatted as ext2, ext3 or ext4). It is one of the methods for solving the problem of small amount of internal memory on HD2.
A2SD + is the same as A2SD, but not only the application itself is recorded in the ext-partition, but also all its data, including cache (can lead to a decrease in the resource of the memory card). It is the most effective method of saving (expanding) space on a memory card.
Data2ext - the method by which the entire / data folder is mounted (redirected), that is, when checking the memory, you can see the size of ext + phone memory
If you have an ext partition, then when you install the application in the "phone memory" it is automatically forwarded to the ext partition. Those. The system says that the application is in the internal memory, and in fact in the ext section on the memory card. When you write an application to a memory card (this will be written in the system), applications are transferred to the FAT partition.
A2SD + does not replace ext partition the internal memory, it only replaces some of the folders are written applications. Here you are in the file manager to find the root of the internal memory, data folder, and so this folder and have the "Internal memory" that shows the android. To relieve her some folders from it forwarded to the ext partition (sd-ext folder). You can redirect the entire data folder in the ext partition (this script is called Data2ext, in this case, ext replaces internal memory and android will be shown in the internal memory of 1GB), but it cherevato system performance and stability, as this system folder and for-and large it can not be transferred to an external medium.
There are firmware with Data2ext script, yes there will not be such a problem with clogging up the internal memory like on A2SD +, but Data2ext is used only in cases of emergency, in very large firmware, when the firmware does not physically fit into the internal memory.
A2SD is a function (script) that allows you to automatically install applications on a memory card in a specially created ext-partition (formatted as ext2, ext3 or ext4). It is one of the methods for solving the problem of small amount of internal memory on HD2.
A2SD + is the same as A2SD, but not only the application itself is recorded in the ext-partition, but also all its data, including cache (can lead to a decrease in the resource of the memory card). It is the most effective method of saving (expanding) space on a memory card.
Data2ext - the method by which the entire / data folder is mounted (redirected), that is, when checking the memory, you can see the size of ext + phone memory
If you have an ext partition, then when you install the application in the "phone memory" it is automatically forwarded to the ext partition. Those. The system says that the application is in the internal memory, and in fact in the ext section on the memory card. When you write an application to a memory card (this will be written in the system), applications are transferred to the FAT partition.
A2SD + does not replace ext partition the internal memory, it only replaces some of the folders are written applications. Here you are in the file manager to find the root of the internal memory, data folder, and so this folder and have the "Internal memory" that shows the android. To relieve her some folders from it forwarded to the ext partition (sd-ext folder). You can redirect the entire data folder in the ext partition (this script is called Data2ext, in this case, ext replaces internal memory and android will be shown in the internal memory of 1GB), but it cherevato system performance and stability, as this system folder and for-and large it can not be transferred to an external medium.
There are firmware with Data2ext script, yes there will not be such a problem with clogging up the internal memory like on A2SD +, but Data2ext is used only in cases of emergency, in very large firmware, when the firmware does not physically fit into the internal memory.
About memory expansion and ext partitions
What is ext (ext2 /ext3/ext4)? - file systemcoreslinux. ext2 is the oldest filesystem (the oldest doesn’t mean bad), ext3 updates it with journaling support, ext4 is the latest version of the filesystem, it provides good work with large files (if there are many large files in the system, then ext4 provides more speed).
Why journaling on HD2 and what could it cause?
Why do I need to create some partitions on the memory card? In the European version of HD2 to work with Android, there is not enough internal memory, so a partition in the Linux format is created on the memory card, which serves to expand this memory.
What is the size of the ext partition? - from 512MB to 2GB. It is recommended to create a partition on 1GB.
Where better to put applications in ext or just transfer to a memory card?How to solve the problems of small amount of internal memory on HD2?
internal memory expansion methods
1) The firmware that supports script A2SD + (this support can be implemented in any firmware). Create a section ext (ext2 / ext3 / ext4) on the memory card. The specific type of file system is selected from its own reasons and on the basis of support in the operating system kernel. It is recommended to create ext partition 1GB capacity, but it is possible and different size. Moreover, if you have created a profile, for example, in GB, that is available will be slightly smaller because a certain amount of memory allocated to the system needs. After loading the OS script automatically activated (in the firmware that supports script A2SD +). Now when the application is installed to the internal memory, it will automatically be installed in the ext partition and all the data that it will create, will also be recorded in the ext partition. In fact, not all the data generated by the application are recorded in the ext partition, so when you install the application amount of the internal memory will be reduced, but not enough. Note after creating ext partition volume of internal memory will not change. View ext partition can not be standard means. The volume of this section can be seen, for example, in the programquick system info. If the program in ap2sd does not show the volume of the partition, then it does not work. Most likely the section was not properly created.
2) Data2SD. The method is similar to the previous one, but for expanding the memory, a specially created partition is used, which requires full formatting of the memory card, but the image data.img.
space saving methods
3) transferring the application to the memory card. See paragraph 10 of this FAQ, in addition, you can give some advice. In the settings in the application management, you can transfer the application to the memory card, but only after the installation. In this case, the Transfer application is incomplete, but a certain amount of memory can be saved. As well it can be done with the help of programs like A2SD. The disadvantage of this method is that for the initial installation of applications still need a place in the internal memory.
4) If you have firmware with Cyanogen mod, then there is an item in its settings: where to install applications. You need to select a memory card as an installation location.
Why journaling on HD2 and what could it cause?
Why do I need to create some partitions on the memory card? In the European version of HD2 to work with Android, there is not enough internal memory, so a partition in the Linux format is created on the memory card, which serves to expand this memory.
What is the size of the ext partition? - from 512MB to 2GB. It is recommended to create a partition on 1GB.
Where better to put applications in ext or just transfer to a memory card?
advantages and disadvantages of each method
On ext:
+ When the phone is connected in drive mode, the storage of all programs is not disabled and they remain accessible.
+ The probability of data loss is minimal if logging is not disabled in the firmware (sd boost).
+ Net speed is higher, since the native ext2,3,4 file system (and even more so ReiserFS).
+ The operation scheme of A2SD + and other partition mounts allows more data to be transferred to the partition.
- It is necessary to immediately allocate a certain space to a section, if it is not fully used, this space cannot be used to store files, music, etc. (well, in usual ways)
- Requires the correct layout of the sections of the map.
- It is impossible to work with data from under Windows (is it a minus?)
- The need to keep the mounted partition on the map slightly reduces the response time of the system and the corresponding programs.
To map:
- When you connect the phone in drive mode, the storage of all programs is turned off and they are unavailable until the card is turned off correctly.
- The probability of data loss is high due to the peculiarities of the vFAT file system, especially when connecting the phone in drive mode.
- Work speed is lower.
- In any case, basically, at least 10-20% of the program volume goes to the main memory.
+ The space for the transferred programs is allocated in proportion to the required for the program automatically (it is allocated from vFAT therefore it only takes as much as necessary).
+ Does not require correct layout of map sections.
+ Easy to work with data from under Windows (is it a plus?)
+ No need to keep the mounted partition on the map, does not slow down the response time.
+ When the phone is connected in drive mode, the storage of all programs is not disabled and they remain accessible.
+ The probability of data loss is minimal if logging is not disabled in the firmware (sd boost).
+ Net speed is higher, since the native ext2,3,4 file system (and even more so ReiserFS).
+ The operation scheme of A2SD + and other partition mounts allows more data to be transferred to the partition.
- It is necessary to immediately allocate a certain space to a section, if it is not fully used, this space cannot be used to store files, music, etc. (well, in usual ways)
- Requires the correct layout of the sections of the map.
- It is impossible to work with data from under Windows (is it a minus?)
- The need to keep the mounted partition on the map slightly reduces the response time of the system and the corresponding programs.
To map:
- When you connect the phone in drive mode, the storage of all programs is turned off and they are unavailable until the card is turned off correctly.
- The probability of data loss is high due to the peculiarities of the vFAT file system, especially when connecting the phone in drive mode.
- Work speed is lower.
- In any case, basically, at least 10-20% of the program volume goes to the main memory.
+ The space for the transferred programs is allocated in proportion to the required for the program automatically (it is allocated from vFAT therefore it only takes as much as necessary).
+ Does not require correct layout of map sections.
+ Easy to work with data from under Windows (is it a plus?)
+ No need to keep the mounted partition on the map, does not slow down the response time.
internal memory expansion methods
1) The firmware that supports script A2SD + (this support can be implemented in any firmware). Create a section ext (ext2 / ext3 / ext4) on the memory card. The specific type of file system is selected from its own reasons and on the basis of support in the operating system kernel. It is recommended to create ext partition 1GB capacity, but it is possible and different size. Moreover, if you have created a profile, for example, in GB, that is available will be slightly smaller because a certain amount of memory allocated to the system needs. After loading the OS script automatically activated (in the firmware that supports script A2SD +). Now when the application is installed to the internal memory, it will automatically be installed in the ext partition and all the data that it will create, will also be recorded in the ext partition. In fact, not all the data generated by the application are recorded in the ext partition, so when you install the application amount of the internal memory will be reduced, but not enough. Note after creating ext partition volume of internal memory will not change. View ext partition can not be standard means. The volume of this section can be seen, for example, in the programquick system info. If the program in ap2sd does not show the volume of the partition, then it does not work. Most likely the section was not properly created.
2) Data2SD. The method is similar to the previous one, but for expanding the memory, a specially created partition is used, which requires full formatting of the memory card, but the image data.img.
space saving methods
3) transferring the application to the memory card. See paragraph 10 of this FAQ, in addition, you can give some advice. In the settings in the application management, you can transfer the application to the memory card, but only after the installation. In this case, the Transfer application is incomplete, but a certain amount of memory can be saved. As well it can be done with the help of programs like A2SD. The disadvantage of this method is that for the initial installation of applications still need a place in the internal memory.
4) If you have firmware with Cyanogen mod, then there is an item in its settings: where to install applications. You need to select a memory card as an installation location.
22. Accelerometer (G-sensor) is calibrated only with the screen down, how to fix it? - decision
23. How to make streaming video work? - CIFS protocol is responsible for this, which supports most of the cores. Those. All modern firmware support streaming video playback. If this function does not work on your firmware, replace the kernel.
24. What is config.txt and where is it located? It lies in the root of the memory card in the FAT section (if you have others).
Explanations
Config.txt - file for specifying some additional parameters of firmware download if supported by the init script
It is an ordinary text file placed in the root of the fat section on a memory card with the name config.txt:
similar to the following:
ppp_mode = 0
gps_zone = europe
sd_boost = 1
Usually through the config is given:
radio type - PPP or RMNET
GPS area
It is an ordinary text file placed in the root of the fat section on a memory card with the name config.txt:
similar to the following:
ppp_mode = 0
gps_zone = europe
sd_boost = 1
Usually through the config is given:
radio type - PPP or RMNET
GPS area
26. Replace files in app and framework folders in SQUASHED firmware - instruction + instructions for replacing files in SquashFS firmware
27. Have you fixedglitch with multitouch(on WM there were problems)? - the problem was not fixed, just like on Windows Mobile, on Android, the points close to the coordinate stick together. This is a hardware disadvantage of HD2, it can not be fixed by software. It appears absolutely on all Android OS, Windows Mobile and Windows Phone 7 firmwares. But there are very rare HD2 samples that do not have this glitch.
28. I can not understand what the abbreviations in the names of the firmware and what they mean? - mini dictionary
29. WhyQuadrantgives such bad results? - Quadrant is a synthetic test and does not display the real performance of the firmware and the device as a whole. In this topic, it is not recommended to use this program to measure the speed of the firmware, since The actual results are very often very different.
30. What is ClockworkMod recovery (CWR / DVR or CWM)? This is an enhanced recovery version (HD2 does not have the usual recovery), which allows you to make a full backup of the firmware, replace system files, install firmware without a PC, easily install fixes and patches, do wipe and create an ext3 partition on a memory card. Supported in MAGLDR version 1.13 and higher, but not originally installed. CWM installs only ZIP firmware. You can learn more about CWM for HD2 and download it in the Android OS firmware manual.
31. All kind of small. How to change the "resolution" of the screen and what to do if the applications do not run in full screen -
decision
The first way.
Edit the build.prop file that is in root / system
Open it with any text editor and changero.sf.lcd_density = 200onro.sf.lcd_density = 240(this can be done, for example, in the root explorer file manager (open in text editor)
lcd_density - This is a parameter that allows you to change the resolution of the interface (the "density" of interface elements). Its standard value is 240.
Second way
In the Spare Parts program, in the last menu item, remove the 'Campatibility Mode' checkbox and reboot.
Third way
Change using the programВ® LCD Density Changerthe density parameter to the desired value.
Edit the build.prop file that is in root / system
Open it with any text editor and changero.sf.lcd_density = 200onro.sf.lcd_density = 240(this can be done, for example, in the root explorer file manager (open in text editor)
lcd_density - This is a parameter that allows you to change the resolution of the interface (the "density" of interface elements). Its standard value is 240.
Second way
In the Spare Parts program, in the last menu item, remove the 'Campatibility Mode' checkbox and reboot.
Third way
Change using the programВ® LCD Density Changerthe density parameter to the desired value.
explanations
After flashing the license for Navitel gets off. The OEM key is reregistered 3 times for whatever reason ( official site ). For the activation of the program meets the file build.prop. thank OmSoft for the information provided. To save the license when changing the firmware, you need to save the file /system/build.prop and /system/build.*.prop (if there is one) from the old firmware with the installed Navitel license. In this file, the following lines affect the registration of Navitel:
In principle, you can save only them, and then manually rewrite.
Comment. If the parameter ro.product.board matters different from bravo , then in some firmwares the auto-rotate of the screen stops working.
ro.product.name
ro.product.device
ro.product.board
ro.build.product
ro.product.model
ro.product.brand
ro.product.device
ro.product.board
ro.build.product
ro.product.model
ro.product.brand
In principle, you can save only them, and then manually rewrite.
Comment. If the parameter ro.product.board matters different from bravo , then in some firmwares the auto-rotate of the screen stops working.
34. I only have 412MB of RAM, is this normal? - appears set to 412 MB, 512 MB, in some in some Android firmware amount of available memory. Regardless of this, in all the Android firmware only ~ 412 MB of memory available to the operating system. Volume "available memory", which is displayed in the settings Android'a registered in the operating system kernel, it has registered to HTC (kernel for HD2 is based on the original nuclei of Android devices from HTC), our developers could not use more. But this does not mean that the remaining 150 MB are doing nothing, they just can not use the operating system and therefore the user.
HTC allocates the remaining memory for the video accelerator. And do not forget that the bootloader (SPL) and the radio module also use RAM. And 412 MB is the amount of RAM available for the Android operating system, i.e. all that remains of the above modules.
35. Where to see the kernel version? - download Android ->go to Settings ->About phone ->Kernel version
36. The kernel is not installed, writesdevice not found - decision
37. The application is installed, but does not start - transfer the application to the internal memory in the settings.
38. I can not synchronize my smartphone with a computer, HTC Sync does not work in my XXX firmware - HTC Sync is intended only for firmware with Sense. As an analogue for other firmware you can use DroidExplorer or MyPhoneEXplorer
39. How to make the screen turn on only by pressing a buttonpower? - edit all files / system / usr / keylayout / * kl by deleting the inscriptions WAKE and WAKE_DROPPED in the lines from HOME, BACK, CALL, MENU. After that, the screen will light up only by pressing a button. power However, the key illumination still lights up and does not go out. The method is not perfect, but the other has not yet been found.
40. I upgraded to another firmware, I connected to the android Market and all programs from the previous firmware start to automatically load, how to remove it? - you need to set up synchronization with Google. When logging in to your phone account, you need to remove the checkmark from the “Backing up data using a Google Account” item.
41. After installing a new firmware application miraculously appeared again? - if you use the ext partition and have not formatted it, the applications installed on the previous firmware will be restored. It can also happen through htcsense.com (to get rid of this you just need to disable synchronization with the htcsense.com service).
42. There is no Russian in the dialer, how to add it? - In the standard call from Google there is no Russian language and you can’t add it there. You can use third-party dialers, for example, Dialer one or Fast dialer . To search for other dialers use Software catalog - Android OS and topic SEARCH software for Android OS .
For those who do not know what a standard dialer from Google looks like, it goes by default in Cyanogen mod firmware (there is Russification in assemblies in 2012), AOSP and Nexus firmware.
43. When flashing through DAF.exe, it constantly gives an errorUSB init failed - most likely before the firmware you used MassStg USB, reboot the device.
44. When you call, regardless of the selected volume level - the volume is always at the maximum.
Method from saap
The problem is definitely missing in the TyphooN CyanogenMod 7 firmware starting from version 2.5. But in recent versions, it has begun to appear again. Also, the problem is missing in the firmware NexusHD2-Gingerbread version 2.4 and higher.
OnxdaThere is a fix volume, but it is damp and works badly. Other solutions:
1) click on the speaker. We end the conversation, but do not exit the dialer, we call anyone - everything is fine with the sound
2) After dialing - the rocker sound DOWN / UP - then everything is fine, but it must be done every time.
3) program auto-hands-free - paid, but the most adequate. There is in the form of automatic switching on Dynamics, when the phone is in a mountain position.
Solutions 1 and 3 are the same, but 1 is manual, 3 is automatic
Method fromeseregin
And you can also try installing another audio driver.
HTC HD2 - Android NAND + MAGLDR (Post # 8764848)
The problem is definitely missing in the TyphooN CyanogenMod 7 firmware starting from version 2.5. But in recent versions, it has begun to appear again. Also, the problem is missing in the firmware NexusHD2-Gingerbread version 2.4 and higher.
OnxdaThere is a fix volume, but it is damp and works badly. Other solutions:
1) click on the speaker. We end the conversation, but do not exit the dialer, we call anyone - everything is fine with the sound
2) After dialing - the rocker sound DOWN / UP - then everything is fine, but it must be done every time.
3) program auto-hands-free - paid, but the most adequate. There is in the form of automatic switching on Dynamics, when the phone is in a mountain position.
Solutions 1 and 3 are the same, but 1 is manual, 3 is automatic
Method fromeseregin
And you can also try installing another audio driver.
HTC HD2 - Android NAND + MAGLDR (Post # 8764848)
decision
There are two ways described below. They can be used both together and separately.
Method number 1. Use new GPS driver from Tytung - GPS_Libraries_v2.1_NMEA.zip - version for most firmware, if not working, then use version GPS_Libraries_v2.1_RPC.zip - Fits most Sense firmwares. Install via CWM. Author's topic on XDA-developers . This driver works on all Android 2.3 (2.2) firmwares, precisely uses AGPS (with Internet access available) and allows you to reduce a cold start to half a minute.
Also for the latest driver versions it is recommended to usefollowing recommendations, you can simply add / remove lines in the /system/etc/gps.conf file. If you use the second method, then you need to do it after installing the patch.
Method number 2 - helps not all.
For CWM / ZIP firmware users, simply install the following ZIP via CWM:RUSSIA.zip- This is the AGPS patch for Russia version 1.2. Patches for other countries can be downloadedhere
For users of DAF firmware: copy and replace the file /system/etc/gps.conf from the archive into a similar folder in the HD2 internal memory.
Author's topic on XDA-developers.
Method number 1. Use new GPS driver from Tytung - GPS_Libraries_v2.1_NMEA.zip - version for most firmware, if not working, then use version GPS_Libraries_v2.1_RPC.zip - Fits most Sense firmwares. Install via CWM. Author's topic on XDA-developers . This driver works on all Android 2.3 (2.2) firmwares, precisely uses AGPS (with Internet access available) and allows you to reduce a cold start to half a minute.
Also for the latest driver versions it is recommended to usefollowing recommendations, you can simply add / remove lines in the /system/etc/gps.conf file. If you use the second method, then you need to do it after installing the patch.
Method number 2 - helps not all.
For CWM / ZIP firmware users, simply install the following ZIP via CWM:RUSSIA.zip- This is the AGPS patch for Russia version 1.2. Patches for other countries can be downloadedhere
For users of DAF firmware: copy and replace the file /system/etc/gps.conf from the archive into a similar folder in the HD2 internal memory.
Author's topic on XDA-developers.
47. On my XXX firmware there are very noticeable stepped gradients, how to fix it?
decision
In the latest firmware, the problem should be absent, the problem is fixed. HD2 cannot physically display more than 65 thousand colors, since he has a 16-bit cable connected to the screen. Older firmwares were designed for more colors, so stepped gradients were obtained.
You can get rid of stepped gradients only by changing all the images in the applications. For example, you can change the color of the wallpaper to 16 bits. In addition, on different firmware gradient gradation is manifested in different ways.
Cotulla quote
More in August 2010 padrecc provided information from Cotulla :
In the screen loop, as far as I know, HD2 has 16 contacts for this case (although it could be 18, but this is not so) = 16bit this is the maximum color depth. 65536 flowers maximum. Nexus is the same.
23:51 manusfreedom anybody can confirm me that our lcd panel is 16bpp?
23:51 gauner1986 it's only 65535 colors
23:52 Cotulla 16 wires
23:54 ali1234 can't speak for but I know even though omap850 supports 18 bit, it’s not a red line. all panels ever seen there are 16 bit.
23:54 Cotulla and?
23:54 ali1234 the controller can emulate a 24 bit framebuffer
23:54 Cotulla most panels are 18 bit
23:54 Cotulla but connected only 16 wires
23:51 gauner1986 it's only 65535 colors
23:52 Cotulla 16 wires
23:54 ali1234 can't speak for but I know even though omap850 supports 18 bit, it’s not a red line. all panels ever seen there are 16 bit.
23:54 Cotulla and?
23:54 ali1234 the controller can emulate a 24 bit framebuffer
23:54 Cotulla most panels are 18 bit
23:54 Cotulla but connected only 16 wires
In the screen loop, as far as I know, HD2 has 16 contacts for this case (although it could be 18, but this is not so) = 16bit this is the maximum color depth. 65536 flowers maximum. Nexus is the same.
You can get rid of stepped gradients only by changing all the images in the applications. For example, you can change the color of the wallpaper to 16 bits. In addition, on different firmware gradient gradation is manifested in different ways.
49. Is there USB host support on HD2? - On May 26, a support core appeared, but USB charging and connecting to a computer does not work, read more here
50. Can I turn off USB charging? - not.
51. Can I add Cyanogen mod to my XXX firmware? - not. If this mod is not built in immediately, then you can’t add it.
52. In Sense firmware there is a mode "turned the phone over - the sound is turned off", how to implement it in other firmware? - use third-party applications, such as Starksoft G-App and RD Mute
53. Is it possible to record telephone conversations from the line on HD2? - Yes
how to do it?
Topic of discussion: HTC. Record telephone conversations from the line .
MIUI firmwares have a built-in call recording function, but the recording goes not from the line, but from the microphone, respectively, the interlocutor is almost unheard of.
In order to record from the line to MIUI and on other firmware you will need:
- Kernel with a special driver. Tytung cores support two-way writing from the line, starting with version 9. Rafpigna cores support writing from the 2.0 line.
- ProgramCallRecorder v1.0.27alpha build 5.apk
MIUI firmwares have a built-in call recording function, but the recording goes not from the line, but from the microphone, respectively, the interlocutor is almost unheard of.
In order to record from the line to MIUI and on other firmware you will need:
- Kernel with a special driver. Tytung cores support two-way writing from the line, starting with version 9. Rafpigna cores support writing from the 2.0 line.
- ProgramCallRecorder v1.0.27alpha build 5.apk
55. Photos of contacts are constantly blurred, how to fix? - disable synchronization of contacts with Google.
56. Is it possible to add programs and widgets from HTC Sense such as a clock, calendar, camera, album, etc. to the firmware without Sense? - no, these widgets and applications use the proprietary HTC framework, which is not in the firmware without Sense. But for many applications there are almost complete counterparts.
57. What is a CWM recovery ZIP and how can I replace system files with them? - small FAQ so the issue from xGETSx
58. Convert DAF to ZIP and vice versa - instruction from xGETSx
59. How to change the size of the system and cache? - these partitions are created with the CWM firmware and can be changed only by flashing the CWM (the internal memory is formatted and your old firmware is erased).
How to do it?
Download the archive with the flash driver of any CWM to the PC and unzip it to any folder. There will be a file flash.cfg something like this:The fourth line is the size of the system partition, the fifth is the size of the cache partition. "135M" - the size of the partition in megabytes. Change to the desired value and flash the CWM, while in the internal memory of the device, partitions of the specified volume will be created.
misc ya 1M
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 135M
cache ya 44M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 135M
cache ya 44M
userdata ya | asize | hr allsize
61. How to delete ext partition? - use the program on your PC SDFormatter , when formatting in the program menu, select "format size adjustment". If you do not have a device for reading memory cards, then this can be done through MAGLDR in mass storage mode.
62. How to format an ext partition?
Method number 1.Go to ClockworkMod recovery and run "mounts and storage ->format sd-ext "
Method number 2.Format with PC. To do this, you need to either connect to the PC in removable disk mode (it is supported by the MAGLDR bootloader - "USB MassStg" and CWM recovery - "mount USB storage"). Or remove the memory card and connect it to the computer through a card reader. Next, you need to format the ext partition with a PC. Under Linux, this can be done with built-in tools. And in Windwos you have to install a third-party program, for example, Paragon Hard Drive Manager.
63. How to change font type and size in firmware? - use programs В® Font Changer and В® Font Size .
64. In the MAGLDR bootloader in USB Flasher mode, the communicator does not connect to the PC - In order for the computer to correctly recognize the connected device, you need to install the driver (usually installed automatically) from the Windows Mobile Device Center (Microsoft ActiveSync) on the PC, or you can install the mobile device center itself, the driver will be installed with it.
65. I have Windows XP and when I try to install firmware via MAGLDR, I get errors all the time - decision
66. Android does not see the memory card (writes that it is damaged), although it works fine on other devices and on the PC - format the memory card using the program panasonic SDFormatter , when formatting in the program menu, select format size adjustment
67. How to access the Internet of a PDA on a PC via USB? - for firmware without Sense: solution for windows 7 , solution for windows xp . For firmware with Sense 2: install HTC sync on the PC (it is not necessary to synchronize) and when connecting the PDA to the PC, select "pass-through connection".
68. The phone sees the Wi-Fi network, but does not connect to it. - decision
69. How to improve the quality of the video? - will require a third-party application LG camera (paid), set the following settings in it: video format - mpeg4, codec - mpeg4, resolution 800 * 480, 3 MB bitrate, 30 frames per second, iso 800. Thanks for the advice tweakos
70. It was stitched on Android and the sensor stopped working on the screen - Android has nothing to do with it. In HD2, there is a loop under the power button that goes to the screen, it is subject to heavy wear, especially in TMOUS HD2. If the firmware WM tezhe symptoms, it will only help the service. Mechanical buttons - a weak point HD2
71. Calibration of the accelerometer (G-sensor) in firmware without Sense - decision from eastic
72. Convert MAGLDR ZIP firmware to cLK ZIP - instruction
73. I install widgets, but I can not install them on the desktop, they do not even appear in the list of available widgets - Widgets must be in the internal memory of the device, then they will be in the list of adding widgets.
74. In my XXX firmware sound is very quiet, how to increase? - the volume can be increased with the help of the DSP manager program built into most of the firmware; for the rest, an alternative variant is suitable: Volume +
75. When an incoming call instead of the interlocutor heard a crash, how to fix it? - root explorer delete the file /etc/firmware/default.acdb . A side effect may be a voice vote.
76. Accelerometer (G-sensor) does not work on Android, although WM is fine -
explanations
Silem
I encountered, like a few here, a non-working accelerometer (g-sensor) in most firmwares. On the other hand, the problem was analyzed, it was suggested that when replacing broken glass with HD2 in the SC, updated sensors are installed that are not perceived. My device was brought from the states and changed the screen on it or not, I do not know. but the sensor is not working.
That's why I decided to install the firmware port from fresh HTC devices in the hope that there are already fresh drivers.
I will please the owners of problematic devices - the BOYPPC-SHIFTPDA DESIRE HD V15 firmware saw and calibrated the sensor without problems.
Home tyrant
The situation with the G-sensor has cleared up. After studying the topic on XDA-Dev, in which there was a discussion of this problem, I found out the following:
Translated into Russian, this means that in HD2, produced after September 2010, there is a new type of sensors.
That is, the problem of its inoperability in Android is associated with the lack of the required module in the kernel.
I encountered, like a few here, a non-working accelerometer (g-sensor) in most firmwares. On the other hand, the problem was analyzed, it was suggested that when replacing broken glass with HD2 in the SC, updated sensors are installed that are not perceived. My device was brought from the states and changed the screen on it or not, I do not know. but the sensor is not working.
That's why I decided to install the firmware port from fresh HTC devices in the hope that there are already fresh drivers.
I will please the owners of problematic devices - the BOYPPC-SHIFTPDA DESIRE HD V15 firmware saw and calibrated the sensor without problems.
Home tyrant
The situation with the G-sensor has cleared up. After studying the topic on XDA-Dev, in which there was a discussion of this problem, I found out the following:
HTC HD2 built after 09/2010
Translated into Russian, this means that in HD2, produced after September 2010, there is a new type of sensors.
That is, the problem of its inoperability in Android is associated with the lack of the required module in the kernel.
78. The battery is very quickly discharged, the consumption in standby mode does not fall below 60 mA, how to calibrate it? - Thanks for the solution found Nutthell :
Charge your phone to 100% and (important) to 0mA according to indications Current widget (this is somewhere else half an hour after the green indicator lights up). After that - without disconnecting the charging - reboot into CWM recovery, go to the menu there Advanced and perform points Wipe Dalvik Cache and Wipe Battery Stat . Then, by pressing the end call key, you return to the main menu and select Reboot system KVM will reboot. Wait for the full load and 0mA for the indications of the Current widget and turn off charging.
FromSemyon but. Increased zhor can also be caused by third-party applications that do not allow to "fall asleep" KMK. In this case, you must either get rid of the parasite, or before each "sleep" to kill unnecessary applications.
FromSemyon but. Increased zhor can also be caused by third-party applications that do not allow to "fall asleep" KMK. In this case, you must either get rid of the parasite, or before each "sleep" to kill unnecessary applications.
Sample file default.xml
81. My device wakes up for a long time when I press the power button, it wakes up from standby for a long time, what should I do? - install the latest firmware or update the kernel in your firmware, there will already be included a patch so that the screen turns on quickly.
82. I have an ext partition, how to change the memory card without losing data? - you need to create an ext partition on the new map (better than the same size), and then copy the contents of the ext section into it from the old map. The same should be done with the rest of the contents of the memory card. The problem is that windows can't work with ext partitions. But the data can be transferred using Paragon Hard Drive Manager.
83. The player displays Russian tags incorrectly, how to fix it? -
decision
Method number 1.
Solution fromsumomo : you want to install fonts with a normal display of Russian letters in the encoding Win-1251. These fonts treat the display of Russian tags in a standard player. Fonts from the archive fonts.zip copy to the / system / fonts folder and reboot.
Method number 2.
Universal method. It consists in the conversion of tags in the desired format. This can be done, for example, using the programmp3tag. Android is based on Linux, so it does not understand standard Windows encodings.
Solution fromsumomo : you want to install fonts with a normal display of Russian letters in the encoding Win-1251. These fonts treat the display of Russian tags in a standard player. Fonts from the archive fonts.zip copy to the / system / fonts folder and reboot.
Method number 2.
Universal method. It consists in the conversion of tags in the desired format. This can be done, for example, using the programmp3tag. Android is based on Linux, so it does not understand standard Windows encodings.
85. When you click in the MAGLDR itemAD Recoverygives an error message1E FATAL HITand flashing does not help - Only flashing to the official Windows Mobile firmware will help. In this case, MAGLDR is removed and it will have to be reinstalled.
86. The current when charging all the time changes, before it was 300 mA, and now 50 - this is normal. When charging the battery, the current constantly decreases until it reaches zero - the battery is charged. The current varies exponentially from 900 mA (or more) to zero. At the same time, the current decreases very quickly, and at the end very slowly, the last percentages charge for a very long time - this is also normal.
87. The microphone when talking is too sensitive, the interlocutor can hear all the people around -
decision
On XDA-developers wrote a microphone fix. To install it - content archive copy to the communicator in the folder system / etc / firmware / replacing the files there. With this audio driver, the sound will be quieter, but the sensitivity of the microphone will be normal, the robotic voice and the loudness that does not change is also inherent in this driver. The fix is ​​already built into the core of Tytung r12 and accordingly into the cores based on it.
This fix allows the user to control the sensitivity of the microphone using the programHD2 Mic Control. You can also manually edit the microphone sensitivity value in the /etc/init.d/10mic_level file. Its default content is:
The first line - the sensitivity of the microphone in normal mode, the second - in hands-free mode. It is worth remembering that when setting a high sensitivity, an echo may appear.
This fix allows the user to control the sensitivity of the microphone using the programHD2 Mic Control. You can also manually edit the microphone sensitivity value in the /etc/init.d/10mic_level file. Its default content is:
echo '0 400'> / proc / mic_level
echo '1 600'> / proc / mic_level
echo '1 600'> / proc / mic_level
89. How to change the maximum and minimum frequency of the processor? - In the Cyanogen mod settings, as well as in the setCPU program, these frequencies are automatically detected and read from the core. You can change the CPU operating frequency limits only by replacing the core. Rafpigna cores support overclock up to 1.5 GHz.
90. Increasing the available internal memory, how to use the backup 24 MB? - small FAK from delphin73 .
91. How to make a full backup of the firmware, so that you can always return the firmware to its previous state? - The DAF firmware in any way. The ZIP firmware: it is necessary to go to the CWM recovery, to find there the item "backup and restore" and there choose "backup" - in this case on the memory card will create a full backup of firmware, including a copy ext section. If you save the backup folder, then later through the same CWM, you can restore that backup point "restore". And most importantly, a system partition size of the internal memory and HD2 ext partition on the memory card at the time of recovery backup should not be less than the size of the sections at the time of the backup firmware.
92. What should I do if the battery is completely discharged and the communicator does not even turn on? - the problem occurs only for MAGLDR users (the CLK allows charging in the off state). You can solve it by connecting the charging clock by 8. If this does not help, it will help
advice from maximglin
1. We take the device and connect to the outlet.
2. The light came on, but then the charge is not enough to enter the MAGLDR.
3. We juggle the battery and again connect to the outlet.
4. The light came on, but then the charge is not enough to enter the MAGLDR.
5. We juggle the battery and connect it to the outlet again.
And so on several times (many times, about 20), and then we try to load the OS. At some point, stop and give the device to turn on.
2. The light came on, but then the charge is not enough to enter the MAGLDR.
3. We juggle the battery and again connect to the outlet.
4. The light came on, but then the charge is not enough to enter the MAGLDR.
5. We juggle the battery and connect it to the outlet again.
And so on several times (many times, about 20), and then we try to load the OS. At some point, stop and give the device to turn on.
94. The operating system is unstable (constant reboots, processes crash), the OS or recovery is not loaded at all - if there were no errors in the firmware process, repeated firmware does not give anything, then most likely the problem is in the memory. In order to mark the broken memory cells install the official firmware WM. After that, repeat the installation of all components of Android. When installing recovery in the configuration of partitions in the internal memory, remove all the "ro" flags. Read more here .
95. How to make the alarm go off? - Update the android loader cLK to version 1.5.1.4 or higher, install the kernel with the built-in alarm clock fix (Tytung kernels support it from version r3.6 for Android 4 and from version 11.11.12 for Android 2.3), to the system section in the internal HD2 memory in the app folder, add the application SysAlarm.apk , set permissions as adjacent files and reboot the machine. After that, SysAlarm will appear in the application menu, with which you can set the alarm. Note: the alarm clock is triggered along with the loading of the operating system and it takes quite a long time, 2-3 minutes after the desired time has arrived.
96. Solving the problem of spontaneous short-term activation of the speakerphone when an incoming call - Install the following fix through recovery - Sound_fix.zip , it will replace the audio drivers in the firmware. Fix may not work on your firmware before using it be sure to do a full backup firmware . After installing the fix (audio driver replacement), the pulsed sound that sometimes appears in the speaker disappears. It occurs when an incoming call and in rare cases when working with multimedia applications. In addition, the bug will go away when, with an incoming call, the sound level is forced to the maximum regardless of the previous settings. Solution found Anton22 .
Comment. In the following cases:
- if you want to clean the internal memory, remove the tails from the custom firmware;
- in the event of problems flowing from one firmware to another;
- it is impossible to launch the firmware, while all other methods have been tried;
- to deal with broken memory blocks (bad blocks);
- and other cases not resolved;
The best way to cure errors is to install the official WM firmware. If you have"Gray"HD2 (not ROSTEST), then you need to install the firmware for your region. You can download the official firmware fromHTC official site, if you have a gray device, then you need to select on the official website the country for sales in which your device was intended. This can be determined throughthis service. Official Russian firmware can be downloaded from our forum.HTC HD2 - Original firmware. Latest official firmware for TMOUS -download.
In this case, you must completely abandon the use of the program (command) task29 (task29 working principle is not exactly known, use at your discretion)
The concepts common to all android-devices can be clarified inAndroid - Glossary . Popular questions about the operating system can be found in the topic. Android OS FAQ .
If users use unknown expressions, you can find them in the topic.Terms and jargon
Post has been editedSemyon - 15.04.13, 20:36
Lightweight Android 2.3 firmware
Classic Android from Google and its modifications
[10.11.12] [MAGLDR / cLK] NexusHD2-Gingerbread V3.3a [Tytung gb r16]
- - Based on the latest official firmware for Nexus One, Android 2.3.7, clean, fast, stable, everything works.
download:
Firmware:
Version for loader MAGLDR
Version for loader cLK
Additionally:
Author's topic on XDA-developers
Widescreen camera:MIUI_Camera_v15_update.zip(456.33 KB)
Firmware is required to be installed on a system partition of 135 MB in size. More about other sections:A2SD + is not initially supported, it is required to be delivered optionally, for this you need to install the following zip via CWM immediately after the firmwaredtapps2sd_2.7.5.2_signed.zip.
Version for loader MAGLDR
Version for loader cLK
Additionally:
Author's topic on XDA-developers
Widescreen camera:
MIUI_Camera_v15_update.zip(456.33 KB)Firmware is required to be installed on a system partition of 135 MB in size. More about other sections:
content flash.cfg
misc ya 1M
recovery rrecov | ro | nospr 5M recovery-raw.img
boot yboot | ro 5M
system ya 135M
cache ya 2M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr 5M recovery-raw.img
boot yboot | ro 5M
system ya 135M
cache ya 2M
userdata ya | asize | hr allsize
Long time not updated firmware
[12/06/11] [MAGLDR / cLK] [CWM] Redux v1.4 [Tytung r12.4]
[09/16/11] [CWM] PureGingerbread gpc hd2 v2.8e [Kernel own]
- - A mixture of several firmware, Android 2.3.5 (AOSP), fast, light, stable, odex'irovan.
download:
Firmware:
version of MAGLDR + patch for cLK
Additionally:
Author's topic on XDA-developers.
Firmware is required to be installed on the system partition of 85 MB. More about other sections (content of flash.cfg):
version of MAGLDR + patch for cLK
Additionally:
Author's topic on XDA-developers.
Firmware is required to be installed on the system partition of 85 MB. More about other sections (content of flash.cfg):
misc ya 1M
recovery rrecov | ro | nospr 5M recovery-raw.img
boot yboot | ro 5M
system ya 85M
cache ya 5M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr 5M recovery-raw.img
boot yboot | ro 5M
system ya 85M
cache ya 5M
userdata ya | asize | hr allsize
[09/16/11] [CWM] PureGingerbread gpc hd2 v2.8e [Kernel own]
- - pure official AOSP Android 2.3.5
download:
Firmware:
gpc hd2 gingerbread v2.8e.zip
Additionally:
Author's site, english translation
XDA-developers topic, the author did not update the cap there for a long time, but in the subject new firmware versions were laid out.
Firmware is required to install 135 MB on the system partition.
gpc hd2 gingerbread v2.8e.zip
Additionally:
Author's site, english translation
XDA-developers topic, the author did not update the cap there for a long time, but in the subject new firmware versions were laid out.
Firmware is required to install 135 MB on the system partition.
CyanogenMod based firmware. This is a series of popular firmware, based on which are released and firmware for HD2. Cyanogen mod is a tweaker. Modification of Android, which allows you to change the interface (top panel, lock screen, etc.) and system settings. There is supportby that. It also allows you to change the frequency of the processor, including overclocking it, and more.Video reviewappearance and features CM7.
FAQ on Cyanogen mod
1 ) Whatcm_bravo base? - Cyanogen mod development team officially released firmware for HD2 based on their fashion. Therefore ROM'odelov there are 2 ways to create a firmware Cyanogen mod for HD2. First, assemble the firmware from source directly from GIT - is an open source, in which the developers spread all their achievements. In this way, it is going Hyperdroid firmware. Second, find the unit that is most close to the characteristics of the HD2, and which officially goes cyan. Initially, such a device is the HTC Desire. Android for HD2 was created for the most part based on it. Codename HTC Desire - bravo. Inscription cm_bravo_109 base means that the firmware founded on firmware C yanogen M od for HTC Desire ( Bravo a) version 109 . On official website can be found with list of changes .
2 ) Does the built-in radio work badly, where can I get another? - program usage may help Spirit FM radio .
3 ) How do I turn off the shutter sound in a standard camera application?
Method number 1: Settings ->Settings CyanogenMod ->Sound ->in the "Camera" section, check the box next to "Disable camera sound"
Method number 2: turn off the phone sound
Method number 3: using a file manager with superuser rights (for example,В® Root Explorer) delete the following file:
system / media / audio / ui / camera_click.ogg
4 ) How to assign a melody to a contact? - open the "phone" application, go to the "contacts" tab, select the desired contact, press the "menu" key (windows) ->options ->melody.
5 ) How to make the battery indicator in the top panel displayed in percent? - Settings ->Settings CyanogenMod ->interface ->status bar settings ->battery style.
6 ) How to take a screenshot? - hold down the power key and select the desired action in the drop-down menu.
2 ) Does the built-in radio work badly, where can I get another? - program usage may help Spirit FM radio .
3 ) How do I turn off the shutter sound in a standard camera application?
Method number 1: Settings ->Settings CyanogenMod ->Sound ->in the "Camera" section, check the box next to "Disable camera sound"
Method number 2: turn off the phone sound
Method number 3: using a file manager with superuser rights (for example,В® Root Explorer) delete the following file:
system / media / audio / ui / camera_click.ogg
4 ) How to assign a melody to a contact? - open the "phone" application, go to the "contacts" tab, select the desired contact, press the "menu" key (windows) ->options ->melody.
5 ) How to make the battery indicator in the top panel displayed in percent? - Settings ->Settings CyanogenMod ->interface ->status bar settings ->battery style.
6 ) How to take a screenshot? - hold down the power key and select the desired action in the drop-down menu.
[27.10.12] [MAGLDR / cLK] [CWM] TyphooN CyanogenMod 7 v3.8.9 [A2SD +] [Tytung r14]
- - Android 2.3.7, fast and stable, low power consumption. Based on the latest build CyanogenMod 7.2 for HTC Desire with a minimum of changes from the author.
download:
Firmware:
v3.8.9 : version for loader MAGLDR + mirror ; version for loader cLK + mirror
v3.8.8 : version for loader MAGLDR + mirror ; version for loader cLK + mirror
v3.8.7 : version for loader MAGLDR + mirror ; version for loader cLK + mirror
v3.8.5 : version for loader MAGLDR + mirror 1 + mirror 2 + mirror 4 ; version for loader cLK + mirror 1 + mirror 2 + mirror 3
v3.8.3 : version for loader MAGLDR + mirror 1 + mirror 2 ; version for loader cLK + mirror 1 + mirror 2 + mirror 3
v3.8.2 : version for loader MAGLDR + mirror 1 + mirror 2 ; version for loader cLK + mirror 1 + mirror 2
v3.8.0 : version for loader MAGLDR + mirror 1 + mirror 2 + mirror 3 ; version for loader cLK + mirror 1 + mirror 2 + mirror 3
v3.7.6 : version for loader MAGLDR + mirror 1 + mirror 2 + mirror 3 ; version for loader cLK + mirror 1 + mirror 2 + mirror 3
v3.7.5 : version for loader MAGLDR + mirror 1 + mirror 2 + mirror 3 ; version for loader cLK + mirror 1 + mirror 2 + mirror 3
v3.7.0 : version for loader MAGLDR + mirror 1 + mirror 2 + mirror 3 ; version for loader cLK + mirror 1 + mirror 2 + mirror 3
v3.6.9 : version for loader MAGLDR + mirror 2 + mirror 3 + mirror 4 ; version for loader cLK + mirror 2 + mirror 3 + mirror 4
v3.6.7 : version for loader MAGLDR + mirror 1 + mirror 2 + mirror 3 ; version for loader cLK + mirror 1 + mirror 2 + mirror 3
v3.6.6 : version for loader MAGLDR + mirror 1 + mirror 2 + mirror 3 ; version for loader cLK + mirror 1 + mirror 2 + mirror 3
v3.6.5 : version for loader MAGLDR + mirror 1 + mirror 2 + mirror 3 ; version for loader cLK + mirror 1 + mirror 2 + mirror 3
v3.6.3 : version for loader MAGLDR + mirror 1 + mirror 2 + mirror 3 ; version for loader cLK + mirror 1 + mirror 2 + mirror 3
v3.6.2 : version for loader MAGLDR + mirror 1 + mirror 2 + mirror 3 ; version for loader cLK + mirror 1 + mirror 2 + mirror 3
Additionally:
Author's topic on XDA-developers. The topic of discussing the firmware onsavagemessiahzine.com.
Install the firmware on the system partition 150 MB.More about other sections:
v3.8.9 : version for loader MAGLDR + mirror ; version for loader cLK + mirror
v3.8.8 : version for loader MAGLDR + mirror ; version for loader cLK + mirror
v3.8.7 : version for loader MAGLDR + mirror ; version for loader cLK + mirror
v3.8.5 : version for loader MAGLDR + mirror 1 + mirror 2 + mirror 4 ; version for loader cLK + mirror 1 + mirror 2 + mirror 3
v3.8.3 : version for loader MAGLDR + mirror 1 + mirror 2 ; version for loader cLK + mirror 1 + mirror 2 + mirror 3
v3.8.2 : version for loader MAGLDR + mirror 1 + mirror 2 ; version for loader cLK + mirror 1 + mirror 2
v3.8.0 : version for loader MAGLDR + mirror 1 + mirror 2 + mirror 3 ; version for loader cLK + mirror 1 + mirror 2 + mirror 3
v3.7.6 : version for loader MAGLDR + mirror 1 + mirror 2 + mirror 3 ; version for loader cLK + mirror 1 + mirror 2 + mirror 3
v3.7.5 : version for loader MAGLDR + mirror 1 + mirror 2 + mirror 3 ; version for loader cLK + mirror 1 + mirror 2 + mirror 3
v3.7.0 : version for loader MAGLDR + mirror 1 + mirror 2 + mirror 3 ; version for loader cLK + mirror 1 + mirror 2 + mirror 3
v3.6.9 : version for loader MAGLDR + mirror 2 + mirror 3 + mirror 4 ; version for loader cLK + mirror 2 + mirror 3 + mirror 4
v3.6.7 : version for loader MAGLDR + mirror 1 + mirror 2 + mirror 3 ; version for loader cLK + mirror 1 + mirror 2 + mirror 3
v3.6.6 : version for loader MAGLDR + mirror 1 + mirror 2 + mirror 3 ; version for loader cLK + mirror 1 + mirror 2 + mirror 3
v3.6.5 : version for loader MAGLDR + mirror 1 + mirror 2 + mirror 3 ; version for loader cLK + mirror 1 + mirror 2 + mirror 3
v3.6.3 : version for loader MAGLDR + mirror 1 + mirror 2 + mirror 3 ; version for loader cLK + mirror 1 + mirror 2 + mirror 3
v3.6.2 : version for loader MAGLDR + mirror 1 + mirror 2 + mirror 3 ; version for loader cLK + mirror 1 + mirror 2 + mirror 3
List of changes for all versions:
v3.8.8 - CyanogenMod updated to the night version from 08/05/12
v3.8.7 - CyanogenMod updated to the night version of 07/15/12
v3.8.6 - CyanogenMod updated to the night version from 07/08/12 (newer than CM 7.2.0.1)
v3.8.5 - CyanogenMod updated to version 7.2 RC3
v3.8.3 - Updated CyanogenMod to version 7.2 RC2
v3.8.2 - Cyanogen mod (firmware base) for Desire updated to version from 2012 04 20 (night build)
v3.8.1 - Play Store updated to version 3.5.15
v3.8.0 - CyanogenMod updated to version 7.2 of RC1. Enable PPTP VPN fix from arne182. The Milaq library is included, which is responsible for adjusting the brightness (it is now possible to use manual backlight levels and LED notifications at the same time).
v3.7.6 - updated CyanogenMod to the latest nightly assembly of cyan for HTC Desire, updated kernel to version Tytung r14, fixed non-smooth gradients fix.
v3.7.5 - updated CyanogenMod, updated kernel to version Tytung r13
v3.7.4 - updated CyanogenMod, updated Market to version 3.3.11
v3.7.3 - updated by CyanogenMod
v3.7.2 - updated CyanogenMod, Updated kernel to tytung r12.4v3
v3.7.1 - updated CyanogenMod; Updated Market version 3.2.0
v3.6.9 - updated CyanogenMod, updated the file 98cpu_voltage - the script responsible for setting the voltage on the processor, added a line about 128 MHz (support appeared in the new kernel). But for some reason, the voltage at 128 MHz is the same as at 245 MHz, i.e. to sense from this zero, who wishes may reduce the voltage.
v3.6.8 - CyanogenMod has been updated (including a new lock screen), Android 2.3.7, the kernel has been updated to version Tytung r12.4: a bug has been fixed, when the outgoing call volume was not remembered, 128 MHz support is enabled (by default, ), an echo could appear
v3.6.7 - updated CyanogenMod, updated kernel to version r12.3: updated audio driver andline recording support is disabled
v3.6.6 - updated CyanogenMod, market updated to version 3.1.5
v3.6.5 - updated CyanogenMod, the core of Tytung r12, Google apps
v3.6.3 - updated CyanogenMod, updated market to version 3.1.3.
v3.6.2 compared to v3.6.0 - CyanogenMod has been updated (many changes), Google applications have been updated. Updated kernel on Tytung r12 beta. Updated GPS driver to version 2.1. Updated audio driver: fixed the problem of high sensitivity of the microphone and a high level of background noise (during the conversation the interlocutor heard everyone around him). Hands-free mode while working without loss.
v3.6.1 - unsuccessful version
v3.6.0 - updated CyanogenMod, updated media_profiles.xml file (why?), included the final version of the Tytung r11 kernel (for changes, see the corresponding section), updated initrd to improve processor performance. It seems that the download speed has increased.
v3.5.9 - updated CyanogenMod, updated gps.conf (for better GPS performance), updated kernel and wi-fi.
v3.5.8 - CyanogenMod has been updated, the update is not very significant, you can skip it.
v3.5.7 - updated CyanogenMod, GPS driver updated to version 2.0
v3.5.6 - updated CyanogenMod, included tweaks fromjan-willem3 (modified build.prop file), reduces power consumption in idle mode due to network optimization. There was a field for birthday at the contacts.
v3.5.5 - updated CyanogenMod - no changes for HD2, you can easily skip the update
v3.5.4 - updated CyanogenMod. Updated GPS driver fromTytung Up to version 1.9 NMEA
v3.5.3 - Updated CyanogenMod. Removed tweaks for tablets, the problem of cyclic restart disappeared
v3.5.2 - unstable version, updated CyanogenMod, Android 2.3.5 version, updated Google Talk. Again in the firmware included tweaks for tablets.
v3.5.1 - not stable version, updated CyanogenMod. Removed tablet tweaks, they caused cyclic reboots.
v3.5.0 - not stable version, updated CyanogenMod. Updated Market to version 3.0.27. Modified build.prop under the new Market. Updated GPS driver fromTytung Up to version v1.8 RPC. Added tweaks for tablets. Added gps.conf from Tytung 'and with automatic loading agps. Updated libhtc_ril.so driver.
v3.4.3 - updated CyanogenMod, finally removed all pribludy fromdorimanx , the stability of the firmware is back again while there are problems with the 3g Internet, as a solution, replace the library libhtc_ril.so with the old one from firmware version 3.4.0
v3.4.2 - CyanogenMod updated, GPS driver updated (now AGPS works exactly and quickly catches satellites), some tweaks fromdorimanx but not all, the T-Mobile Wifi Calling application has been removed, libaudio v2 from drizztje is built in (some kind of new driver)
v3.4.1 - updated CyanogenMod, updated GPS driver (automatic daylight saving time), updated Google applications on 13.06.11, included sometweaksfromdorimanx (apparently improving the speed of the OS and increasing the amount of available RAM).
v3.4.0 - Updated CyanogenMod to version 7.1.0 of RC1. Updated GPS driver.
v3.3.9 - updated by CyanogenMod
v3.3.8 - updated CyanogenMod, including FM radio
v3.3.7 - Updated CyanogenMod. Updated GPS driver, fixed reboot problem in previous version
v3.3.4 - updated CyanogenMod, a new GPS driver fromtytung
v3.3.3 - updated by CyanogenMod
v3.3.2 - updated CyanogenMod, including reduced delay in answering a call, fixed a bug leading to stop mail synchronization
v3.8.7 - CyanogenMod updated to the night version of 07/15/12
v3.8.6 - CyanogenMod updated to the night version from 07/08/12 (newer than CM 7.2.0.1)
v3.8.5 - CyanogenMod updated to version 7.2 RC3
v3.8.3 - Updated CyanogenMod to version 7.2 RC2
v3.8.2 - Cyanogen mod (firmware base) for Desire updated to version from 2012 04 20 (night build)
v3.8.1 - Play Store updated to version 3.5.15
v3.8.0 - CyanogenMod updated to version 7.2 of RC1. Enable PPTP VPN fix from arne182. The Milaq library is included, which is responsible for adjusting the brightness (it is now possible to use manual backlight levels and LED notifications at the same time).
v3.7.6 - updated CyanogenMod to the latest nightly assembly of cyan for HTC Desire, updated kernel to version Tytung r14, fixed non-smooth gradients fix.
v3.7.5 - updated CyanogenMod, updated kernel to version Tytung r13
v3.7.4 - updated CyanogenMod, updated Market to version 3.3.11
v3.7.3 - updated by CyanogenMod
v3.7.2 - updated CyanogenMod, Updated kernel to tytung r12.4v3
v3.7.1 - updated CyanogenMod; Updated Market version 3.2.0
v3.6.9 - updated CyanogenMod, updated the file 98cpu_voltage - the script responsible for setting the voltage on the processor, added a line about 128 MHz (support appeared in the new kernel). But for some reason, the voltage at 128 MHz is the same as at 245 MHz, i.e. to sense from this zero, who wishes may reduce the voltage.
v3.6.8 - CyanogenMod has been updated (including a new lock screen), Android 2.3.7, the kernel has been updated to version Tytung r12.4: a bug has been fixed, when the outgoing call volume was not remembered, 128 MHz support is enabled (by default, ), an echo could appear
v3.6.7 - updated CyanogenMod, updated kernel to version r12.3: updated audio driver andline recording support is disabled
v3.6.6 - updated CyanogenMod, market updated to version 3.1.5
v3.6.5 - updated CyanogenMod, the core of Tytung r12, Google apps
v3.6.3 - updated CyanogenMod, updated market to version 3.1.3.
v3.6.2 compared to v3.6.0 - CyanogenMod has been updated (many changes), Google applications have been updated. Updated kernel on Tytung r12 beta. Updated GPS driver to version 2.1. Updated audio driver: fixed the problem of high sensitivity of the microphone and a high level of background noise (during the conversation the interlocutor heard everyone around him). Hands-free mode while working without loss.
v3.6.1 - unsuccessful version
v3.6.0 - updated CyanogenMod, updated media_profiles.xml file (why?), included the final version of the Tytung r11 kernel (for changes, see the corresponding section), updated initrd to improve processor performance. It seems that the download speed has increased.
v3.5.9 - updated CyanogenMod, updated gps.conf (for better GPS performance), updated kernel and wi-fi.
v3.5.8 - CyanogenMod has been updated, the update is not very significant, you can skip it.
v3.5.7 - updated CyanogenMod, GPS driver updated to version 2.0
v3.5.6 - updated CyanogenMod, included tweaks fromjan-willem3 (modified build.prop file), reduces power consumption in idle mode due to network optimization. There was a field for birthday at the contacts.
v3.5.5 - updated CyanogenMod - no changes for HD2, you can easily skip the update
v3.5.4 - updated CyanogenMod. Updated GPS driver fromTytung Up to version 1.9 NMEA
v3.5.3 - Updated CyanogenMod. Removed tweaks for tablets, the problem of cyclic restart disappeared
v3.5.2 - unstable version, updated CyanogenMod, Android 2.3.5 version, updated Google Talk. Again in the firmware included tweaks for tablets.
v3.5.1 - not stable version, updated CyanogenMod. Removed tablet tweaks, they caused cyclic reboots.
v3.5.0 - not stable version, updated CyanogenMod. Updated Market to version 3.0.27. Modified build.prop under the new Market. Updated GPS driver fromTytung Up to version v1.8 RPC. Added tweaks for tablets. Added gps.conf from Tytung 'and with automatic loading agps. Updated libhtc_ril.so driver.
v3.4.3 - updated CyanogenMod, finally removed all pribludy fromdorimanx , the stability of the firmware is back again while there are problems with the 3g Internet, as a solution, replace the library libhtc_ril.so with the old one from firmware version 3.4.0
v3.4.2 - CyanogenMod updated, GPS driver updated (now AGPS works exactly and quickly catches satellites), some tweaks fromdorimanx but not all, the T-Mobile Wifi Calling application has been removed, libaudio v2 from drizztje is built in (some kind of new driver)
v3.4.1 - updated CyanogenMod, updated GPS driver (automatic daylight saving time), updated Google applications on 13.06.11, included sometweaksfromdorimanx (apparently improving the speed of the OS and increasing the amount of available RAM).
v3.4.0 - Updated CyanogenMod to version 7.1.0 of RC1. Updated GPS driver.
v3.3.9 - updated by CyanogenMod
v3.3.8 - updated CyanogenMod, including FM radio
v3.3.7 - Updated CyanogenMod. Updated GPS driver, fixed reboot problem in previous version
v3.3.4 - updated CyanogenMod, a new GPS driver fromtytung
v3.3.3 - updated by CyanogenMod
v3.3.2 - updated CyanogenMod, including reduced delay in answering a call, fixed a bug leading to stop mail synchronization
Author's topic on XDA-developers. The topic of discussing the firmware onsavagemessiahzine.com.
Install the firmware on the system partition 150 MB.More about other sections:
Contents of flash.cfg
misc ya 1M
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 150M
cache ya 5M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 150M
cache ya 5M
userdata ya | asize | hr allsize
[04.22.12] [MAGLDR / cLK] [CWM] HyperDroid CM7 v6.0.0 [A2SD +] [seader R9]
- - Only HyperDroid firmware made specifically for HD2 and is not a port of firmware dumps for other devices. Android 2.3.7. Very fast firmware with low power consumption.
download:
Firmware:
multiupload | mediafire | 2shared.com
Additionally:
Author's topic on XDA-developers + discussion thread on firmwaresavagemessiahzine.com
Install the firmware on the system partition size of 130 MB. More about other sections (content of flash.cfg):
multiupload | mediafire | 2shared.com
Additionally:
Author's topic on XDA-developers + discussion thread on firmwaresavagemessiahzine.com
Install the firmware on the system partition size of 130 MB. More about other sections (content of flash.cfg):
misc ya 1M
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 130M
cache ya 5M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 130M
cache ya 5M
userdata ya | asize | hr allsize
[27.04.12] [MAGLDR / cLK] [CWM] BOYPPC-SHIFTPDA GINGER CM7 v62 [Tytung r14]
- - Android 2.3.7, additional applications, various graphic modifications, honeycomb themes
download:
Firmware:
Versions for both bootloaders can be downloaded from the link.BOYPPC CM7 HoneyComB v62
Additionally:
XDA-developers developers theme
Install the firmware on the system partition 130 MB
Versions for both bootloaders can be downloaded from the link.BOYPPC CM7 HoneyComB v62
Additionally:
XDA-developers developers theme
Install the firmware on the system partition 130 MB
[24.05.12] [MAGLDR / cLK] [CWM] Dorimanx ROM-HIGH-END v3.1.9 [Dorimanx 7.1A]
- - firmware with a very large number of tweaks and additions from the author, its own core, support for ZRAM, SWAP. Based on CM7 nightly builds.
download:
Firmware:
You can download all the firmware versions from the author’s site:
http://www.bourseanalyse.fr/dorimanx/
Additionally:
Author's topic on XDA-developers + topic of discussion firmware onsavagemessiahzine.com
Install the firmware on the system partition of 150 MB
You can download all the firmware versions from the author’s site:
http://www.bourseanalyse.fr/dorimanx/
Additionally:
Author's topic on XDA-developers + topic of discussion firmware onsavagemessiahzine.com
Install the firmware on the system partition of 150 MB
[11/06/12] [MAGLDR / cLK] [CWM] Pure CyanogenMod 7 [Tweakos 6]
- - The firmware is almost native CyanogenMod 7 with the addition of Google applications. In essence, this is an alternative to TyphooN, but with its own core.
download:
Firmware:
Version for loader MAGLDR, Version for loader cLK
Additionally:
Author's topic onsavagemessiahzine.com, author topic on XDA-developers.
Firmware must be installed on the system partition of 150 MB. More about other sections (content of flash.cfg):
Version for loader MAGLDR, Version for loader cLK
Additionally:
Author's topic onsavagemessiahzine.com, author topic on XDA-developers.
Firmware must be installed on the system partition of 150 MB. More about other sections (content of flash.cfg):
misc ya 1M
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 150M
cache ya 5M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 150M
cache ya 5M
userdata ya | asize | hr allsize
What is MIUI? - This is a series of popular alternative firmware, HD2 is also supported by the development team. MIUI firmware combines beauty, original interface (apple style and support for many other topics), speed of work, high-quality standard software.Overview.
MIUI FAQ
1) How to enter the application menu (similar to the start menu)? - in any way, all recorded applications are added to one of the desktops, you can organize them using folders.
2) How to increase the number of desktops in a standard launcher? - enter the mode with thumbnails of all desktops with a pinch motion on the screen; there you can arrange the desktops and add desktops
3) In the firmware there is no Russian language, how to add it there? - use Russian language pack for versions based on 1.5.27 - Russification of any MIUI downloaded zip install via CWM, Russian language package for firmware based on version 1.6.10 , Russian language package for firmware based on version 1.6.24 , Russian language package for firmware based on version 1.7.1
4) What is updater.apk responsible for and is it possible to remove it? - for updating the firmware (checking for updates and downloading them). The application can be deleted, only the only negative - in the settings the update button stops working, the application crashes.
5) Is it possible to scale widgets in the native louncher of MIUI? - not
6) What does the round icon with the digit inside on the lock screen in the top panel mean? - the number of events in the "Notifications", you can delete by clicking on "clear"
7) Where to get FM radio for MIUI? - here
8) Can I change the density of the screen (density parameter) in the MIUI firmware? - It is extremely undesirable to do this, because After that, the firmware goes into a constant reboot. The interface is designed exclusively for the standard value (240), only very small changes are possible.
9) Did you not catch the ext-partition or is A2SD not working? - it is not recommended to create this partition through CWM recovery, because a section created in this way is most likely not picked up.
10) Does not workcluBalanceor another application - in the Superuser program, set the application rights.
11) On the MIUI firmware, the game does not work or simply does not see the cache - in the file at /system/build.prop, change the line "ro.product.manufacturer = unknown" to "ro.product.manufacturer = HTC".
12) There is no root (superuser rights) - in the last MIUI, these rights are initially disabled. To get these rights go to "Settings ->System ->Security ->Menu ->Settings "and enable superuser rights.
13) Can I put ringtones on several contacts at once? - it is possible, but groups should be created. We go to the phone ->contacts ->Next, at the top of the group tab, then select the desired group, press the "windows" button (middle), among the pop-ups there will be a "ringtone group" button
14) Why did the updates stop? - MIUI developers completely switched to Android 4.0 and older versions are no longer supported. Who wants to use the new MIUI should go to the new Android (discussion in a separate topic).
FAQ in the general MIUI topic
Continuation of the FAQon the official site
2) How to increase the number of desktops in a standard launcher? - enter the mode with thumbnails of all desktops with a pinch motion on the screen; there you can arrange the desktops and add desktops
3) In the firmware there is no Russian language, how to add it there? - use Russian language pack for versions based on 1.5.27 - Russification of any MIUI downloaded zip install via CWM, Russian language package for firmware based on version 1.6.10 , Russian language package for firmware based on version 1.6.24 , Russian language package for firmware based on version 1.7.1
4) What is updater.apk responsible for and is it possible to remove it? - for updating the firmware (checking for updates and downloading them). The application can be deleted, only the only negative - in the settings the update button stops working, the application crashes.
5) Is it possible to scale widgets in the native louncher of MIUI? - not
6) What does the round icon with the digit inside on the lock screen in the top panel mean? - the number of events in the "Notifications", you can delete by clicking on "clear"
7) Where to get FM radio for MIUI? - here
8) Can I change the density of the screen (density parameter) in the MIUI firmware? - It is extremely undesirable to do this, because After that, the firmware goes into a constant reboot. The interface is designed exclusively for the standard value (240), only very small changes are possible.
9) Did you not catch the ext-partition or is A2SD not working? - it is not recommended to create this partition through CWM recovery, because a section created in this way is most likely not picked up.
10) Does not workcluBalanceor another application - in the Superuser program, set the application rights.
11) On the MIUI firmware, the game does not work or simply does not see the cache - in the file at /system/build.prop, change the line "ro.product.manufacturer = unknown" to "ro.product.manufacturer = HTC".
12) There is no root (superuser rights) - in the last MIUI, these rights are initially disabled. To get these rights go to "Settings ->System ->Security ->Menu ->Settings "and enable superuser rights.
13) Can I put ringtones on several contacts at once? - it is possible, but groups should be created. We go to the phone ->contacts ->Next, at the top of the group tab, then select the desired group, press the "windows" button (middle), among the pop-ups there will be a "ringtone group" button
14) Why did the updates stop? - MIUI developers completely switched to Android 4.0 and older versions are no longer supported. Who wants to use the new MIUI should go to the new Android (discussion in a separate topic).
FAQ in the general MIUI topic
Continuation of the FAQon the official site
[17.02.12] [MAGLDR] [CWM] MIUI for HD2 from the official community v2.3.7c [A2SD +] [Tytung r12.4]
- - Android 2.3.7, everything works, low power consumption, updates over the air
download:
Firmware:
version 2.3.7c- stable version, released once a month.
This is the latest stable version released for Android 2.3. Further, only the MIUI branch for Android 4.0 is supported.
Additionally:
Official Russian site
Firmware must be installed on the system partition 130 MB, more details about other sections:
version 2.3.7c- stable version, released once a month.
This is the latest stable version released for Android 2.3. Further, only the MIUI branch for Android 4.0 is supported.
Additionally:
Official Russian site
Firmware must be installed on the system partition 130 MB, more details about other sections:
misc ya 1M
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 130M
cache ya 5M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 130M
cache ya 5M
userdata ya | asize | hr allsize
[13.02.12] [MAGLDR / cLK] [CWM] NDT MIUI [Tytung14]
- - Based on the latest official MIUI, fast, stable
download:
Firmware:
Dev 48.0: version of MAGLDR + patch for cLK (core Tytung r14)
In order to install the firmware on the cLK bootloader, you must first install the ZIP MAGLDR version, and above it you can already sew the patch for the CLK
Stable v6.0: version for MAGLDR + patch for cLK (core Tytung r14).
Dev- The firmware version, based on the version of the official MIUI for developers, designed for running functions, includes rapid changes with a weekly firmware update.
Stable- firmware version, based on the stable version of the official MIUI, in which there are no minor bugs, but the functionality is reduced, compared with the versions for developers.
Additionally:
Author's topic on XDA-developers + discussion thread on firmwaresavagemessiahzine.com
Firmware needs to be installed on a system partition of 150 MB or more. More about other sections, the contents of flash.cfg:
Dev 48.0: version of MAGLDR + patch for cLK (core Tytung r14)
In order to install the firmware on the cLK bootloader, you must first install the ZIP MAGLDR version, and above it you can already sew the patch for the CLK
Stable v6.0: version for MAGLDR + patch for cLK (core Tytung r14).
Dev- The firmware version, based on the version of the official MIUI for developers, designed for running functions, includes rapid changes with a weekly firmware update.
Stable- firmware version, based on the stable version of the official MIUI, in which there are no minor bugs, but the functionality is reduced, compared with the versions for developers.
Additionally:
Author's topic on XDA-developers + discussion thread on firmwaresavagemessiahzine.com
Firmware needs to be installed on a system partition of 150 MB or more. More about other sections, the contents of flash.cfg:
misc ya 1M
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 150M
cache ya 5M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 150M
cache ya 5M
userdata ya | asize | hr allsize
[16.02.12] [MAGLDR / cLK] [CWM] BOYPPC-SHIFTPDA MIUI v35 [A2SD] [Tytung r14]
- - Android 2.3.7, based on the latest MIUI from the official community, changed the graphics, added applications.
download:
Firmware:
Versions for both bootloaders can be downloaded from the link -BOYPPC-MIUI-V35
Additionally:
XDA-developers developers theme
Versions for both bootloaders can be downloaded from the link -BOYPPC-MIUI-V35
Additionally:
XDA-developers developers theme
[24.02.12] [MAGLDR / cLK] [CWM] PRJ PureSpeed ​​vX2 [Dorimanx 3.8 2WayRec]
- - A special feature of the firmware is its lightness from additional and unused software, plus developments in improving performance.
download:
Firmware:
MAGLDR version
Additionally:
Topic onsavagemessiahzine.com
Firmware is required to be installed on a system partition of 135 MB in size. More about other sections (content of flash.cfg):
MAGLDR version
Additionally:
Topic onsavagemessiahzine.com
Firmware is required to be installed on a system partition of 135 MB in size. More about other sections (content of flash.cfg):
misc ya 1M
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 135M
cache ya 5M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 135M
cache ya 5M
userdata ya | asize | hr allsize
[17.04.12] [MAGLDR / cLK] [CWM] MIUI LAEdroid 3D Universal [Dorimanx v7.3]
- - The firmware is assembled on the final for Android 2.3.7 MIUI build version 2.4.20 using MFB Lite from KOJAN, filled with various software for fine-tuning the device, additional optimizations, many tweaks built in to improve performance.
download:
Firmware:
http://rusfolder.com/30450096
Additionally:
Author's topic onsavagemessiahzine.com.
Firmware is required to install on the system partition of 140 MB. More about other sections (content of flash.cfg):
http://rusfolder.com/30450096
Additionally:
Author's topic onsavagemessiahzine.com.
Firmware is required to install on the system partition of 140 MB. More about other sections (content of flash.cfg):
misc ya 1M
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 140M
cache ya 5M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 140M
cache ya 5M
userdata ya | asize | hr allsize
It has long been not updated firmware, but not lost from this as
[10.12.11] [MAGLDR / cLK] [CWM] LADY MIUI v42 [A2SD +] [Tytung r14]
- - the basis of the latest MIUI for developers from the official community, Android 2.3.7, changed graphics
download:
Firmware:
MAGLDR;Clk
Additionally:
Author's topic on XDA-developers
Firmware is required to be installed on a 150Mb system partition.
The author recommends moving DALVIK CACHE to an ext partition using A2SDGUI (A2SD graphical user interface) for optimal operation of the A2SD script.
MAGLDR;Clk
Additionally:
Author's topic on XDA-developers
Firmware is required to be installed on a 150Mb system partition.
The author recommends moving DALVIK CACHE to an ext partition using A2SDGUI (A2SD graphical user interface) for optimal operation of the A2SD script.
Post has been editedDisplax - 30.08.17, 12:28
Reason for editing: Widescreen camera
HTC Sense based firmware
Android 2.2 + Sense 2
Firmware based on Desire HD \ Desire Z \ Incredible S. What is good about Sense 2? -comparative reviewwith first sense[30.01.12] [MAGLDR / cLK] [CWM] Android 2.2.1 Sense 2.0 by Mikhei777 final [Rafpingna 1.9mod]
- - firmware based on Desire HD (RUU 1.84), Android 2.2.1, full Sense 2.0
download:
Firmware:
Final version
And for the MAGLDR bootloader and for the cLK bootloader, there is one ZIP. When installing, select the desired version.
Additionally:
Author's topic onsavagemessiahzine.com, Author topic on XDA-developers.
The firmware uses the standard Rafpingna 1.9 kernel, but with an already built-in patch, which accelerates the inclusion of the screen on old matrices.
Firmware to put on the system partition size of 200MB. More about the remaining sections (content flash.cfg):
Final version
And for the MAGLDR bootloader and for the cLK bootloader, there is one ZIP. When installing, select the desired version.
Additionally:
Author's topic onsavagemessiahzine.com, Author topic on XDA-developers.
The firmware uses the standard Rafpingna 1.9 kernel, but with an already built-in patch, which accelerates the inclusion of the screen on old matrices.
Firmware to put on the system partition size of 200MB. More about the remaining sections (content flash.cfg):
misc ya 1M
recovery rrecov | ro | nospr filesize recovery.img
boot yboot | ro 5M
system ya 200M
cache ya 5M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery.img
boot yboot | ro 5M
system ya 200M
cache ya 5M
userdata ya | asize | hr allsize
[17.08.11] [CWM / DAF] BOYPPC-SHIFTPDA DESIRE HD v23 [Data2SD]
- - Based on Desire HD (RUU 1.84.832.2), Sense with auto rotation, changed graphics (glass theme), built-in many additional applications and widgets.
download:
Firmware:
BOYPPC-SHIFTPDA DESIRE HD v23
Additionally:
XDA-developers developers theme
The firmware does not support memory expansion due to ext partitions. Instead, the data2SD script is used. It transfers applications not to the ext partition, but to a special image on the memory card. For this to work, you need to copy the folder.data2SDand fileconfigIn the root of the memory card, they go in the archive with the firmware.
BOYPPC-SHIFTPDA DESIRE HD v23
Additionally:
XDA-developers developers theme
The firmware does not support memory expansion due to ext partitions. Instead, the data2SD script is used. It transfers applications not to the ext partition, but to a special image on the memory card. For this to work, you need to copy the folder.data2SDand fileconfigIn the root of the memory card, they go in the archive with the firmware.
It has long been not updated firmware, but not lost from it as a
[15.06.11] [ZIP] [LEO512 / 1024] CMYLXGOs Stock Desire HD [A2SD] [RAF 1.9OC]
[13.02.11] [DAF] AF403 DesireHD stock base 1.5 [Data2ext] [Rafpigna 1.7]
[07.08.11] [CWM] RAFDROID HD 4.2.0 [Data2ext] [Rafpigna 2.0OC]
[15.04.2011] [MAGLDR / cLK] imilka's Incredible Sense v1.1 [RAM HD v2.1] [RAF 1.9OC]
[03.03.11] [CWM] RAFDROID HD 3.2.1 LIGHT [Rafpigna 1.7OC]
[10.04.2011] [CWR] Korand Incredible S v1.4 Odex / Sqfs [Core Givis 0.53]
[15.04.2011] [MAGLDR / cLK] imilka's Vision Sense v5.0 [RAM] [A2SD] [RAF 1.9OC]
[13.04.11] imilka's RAM Desire HD v2.0 [RAM] [A2SD] [Rafpigna 1.9OC]
[08.24.11] [ZIP] HD2 CoreDroid HD v1.7 [EU / TMOUS]
[30.04.11] [CWM] CME DHD2 Compact v1.6 [RAM] [Rafpigna 1.9OC]
- - firmware as close as possible to the official firmware Desire HD (RUU 1.84), conceived for TMOUS HD2
download:
Firmware:
v1.1.18 TMOUS- updated embedded applications
v1.1.17 LITE Edition- lightweight version for European HD2
Additionally:
Author's topic on XDA-developers
For TMOUS HD2, install the firmware on a system partition of 445 MB in size. On the remaining sections:For the European HD2, the firmware should be installed on the system partition of 283 MB. On the remaining sections:
v1.1.18 TMOUS- updated embedded applications
v1.1.17 LITE Edition- lightweight version for European HD2
Additionally:
Author's topic on XDA-developers
For TMOUS HD2, install the firmware on a system partition of 445 MB in size. On the remaining sections:
Content flash.cfg
misc ya 1M
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 445M
cache ya 2M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 445M
cache ya 2M
userdata ya | asize | hr allsize
Content flash.cfg
misc ya 1M
recovery rrecov | ro | nospr filesize MAGLDR_recovery_3.0.2.4-seadersn.img
boot yboot | ro 4M
system ya 283M
cache ya 2M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize MAGLDR_recovery_3.0.2.4-seadersn.img
boot yboot | ro 4M
system ya 283M
cache ya 2M
userdata ya | asize | hr allsize
[13.02.11] [DAF] AF403 DesireHD stock base 1.5 [Data2ext] [Rafpigna 1.7]
- - firmware based on DesireHD, is an exact copy, ext partition is required, including for TMOUS
download:
Firmware: here
Additionally:
Author's topic on XDA-developers
Description
Together with the firmware during the installation, CWM recovery is installed
Raf 1.9 kernel installer
Additionally:
Author's topic on XDA-developers
Description
Together with the firmware during the installation, CWM recovery is installed
Raf 1.9 kernel installer
[07.08.11] [CWM] RAFDROID HD 4.2.0 [Data2ext] [Rafpigna 2.0OC]
- - full firmware based on ROM Desire HD, for installing this firmware on the European HD2 ext partition is required
download:
Firmware:
RAFDROID HD 4.2.0- In this version, bluetooth does not work, the reason is in the kernel, install Rafpigna 1.9OC and the problem will disappear.
Additionally:
Author's topic on XDA-developers
When loading all the time, the error "oh does not respond system" pops up - decision or that decision
Internet browser crashes when working with flash - decision , if it does not help, install the following fix (zip) via CWM DHDport_streamingfixV2
Buttons are constantly on, what to do? - At the root of the memory card, find the CONFIG.TXT file (if not, create it), write the string old_light_driver = [1] into it, reboot the device. After that, the keyboard buttons will go out after 10 seconds.
RAFDROID HD 4.2.0- In this version, bluetooth does not work, the reason is in the kernel, install Rafpigna 1.9OC and the problem will disappear.
Additionally:
Author's topic on XDA-developers
When loading all the time, the error "oh does not respond system" pops up - decision or that decision
Internet browser crashes when working with flash - decision , if it does not help, install the following fix (zip) via CWM DHDport_streamingfixV2
Buttons are constantly on, what to do? - At the root of the memory card, find the CONFIG.TXT file (if not, create it), write the string old_light_driver = [1] into it, reboot the device. After that, the keyboard buttons will go out after 10 seconds.
[15.04.2011] [MAGLDR / cLK] imilka's Incredible Sense v1.1 [RAM HD v2.1] [RAF 1.9OC]
- - Incredible S based firmware fromimilka , android 2.2, Sense 2.0 partially modified to Sense 2.1 with a working camera, ext section for the European version of HD2 is required
download:
Firmware:
Versions for the cLK bootloader:Incredible 1.1 EU, Incredible 1.1 T-MobilethankAndy-HierOS
EU RAM TMOUS- since version 1.1 video recording works
Additionally:
Author's topic on XDA-developers
For TMOUS HD2, install the firmware on a 350Mb system partition.
For European HD2, the firmware should be installed on a 130Mb system partition. On the remaining sections:
Versions for the cLK bootloader:Incredible 1.1 EU, Incredible 1.1 T-MobilethankAndy-HierOS
EU RAM TMOUS- since version 1.1 video recording works
Additionally:
Author's topic on XDA-developers
For TMOUS HD2, install the firmware on a 350Mb system partition.
For European HD2, the firmware should be installed on a 130Mb system partition. On the remaining sections:
Content flash.cfg
misc ya 1M
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 130M
cache ya 5M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 130M
cache ya 5M
userdata ya | asize | hr allsize
[03.03.11] [CWM] RAFDROID HD 3.2.1 LIGHT [Rafpigna 1.7OC]
- - Complete firmware based on Desire HD. A stable "squashed" firmware based on a stable full deodexed (deodexed) version.
download:
Firmware:
full raf allex hd 3.1 super light + full raf allex hd 3.1 light- modification of firmware fromallex
Full Rafdroid HD 3.2 LIGHT
Additionally:
Author's topic on XDA-developers
Firmware to put on the system partition size of 290MB. On the remaining sections:
full raf allex hd 3.1 super light + full raf allex hd 3.1 light- modification of firmware fromallex
Full Rafdroid HD 3.2 LIGHT
Additionally:
Author's topic on XDA-developers
Firmware to put on the system partition size of 290MB. On the remaining sections:
Content flash.cfg
misc ya 1M
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 290M
cache ya 4M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 290M
cache ya 4M
userdata ya | asize | hr allsize
[10.04.2011] [CWR] Korand Incredible S v1.4 Odex / Sqfs [Core Givis 0.53]
- - firmware from well-known WM users to ROMkorand , Android 2.2.1 Sense 2.0, based on the Incredible S 1.36.405.1 build
download:
Firmware:
Korand Incredible S 1.4 NAND Odex / Sqfs
Additionally:
Author's topic on XDA-developers
Author's topic onsavagemessiahzine.com
Firmware to put on the system partition size of 280MB. On the remaining sections:
Korand Incredible S 1.4 NAND Odex / Sqfs
Additionally:
Author's topic on XDA-developers
Author's topic onsavagemessiahzine.com
Firmware to put on the system partition size of 280MB. On the remaining sections:
Content flash.cfg
misc ya 1M
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 280M
cache ya 10M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 280M
cache ya 10M
userdata ya | asize | hr allsize
[15.04.2011] [MAGLDR / cLK] imilka's Vision Sense v5.0 [RAM] [A2SD] [RAF 1.9OC]
- - firmware based on Desire Z ROM, Deodexed. Horizontal Sense. Nothing is compressed, nothing is cut.
download:
Firmware:
Versions for the cLK bootloader:Vision 5.0 EU, Vision 5.0 T-MobilethankAndy-HierOS
EU, TMOUS
Additionally:
Author's topic on XDA-developers
Internet settings (APN access points) in the firmware are missing, so the Internet will not work until you configure it. You can learn the settings from your mobile operator, either on the website or by calling the operator. Entering these settings is also easy:
settings ->wireless network ->mobile network ->access points (APN) ->press the "windows" ->new access point. [/ QUOTE]
For TMOUS HD2, install the firmware on a 400Mb system partition. On the remaining sections:For European HD2, install the firmware on a system partition of 130 MB in size, besides you need to create an ext partition on the memory card. On the remaining sections:
Versions for the cLK bootloader:Vision 5.0 EU, Vision 5.0 T-MobilethankAndy-HierOS
EU, TMOUS
Additionally:
Author's topic on XDA-developers
Internet settings (APN access points) in the firmware are missing, so the Internet will not work until you configure it. You can learn the settings from your mobile operator, either on the website or by calling the operator. Entering these settings is also easy:
settings ->wireless network ->mobile network ->access points (APN) ->press the "windows" ->new access point. [/ QUOTE]
For TMOUS HD2, install the firmware on a 400Mb system partition. On the remaining sections:
Content flash.cfg
misc ya 1M
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 400M
cache ya 44M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 400M
cache ya 44M
userdata ya | asize | hr allsize
Content flash.cfg
misc ya 1M
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 130M
cache ya 44M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 130M
cache ya 44M
userdata ya | asize | hr allsize
[13.04.11] imilka's RAM Desire HD v2.0 [RAM] [A2SD] [Rafpigna 1.9OC]
- - firmware based on the latest RCMixHD v3.6 [Telus WWE 1.84] for Desire HD fromimilka
download:
Firmware:
EU, TMOUS
Additionally:
Author's topic on XDA-developers
For TMOUS HD2, install the firmware on a 400Mb system partition. On the remaining sections:For European HD2, the firmware should be installed on a 130Mb system partition, as well as an ext partition must be created on the memory card. On the remaining sections:
EU, TMOUS
Additionally:
Author's topic on XDA-developers
For TMOUS HD2, install the firmware on a 400Mb system partition. On the remaining sections:
Content flash.cfg
misc ya 1M
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 400M
cache ya 44M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 400M
cache ya 44M
userdata ya | asize | hr allsize
Content flash.cfg
misc ya 1M
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 130M
cache ya 44M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 130M
cache ya 44M
userdata ya | asize | hr allsize
[08.24.11] [ZIP] HD2 CoreDroid HD v1.7 [EU / TMOUS]
- - fast firmware based on Desire HD
download:
Firmware:
CoreDroid v1.7
CoreDroid GB v3- unstable version
COREDROID GB v2.1 Release Version + mirror on the people + List of changes- unstable version
CoreDroid GB v2 + List of changes- unstable version
Core Droid v1.6 + mirror on the people, thankm10n73
[21.03.11] CoreDroid DHD v1.5 Repackfrompekus
version 1.5mirror on mail.ru
Additionally: :
Author's topic on XDA-developers + own site ROM'omodela
For TMOUS HD2, install the firmware on a system partition of 390 MB in size. On the remaining sections:For European HD2, in addition, you need to create an ext partition on the memory card.
CoreDroid v1.7
CoreDroid GB v3- unstable version
COREDROID GB v2.1 Release Version + mirror on the people + List of changes- unstable version
CoreDroid GB v2 + List of changes- unstable version
Core Droid v1.6 + mirror on the people, thankm10n73
[21.03.11] CoreDroid DHD v1.5 Repackfrompekus
version 1.5mirror on mail.ru
Additionally: :
Author's topic on XDA-developers + own site ROM'omodela
For TMOUS HD2, install the firmware on a system partition of 390 MB in size. On the remaining sections:
Content flash.cfg
misc ya 1M
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 10M
system ya 390M
cache ya 5M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 10M
system ya 390M
cache ya 5M
userdata ya | asize | hr allsize
[30.04.11] [CWM] CME DHD2 Compact v1.6 [RAM] [Rafpigna 1.9OC]
- - firmware based on Desire HD (RUU 1.84), Android 2.2.1, lightweight Sense2 (cut out launcher and widgets), for European HD2 ext is not required
download:
Firmware:
CME_v1.6_CWM_ODEX_RAM
Additionally:
Author's topic on XDA-developers
Firmware to put on the system partition size of 230MB. On the remaining sections:
CME_v1.6_CWM_ODEX_RAM
Additionally:
Author's topic on XDA-developers
Firmware to put on the system partition size of 230MB. On the remaining sections:
Content flash.cfg
misc ya 1M
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 4M
system ya 230M
cache ya 1M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 4M
system ya 230M
cache ya 1M
userdata ya | asize | hr allsize
Android 2.2 + first Sense (Desire ROM)
Sense - is a shell of of HTC. She brings a lot of Android proprietary graphics and animation, your desktop and screen lock. Virtually all of the standard applications are replaced by branded with advanced features, added a number of additional programs to work "out of the box." On a modified schedule and the shell does not stop adding applications, Sense introduces as his driver. First Sense Sense less functional than 2 and subsequent modifications, but has no less speed than light EEPROM.[30.12.10] [DAF] LEO "Stock" Android ROM
- - The first Android firmware for HD2, is an exact copy of the firmware HTC Desire, is missing root. Slightly outdated :-)
download:
[07.27.11] [MAGLDR / cLK] [DAF / CWM] "Stock Desire" MOD v5 RC1 [A2SD / Data2SD] [Bauner io]
- - Mod based on the official firmware HTC Desire
download:
Firmware:
Version 5 (pre-release 1):MAGLDR, cLK
Version 4 (latest stable version, February 20):DAF, CWM
Additionally:
Author's topic on XDA-developers
Install the firmware on the system partition 240 MB. Cache section 40 MB.
Version 5 (pre-release 1):MAGLDR, cLK
Version 4 (latest stable version, February 20):DAF, CWM
Additionally:
Author's topic on XDA-developers
Install the firmware on the system partition 240 MB. Cache section 40 MB.
[21.03.11] [CWM] skink Clean Desire v1.4 [A2SD +] [Kernel prj v0.4]
- - firmware based on prj Clean Desire v0.3.2, very fast, stable and not demanding to the battery
download:
Firmware:
v1.4_package.zip + mirror on the people, thankPostengineer
Additionally:
Author's topic on XDA-developers
v1.4_package.zip + mirror on the people, thankPostengineer
Additionally:
Author's topic on XDA-developers
[14.09.12] [MAGLDR / cLK] [CWM] Android 2.3.5 Sense 1.0 [marc1706_desire_0.2.1]
- - based on firmware from HTC EVO 4G (build 4.67.651.3), modified interface, wallpapers and melodies from Sense 4.0, can be installed without an ext-partition on a memory card
download:
Firmware:
full version, mirror | light version, mirror
Additionally:
Author's topic on XDA-developers
Install the firmware on the system partition size:
- 250 MB, for the full version without using the ext-partition on the memory card;
- 120 MB, for the full version using the ext-partition on the memory card;
- 210 MB, for the light version without using the ext-partition on the memory card;
- 120 MB, for the light version using the ext-partition on the memory card.
The size of the cache partition for all types of firmware should be at least five MB.
full version, mirror | light version, mirror
Additionally:
Author's topic on XDA-developers
Install the firmware on the system partition size:
- 250 MB, for the full version without using the ext-partition on the memory card;
- 120 MB, for the full version using the ext-partition on the memory card;
- 210 MB, for the light version without using the ext-partition on the memory card;
- 120 MB, for the light version using the ext-partition on the memory card.
The size of the cache partition for all types of firmware should be at least five MB.
Post has been editedSemyon - 17.02.13, 13:57
Firmware based on Android 2.3 + Sense 3
This section presents the firmware with the latest version of the shell from HTC. In the new Sense new graphics, as well as it is better optimized compared to the second version. You can evaluate the appearance of the new shell invideo review. However, it is designed for devices with a large amount of RAM and storage, it does not really interfere with the correct operation of these firmware, but because of this, some firmware may have problems with the forced termination of some processes.
[12.19.12] [MAGLDR / cLK] [CWM] UrDroid [marc1706_v0.2.3]
- - pure Sense 3.5 with HTC Sensational XL (firmware 1.30.461.1), black theme
download:
Firmware:
UrDroid Custom v3 marc1706 0.2.3 kernel 2.9.3.zip- universal installer for CLK and MAGLDR, TMOUS and EU
Additionally:
Author's topic on XDA-developers
When installing the firmware using the ext-partition on the memory card on the internal drive, you need to create the following partition configuration (contents of flash.cfg):
UrDroid Custom v3 marc1706 0.2.3 kernel 2.9.3.zip- universal installer for CLK and MAGLDR, TMOUS and EU
Additionally:
Author's topic on XDA-developers
When installing the firmware using the ext-partition on the memory card on the internal drive, you need to create the following partition configuration (contents of flash.cfg):
misc ya 1M
recovery rrecov | nospr 5M
boot yboot | 5M
system ya 210M
cache ya 5M
userdata ya | asize | hr allsize
recovery rrecov | nospr 5M
boot yboot | 5M
system ya 210M
cache ya 5M
userdata ya | asize | hr allsize
[24.11.12] [MAGLDR / cLK] [CWM] "LEGENDARY-THEMED" SUNDAWG TBD [Data2ext] [marc1706_v0.2.3 +]
- - graphically modified Sense 3.5 with HTC One X, transparent theme, beats audio
download:
Firmware:
SUNDAWG LEGENDARY ROMS.zip- universal installer for CLK and MAGLDR, TMOUS and EU
Additionally:
Author's topic on XDA-developers
When installing the firmware using the ext-partition on the memory card on the internal drive, you need to create the following partition configuration (contents of flash.cfg):
When installing the firmware without using the ext-partition on the memory card (for TMOUS HD2) on the internal drive, you need to create the following partition configuration (contents of flash.cfg):
SUNDAWG LEGENDARY ROMS.zip- universal installer for CLK and MAGLDR, TMOUS and EU
Additionally:
Author's topic on XDA-developers
When installing the firmware using the ext-partition on the memory card on the internal drive, you need to create the following partition configuration (contents of flash.cfg):
misc ya 1M
recovery rrecov | nospr 7M
boot yboot | 7M
system ya 150M
cache ya 7M
userdata ya | asize | hr allsize
recovery rrecov | nospr 7M
boot yboot | 7M
system ya 150M
cache ya 7M
userdata ya | asize | hr allsize
When installing the firmware without using the ext-partition on the memory card (for TMOUS HD2) on the internal drive, you need to create the following partition configuration (contents of flash.cfg):
misc ya 1M
recovery rrecov | nospr 7M
boot yboot | 7M
system ya 250M
cache ya 7M
userdata ya | asize | hr allsize
recovery rrecov | nospr 7M
boot yboot | 7M
system ya 250M
cache ya 7M
userdata ya | asize | hr allsize
[22.01.14] [MAGLDR / cLK] [CWM] Sense of Eclipse v3.9 [AD2SDX, DA2SDM, DataOnEXT + DalvikOnNAND, NAND] [Eclipse 1.4]
- - Android 2.3.5, Sense 3.5, firmware based on the official HTC Sensation XL Beats Audio version 1.27.1400.4
download:
Firmware:
eclipse_3.90_full.zip, mirror- universal installer for CLK and MAGLDR, TMOUS and EU
Additionally:
Author's topic on XDA-developers
When installed using the DataOnEXT method, the internal memory of TMOUS HD2 should be a system partition of 445, for EU HD2 it should be 405 MB.
To install the firmware by other methods, the internal partition must have a 100 MB system partition. For the international version of HD2, in addition, an ext-partition should be created on the memory card, with an available capacity of at least 1 GB. More about the remaining sections (content of flash.cfg):
eclipse_3.90_full.zip, mirror- universal installer for CLK and MAGLDR, TMOUS and EU
Additionally:
Author's topic on XDA-developers
When installed using the DataOnEXT method, the internal memory of TMOUS HD2 should be a system partition of 445, for EU HD2 it should be 405 MB.
To install the firmware by other methods, the internal partition must have a 100 MB system partition. For the international version of HD2, in addition, an ext-partition should be created on the memory card, with an available capacity of at least 1 GB. More about the remaining sections (content of flash.cfg):
misc ya 1M
recovery rrecov | nospr 5M
boot yboot | 5M
system ya 100M
cache ya 5M
userdata ya | asize | hr allsize
recovery rrecov | nospr 5M
boot yboot | 5M
system ya 100M
cache ya 5M
userdata ya | asize | hr allsize
[07.24.12] [MAGLDR / cLK] [CWM] Energy в„ў -.ВёВё. В· ВґВЇ Sense 3.5 [marc1706_v0.2.3 +]
- - Android 2.3.5 firmware, Sense 3.5, transparent launcher
download:
Firmware:
version dated 07.24.12, universal installer for CLK and MAGLDR, TMOUS and EU
Additionally:
Author's topic on XDA-developers
For TMOUS HD2 firmware, install on a 380 MB system partition.
For the international version of HD2, install the firmware on a 200 MB system partition with a 1 GB ext partition on a memory card. More about the remaining sections (content of flash.cfg):
version dated 07.24.12, universal installer for CLK and MAGLDR, TMOUS and EU
Additionally:
Author's topic on XDA-developers
For TMOUS HD2 firmware, install on a 380 MB system partition.
For the international version of HD2, install the firmware on a 200 MB system partition with a 1 GB ext partition on a memory card. More about the remaining sections (content of flash.cfg):
misc ya 1M
recovery rrecov | ro | nospr filesize recovery.img
boot yboot | ro 5M
system ya 200M
cache ya 5M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery.img
boot yboot | ro 5M
system ya 200M
cache ya 5M
userdata ya | asize | hr allsize
[31.05.12] [MAGLDR / cLK] [CWM] AlexRunny v7.0 [marc1706_desire_0.2.2]
- - Android 2.3.5 Sense 3.5, based on Runnymede firmware
download:
Firmware:
people
Additionally:
Author's topic onsavagemessiahzine.com
Install the firmware on the system partition size of 185 MB. In addition, there must be an ext partition on the card. For those who want to install the firmware on TMOUS HD2 without an ext-partition, before installing, do the following: open the installation archive with the firmware on your computer, go to system / etc / init.d, and in this folder delete the file 40ad2sdxAlexMod-2.
people
Additionally:
Author's topic onsavagemessiahzine.com
Install the firmware on the system partition size of 185 MB. In addition, there must be an ext partition on the card. For those who want to install the firmware on TMOUS HD2 without an ext-partition, before installing, do the following: open the installation archive with the firmware on your computer, go to system / etc / init.d, and in this folder delete the file 40ad2sdxAlexMod-2.
[30.01.12] [MAGLDR / cLK] [CWM] Android 2.3.5 Sense 3.0 by Mikhei777 v1.5 [HierOS 1.8.5]
- - firmware based on RUU Desire HD 3.12.405.1, Android 2.3.5, full Sense 3.0
download:
Firmware:
Firmware
And for the MAGLDR bootloader and for the cLK bootloader, there is one ZIP. When installing, select the desired version.
Additionally:
Author's topic onsavagemessiahzine.com
Firmware to put on the system partition size 275MB + ext partition. More about the remaining sections (content of flash.cfg):
Firmware
And for the MAGLDR bootloader and for the cLK bootloader, there is one ZIP. When installing, select the desired version.
Additionally:
Author's topic onsavagemessiahzine.com
Firmware to put on the system partition size 275MB + ext partition. More about the remaining sections (content of flash.cfg):
misc ya 1M
recovery rrecov | ro | nospr filesize recovery.img
boot yboot | ro 5M
system ya 260M
cache ya 5M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery.img
boot yboot | ro 5M
system ya 260M
cache ya 5M
userdata ya | asize | hr allsize
[13.01.12] [MAGLDR / cLK] [CWM] Android 2.3.5 Sense 3.5 by Mikhei777 v2.3 [2.6.35.14_0.1.3 by Marc]
- - firmware based on Runnymede 1.22.461.2, Android 2.3.5, full Sense 3.5
download:
Firmware:
Firmware
And for the MAGLDR bootloader and for the cLK bootloader, there is one ZIP. When installing, select the desired version.
Additionally:
Author's topic onsavagemessiahzine.com
Firmware to put on the system partition size 260Mb + ext partition. More about the remaining sections (content of flash.cfg):
Firmware
And for the MAGLDR bootloader and for the cLK bootloader, there is one ZIP. When installing, select the desired version.
Additionally:
Author's topic onsavagemessiahzine.com
Firmware to put on the system partition size 260Mb + ext partition. More about the remaining sections (content of flash.cfg):
misc ya 1M
recovery rrecov | ro | nospr filesize recovery.img
boot yboot | ro 5M
system ya 260M
cache ya 5M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery.img
boot yboot | ro 5M
system ya 260M
cache ya 5M
userdata ya | asize | hr allsize
It has long been not updated firmware, but not lost from this as
[24.06.11] [MAGLDR / cLK] [CWM] LeoRCMix S v1.9 [Rafpigna 1.9OC]
[07.27.11] [CWM] AngelDeath Kingdom v1.5 [Tytung r10]
[15.10.11] [MAGLDR / cLK] [CWM] Pyramid v2.5 Final [Herios 1.8.3nob]
[10/31/11] [MAGLDR] [CWM] NDT SENSE v9.0 [A2SD +] [HierOS1.8.5]
[05.12.11] [MAGLDR] [CWM] Desire HD 3.12.405.1 v1.6 [HierOS1.8.5 N-2]
[08.12.11] [MAGLDR] RUNNYMEDE 1.11.1113.1 v2.2 [HIEROS or RCMIX or MARC]
- - Based on HTC Desire RCMix S v2.1 test 4 firmware, Sense 2.1 with parts from Sense 3.0
download:
Firmware:
v1.9 for MAGLDR bootloader + v1.9 for loader cLK_ update_ pack
To install the cLK version, you must first install the version for MAGLDR, and then install the cLK_ update_ pack from above.
Additionally:
Firmware support has been discontinued.
Author's topic onsavagemessiahzine.com
Install the firmware on the system partition of 260 MB. In addition, there must be a 1 GB ext partition on the card, even for TMOUS. More about other sections:
v1.9 for MAGLDR bootloader + v1.9 for loader cLK_ update_ pack
To install the cLK version, you must first install the version for MAGLDR, and then install the cLK_ update_ pack from above.
Additionally:
Firmware support has been discontinued.
Author's topic onsavagemessiahzine.com
Install the firmware on the system partition of 260 MB. In addition, there must be a 1 GB ext partition on the card, even for TMOUS. More about other sections:
Contents of the flash.cfg file
misc ya 1M
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 260M
cache ya 5M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 260M
cache ya 5M
userdata ya | asize | hr allsize
[07.27.11] [CWM] AngelDeath Kingdom v1.5 [Tytung r10]
- - Based on Kingdom WWE 0.81.651.0, Sense 2.1 firmware with parts from Sense 3.0.
download:
Firmware:
EU_Kingdom_v1.5_FINAL.zip | TMOUS_Kingdom_v1.5_FINAL.zip
Additionally:
Author's topic on XDA-developers
For TMOUS HD2, install the firmware on a 400 MB system partition. On the remaining sections:
For European HD2, install the firmware on a system partition of 220 MB. In addition, there must be an ext partition on the card. On the remaining sections:
EU_Kingdom_v1.5_FINAL.zip | TMOUS_Kingdom_v1.5_FINAL.zip
Additionally:
Author's topic on XDA-developers
For TMOUS HD2, install the firmware on a 400 MB system partition. On the remaining sections:
Contents of flash.cfg
misc ya 1M
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 8M
system ya 400M
cache ya 16M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 8M
system ya 400M
cache ya 16M
userdata ya | asize | hr allsize
For European HD2, install the firmware on a system partition of 220 MB. In addition, there must be an ext partition on the card. On the remaining sections:
Contents of flash.cfg
misc ya 1M
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 8M
system ya 220M
cache ya 8M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 8M
system ya 220M
cache ya 8M
userdata ya | asize | hr allsize
[15.10.11] [MAGLDR / cLK] [CWM] Pyramid v2.5 Final [Herios 1.8.3nob]
- - Based on HTC Pyramid v1.35.401.1 firmware, Sense supports real 3D.
download:
Firmware:
For EU : MAGLDR / clk + mirror ;
For tmous : MAGLDR / CLK ;+ Mirror
Additionally:
Author's topic on XDA-developers
For TMOUS HD2, install the firmware on a 445 MB system partition. On the remaining sections:
For the European HD2, the firmware should be installed on a 150 MB system partition. In addition, there must be an ext partition on the card. On the remaining sections:
For EU : MAGLDR / clk + mirror ;
For tmous : MAGLDR / CLK ;+ Mirror
Additionally:
Author's topic on XDA-developers
For TMOUS HD2, install the firmware on a 445 MB system partition. On the remaining sections:
Contents of flash.cfg
misc ya 1M
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 445M
cache ya 5M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 445M
cache ya 5M
userdata ya | asize | hr allsize
For the European HD2, the firmware should be installed on a 150 MB system partition. In addition, there must be an ext partition on the card. On the remaining sections:
Contents of flash.cfg
misc ya 1M
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 150M
cache ya 5M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 150M
cache ya 5M
userdata ya | asize | hr allsize
[10/31/11] [MAGLDR] [CWM] NDT SENSE v9.0 [A2SD +] [HierOS1.8.5]
- - Based on HTC Sensation firmware, transparent Sense.
download:
Firmware:
Version for MAGLDR+patch for CLK
Additionally:
Author's topic on XDA-developers
For TMOUS HD2 and for European HD2, the firmware should be installed on the 170 MB system partition. In addition, there must be an ext partition on the card. More about other sections (content of flash.cfg):
Version for MAGLDR+patch for CLK
Additionally:
Author's topic on XDA-developers
For TMOUS HD2 and for European HD2, the firmware should be installed on the 170 MB system partition. In addition, there must be an ext partition on the card. More about other sections (content of flash.cfg):
misc ya 1M
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 170M
cache ya 5M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 170M
cache ya 5M
userdata ya | asize | hr allsize
[05.12.11] [MAGLDR] [CWM] Desire HD 3.12.405.1 v1.6 [HierOS1.8.5 N-2]
- - Android 2.3.5, Sense 3.0, is based on the latest update for HTC Desire HD.
download:
Firmware:
For EU:MAGLDR
For tmous:MAGLDR;
In order to install the CLK version, you need to install the version under MAGLDR +Clk patch.
Fix from strips- completely removes the strip, but reduces performance.
Additionally:
Author's topic on XDA-developers
For TMOUS HD2, install the firmware on a 445 MB system partition. On the remaining sections:
For the European HD2, the firmware should be installed on a 150 MB system partition. In addition, there must be an ext partition on the card. On the remaining sections:
For EU:MAGLDR
For tmous:MAGLDR;
In order to install the CLK version, you need to install the version under MAGLDR +Clk patch.
Fix from strips- completely removes the strip, but reduces performance.
Additionally:
Author's topic on XDA-developers
For TMOUS HD2, install the firmware on a 445 MB system partition. On the remaining sections:
Contents of flash.cfg
misc ya 1M
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 445M
cache ya 5M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 445M
cache ya 5M
userdata ya | asize | hr allsize
For the European HD2, the firmware should be installed on a 150 MB system partition. In addition, there must be an ext partition on the card. On the remaining sections:
Contents of flash.cfg
misc ya 1M
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 150M
cache ya 5M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 150M
cache ya 5M
userdata ya | asize | hr allsize
[08.12.11] [MAGLDR] RUNNYMEDE 1.11.1113.1 v2.2 [HIEROS or RCMIX or MARC]
- - Android 2.3.5, Sense 3.5, based on HTC Sensation XL firmware
download:
Firmware:
European HD2 version (512 ROM): [http://uploaded.to/file/6jg5pwu2""MAGLDR[/url]
Version for TMOUS HD2 (1024 ROM):MAGLDR
In order to install the firmware on cLK, you must first install the ZIP MAGLDR version, and then install the kernel for clk.
To get rid of graphical glitches install via CWM:
Version for European HD2 (512 ROM):glitches_fix_Runnymede_0.82.401.1_v1.0_EU.zip(1.31 MB)
Version for TMOUS HD2 (1024 ROM):glitches_fix_Runnymede_0.82.401.1_v1.0_Tmous.zip(1.31 MB)
Additionally:
Author's topic on XDA-developers
For TMOUS HD2, install the firmware on a 445 MB system partition. On the remaining sections:
For European HD2, the firmware should be installed on a system partition of 145 MB in size. In addition, there must be an ext partition on the card. On the remaining sections:
European HD2 version (512 ROM): [http://uploaded.to/file/6jg5pwu2""MAGLDR[/url]
Version for TMOUS HD2 (1024 ROM):MAGLDR
In order to install the firmware on cLK, you must first install the ZIP MAGLDR version, and then install the kernel for clk.
To get rid of graphical glitches install via CWM:
Version for European HD2 (512 ROM):
glitches_fix_Runnymede_0.82.401.1_v1.0_EU.zip(1.31 MB)Version for TMOUS HD2 (1024 ROM):
glitches_fix_Runnymede_0.82.401.1_v1.0_Tmous.zip(1.31 MB)Additionally:
Author's topic on XDA-developers
For TMOUS HD2, install the firmware on a 445 MB system partition. On the remaining sections:
Contents of flash.cfg
misc ya 1M
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 445M
cache ya 5M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 445M
cache ya 5M
userdata ya | asize | hr allsize
For European HD2, the firmware should be installed on a system partition of 145 MB in size. In addition, there must be an ext partition on the card. On the remaining sections:
Contents of flash.cfg
misc ya 1M
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 145M
cache ya 5M
userdata ya | asize | hr allsize
recovery rrecov | ro | nospr filesize recovery-raw.img
boot yboot | ro 5M
system ya 145M
cache ya 5M
userdata ya | asize | hr allsize
Post has been editedSemyon - 10.11.14, 16:34
Reason for editing: updated Sense of Eclipse
M
Topic created 12/30/2010 10:48 PM
and how can clk assemble your mod yourself?
Post has been editedSemyon - 16.12.11, 20:49
How to make WiFi work on AlexRunny 1.2 firmware? I turn on, the inscription "Enable ..." appears, and then "Error". : blink:
clarion2000 @ 10/13/2011, 19:19
How to make WiFi work on AlexRunny 1.2 firmware? I turn on, the inscription "Enable ..." appears, and then "Error".
Try to change the core. for starters Raping 1.9 OC GB. Do not forget backup.
VeiSQ @ 10/13/2011, 19:15
XAPOHbl4,
and how can clk assemble your mod yourself?
and how can clk assemble your mod yourself?
Artikul29 @ 10/13/2011, 20:36
Try to change the core. for starters Raping 1.9 OC GB. Do not forget backup.
It also does not help, I went through four pieces.
Nerovinger @ 10/13/2011, 20:34
clarion2000, why not ask the author's topic?
This problem is found not only on this one.
Okay, hammer, come back to MIUI.
Post has been editedclarion2000 - 13.10.11, 19:55
clarion2000 @ 10/13/2011, 20:19
How to make WiFi work on AlexRunny 1.2 firmware? I turn on, the inscription "Enable ..." appears, and then "Error".
Actually, wifi works on it. In your case, a simple reboot should help. If wifi doesn’t turn on at all, then the firmware has crookedly risen, you need to change to a clean one.
Guys who know the firmware from 3.5 sensor support the phonebook access profile via BluetoothВ® (PBAP)? : blush:
I apologize, but I wonder, the camera in the new sensors does not work normally, is it necessary to nobody? and for which romodels make firmware every day with this lag ... correct me wretched .... Well, I don't understand .... sorry
oberon23 @ 10/13/2011, 23:12
and why romodels make firmware every day with this lag ...
Because the camera is still unbeatable
In the firmware the typhoon (and in some others too) in the settings of Cyanogen Mod->Enter->Response settings have various options + click patterns. There are templates in my firmware, but there is no data (by default they are in the typhoon) i. It is necessary to vystovlyat. Can anyone look at the firmware and throw me the data, what are the default templates? 1. Pressing pattern: ... 2. Shutting pattern ... 3. Long-pressing pattern ... 4. Claudia pattern ... Just numbers are needed. I would be very grateful for the help!
Post has been editedDamask - 14.10.11, 00:25
Post has been editedDamask - 14.10.11, 00:25
nikerossxp @ 10/14/2011, 00:05
who, how much and on what squeezed out battery life?
If you ruin the WiFi, bluetooth and disable hardware video processing, enough for three days. Proshiva- vedroid 2.3 sense 2
Now I use the Dorimax-rom-2.8.9, it lasts for a day, with calls for 30 minutes, constant listening to music on the phone and WiFi for 5-10 sessions of 5-30 minutes
Post has been editedtit7805 - 14.10.11, 00:25
Damask , Template pressing 0 10 20 30; Template release 5 18; Template long pressing 0 1 20 21; Template Claudia 30.
Friends, please explain how to use the program from the Attcha to spy on the battery. What you need to pay attention to? How to get data on consumption during sleep? What are the optimal parameters?
Hyperdroid firmware.
I understand the meaning of the parameters. Just do not understand what's what and what to compare
Hyperdroid firmware.
I understand the meaning of the parameters. Just do not understand what's what and what to compare
I downloaded RUNNYMEDE 0.82.401.1 v1.1 [HierOS 1.7.2]
did everything according to the instructions and when I copied the archive to the phone, then a message came out saying insert the continuation of the multi-volume (where can I get it?)
I clicked cancel, rebooted, then did everything according to the instructions, but the installation is canceled, so how bad is the bad password written (bad)
WTF? what to do, people help! Vinfon is going well and I can’t put it on orroid ... I also ask the designer to download it from here ((((these are my first experiments)
did everything according to the instructions and when I copied the archive to the phone, then a message came out saying insert the continuation of the multi-volume (where can I get it?)
I clicked cancel, rebooted, then did everything according to the instructions, but the installation is canceled, so how bad is the bad password written (bad)
WTF? what to do, people help! Vinfon is going well and I can’t put it on orroid ... I also ask the designer to download it from here ((((these are my first experiments)
[email protected], 01:52
Friends, please explain how to use the program from the Attcha to spy on the battery.
If you mean current_widget, then in the settings you should check the Log file and the consumption log will be written as txt in the root of the flash drive. At the expense of consumption something like this:
Hibernation 2G- 2-4mA
hibernation 3G- 4-6mA
Hibernation blupup- 17-60mA
WiFi in hibernation is 12-17mA, and as suggested by bondxxx_nnm- 4-6mA
Camera work - 400-600mA
Listen to music in your ears- 90-120mA
Listen to music on the bluetooth 70-90mA
Phone calls - 250-350mA
View menus, contacts, and more. 112-190mA
Installing applications- 190-290 (without SD_EXT), 220-350 (with SD-EXT)
Playing a toy is dependent on the appetite of the application, but usually not higher than 370mA.
Values ​​cited for the backlight mode - automatic when the average illumination of the room
Post has been editedtit7805 - 14.10.11, 07:28
©savagemessiahzine.com2005-2020 All rights reserved.
savagemessiahzine.com®- registered trademark.
Terms of Use | Denial of responsibility | Advertising placement
savagemessiahzine.com®- registered trademark.
Terms of Use | Denial of responsibility | Advertising placement