Develop Bugs

[Q] DHD android most beginner know how

Finally I got my DHD, the time where everything is rolling out, from perm root, to recovery...
The good thing, I'm very happy with my DHD, the bad thing, I'm not familiar yet with android system.
I revised a lot of android and DHD threads, and I faced many new terminologies that belong to android where I like to have explanation for each.
Please let me understand the following issues the beginner way, allowing me to maybe make a simple guide answers for most new android users coming from winmo.
I-General questions:
1-DHD should be multitouch. Then why games like Gameloft are not multitouch like on ipod or iphone?
2-What are the buttons combinations for the different operations like hard reset & boot loader?
3-I read that android can’t share internet via USB for those with no WIFI at home or office. As I knew it’s due to ad hoc issue so it's impossible to get internet via USB cable from desktop. When I plugged my DHD, I choose internet pass through and I got internet on my DHD, is it a new feature implemented in DHD only, or is it a 2.2 update that will work on other devices?
4-Winmo gives the choice to install applications on either the device or SD card. Android have nothing like this, so when I install applications, where do they go, and is there a workaround to put everything on SD card, or maybe give choice to where to install?
5-My DHD comes with an 8 GB mini SD card where there are some folders and files on it. Are they necessary to run the system, what if I replaced this card with another formatted one, what will happen, or what if I format this card?
II-System info:
1-Baseband version (is it like the radio in winmo?)
2-Kernel version (is it one kernel for the entire device? Does it updates like rom or like radio?) e.g. (kAmMa's OC&GOV&BFS Kernel - Performance and Stability. Is this a rom or just kernel that will update some parts of the rom without losing data on the device?)
3-Build number (is this the firmware?) e.g. (i have 1.32.405.3 CLxxxxxx release-keys, what does release keys means?)
4-Software number (or this is the firmware?)
III-OTA ACE with radio:
1-OTA (is it a rom, does it mean over the air, if yes what does that mean? Can we update OTA with no root?)
2-ACE
On winmo (HD2), I know HSPL will let me unlock ISPL so I can install any custom or cooked rom, languages and applications...
For android, as far as I know there is no one click solution. From what I understand to do everything in android with no restrictions u need to do the followings:
IV-How to root Desire HD install h-boot (S-Off) and Clockwork recovery?
Please identify which one is just a process that we do it once in order to unlock it, which is a boot loader run application and which one is an android application:
1-Root (is it what gives access to the root folders of the system that maybe are hidden by default or encrypted?)
2-Hboot
3-S-off (is it security off? if yes, it is security off for what? installing applications, or read write to some encrypted partitions?)
4-Clockwork (is it something necessary to do in order to install custom rom, no adds, backup and so on, or is it something totally independent and related only to unlock the speed of the CPU where you can leave it intact if you won’t play with the CPU speed?)
5-Recovery (from what I understand it seems that recovery is a system shell command like dos or more like bios for android but named as recovery, what can we do with the recovery other than recovering the device?)
6-Recovery image (is it a rom backed on the form of image and provided by developers, so we can install it directly on the device using only the recovery shell?)
V-More things to know about:
1-What is adb?
2-What is busybox?
2-What is fast boot?
3-What is eMMC write?
4-What is ext2 or ext4 (is it like the partition type of the SD card based on UNIX system? if yes, why should we change or modify this ext)
5-Rom manager (is it a desktop pc application or android device application? is it something like I can put the RUU file of the rom on my SD card and using the rom manager I can install the rom from there, nothing more nothing less?)

vuedesprit said:
Finally I got my DHD, the time where everything is rolling out, from perm root, to recovery...
The good thing, I'm very happy with my DHD, the bad thing, I'm not familiar yet with android system.
I revised a lot of android and DHD threads, and I faced many new terminologies that belong to android where I like to have explanation for each.
Please let me understand the following issues the beginner way, allowing me to maybe make a simple guide answers for most new android users coming from winmo.
I-General questions:
1-DHD should be multitouch. Then why games like Gameloft are not multitouch like on ipod or iphone?
2-What are the buttons combinations for the different operations like hard reset & boot loader?
3-I read that android can’t share internet via USB for those with no WIFI at home or office. As I knew it’s due to ad hoc issue so it's impossible to get internet via USB cable from desktop. When I plugged my DHD, I choose internet pass through and I got internet on my DHD, is it a new feature implemented in DHD only, or is it a 2.2 update that will work on other devices?
4-Winmo gives the choice to install applications on either the device or SD card. Android have nothing like this, so when I install applications, where do they go, and is there a workaround to put everything on SD card, or maybe give choice to where to install?
5-My DHD comes with an 8 GB mini SD card where there are some folders and files on it. Are they necessary to run the system, what if I replaced this card with another formatted one, what will happen, or what if I format this card?
II-System info:
1-Baseband version (is it like the radio in winmo?)
2-Kernel version (is it one kernel for the entire device? Does it updates like rom or like radio?) e.g. (kAmMa's OC&GOV&BFS Kernel - Performance and Stability. Is this a rom or just kernel that will update some parts of the rom without losing data on the device?)
3-Build number (is this the firmware?) e.g. (i have 1.32.405.3 CLxxxxxx release-keys, what does release keys means?)
4-Software number (or this is the firmware?)
III-OTA ACE with radio:
1-OTA (is it a rom, does it mean over the air, if yes what does that mean? Can we update OTA with no root?)
2-ACE
On winmo (HD2), I know HSPL will let me unlock ISPL so I can install any custom or cooked rom, languages and applications...
For android, as far as I know there is no one click solution. From what I understand to do everything in android with no restrictions u need to do the followings:
IV-How to root Desire HD install h-boot (S-Off) and Clockwork recovery?
Please identify which one is just a process that we do it once in order to unlock it, which is a boot loader run application and which one is an android application:
1-Root (is it what gives access to the root folders of the system that maybe are hidden by default or encrypted?)
2-Hboot
3-S-off (is it security off? if yes, it is security off for what? installing applications, or read write to some encrypted partitions?)
4-Clockwork (is it something necessary to do in order to install custom rom, no adds, backup and so on, or is it something totally independent and related only to unlock the speed of the CPU where you can leave it intact if you won’t play with the CPU speed?)
5-Recovery (from what I understand it seems that recovery is a system shell command like dos or more like bios for android but named as recovery, what can we do with the recovery other than recovering the device?)
6-Recovery image (is it a rom backed on the form of image and provided by developers, so we can install it directly on the device using only the recovery shell?)
V-More things to know about:
1-What is adb?
2-What is busybox?
2-What is fast boot?
3-What is eMMC write?
4-What is ext2 or ext4 (is it like the partition type of the SD card based on UNIX system? if yes, why should we change or modify this ext)
5-Rom manager (is it a desktop pc application or android device application? is it something like I can put the RUU file of the rom on my SD card and using the rom manager I can install the rom from there, nothing more nothing less?)
Click to expand...
Click to collapse
Congratulations. You win the "most questions asked in a single post" award.
Sent from my Desire HD using XDA App

That is a ridiculous amount of questions, and the thread is in completely the wrong area of the forum. I'm sure you'd find the answer to pretty much all your questions if you looked hard enough, but to answer the one about multi-touch. It is multi touch and all the games I've played from your example 'Gameloft' are multi-touch, so I don't know what you're smoking buddy, but ease off.

1. Inb4 "search".
2. Wrong forum.
3. No really, try searching. At least 30% of that is googleable.
Sent from my Desire HD using XDA App

Ok guys, thank you all for your replies, and yes I knew that a war and flames will go on here, but seriously if you think this is ridiculous or newbie or most dumb questions, do not turn the way of the thread or flame me, my intentions are to make this as a one small guide for most new androids functions, it's not a bad thing to do, in fact I will learn as much as other new users here, no one is asked to answer all those ridiculous questions, just answer what you know about, guys please take it seriously and easy, saying look harder will not help the thread, it may help me personaly, but be sure that I did a lot of search, and it will not hurt to put everything in one place, and as you can see, I answered most of the questions up to what I gathered, you can correct me about my answers, put your thoughts or not answer at all, but please be constructive here, and if you all think that i'm in the wrong forum, or asking too much, or asking ridiculous questions, please moderator feel free to do what you think is better for the forum.
Sorry guys for bothering you. Thank you for your response.
N.B.: just to be more accurate, I tried the prince of persia pre installed on the phone by the dealer, and it was not multi touch, so you cant walk and use any of the right actions at same time.

@vuedesprit: Good thread, and thanks for taking all the criticism from the more experienced users.
@all chimers chiming the "use search, wrong forum" tune: c'mon guys, there's at least 2 of us reading this thread going, it's about time all this information got consolidated into one place! The easier it is to find this information, the easier it would be for more of us to get engaged in the process and thus further development, enhancement and adoption.
While our "friendly" mod is doing his best to keep the forums clean, they're as fragmented as ever and from time-to-time, it becomes necessary to consolidate the information into a single thread. I'm sure most of you started some place too and remember the time not so long ago when it was difficult to find even the most basic info? I think by sharing your knowledge, you will gain a much better following and the platform will gain much better adoption.
My 2 cents worth anyways...I've had my DHD for 3 days now and I too am struggling to perform even the most basic tasks.

We really need a questions and answers sub forum

Fair enough, maybe my first comment was a bit rash, but I didn't mean to appear rude. I shall try to answer some questions here:
GENERAL.
1. From my own experience all games advertised as multitouch are exactly that. I don't know about the version of PoP that you have installed from carrier, but I do find that odd.
2. Hard reset is a little perverse with the new "fastboot" hibernation feature that HTC have implemented. You have to go to MENU>SETTINGS>APPLICATIONS and disable "fastboot" (this is where confusion may arise as this is not the bootloader fastboot that allows images to be flashed)!! Now when you hold down the power button and get the option to power off, you will properly power off the phone. Next if you hold "VOLUME DOWN" and "POWER" buttons you will reboot into HBoot, from here the VOLUME UP/DOWN keys navigate the menu and POWER selects menu options.
3. Not sure about this one.
4. Since the release of FROYO you can go to MENU>SETTINGS>APPLICATIONS>MANAGE APPLICATIONS then select any app and move to either SD or to phone memory.
5. The folders on the SD card are mostly generated by the phone when you first insert it. The user guide and HTC sync software are there to move onto your PC for safe keeping. If you insert a freshly formatted SD card, the phone will make fresh folders such as DCIM for pictures, etc...
SYSTEM INFO.
1. Baseband is radio software.
2. Kernel is the linux kernel that is running below Android, this can be updated separately from the main ROM, radio etc. HOWEVER CAUTION IS ADVISED AS CERTAIN KERNELS WILL NEED NEW MODULES FOR HARDWARE TO FUNCTION CORRECTLY as you will see from the wifi modules bundled with the OC kernels.
3. Build number pertains to HTC's internal software version classification (some are built specific for carriers) they are generally released via RUU (ROM Update Utility aimed at windows) or OTA (Over The Air update received on phone [again sometimes carrier specific]). Release keys pertains to the fact that the firmware has been signed by HTC (I think).
4. Software number, basically as above.
OTA ACE with Radio.
1. As Above.
2. ACE: internal HTC name for Desire HD (also reportedly known as "SPADE")
ROOT DESIRE HD ETC.
Most of what you have written is pretty much correct.
MORE THINGS TO KNOW ABOUT.
1. http://developer.android.com/guide/developing/tools/adb.html
2. http://www.busybox.net/about.html
3. http://android-dls.com/wiki/index.php?title=Fastboot
4. eMMC write basically means that you can write to the internal phone (normally protected) memory such as /SYSTEM, this is what S-OFF allows you to do whenever you want. However, the modules that allow the ENG HBoot image to be flashed are what really accomplish this in the first place so theoretically you could just run that module every time you wanted to write to /SYSTEM but that would become very tedious very quickly. I can't really explain further, as I don't have the knowledge.
5. EXT2 or EXT4 are filesystem structures just like FAT, FAT16, FAT32, NTFS, HFS+ etc, EXT4 is newer and more advanced than EXT2 and therefore is more efficient. (kinda general but you get the idea. NEWER=BETTER)
6. ROM manager, find this in the android market, it is free, you install it on your phone and with the addition of clockworkmod it gives you the ability of flashing ROMs etc. USE WITH CAUTION.
I hope that this answers or clarifies most of what you have asked or said, please feel free to cut and paste any of this info into your first post so that we can actually consolidate this.
P.S. I too am a complete android noob and this is my first android phone, I have picked this info up mainly from this forum so all credit for information goes to XDA-DEVELOPERS.COM and not me.
Cheers,
Dok

berek9999 said:
congratulations. You win the "most questions asked in a single post" award.
Sent from my desire hd using xda app
Click to expand...
Click to collapse
+1111111111^2

1-DHD should be multitouch. Then why games like Gameloft are not multitouch like on ipod or iphone?
Click to expand...
Click to collapse
an application must support multitouch and other gestures. eg, opera doesnt support multitouch (ie you cant zoom in and out) but the browser that comes with the DHD does.
2-What are the buttons combinations for the different operations like hard reset & boot loader?
Click to expand...
Click to collapse
boot loader = turn phone off. then, volume down + power on.
4-Winmo gives the choice to install applications on either the device or SD card. Android have nothing like this, so when I install applications, where do they go, and is there a workaround to put everything on SD card, or maybe give choice to where to install?
Click to expand...
Click to collapse
application must support running from /sdcard. When you install an app go to settings -> Applications -> manage applications. From here you can uninstall or move apps to the sdcard. Bear in mind if you have not rooted your phone you may not be able to uninstall some apps (eg amazon reader).
5-My DHD comes with an 8 GB mini SD card where there are some folders and files on it. Are they necessary to run the system, what if I replaced this card with another formatted one, what will happen, or what if I format this card?
Click to expand...
Click to collapse
some application data is stored on your sdcard, and apps are stored here if you have moved them by using the steps above. if you change sd cards this info is unavailable to the app but the app should still work. any settings you had need to be redone.
2-Kernel version (is it one kernel for the entire device? Does it updates like rom or like radio?) e.g. (kAmMa's OC&GOV&BFS Kernel - Performance and Stability. Is this a rom or just kernel that will update some parts of the rom without losing data on the device?)
Click to expand...
Click to collapse
the kernel is not part of a rom or the radio. It is stored in the boot partition in the emmc (where fastboot(aka hboot)/splash images/boot(kernel)/recovery/ are all stored). It is generally included with but not required by a custom rom. ie, a custom rom builder may choose to include a specific kernel with his rom but it is not mandatory.
1-OTA (is it a rom, does it mean over the air, if yes what does that mean? Can we update OTA with no root?)
Click to expand...
Click to collapse
yes, you can do OTA HTC updates. but, there are no custom (non signed) updates delivered OTA. An unrooted rom will not be able to flash non signed updates (or roms).
How to root Desire HD install h-boot (S-Off) and Clockwork recovery?[/U][/B]
Click to expand...
Click to collapse
there is a good thread here - http://forum.xda-developers.com/showthread.php?t=841076.
Please identify which one is just a process that we do it once in order to unlock it, which is a boot loader run application and which one is an android application:
1-Root (is it what gives access to the root folders of the system that maybe are hidden by default or encrypted?)
Click to expand...
Click to collapse
android application. eg, visionary+.
2-Hboot
Click to expand...
Click to collapse
hboot is also known as bootloader. it is the white screen with the skating androids when you do the volume-down + power combination when switching on your phone.
3-S-off (is it security off? if yes, it is security off for what? installing applications, or read write to some encrypted partitions?)
Click to expand...
Click to collapse
s-off stands for security off. you can check the status by doing the volume-down + power combo. At the top it will either say s-on or s-off. If you have s-on then your bootloader (hboot), boot (kernel) /system (android) and recovery (eg clockworkmod) partitions are all read only.
4-Clockwork (is it something necessary to do in order to install custom rom, no adds, backup and so on, or is it something totally independent and related only to unlock the speed of the CPU where you can leave it intact if you won’t play with the CPU speed?)
Click to expand...
Click to collapse
clock work is the recovery partition. you have 3 possible options before loading android when you do the volume-down + power on combo. hboot, then either fastboot or recovery. fastboot and recovery are both ways to flash images to your phone although through different ways (fastboot uses the fastboot command on your pc to send the image, recovery uses .zip's on your /sdcard). clockworkmod is a custom recovery image which you need to flash after achieving s-off. it's also where nandroid backups can be done. if you select recovery before doing this you will get the phone + red triangle icon. thats the stock recovery. the clockworkmod is the green menu selection one.
5-Recovery (from what I understand it seems that recovery is a system shell command like dos or more like bios for android but named as recovery, what can we do with the recovery other than recovering the device?)
Click to expand...
Click to collapse
see above.
6-Recovery image (is it a rom backed on the form of image and provided by developers, so we can install it directly on the device using only the recovery shell?)
Click to expand...
Click to collapse
clockwork mod can backup your phone's partitions (boot/userdata/system) so that if you mess up installing a rom you have a way to recover. this is known as a nandroid backup.
1-What is adb?
Click to expand...
Click to collapse
adb is android debug something. It is a way to send commands to the android operation system from your pc (either windows or linux). eg, you can run a single command, or run a shell (terminal session). it is part of the android sdk under tools.
2-What is busybox?
Click to expand...
Click to collapse
busybox is a single executable whihc runs under the android OS that provides standard linux commands (eg, ls, rm, cd) to any application. it is so that a script writer does not need to know the partiticular rom you have and then cater for it, but only that you have a certain version of busybox. eg, busybox 1.17.1 provides the same commands whether it is on a leedroid rom or a cyanogen rom.
2-What is fast boot?
Click to expand...
Click to collapse
fastboot is a way to flash images to your phone. it is accessed via hboot. you need the fastboot exe from the htc developer site. it can flash the boot (kernel), recovery (eg clockworkmod) and the radio (i think).
3-What is eMMC write?
Click to expand...
Click to collapse
the emmc is the storage device which holds hboot, fastboot, recovery, /system, /userdata and (not sure about this one) radio. when you switch on your phone the emmc is read-only due to the s-on flag being set by hboot. you need to flash the engineering hboot which does not set s-on when you switch your phone on.
4-What is ext2 or ext4 (is it like the partition type of the SD card based on UNIX system? if yes, why should we change or modify this ext)
Click to expand...
Click to collapse
ext2 and ext4 are linux file system types. eg, windows is ntfs, linux has ext2/3/4 and others.
5-Rom manager (is it a desktop pc application or android device application? is it something like I can put the RUU file of the rom on my SD card and using the rom manager I can install the rom from there, nothing more nothing less?)
Click to expand...
Click to collapse
rom manager is an android app available on the market place to help with the flashing process. it can flash recovery partitions (as long as your phone is s-off), make nandroid backups (as long as you have clockworkmod & s-off). it can also flash custom roms. it does not flash these from within the android OS (afaik) but it will reboot into (not sure on this one) the recovery partition and leaves it instructions to flash a particular rom.

This thread is amazing!!
We had a lot threads like this in the HTC Blackstone Board of pocketpc.ch....
Hope to get more threads like this in every device category....
Thumbs up
Perhaps Threadstarter can write the answers in the first post...??

50chickens said:
an application must support multitouch and other gestures. eg, opera doesnt support multitouch (ie you cant zoom in and out) but the browser that comes with the DHD does.
boot loader = turn phone off. then, volume down + power on.
application must support running from /sdcard. When you install an app go to settings -> Applications -> manage applications. From here you can uninstall or move apps to the sdcard. Bear in mind if you have not rooted your phone you may not be able to uninstall some apps (eg amazon reader).
some application data is stored on your sdcard, and apps are stored here if you have moved them by using the steps above. if you change sd cards this info is unavailable to the app but the app should still work. any settings you had need to be redone.
the kernel is not part of a rom or the radio. It is stored in the boot partition in the emmc (where fastboot(aka hboot)/splash images/boot(kernel)/recovery/ are all stored). It is generally included with but not required by a custom rom. ie, a custom rom builder may choose to include a specific kernel with his rom but it is not mandatory.
yes, you can do OTA HTC updates. but, there are no custom (non signed) updates delivered OTA. An unrooted rom will not be able to flash non signed updates (or roms).
there is a good thread here - http://forum.xda-developers.com/showthread.php?t=841076.
android application. eg, visionary+.
hboot is also known as bootloader. it is the white screen with the skating androids when you do the volume-down + power combination when switching on your phone.
s-off stands for security off. you can check the status by doing the volume-down + power combo. At the top it will either say s-on or s-off. If you have s-on then your bootloader (hboot), boot (kernel) /system (android) and recovery (eg clockworkmod) partitions are all read only.
clock work is the recovery partition. you have 3 possible options before loading android when you do the volume-down + power on combo. hboot, then either fastboot or recovery. fastboot and recovery are both ways to flash images to your phone although through different ways (fastboot uses the fastboot command on your pc to send the image, recovery uses .zip's on your /sdcard). clockworkmod is a custom recovery image which you need to flash after achieving s-off. it's also where nandroid backups can be done. if you select recovery before doing this you will get the phone + red triangle icon. thats the stock recovery. the clockworkmod is the green menu selection one.
see above.
clockwork mod can backup your phone's partitions (boot/userdata/system) so that if you mess up installing a rom you have a way to recover. this is known as a nandroid backup.
adb is android debug something. It is a way to send commands to the android operation system from your pc (either windows or linux). eg, you can run a single command, or run a shell (terminal session). it is part of the android sdk under tools.
busybox is a single executable whihc runs under the android OS that provides standard linux commands (eg, ls, rm, cd) to any application. it is so that a script writer does not need to know the partiticular rom you have and then cater for it, but only that you have a certain version of busybox. eg, busybox 1.17.1 provides the same commands whether it is on a leedroid rom or a cyanogen rom.
fastboot is a way to flash images to your phone. it is accessed via hboot. you need the fastboot exe from the htc developer site. it can flash the boot (kernel), recovery (eg clockworkmod) and the radio (i think).
the emmc is the storage device which holds hboot, fastboot, recovery, /system, /userdata and (not sure about this one) radio. when you switch on your phone the emmc is read-only due to the s-on flag being set by hboot. you need to flash the engineering hboot which does not set s-on when you switch your phone on.
ext2 and ext4 are linux file system types. eg, windows is ntfs, linux has ext2/3/4 and others.
rom manager is an android app available on the market place to help with the flashing process. it can flash recovery partitions (as long as your phone is s-off), make nandroid backups (as long as you have clockworkmod & s-off). it can also flash custom roms. it does not flash these from within the android OS (afaik) but it will reboot into (not sure on this one) the recovery partition and leaves it instructions to flash a particular rom.
Click to expand...
Click to collapse
Thank you very much.

[Q] Confused and Overwhelmed. After some Clarity!

Hello!
I recently purchased a HTC Desire HD through a carrier in Australia after being a nokia dumbphone owner for my "connected life". I have done some reading into the Custom ROM scene and I am loving the potential benefits and modifications that are possible with them, however being new to Android, new to Smartphones and new to Custom Roms I am to say the least a little confused.
I decided this carrier added bloatware just has to go and after a little reading I like the idea of LeeDrOiD HD v1.2.
I have attempted to follow the instructions in the Leedroid HD thread.
http://forum.xda-developers.com/showthread.php?t=842802
Which tells me i Need to flash.
http://forum.xda-developers.com/showthread.php?t=842819
Which in turn tells "You will need the ENG HBOOT installed on your device to flash this recovery!"
and of course I could not find any details on what ENG HBOOT is let alone how to install it.
How deep does the rabbit hole go Alice? The multiple tears are becoming confusing and complicated and I am wondering if this is just a LeeDroid thing, or are these steps necessary for all custom roms? Or just the Desire HD. I am fairly confident with the safety of replacing a rom but the more steps by more people are adding uncertainty in the safety of the whole procedure and of course raising the probability of an under informed and maybe slightly reckless newby to brick a perfectly acceptable phone.
Is anyone able to reccomend a resource to better acquaint a Newby with this new territory? Is thier a more comprehensive guide to installing LeeDroid or "Rom-ing" an android phone.

Hi,
Give me a few minutes to pull together a few guides for you.
This Guide with Video is very helpful at performing all the little tasks that allow you to flash custom ROMs.
In short the ENG HBOOT allows the flashing of an unsigned recovery "Clockwork Mod", which then allows you to flash custom ROMs. Flashing the ENG HBOOT is a one time process, once you have done it there is no need to do it again.
Just a few questions,
1). Do you have a Stock HTC Unbranded & Unlocked ROM or a Carrier Branded ROM?
2). Have you rooted you DHD yet?

This is the way I personally went about the whole process, its a guide that zexbig posted and can be found HERE
Summary:
1) Download Paul's Visionary+ tool (I have used version r12) (google removed this app from market) so You will have to download it from Paul's website.
This tools enables root and removes new HTC protection.
2) Install engineering version of HBOOT to get S-Off (HTC bootloader, something like BIOS for Your PC)
This step is optional and it's not required in order to flash custom ROM's on Your DHD but gives You more freedom with Your device.
3) Install custom recovery image (recovery is special program which is invoked from HBOOT
in order to flash ROM onto Your device.
Detailed description:
1) Download Paul's Visionary+ tool
1.1) Click here to download http://android.modaco.com/content/ht...ne-click-root/ or download it from here http://forum.xda-developers.com/atta...3&d=1290501865
1.2) Install Visionary+ on Your DHD
1.3) Run it, enable "Set system r/w after root
1.4) Click "Temproot Now!" - Wait until it's finished
1.5) Click Attempt Permroot Now!
1.6) DHD automatically reboot's
To test that everything went fine download from market application "terminal emulator"
run it, type su
If You get after that sign # it mean's that everything went fine.
Time for next step!
2) Install engineering version of HBOOT to get S-Off
2.1) Download sfjuocekr DHD script for flashing HBOOT from here
http://forum.xda-developers.com/showthread.php?t=835746
2.2) Unzip it and copy it to Your SDCard (It's important that You have on Your SDCard root directory with name DHD and all files inside this directory.
(I have run into the strange problem for which I'm not sure is it problem with my PC or DHD, each time when I connected my DHD via USB cable my SDCard was automatically mounted as Disk Drive instead of just being in "Charge only" mode. I resolved this by removing back cover and ejecting SDCard and inserting it again while phone was operational, which is very unsafe thing to do!).
2.3) Run Terminal Emulator
2.4) Type su
2.5) Type "sh /sdcard/DHD/check
(Please be aware that You have to type "sh" in front of command)
2.6) If everything went OK type
sh /sdcard/DHD/backup
2.7) If this also went OK proceed with
sh /sdcard/DHD/hboot
This command will install engineering hboot which have S-Off turned off.
3) Install custom recovery image
3.1) Since ROM manager now officially support's Desire HD, we will use it to download and install custom clockwork image.
3.2) Run android market app on Your DHD and download and install ROM Manager app from market.
3.3) Download and install ROM manager.
3.4) Run ROM manager and select first option (Flash ClockWorkMod Recovery).
3.5) Wait until ROM Manager say's that installation went successfully (Current version of ClockWorkMod is 2.5.1.3)
3.6) After installation tap in Rom manager option Reboot into Recovery to test that everything went well.
3.7) DHD should reboot in clockwork recovery manager.
Click to expand...
Click to collapse
-Visionary is now v14+, not 12 as posted.
If you have any problems, just let us know.

Quick Response thanks!
It is unfortunatly a Carrier Branded rom. Full of widgets that are just links to webpages. What is even worse is I bought my phone through a company who leases lines off the carrier so because I am technically not with the carrier I can't use their aps even if i wanted to.
I believe I have temp rooted it so far. I have downloaded VISIONary +

Epic.. Thank you kindly. I am in the process.

I don't understand why carriers have to ruin the whole "Android Experience" by bundling awful apps that nobody wants, otherwise they would of downloaded them themselves.
The last guide I posted is the one I used. Once you have followed all of the steps then your in a position to flash a custom ROM. If you are planning to overclock or underclock then you will also need to find a suitable "Kernel" to flash with your ROM. Most ROMs do come complete with a custom kernel but that may not be the best for your particular needs.
Once bit of advice. Always, always a backup of your ROM before you flash anything else.
Flashing custom ROMs is easy once the above steps are complete.
1). Download your chosen ROM.
1a). Optional Download your chosen Kernel.
2). Transfer ROM (+ Kernel) to your SD Card, place in the root of the card.
3). Boot into Recovery. Power off (Ensure HTC Fast Boot is disabled), Power on whilst holding VOL DOWN, using volume keys select Recovery, press power to enter.
4). Create Backup, backup and restore > backup.
5). Wipe All Data including cache
6). Install .zip from SD Card, Select the correct ROM zip and confirm.
7). Optional, repeat with Kernel, if necessary.
8). Reboot.
9). Bask in glory, you have conquered your smartphone.
Again, if you want more info feel free to ask. We all had to learn once, or twice.

For Clarification on HBOOT loading.
2.2) Unzip it and copy it to Your SDCard (It's important that You have on Your SDCard root directory with name DHD and all files inside this directory.
(I have run into the strange problem for which I'm not sure is it problem with my PC or DHD, each time when I connected my DHD via USB cable my SDCard was automatically mounted as Disk Drive instead of just being in "Charge only" mode. I resolved this by removing back cover and ejecting SDCard and inserting it again while phone was operational, which is very unsafe thing to do!).
I do want to be viewing the Android device as a disk drive?
Secondly Do I create a folder on the SD card in the root directory called DHD and then drop the 3 files contained in the Zip file into that folder?
Example
Root Directory
>.data
>Alarms
>Android
>bugreports
>DCIM
>DHD --Newly created folder
>>DHD-dumb --dragged and dropped
>>DHD-smart --dragged and dropped
RTFM.txt --dragged and dropped
>downloads
etc..

Yes you do want to view it as a disk drive.
You are also correct with the folders.
SDCard/DHD/ - place files here -

Ok my description failed.
Instead of the folders listed above
">>DHD-dumb --dragged and dropped
>>DHD-smart --dragged and dropped
RTFM.txt --dragged and dropped"
should I be taking the contents of (smart or dumb?) and placing that in the DHD created directory?
obviously the commands in the terminal dont correspond to having the files in a sub folder. I appologise for you having to answer obvious questions however I am a little weary of bricking.

I'd rather you post a question and get it answered before you post a problem and have an expensive paperweight.
Take the "DHD-smart" folder from wherever you extracted it, place that on your SD Card, then rename that folder to just "DHD".

Excellent. All Is working as planned. I'm in the process of D/L ing Leedroid rom.
Thanks for your help again.
I'll post back once I have things up and rolling.

No problem at all.
Just remember to make a backup from within "Recovery", it will save you one day.

I appologise I forgot to Post back.
Everything is running sweetly now, absolutley no bugs with the Root or new LeeRoid rom.
Thanks again for your help.

Daft Templar said:
I appologise I forgot to Post back.
Everything is running sweetly now, absolutley no bugs with the Root or new LeeRoid rom.
Thanks again for your help.
Click to expand...
Click to collapse
Welcome to the ranks of Android hackers. Health warning: flashing is addictive.
Sent from my performance enhanced Desire HD.

Yes it is
Sent from my Desire HD using XDA App

[UPDATE][WIFI ONLY][3.1] - Flashable, No Wipe Necessary, External Storage Enabled

FIRST THINGS FIRST:
This represents very little work that I've done on my own. It is mostly appropriating the work of others. The important thing to note is that the file works and it works well.
All I did to create this file was incorporate a modified version of stachre's updater-script into the official WiFi 3.1 update from Google (this is not the file you should flash).
I then added the kernel & all of the files from bigrushdog's HC3.1 .zip EXCEPT the system.img file (which is the vast majority of the update). BRD's HC3.1 installs the 3G version of 3.1 with Hotspot/Tethering options in the settings menu under Wireless & Networks, and I personally want to have the WiFi-only software on my WiFi XOOM. His version seems to work just fine and the only difference I noticed was in the Settings menu, but that was enough of a difference for me to prefer the WiFi only software. I'm sure more of you may feel the same. If there are any other differences between the WiFi & 3G software I'd be curious to know what, if any, there are.
I then added the code from BRD's updater-script (minus the parts relevant to flashing the system.img) on to the end of the updater-script from stachre's updater-script.
One of the benefits of this approach is that it does not require you to perform a factory data reset, as BRD's method currently does. And yes, you will have access to your external SD Card in the /sdcard/external folder.
It is super late and I am exhausted, but I wanted to share this with you before I fall asleep. If you seem to notice that these instructions are more or less copy and pasted verbatim from stachre's thread, that is because they are. This is a simplified version of his method with the addition of BRD's modified version of the stock 3.1 kernel for SD Card storage. There are fewer steps (now only 2) because more files are included in the zip.
[size=+1]DOWNLOAD HERE - FLASH IN CLOCKWORK RECOVERY:[/size]
MZ604_3.1_ROOT_update.zip
WARNING: Following this procedure may damage or permamently destroy your device. This procedure is provided with NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Perform this procedure at your own risk.
COMPATIBILITY NOTE: I have personally tested this procedure ONLY ON THE US XOOM WIFI MZ604. If other devices (i.e., Euro Xoom WiFi) implement the same Android 3.1 update file, then this procedure *should* work; some users have reported success with UK and Canadian models (see this post for more info). Know, however, that you proceed at your own risk. If you're stuck in a boot cycle, try a factory data reset in recovery.
[size=+1]SUMMARY[/size]
Here's a run-down on the current procedure:
Updates the Xoom WiFi to Android 3.1 using ClockworkMod Recovery (MZ604_3.1_ROOT_update.zip)
Resolves issue in updater-script: get_prop ro.product.device wingray
Pushes Superuser and su, sets correct permissions to enable functioning root
Flashes the system partitions to stock (required at this time)
Flashes bigrushdog modified stock boot.img (kernel) to enable external storage
Updates bootloader to include Recovery in the boot menu
Leaves user data intact
Leaves recovery intact
Outstanding Issues:
The new
Videos.apk does not appear in app drawer after update, according to Motorola this was done intentionally. Videos still play in Gallery. For some reason Motorola doesn't want us to use this app yet on the WiFi Xoom, but it's available on the 3G Xoom.
Now, without further ado...
[size=+1]ASSUMPTIONS[/size]
You've downloaded the update here: MZ604_3.1_ROOT_update.zip
You've downloaded and unzipped the stock Xoom WiFi MZ604 HWI69 images from Motorola also available via torrent
You've flashed a recent version of ClockworkMod Recovery (thanks, bigrushdog, koush, et al)
You've installed a physical SDCard in your Xoom (required for ClockworkMod Recovery updates) and have it functioning properly
You've configured the Android SDK on your PC, with adb functioning properly
You've downloaded fastboot and have it functioning properly (usually alongside adb in platform-tools)
[size=+1]PROCEDURE[/size]
Flash stock system.img & boot.img
Prior to performing the actual update, the update script checks a number of files (including bcm4329.ko, which is usually built with the kernel) in /system. If any file doesn't match what's expected, the update halts. Flashing the stock system.img ensures a smooth update.
The pre-update checks also include the boot partition. The actual update flashes this partition with a new kernel that implements the new 3.1 features.
If you are unlocked and running unrooted stock Android 3.0.1, you can skip step 1. If you are already on 3.1 and just need root and/or external SD card storage, see this thread.
Code:
adb reboot bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
Perform update
Code:
adb reboot recovery
You may need to re-enable USB debugging in the Application settings menu before you can send the above adb command. Alternately after sending 'fastboot reboot' in step 1, wait a few seconds after you see the Motorola logo and tap the Volume Down button. If you see "Android Recovery" at the top of the screen, tap the Volume Up button to boot into recovery and install from there.
Note that in recovery, you use the hardware volume buttons to navigate up and down, and the power button to select.
In ClockworkMod Recovery, select "mounts and storage"
Ensure your Xoom is connected to your PC via USB, then select "mount USB storage"
On your PC, copy MZ604_3.1_ROOT_update.zip to the root of the Xoom's SDCard ("Removable Disk" in Windows)
In ClockworkModRecovery (still on the "USB Mass Storage device" screen) select "Unmount"
In the "Mounts and Storage Menu" screen, if the option "unmount /sdcard" is present, continue to the next step; if "mount /sdcard" is present, select it then continue
Select "+++++Go Back+++++"
Select "install zip from sdcard"
Select "choose zip from sdcard"
Select "MZ604_3.1_ROOT_update.zip"
Select "Yes - Install MZ604_3.1_ROOT_update.zip"
"Install from sdcard complete." will indicate that the update is completed.
.
Select "reboot system now"
New bootloader will install. The message, "Congratulations! Your bootloader was successfully upgraded" will be immediately followed by an automatic reboot.
Enjoy your rooted Xoom WiFi, running on Android 3.1!
CUSTOM KERNELS:
I told you guys it wouldn't be long. TDR has already released an overclock kernel for WiFi Xooms on 3.1.
Tips & Tricks for quick-booting into Fastboot & Recovery:
Booting into Fastboot:
Hold down both the power button and the Volume Down button. Fastboot support will boot and you can flash system/recovery/userdata images.
Booting into Recovery:
I haven't seen anyone else mention this. If you power up, wait a few seconds after the Motorola logo appears, then hit the Volume Down button you will see "Recovery" appear at the top of the screen. Hit the Volume Up key to boot into recovery!

Great instructions, the simplest I could see so far! The above process worked for my WIFI only XOOM which I had rooted and installed the Tiamat Xoom Kernel. I am in Australia so was impatient to wait for OTA which probably wouldn't have worked anyways from what I have read.

How does this differ from bigrushdogs procedure? I have a wifi only xoom and am not sure which method to follow. Is this for stockusers?

it is different because no wipe is needed, if you are stock (unrooted) you will have to wipe when you unlock the bootloader
This is exactly the method I used, though I did thinks manually and it took a while, but works great
I don't know about the videos.APk thing, there are some 3g users with the same problem, one current theory is that it has something to do with root
Sent from my Xoom using Tapatalk

Dubar said:
I don't know about the videos.APk thing, there are some 3g users with the same problem, one current theory is that it has something to do with root
Click to expand...
Click to collapse
I think this problem is a bit two-faced, as a few of us on the 3G/VZW XOOM have updated fine and have a working video player, but rentals purchased do not play instead throw an Error 49 license error, while local content plays fine.
The Wifi users are reporting that the videos app doesn't even show up, let alone open. General suckage, not even being able to play local content.
I've been tinkering around with logs and trying to narrow down my error 49 issue but thus far have been unsuccessful.

xoppaw said:
How does this differ from bigrushdogs procedure? I have a wifi only xoom and am not sure which method to follow. Is this for stockusers?
Click to expand...
Click to collapse
Yeah, the two main differences between this and BRD's procedure is that you don't have to perform a factory reset to get this one to work, and this method requires adb/fastboot. I don't think you should have to erase all your data just to install an official update. It's also only one file to flash.
The other difference is that this version doesn't have artifacts from the 3G version in the Wireless & Networks Settings menu (if that bothers you).
I don't know if this update would apply on an unlocked and unrooted Xoom, but if your Xoom is unlocked this version of the update should give you root. Both would be worth testing
Dubar said:
I don't know about the videos.APk thing, there are some 3g users with the same problem, one current theory is that it has something to do with root
Click to expand...
Click to collapse
tekuru said:
I think this problem is a bit two-faced, as a few of us on the 3G/VZW XOOM have updated fine and have a working video player, but rentals purchased do not play instead throw an Error 49 license error, while local content plays fine.
The Wifi users are reporting that the videos app doesn't even show up, let alone open. General suckage, not even being able to play local content.
I've been tinkering around with logs and trying to narrow down my error 49 issue but thus far have been unsuccessful.
Click to expand...
Click to collapse
You can still play videos/local content fine through the gallery app, so we are safe in that respect. I can still watch all my movies or videos filmed on the Xoom just fine.
Here are some observations that I made. The WiFi update only included the Videos.apk file while the 3G update also included a Videos.odex file as well. I chose to add the Videos.odex to the update file in the OP, but it didn't make a difference (Videos apk still doesn't show in the app drawer).

Thanks.. Worked great.
Note: I had to re-enable USB debugging on the Xoom after flashing the Stock System and Boot Images.

Land Master said:
Thanks.. Worked great.
Note: I had to re-enable USB debugging on the Xoom after flashing the Stock System and Boot Images.
Click to expand...
Click to collapse
Thanks, I updated the OP to take account of that. Ever since I figured out how to boot into recovery from the Motorola logo I haven't really needed to send the 'adb reboot recovery' command.

I used BRD update method for my wifi zoom (don't care about the extra settings) and I have a working videos.apk that plays local content. I have not yet tried to rent a video.

kev0153 said:
I used BRD update method for my wifi zoom (don't care about the extra settings) and I have a working videos.apk that plays local content. I have not yet tried to rent a video.
Click to expand...
Click to collapse
Yes, I'm pretty sure for whatever reason the Videos.apk is enabled for the 3G version of 3.1 but not for the WiFi version of 3.1. I agree that the extra settings isn't a big deal, I made this file mostly because I wanted a way around wiping all of my user data.
Rumor has it that Google has said that the Videos.apk will be working on the WiFi Xoom in a few days.

I used the method posted by stachre from yesterday, and I don't have access to my sdcard in sdcard/external. Any way I can change that? The two methods seem to be very similar...and I want my SD!

IXIKelsonIXI said:
I used the method posted by stachre from yesterday, and I don't have access to my sdcard in sdcard/external. Any way I can change that? The two methods seem to be very similar...and I want my SD!
Click to expand...
Click to collapse
Download and flash this file:
http://www.mediafire.com/download.php?2bj5taicy3buc5c
Basically do what I said to do in the OP but skip step 1.

You are beautiful, and I love you.

I installed brd's 3.1 update yesterday, and i tried to install this zip over his method because i have a wifi xoom and wanted to get rid of the hotspot settings, but when i try to flash this in cwm i get an error:
Assert failed: file_getprop("system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.0.1/hwi69/110420:user/release-keys" || file_getprop("system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.1/hmj37/124251:user/release-keys"
E: error in /sdcard/mz604_3.1_ROOT_update.zip
(status 7)
installation aborted
What is the problem? Is it not possible to flash this over his method? Do i have to change the build.prop?
Thanks
Edit:
Solved by going back to stock 3.0.1 and installing the cwm to get updated to 3.1.

WARNING Boot Loop!
Warning. This method set me in to a boot loop. The tip at the bottom of the instructions eventually saved me as I booted in to recovery (adb stopped working after awhile) and upgraded via bigrushdog's clockwork thread. Not sure if it was my custom boot theme or something else. I reflashed twice while adb was still working. All looked good each time but then when I rebooted to do the final cwm step, this is where I looped each time. I was careful. Not sure why it messed up.

Thanks a lot for putting this together, worked like a charm.

So what about overclocking. I don't have option above 1ghz. Is this because we are back on a stock kernal. Will we have to wait for Tia to make a new one?
Sent from my Xoom using XDA Premium App

kntdookoo said:
So what about overclocking. I don't have option above 1ghz. Is this because we are back on a stock kernal. Will we have to wait for Tia to make a new one?
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Bigrushdog has said that they are working on an overclock tiamat kernel for Android 3.1. So yes it is expected that you can not overclock your xoom in 3.1 currently.
A few questions since I have not updated my xoom to 3.1 yet:
1) Is everyone experiencing the Videos.apk error where they can't install the videos app?
2) How are the 3.1 updated features? Can anyone share if the overall user experience is better in 3.1 (better scrolling, smoother, etc).
I am kinda holding off updating 3.1 until I hear more of the drawbacks of 3.1.

ericdabbs said:
Bigrushdog has said that they are working on an overclock tiamat kernel for Android 3.1. So yes it is expected that you can not overclock your xoom in 3.1 currently.
A few questions since I have not updated my xoom to 3.1 yet:
1) Is everyone experiencing the Videos.apk error where they can't install the videos app?
2) How are the 3.1 updated features? Can anyone share if the overall user experience is better in 3.1 (better scrolling, smoother, etc).
I am kinda holding off updating 3.1 until I hear more of the drawbacks of 3.1.
Click to expand...
Click to collapse
1. It's weird. My understanding is that even, unrooted stock WiFi Xoom owners can't access the new Videos apk on 3.1. The Videos.apk is there it just doesn't show up in the app drawer so there isn't any way to access it. If you look for it in a file manager like Root Explorer you can see it. There are other "ghost" apps like that in Android like the SoundRecorder.apk, so that's not completely unheard of. What's puzzling is why the 3G Xoomers got one that works and we didn't. If/when this is solved I will update the OP. It does work if you use bigrushdog's update method (but you gotta wipe all your data).
The Videos apk is mostly a showcase for their Video rental service that they announced Tuesday, you can still play videos in Gallery, so you're not really missing out on any major functionality at the moment.
2. The new features are cool! It's hard to compare performance since I was overclocked before and now I'm not. I love the resizable widgets. Overall it does feel like a more polished OS, they fixed a whole bunch of little itty bitty issues here and there. I can't really think of any downsides to the upgrade, it just feels like a step in the right direction. I'm definitely looking forward to see where Honeycomb development goes in the future.

I have installed this update over my rooted wifi only 3.0. It worked great, i did get a boot loop and was forced to wipe in recovery (luckily i did a titanium backup first), apart from that it went through no problem.
I haven't used the browser extensively yet, but it does seem more stable, hasn't crashed yet and the overall browser seems much better, especially the thumb menu from labs.
Good work!!
(I have the wifi only UK version BTW)

[GUIDE][FAQ][Android 4.4 KitKat] Installing & Customizing CM11 or SlimKat

This guide explains how to install and update CyanogenMod 11 (CM11) and SlimKat roms (aftermarket firmwares of Android 4.4) on your Motorola Defy (MB525) or Defy+ (MB526). Neither the CyanogenMod development team nor the Slim Roms development team officially support the Defy. Thankfully, a number of independent developers (listed below) are working hard to port those roms to the Defy, and the present versions are mostly (but not completely) bug-free and stable.
Please note: The latest CM11 and SlimKat roms for the Defy still have a few bugs, most of which are explained in a bug list that is frequently updated by okij. Although okij's bug list concerns the CM11 roms built by Quarx, most of these bugs also apply to TJKV's SlimKat roms, which are based partly on Quarx's sources.
If you just want a perfectly stable, bug-free phone, and don't care about having the latest and coolest features of Android, CM11 and SlimKat are not for you. I recommend installing CyanogenMod 7 (CM7) instead: it's very fast and perfectly stable. However, CM11 and SlimKat are continually becoming more stable, and are already usable as daily drivers if you can live with the few remaining bugs.
How to install Android 4.4 SlimKat or CM11 on the Motorola Defy or Defy+
Step 1: Download the correct files for installation.
If installing SlimKat, download the rom (Slim-mb526-4.4.2.build.4-UNOFFICIAL-20140407-2344.zip) and Google Apps package (minimal_Slim_AIO_gapps.4.4.2.build.4.zip) here.
If installing CM11, download the rom here (or here) and the minimal Google Apps package here (or here or here). (You want the file called "GApps_Minimal_4.4.4_signed.zip". Do NOT try to install the "Standard" Google Apps package, as there is not enough room on the Defy's system partition.)
Customize the rom file if desired. (See "Tips for customizing & improving performance," below.) Then put both files on your phone's SD card. Also download defy_twrp_recovery_2.6.3.0.zip and safewipe.zip, and put those files on the SD card too.
Note: SlimKat build 4 is very stable, but it does have a bug that causes the phone to reboot into recovery mode automatically if the phone encounters a telephony error, instead of rebooting normally. To fix this issue, download DefyParts.apk here and replace the old DefyParts.apk by following the instructions in this post.​
Step 2: Install Team Win Recovery (TWRP) version 2.6.3.0 (or newer).
If you have already installed a custom recovery on your phone (e.g. ClockWorkMod or an earlier version of TWRP) and you know how to use it, just flash defy_twrp_recovery_2.6.3.0.zip and proceed to step 3. If you've never used a custom recovery, keep reading.
If you're using a stock rom from Motorola, you first need to root the phone (I recommend using either Framaroot or SuperOneClick), then install 2ndInit. Run the 2ndInit app and use it to install the custom recovery (ClockworkMod Recovery). Then reboot the phone, and watch the small LED light at the top of your phone. If the recovery was installed properly, the LED will light up with a blue color for a few seconds during startup. Allow the phone to fully boot up, then reboot the phone again and watch for the blue light. As soon as you see the blue light, press the volume down button to enter the bootmenu. Use the volume buttons to navigate the menu and the power button to select an option. Select Recovery > Custom Recovery > Backup and restore > Backup (all), and wait for the backup process to complete. This will create a backup of your system on your SD card, so you can revert to the stock rom later if needed. Next, select Go Back > install zip from sdcard > choose zip from sdcard, and install defy_twrp_recovery_2.6.3.0.zip.
Step 3: Install CM11 or SlimKat, and the corresponding Google Apps package.
After installing TWRP 2.6.3.0, reboot the phone and enter the bootmenu again by pressing the volume down button when you see the blue LED. (Note: If you're updating from a recent version of SlimKat or CM11, you won't see any blue light. Instead you'll see a screen that tells you to either press the menu button to enter recovery or the search button to continue with normal bootup.)
Enter TeamWin Recovery, which you can navigate with the touchscreen rather than the volume buttons. Wait 30 seconds before proceeding, to make sure the recovery is behaving in a stable way. (If the phone spontaneously reboots, just try again.)
Select Install, choose safewipe.zip, then swipe to confirm the flash.
In the same way, flash the rom of your choice (either SlimKat or CM11), followed by the Google Apps package.
Reboot the phone. The first boot will take a while (typically 5-10 minutes), since the phone has to build the Dalvik Cache.
Step 4: Set the correct baseband, and adjust performance settings.
Go to System settings > Advanced options > Device > Baseband selection, and make sure that the correct baseband is selected for your region and carrier. (Note: This step is not necessary if you already changed the default baseband in the zip file. See "Tips for customizing & improving performance," below.)
I also strongly recommend configuring the rom for better performance, by following the tips listed below. (See especially the tips about using Aero Kernel Control. This will help with many problems, for example the infamous call wakeup delay issue.)
Step 5: Thank our awesome developers, and donate to them if you can.
You can find donation links under any post by the developers. (Just look for the button that says "donate to me.") Here's the donation link for Quarx.
How to update SlimKat or CM11 to newer versions (or downgrade to older versions)
Step 1: Backup your current rom, apps, and settings.
I recommend using Online Nandroid Backup to create TWRP-compatible backups, for the reasons mentioned here (see bug #36). In the Online Nandroid Backup app, select Custom Backup > Backup Type > TWRP. Then select Backup Mode > Selective, and select the "system" and "data" partitions to backup. Make sure the Save Location is set to /sdcard, and also check the box to "Exclude Dalvik Cache." Then press the blue arrow (looks like a "play" button) at the top right corner of the screen to begin the backup.
Also back up your apps and settings with Titanium Backup.
Step 2: Download the updated rom.
Customize the rom file if desired. (See "Tips for customizing & improving performance," below.) Then place it on your phone's SD card along with the appropriate Google Apps package. [Note: if using CM updater, you don't have to download the rom ahead of time.]
Step 3: Install the updated rom using one of the following three methods:
Note: If switching from SlimKat to CM11 or vice versa, you must use the clean install method.
"Clean" install (recommended)
- Boot into TWRP by pressing the menu button when you see the bootstrap image (the screen that tells you to either press the menu button to enter recovery or the search button to continue with normal bootup), which should appear just after the Motorola logo disappears and before the boot animation begins.
- Select "Install" and flash safewipe.zip, then flash the updated rom, followed by Google Apps.
- After rebooting the phone, you'll have to restore your apps and settings using Titanium Backup. Don't restore settings for system apps unless necessary, as that may lead to problems.
"Dirty" flash (easier, but may cause problems)
- Boot into TWRP and select Wipe > Advanced Wipe, and select Dalvik Cache, Cache, and System (not Data), then swipe to wipe. (WARNING: Wiping the system partition also deletes the custom recovery, so you must either flash a rom or restore a backup before rebooting the phone. If the phone is rebooted before a new system is installed, it will be "soft bricked" and you'll have to flash a stock sbf with RSD Lite to recover it.) Then press the back button to return to the main menu and select Install. Flash the updated rom, followed by Google Apps. Now it is safe to reboot the phone.
- Since this method does not affect the /data partition, you won't have to restore all of your apps and settings, but you may still need to switch the baseband. If you encounter any bugs or problems after updating the firmware by this method, do not report them. First try a "clean" install, and check whether that solves the issue.
CM updater method (easiest, but may cause problems)
- If you're using CM11, you can update via the built-in CM updater located under Settings > About Phone > CyanogenMod Updates. (Obviously this won't work on SlimKat.)
- If you encounter any bugs or problems after updating the firmware by this method, do not report them. First try a "clean" install, and check whether that solves the issue.
Tips for customizing & improving performance
How to customize the rom before installation:
Install 7-zip on your PC.
Right-click on the CM11 or SlimKat zip file and select 7-zip > Open archive. (Don't extract it; just open it.) Now you can:
Remove unnecessary files to save space on the system partition. For example, you can navigate to system > media > audio, and delete any ringtones you don't use. You can also delete unused apps from system > app. See @x53's post here for a list of system apps that are safe to remove; see also here and here for more info. Here's a list of system apps that I removed before installing SlimKat: BasicDreams (live wallpaper), Browser (I use Next Browser instead), Calendar, Dashclock, Deskclock, Email (I just use Gmail app), Exchange2, Gallery2, Livewallpaperspicker, PhaseBeam (live wallpaper), PhotoTable, PicoTTS, Slimcenter, SlimFileManager, SlimIRC, SoundRecorder, VisualizationWallpapers.
Replace the default bootanimation in system > media. (Just drag and drop your custom bootanimation to replace the original.)
Replace the default bootstrap image in system > bootstrap > images.
Change the default baseband. To do this, navigate to system > etc > motorola > basebands, and find the zip file that corresponds to your region and carrier. Drag that file out to a folder on your PC, and extract (unzip) it. Then drag and drop those extracted baseband files into system > etc > motorola > bp_nvm_default, replacing the default baseband files in the rom.
Edit build properties. To do this, find the build.prop file in the system directory, and drag it out to a folder on your PC. Open the file in Notepad++, and edit the build properties as desired. (For example, you can change the LCD screen density by editing the line that says "ro.sf.lcd_density=". The default density in CM11 is 240, and the default in SlimKat is 213. Larger numbers make icons appear larger on your screen.) After making any desired changes, save the file and drag it back into the rom zip file where you found it, replacing the original.
After installation, configure the rom for better performance:
Install Aero Kernel Control from the Google Play store, which will allow you to tweak many settings to improve the performance of your phone. For starters, I recommend the following: In the Aero Control app, go to CPU Performance > Governor Settings, and select “ondemand”. The default is Interactive governor, which may be able to deliver slightly better performance if you know how to tweak its settings, but its default settings aren’t very good, so I recommend using On Demand at least initially.
If you want to try using Interactive governor, I recommend the following settings: open Aero Kernel Control, go to CPU Performance, select Interactive governor, then tap the little phone icon at the top right corner of the screen to open the settings for the Interactive governor. Set suspend_enabled to 0. That should help to reduce the call wakeup delay. Changing hispeed_freq and input_boost_freq to your maximum value (e.g. 1200000 if you've overclocked to 1200 MHz) will also boost performance, though you may see a slight drop in battery life. Note: Interactive governor is not recommended for CM11 builds prior to the 06-10 nightly, because the suspend/resume handler was missing. (See okij's note on bug #26 for more info.)​
Open the HWA Settings app (which is already installed as part of the rom) and disable HWA for all apps except ones that really need it. (Explanation: HWA requires more RAM, and the Defy is already short on RAM, so enabling HWA usually does more harm than good. That's why it's best to disable it whenever it's not really needed for an app to function properly.)
The following apps require HWA: Camera, Dialer (on CM11 only), Google Maps (version 7+), Chrome browser. Other apps may also require HWA. If an app doesn't display properly, try enabling HWA again to see if that solves the problem.​
Install Greenify, which you can use to “hibernate” any apps that you don’t want to run automatically at startup.
Other tips & suggestions:
You may wish to install Google Camera instead of the stock camera, for the reasons mentioned here.
For offline voice recognition, see here.
For better GPS performance, you may want to try flashing this zip and/or using this app. (Thanks to @Male_zvire and @okij for recommending these solutions.)
FAQ & what to do if something goes wrong
A freshly installed rom takes some time to "settle" while various services run in the background, so the phone may be a bit unstable at first. If you're still encountering errors or other problems after a few hours, first check the bug list and use the XDA forum search feature to see if the issue you are having has already been reported.
If you think you've found a new bug, don't just complain about it; try to help solve it by taking logs. @measel has provided a very helpful guide for taking logs.
What if the phone doesn't boot up properly?
If you can still access the custom recovery, just flash safewipe again and re-install the rom, or restore a backup. (To enter TeamWin recovery after installing SlimKat or CM11, press the menu button when you see the screen that tells you to either press the menu button to enter recovery or the search button to continue with normal bootup. That screen should appear just after the Motorola logo disappears, and before the boot animation begins.)
If you can't access the recovery, you may need to flash an sbf file using RSD Lite. Be careful! Flashing an sbf file improperly is one of the few things that can actually hard-brick the Defy, and if you flash the wrong sbf file for your phone, it may be impossible to restore your phone back to its original firmware. Read the All-in-One Defy Beginner's guide for more information about sbfs and RSD Lite. You can also check out the Motorola Defy wiki page for other tips and tutorials.
A special thanks to @Quarx, who has been faithfully updating our phone to newer and better firmwares since the beginning of Defy history, and has undoubtedly put more work into this project than anyone else. Thanks also to our many other developers, past and present: @TJKV (who uses Quarx's kernel sources to port SlimKat to the Defy), @Blechd0se (who has made significant contributions to the kernel development for the Defy and also developed the Aero Control app that we use to fine-tune the performance of our phones), @SlugZero, @YetAnotherForumUser, @struq, @htto, @Epsylon3, @maniac103, @walter79, @czechop, @kabaldan, and @Kayant. Many thanks to all of them, and to anyone I may have forgotten. Thanks also to @okij and other Defy users who have helped with testing new builds and identifying bugs for the developers to solve.

suggestion for improvement
Thanks for the guide. I'm pretty sure it is very useful for beginners!
I would suggest to try to get rid of as much text as possible and make it more step-by-step-y, you know what I mean? People (at least I recognized that on me) tend to give up quickly when it comes to reading. Right now it looks really difficult!
Just a suggestions. People will still appreciate your work as is. Thanks.

CM 7 and SBFS
Proverbs2 said:
The following is a guide that I wrote for one of my family members, and I decided to post it here so that others may benefit. I know there are numerous similar guides already in the forums, but they have not been updated recently. I intend to keep this guide updated for as long as I own a Defy (and I have no plans to get rid of my beloved phone anytime soon).
This guide explains how to install either CyanogenMod 11 (CM11) or SlimKat roms (aftermarket firmwares of Android 4.4) on your Motorola Defy (MB525) or Defy+ (MB526). Please note that neither the CyanogenMod development team nor the Slim Roms development team officially support the Defy. Thankfully, a number of independent developers are working hard to port those roms to the Defy, and the present versions are mostly (but not completely) bug-free and stable. A special thanks to @Quarx, who has been faithfully updating our phone to newer and better firmwares since the beginning of Defy history, and has undoubtedly put more work into this project than anyone else. Thanks also to our many other developers, past and present: @TJKV (who uses Quarx's kernel sources to port SlimKat to the Defy), @Blechd0se (who has made significant contributions to the kernel development for the Defy and also developed the Aero Control app that we use to fine-tune the performance of our phones), @SlugZero, @YetAnotherForumUser, @struq, @htto, @Epsylon3, @maniac103, @walter79, @czechop, @kabaldan, and @Kayant. Many thanks to all of them, and to anyone I may have forgotten. Thanks also to @okij and other Defy users who have helped with testing new builds and identifying bugs for the developers to solve.
Please note: The latest CM11 and SlimKat roms for the Defy still have a few bugs, most of which are explained in a bug list that is frequently updated by okij. Although okij's bug list concerns the CM11 roms built by Quarx, most of these bugs also apply to TJKV's SlimKat roms, which are based partly on Quarx's sources.
If you just want a perfectly stable, bug-free phone, and don't care about having the latest and coolest features of Android, CM11 and SlimKat are not for you. I recommend installing CyanogenMod 7 (CM7) instead: it's very fast and perfectly stable. However, CM11 and SlimKat are continually becoming more stable, and are already usable as daily drivers if you can live with the few remaining bugs.
Installation instructions for Android 4.4 SlimKat or CM11 on the Motorola Defy or Defy+
Step 1: Make sure you've downloaded the correct files for installation.
If installing SlimKat, download the rom (Slim-mb526-4.4.2.build.4-UNOFFICIAL-20140407-2344.zip) and Google Apps package (minimal_Slim_AIO_gapps.4.4.2.build.4.zip) here.
If installing CM11, download the rom here and the minimal Google Apps package (4-16_GApps_Minimal_4.4.2_signed.zip) here.
Put both files on your phone's SD card. Also download defy_twrp_recovery_2.6.3.0.zip and safewipe.zip, and put those files on the SD card too.
Step 2: Install Team Win Recovery (TWRP) version 2.6.3.0 or newer.
If you have already installed a custom recovery on your phone (e.g. ClockWorkMod or an earlier version of TWRP) and you know how to use it, just flash defy_twrp_recovery_2.6.3.0.zip and proceed to the next step. If you've never used a custom recovery, keep reading.
If you're using a stock rom from Motorola, you first need to root the phone and install 2ndInit. Run the 2ndInit app and use it to install the custom recovery (ClockworkMod Recovery). Then reboot the phone, and watch the small led light at the top of your phone. If the LED lights up with a blue color for a few seconds during startup, the custom recovery was installed properly, but you still need to upgrade the recovery to TWRP 2.6.3.0. Reboot the phone again and watch for the blue LED light. As soon as you see the blue light, press the volume down button to enter the bootmenu. Use the volume buttons to navigate the menu and the power button to select an option. Select Recovery > Custom Recovery > Backup and restore > Backup (all), and wait for the backup process to complete. This will create a backup of your system on your SD card, so you can revert to the stock rom later if needed. Next, select Go Back > install zip from sdcard > choose zip from sdcard, and install defy_twrp_recovery_2.6.3.0.zip.
Step 3: Installing CM11 or SlimKat
After installing TWRP 2.6.3.0, reboot the phone and enter the bootmenu again by pressing the volume down button when you see the blue LED. (Note: If you're updating from a recent version of SlimKat or CM11, you won't see any blue light, instead you'll see a screen that tells you to either press the menu button to enter recovery or the search button to continue with normal bootup.)
Enter the newly installed TeamWin Recovery, which you can navigate with the touchscreen rather than the volume buttons. Wait 30 seconds before proceeding, to make sure the recovery is behaving in a stable way. (If the phone spontaneously reboots, just try again.) Then select Install, choose safewipe.zip, then swipe to confirm the flash. In the same way, flash the rom of your choice (either SlimKat or CM11).
If you installed SlimKat, you can now install the minimal_Slim_AIO_gapps file in the same way, then reboot the phone.
If you installed installed CM11, don't flash the Google Apps package yet, or it will conflict with the Cyanogenmod setup and cause an error. You must first reboot the phone and allow it to fully boot up. Then reboot the phone once more and go into TWRP recovery again. (Note: This time, you won't see the blue LED light; instead you'll see a screen indicating that you can press the menu button to enter the recovery.) Select Wipe > Advanced Wipe > and wipe the Dalvik Cache and the Cache. Then press the back button twice to return to the main menu and select Install, then install the GApps_Minimal_4.4.2 zip file, and reboot the phone.
Note: The first boot will take a while (typically 5-10 minutes), since the phone has to build the Dalvik Cache.
Step 4: Configure the Rom.
Go to System settings > Advanced options > Device > Baseband selection, and make sure that the correct baseband is selected for your region and carrier.
Open the HWA Settings app (which is already installed as part of the rom) and disable HWA for all apps except ones that really need it. (I disable HWA for everything except the camera. The latest version of Google Maps also requires HWA, but I’m using an older version that doesn’t.)
I recommend installing Aero Control from the Google Play store, which will allow you to tweak many settings to improve the performance of your phone. I'll post some suggested settings when I have time later; but for starters, I recommend the following: In the Aero Control app, go to CPU Performance > Governor Settings, and select “ondemand”. The default is Interactive governor, which may be able to deliver slightly better performance if you know how to tweak its settings, but its default settings aren’t very good, so I recommend using On Demand at least initially.
I also recommend installing Greenify, which you can use to “hibernate” any apps that you don’t want to run automatically at startup.
Step 5: Thank our awesome developers, and donate to them if you can.
Click to expand...
Click to collapse
Hey
very usefull guide, thank you for it.
Two suggestions
Can you add how to switch back to CM7 from CM11 for those that installed and did not liked it?
and SBFS this Guide is intented for those who already know alot of topics like TWRP
can you insert a referneces to guide explaining how to root?

Thanks @measel and @yosef_a for your suggestions. I'll try to implement these ideas as soon as I have time.

Nice Guide
Thanks @Proverbs2 for this great guide.
For the sake of completeness, I would suggest you to add a section in the post on How to safely update from one nightly to a another newer/older nightly.

Iloveyou and thanks for that guide I've made my first succeded rom install ever

MelaPL said:
Iloveyou and thanks for that guide I've made my first succeded rom install ever
Click to expand...
Click to collapse
Congratulations! :laugh:

Aero kernel on SlimKat
Hello, first of all great guide, big thanks.
Did anyone have this problem using Aero Kernel (which is still awesome app :good on SK, every time i instal Aero k. and start to using it phone display become so dark that only in total dark place (brightnes is set to auto) is posible to read (relly hard), and after uninstaling AK every is fine
Did I miss something? tx

Mislav12 said:
Hello, first of all great guide, big thanks.
Did anyone have this problem using Aero Kernel (which is still awesome app :good on SK, every time i instal Aero k. and start to using it phone display become so dark that only in total dark place (brightnes is set to auto) is posible to read (relly hard), and after uninstaling AK every is fine
Did I miss something? tx
Click to expand...
Click to collapse
That's a strange bug. I'm using Aero Control on SlimKat 4.0, and I've never had that problem. Which SlimKat version are you using? Are you using the latest version of Aero Control from the Play store?

Proverbs2 said:
That's a strange bug. I'm using Aero Control on SlimKat 4.0, and I've never had that problem. Which SlimKat version are you using? Are you using the latest version of Aero Control from the Play store?
Click to expand...
Click to collapse
Firs of all thaks for reply.
I'm got one device on SK 3.85 (20140323) and other on 4.0 (didn't try to use aero kernel because of problems with first one-stupid me), eveythig working great, (first time I instal it, SK take my breath, really can't searching for more with that old and hardware limited device like Defy is). Used Aero Kernel from Play store, these days was the latest (about month ago), take a chance 3-4 times during 10 days but allways with same result - start to using AK, about 5-10 hours having no issue and then darknes
Another thing that I notice (forgive me if i'm on wrong thread, can't make post on dev section), when my devices was on stock ROM after installing 2nd booth app (nothing else) the phones start to have screen wake up delay, just like now, 2-3 sec. Is it possible to exist some connection or is just coincidence!?

Mislav12 said:
start to using AK, about 5-10 hours having no issue and then darknes
Click to expand...
Click to collapse
In Aero Control settings, try going to GPU Control > Display Color, and make sure "Energy Saver" is not selected.
after installing 2nd booth app (nothing else) the phones start to have screen wake up delay, just like now, 2-3 sec. Is it possible to exist some connection or is just coincidence!?
Click to expand...
Click to collapse
Do you mean 2nd Boot (not Booth)? What exactly are you installing, and where did you get it?
Have you tried changing your governor settings for better wake-up performance? The default governor (Interactive) is set to limit the CPU frequency to 600 MHz when the screen is off, which can cause slow wakeup. In Aero Control, try changing the governor to OnDemand (or set suspend_enabled to 0 for Interactive governor). That might help.

Proverbs2 said:
In Aero Control settings, try going to GPU Control > Display Color, and make sure "Energy Saver" is not selected.
Do you mean 2nd Boot (not Booth)? What exactly are you installing, and where did you get it?
Click to expand...
Click to collapse
You're wright, there is no left or right boot for Defy :silly:, i was thinking about 2ndInitDefy app, just didn't read well before posted. Defy on stock ROM with this app (only rooted, and 2ndInit installed!) became lagy when call is reciving.
Have you tried changing your governor settings for better wake-up performance? The default governor (Interactive) is set to limit the CPU frequency to 600 MHz when the screen is off, which can cause slow wakeup. In Aero Control, try changing the governor to OnDemand (or set suspend_enabled to 0 for Interactive governor). That might help.
Click to expand...
Click to collapse
Will try tomorrow and report.
Thanks a lott.

Mislav12 said:
i was thinking about 2ndInitDefy app, just didn't read well before posted. Defy on stock ROM with this app (only rooted, and 2ndInit installed!) became lagy when call is reciving.
Click to expand...
Click to collapse
That's very strange. I wonder if the SndInitDefy app is somehow conflicting with another app that you use. Try taking logs with CatLog and see if that provides any clues.

Proverbs2 said:
That's very strange. I wonder if the SndInitDefy app is somehow conflicting with another app that you use. Try taking logs with CatLog and see if that provides any clues.
Click to expand...
Click to collapse
To late for log taking, won't go back on stock rom. Beside, settings for Aero K. you recommend are super, no problem annymore. Got my voice on presidential elections!:good:

Thanks for compiling this guide. I've been using OmniRom for some weeks on both my Defys and it's worked with very few problems. I wanted to give Quarx latest build a try though, so followed your guide, as previously when I've flashed Quarx CM11, I've had problems with the 4 lower buttons not working. However after attempting to install Safewipe from TWRP, my phone froze on the Moto logo and I had to flash the stock rom and start again. I'm running CM7.2 on my spare phone. Strange that Safewipe caused the very problem that it's meant to avoid on my phone.

Snugglehog said:
Thanks for compiling this guide. I've been using OmniRom for some weeks on both my Defys and it's worked with very few problems. I wanted to give Quarx latest build a try though, so followed your guide, as previously when I've flashed Quarx CM11, I've had problems with the 4 lower buttons not working. However after attempting to install Safewipe from TWRP, my phone froze on the Moto logo and I had to flash the stock rom and start again. I'm running CM7.2 on my spare phone. Strange that Safewipe caused the very problem that it's meant to avoid on my phone.
Click to expand...
Click to collapse
That's unusual. Did you remember to flash defy_twrp_recovery_2.6.3.0, reboot into TWRP version 2.6.3.0, and wait 30 seconds before flashing safewipe?

Proverbs2 said:
That's unusual. Did you remember to flash defy_twrp_recovery_2.6.3.0, reboot into TWRP version 2.6.3.0, and wait 30 seconds before flashing safewipe?
Click to expand...
Click to collapse
The TWRP version was integral to OmniRom, so I think it was v2.7.0.0. However after booting into TWRP I doubt I waited 30 seconds before flashing Safewipe. Why the need to wait?

Snugglehog said:
The TWRP version was integral to OmniRom, so I think it was v2.7.0.0. However after booting into TWRP I doubt I waited 30 seconds before flashing Safewipe. Why the need to wait?
Click to expand...
Click to collapse
TWRP is unstable, and sometimes causes random reboots within the first 20 seconds. I'm guessing your phone rebooted while flashing safewipe.

Home buuton stopped working
After a couple of months of using slimkat v.3.85 today home button stopped working. There is also problem with notification, and telephony (not able to reach the phone, but making calls from device is possible). I found that someone has similar symptoms in Quarks kk4.4 thread:
Sounds like the device got 'unprovisioned', this sometimes happens and leads to at least some of the effects you listed: status bar problems, home button, settings. If you haven't nuked the thing yet you might try to manually set the provisioning bits:
Code:
#!/system/bin/sh
db=/data/data/com.android.providers.settings/databases/settings.db
prv_dev="INSERT INTO secure (name,value) VALUES ('device_provisioned','1'); INSERT INTO global (name,value) VALUES ('device_provisioned','1'); INSERT INTO secure (name,value) VALUES ('user_setup_complete','1');"
/system/xbin/sqlite3 "$db" "$prv_dev"
Click to expand...
Click to collapse
I'v tried tu run that script but with no luck, i am getting errors. It is probably becaouse this script is for Quarq KK not SLimkat.
Any Help? (Sorry for posting this question here, but i am unable to post in dev section.)

ktwist said:
After a couple of months of using slimkat v.3.85 today home button stopped working. There is also problem with notification, and telephony (not able to reach the phone, but making calls from device is possible). I found that someone has similar symptoms in Quarks kk4.4 thread:
I'v tried tu run that script but with no luck, i am getting errors. It is probably becaouse this script is for Quarq KK not SLimkat.
Any Help? (Sorry for posting this question here, but i am unable to post in dev section.)
Click to expand...
Click to collapse
I've never run into that problem, and I don't know if there's any easy way to fix it, but you could try just wiping data then restoring your apps and settings with Titanium Backup. Make a nandroid backup (so if wiping data doesn't help you can restore all your data easily), then wipe data, cache, and dalvik. If that doesn't work, you may have to do a clean install.

[Q] Desire 820u has no Google Play.

I have Desire 820u CHinese version and it has only English and Chinese languages. No Goggle play and even does not allow to install Google play. Blocks it. I would like to install Google play. Is there any international ROM ?

Just unlocked it. But cannot flash any recovery.

[email protected] said:
Just unlocked it. But cannot flash any recovery.
Click to expand...
Click to collapse
What did you use? I have just used WinDroid Universal Toolkit to unlock bootloader, flash TWRP and root the phone. It worked, although it did take me a while to get it sorted due to issues with the drivers.
Everything seems to be working.

I hope it can help.
I have the same model, chinese version.
open HTC market, and look for GMS.... app.
download it, launch it, and when required enter the code *#*#.....
it will download somethink like 150M, your mobile will reboot, and at the end you'll find all google app in your mobile.
done.
without root, unlock or other

PLease can you write detaily ? What you said is unclear for me.
1. What do you mean with HTC Market ? I do not have HTC Market. It is called AppMarket and all in Chinese.
2. There are lots of GSM apps there and nothing worked in AppMarket.
Can you put url here ?
involato said:
I hope it can help.
I have the same model, chinese version.
open HTC market, and look for GMS.... app.
download it, launch it, and when required enter the code *#*#.....
it will download somethink like 150M, your mobile will reboot, and at the end you'll find all google app in your mobile.
done.
without root, unlock or other
Click to expand...
Click to collapse

sorry for my previous post....
1) open AppMarket (ok, it's all in chinese)
2) in the search bar enter GMS
3) download and install GMS安装器 (the icon is the android robot, with some gapp icon inside). it is 0,17M
4)launche the app
5) you'll be prompted to remove the SD card before proceed. when done press OK
6) the app will download more or less 190M. be sure to be connected to a wifi
7) when done, you'll be required to enter the code *#*#442#*#* in the phone dialer
8) the phone will reboot in recovery and will install the play store and all gapps
9) the phone will reboot
don't forget to remove the SD card!!!!!!!
I hope this can help you.
it worked for me!
I've found this information in a chinese bbs, btw, you can look in youtube for "HTC E8 Dual Sim ( 4G Version ) - How to install the Google Play Service" at 1:52 .......
let me know!

Flash'em
[email protected] said:
I have Desire 820u CHinese version and it has only English and Chinese languages. No Goggle play and even does not allow to install Google play. Blocks it. I would like to install Google play. Is there any international ROM ?
Click to expand...
Click to collapse
Hi,
No official international rom so far (I doubt if it's planned, this phone's target is Asia)
Convenient solution is to flash GAPPS on top of existing software (without erase, just clear cache). Base package can be found at htcui[dot]com//androidrom/htc_820_rom [replace dot] - look for BillGates-li tread (you may need to use chrome with translation, as it's all Chinese). I'm sorry for confusion, but due to rookie rank, I'm not allowed to post external links.
Beware, each major upgrade (that flashes, not patches) will erase those GAPPS.
You'll need:
- customer recovery .img (can be found in orygnial android development section)
- fastboot (to flash i.e. install it)
- (suggested) original recovery.img (to enable future upgrades from HTC, that will download but not install on custom recovery)
Don't forget to backup before flashing - "just'n'case".

gareth824 said:
....I have just used WinDroid Universal Toolkit to unlock bootloader, flash TWRP and root the phone.....Everything seems to be working.
Click to expand...
Click to collapse
@gareth824, are you running any custom rom? is there a deodexed stock rom for D820u?
have you tried xposed framework and any module(s), esp. gravitybox?
btw, i've sent you a p.m. please reply. thanks.

involato said:
I hope it can help.
I have the same model, chinese version.
open HTC market, and look for GMS.... app.
download it, launch it, and when required enter the code *#*#.....
it will download somethink like 150M, your mobile will reboot, and at the end you'll find all google app in your mobile.
done.
without root, unlock or other
Click to expand...
Click to collapse
hey i have ordered HTC Desire 820 from China. It doesn't have google services. Will the above procedure work for it too? and how to get everything in english. I have selected language English, than toohalf of the things in blinkfeed occurs in chinese. please help

GMS App not working
Hi, just bought an HTC 820us, and just like everyone, no google apps. What's weird is that my phone is not even recognized by HTC sync manager, Windroid, HTC tool, fastboot under command line or any other program.
I'm unable to get this device's token in order to unlock the bootloader and install google apps, root, etc. When I try to install the GMS app I get an "App not installed error". If anyone finds a solution for this i'll be more than happy to donate to the cause.
Thanks for reading!

same device, no google play too...
oscarat50 said:
Hi, just bought an HTC 820us, and just like everyone, no google apps. What's weird is that my phone is not even recognized by HTC sync manager, Windroid, HTC tool, fastboot under command line or any other program.
I'm unable to get this device's token in order to unlock the bootloader and install google apps, root, etc. When I try to install the GMS app I get an "App not installed error". If anyone finds a solution for this i'll be more than happy to donate to the cause.
Thanks for reading!
Click to expand...
Click to collapse
well, I have the same device since two days and I still try to install google play without success yet. it is possible at all or I can just use a limited version of this smartphone?
this is my first android phone and I have no idea what to do...any suggestions are welcome

found a solution
Ok, so after dealing with this phone for a while I found many solutions for the common problems of having an imported phone from china.
I found solutions for: Google Apps, Root, CallerID mismatch (Contacts not recognized when receiving calls due to chinese format of their CallerID)
- How to install Google Apps
1. Do a Factory Reset of your phone in the recovery screen (volume down+power button)
2. Download the GMS安装器 apk in your computer from google or any other source, make sure it's the apk with the android robot with the google apps logo in it. (app is no longer distributed in the included App Market)
3. Tranfer the downloaded file to a SD card (32gb maximum size or else it wont be recognized)
4. Insert the SD card in your phone
5. Using the "File Transfer" app in your phone copy the GMS app to the phone's "Download" folder.
6. Enable "Unknown Sources" in Settings/Security/Device Administration
7. Install the App, DON'T RUN IT. (Installation failed for me at first, a factory reset solved this)
8. Unmount the SD Card
9. Using the "File Transfer" app, install the GMS apk
10. Follow the instructions the GMS app is giving you, remember to remove the SD card before installation
11. The app will download something like 200mb, after that it will ask you to enter a code in your phone's dialer, enter it, it will automatically will reboot.
12. If you are lucky, the phone will have all Google Apps installed.
- Root
Once you have Google apps installed, it's easier for some root exploits to work.
1. Use Kingo Root for windows, it will try many methods of Rooting your device, the one that worked used an installation of various apps. Kingo root needed "USB Debugging" activated in Settings/Developer Options. If you don't have the Developer options menu enabled, please google it.
Once you have Root access it's easier to remove the Chinese apps that came with the phone.
- How to fix the CallerID not recognizing contacts problem
1. Download and Install "ES File Explorer" using the Google Play Store app.
2. Allow Root access when prompted to.
3. Head over to the "Tools" menu using the button in the upper left corner of the "ES File Explorer" app.
4. Enable "Root Explorer"
5. Click on "Root Explorer"
6. Click on "Mount R/W
7. Set "/system" to the RW value.
8. Press OK
9. Navigate to: Local, then /Device/system
10. Look for file named: "build.prop" and open it
11. Open it using ES Note Editor
12. Edit the file (using the 3 dots menu on the upper right corner)
13. Find the entry named: ro.phone.min_match=11 and change the number to 7.
14. Entry has to be named ro.phone.min_match=7
15. Press the return button, it will ask you to save changes, save them.
16. Just in case, remove the RW access mentioned in step 7.
17. Go to Settings/apps/all/ contacts and force stop, clear data
18. Do the same with the Contact Storage App.
19. Reboot Phone, cross your fingers and problem is solved.
I hope this helps a lot of people.
BTW: My phone is an HTC 820us, China Mobile.

get gapps...
htc_china_no_google_play said:
well, I have the same device since two days and I still try to install google play without success yet. it is possible at all or I can just use a limited version of this smartphone?
this is my first android phone and I have no idea what to do...any suggestions are welcome
Click to expand...
Click to collapse
I describe here how to get GAPPS for HTC D820US and maybe for any other "China-smartphone"
1_: Unmount the SD Card
2_: go to nduoa.com/package/detail/225445 with Chrome
3_: Right click on the page > translate to english
4_: Choose the green button next to blue one and above the other three green ones to download a small file called com.gmainstaller.apk
5_: install it
6_: this apk will download a file of abt. 246MB and needs following code in the dialer which pop-ups automatically [ code: * # * # 442 # * # * ]
7_: The device automatically restart and automatically install GAPPS, after the completion of all applications please check the list.
8_: if needed after all, download separately from "apkmirror.com" following two apk's: Google Play Services and Google Play Store.
tried on two HTC D820us and works like a charm

involato said:
sorry for my previous post....
1) open AppMarket (ok, it's all in chinese)
2) in the search bar enter GMS
3) download and install GMS安装器 (the icon is the android robot, with some gapp icon inside). it is 0,17M
4)launche the app
5) you'll be prompted to remove the SD card before proceed. when done press OK
6) the app will download more or less 190M. be sure to be connected to a wifi
7) when done, you'll be required to enter the code *#*#442#*#* in the phone dialer
8) the phone will reboot in recovery and will install the play store and all gapps
9) the phone will reboot
don't forget to remove the SD card!!!!!!!
I hope this can help you.
it worked for me!
I've found this information in a chinese bbs, btw, you can look in youtube for "HTC E8 Dual Sim ( 4G Version ) - How to install the Google Play Service" at 1:52 .......
let me know!
Click to expand...
Click to collapse
This solution doesn't work when when the Android software is upgraded to Marshmallow. Is there an updated solution to getting gApps for the HTC Desire 820u (from China)?

GMS from Chinese APP MArket don't install Google Play Store on my HTC Desire 820u
Hello Freinds.
I imported from China a HTC Desire 820u.
It is Unlocked and S-on, running Android 6.0.1, Sense 7.0.
I've made GMS download from chinese Appmarket to install Google Play Store on my device.
For the first time I could not instal it.
Can you tell me the procedures to install Google play Store on my device??
***UNLOCKED***
A51_DTUL PVT SHIP S-ON
HBOOT-3 . 19 . 0 . 0000
RADIO-01.01.010_UI0305041_08.01.51015
OS-
eMMC-boot 2048MB
Aug 31 2016, 18:10:00.0

I have same problem..please