DO NOT ATTEMPT TO ROOT OR INSTALL A CUSTOM ROM IF YOUR PHONE IS A LIFELINE! There is a GOOD reason why this voids your warranty and manufacturers recommend against it. Once you leave the 'safe confines' of your stock ROM, anything can happen! For most people the results are well worth it. However, most people also experience some issue at some point - crashes, complete loss of functionality (boot loops), inexplicable crashes, etc.
Generally, if you read the instructions on rooting carefully along with this wiki before you do anything, you should be ok.
Remember that everything you see here is driven by volunteers with jobs, families and real lives that take priority over giving free support to you. Do not ever demand support from the forum or post stupid questions that have already been answered here or in the forum.
Read this wiki first then search the forum before posting any new questions.
What is Alex-V
It's a ROM. Created by a guy called Alex-V.
Not enough? Ok, it's actually two ROMS. One Sense based, one Sense HD based. Alex-V ROMS are 'clean', they look like Stock ROMS and he provides all the links to any extras you may want to add yourself. You will find all main mods on the first post in the relevant thread (Sense or Sense HD). If you come across a mod that is not in the first post and you think it should be, let him know.
DO NOT BOTHER HIM WITH ANY QUESTIONS THAT HAVE ALREADY BEEN ANSWERED HERE AS HE IS A VOLUNTEER DEVELOPER ONLY. TIME IS PRECIOUS. TIME IS FOR ROM DEVELOPMENT. Unless it's a good question. He likes good questions that need good answers. We all like them.
IF YOU HAVE ANYTHING TO ADD, THEN ADD IT.
[This Wiki will only be as good as the contributions it receives. Rather than blast poor newbs, welcome them to our ever growing community and point them to this Wiki. If their questions are not answered here, we have failed them. We have succeeded when there are no more repeated questions on the forums, and Alex no longer has to waste any of his valuable ROM developing time answering them.
What is the latest stable version?
USE THE STABLE VERSION IF YOU REQUIRE STABILITY, USABILITY OR ARE NEW TO THE ROM SCENE Just because a Development version has features you want is no reason to use it. Stable versions have been tested and are well understood.
Non-HD Rom (Standard Sense) Alex-V 2.3 A2sd+
HD Rom (Sense HD - Note: For a standard Desire only) Alex-V 1.5 HD A2sd+
What is the latest development version?
DO NOT USE A DEVELOPMENT VERSION UNLESS YOU ACCEPT THE RISKS AND ARE HAPPY TO PROVIDE FEEDBACK TO THE DEVELOPERS
Non-HD Rom (Standard Sense) Alex-V 2.3 Data2sd (Whatever) 27.01.
HD Rom (Sense HD - Note: For a standard Desire only) Alex-V 1.5 HD Data2whatever Test Rom 08.01
HD Rom (Sense HD - Note: For a standard Desire only) Alex-V 1.5 HD Data2sd
Where Can I Get The Extras?
For normal Sense
--> Rosie (HTC Launcher) with Drag&Drop in Helicopter View (for 2.29) http://forum.xda-developers.com/showpost.php?p=10325408&postcount=1540
--> Turn Alex's rom back to 998mhz http://forum.xda-developers.com/showpost.php?p=10286151&postcount=1494
for new HD Sense
Latest tested Kernel
couttstech-126.96.36.199_oc1190_CMBattFix_BFS_BFQ (faster :))
Alex-V 1.4/1.5 HD data2sd fixed in 1.5 test Rom
After you install/restore a numer of apps Dalvik Cache fills up internal memory.
The number of applications depends on what kind of applications you are installing (they have different size of Dalvik usage).
Use Root explorer to check the size of the Data/Dalvik Cache folder.
The phone will not say its full but you can't restore or install any more applications.
You will either see a reboot or it will give a general error or none at all (won't restore the app).
Alex-V 2.1 Stable app2sd+ and data2sd Done...and reported as worked also in 2.2 :)
Droidbois has reported random lockups and freezing. Cause unknown. Not occuring with LeeDroid 2.2f or other ROMs tried to date (new issue). Not known to affect any other user yet, however investigations are ongoing. Alex-V suggested the RW System Overlay (see below) could be causing issues. Droidbois has suggested CPU clocking. Alex-V has offered to produce a ROM with both features removed to test again.
Done...and reported as worked :)
Current Feature Requests
Baking in security
HTC Desire HD mods
Add hibernation mod and notification recent apps like Droid Incredible Android Developers did ..
Q: Droidbois asks "Is the overclocking feature of the new kernel a risk to our phone hardware?"
NOT, BECAUSE IT USES SAME VOLTAGES AS ORIGINAL HTC KERNELS
Q: How to remove RW System Overlay file-system..?
THIS IS FOR PEOPLE HAVING S-OFF ONLY From adb in recovery type: -adb shell -mount /system -rm /system/bin/unionfs -and now you have fully write with your s-off
Q: What's the default kernel of v2.1 / 2.2 /2.3 Standard?
Also on the first post of the thread
Q: What's the default kernel of v1.5 HD?
Also on the first post of the thread
Q: Is there a non-overclocked kernel available?
Q: How do I remove system apps I don't want?
Before flashing the ROM: Delete the unwanted files from within the ROM's zip file.
After flashing the ROM: Using a file manager (choose from the many on the Market) ensuring that you have r/w access when in the System or Data folder.
Using an Emulator from the Market, again ensuring you mount the directory as r/w, for example, to remount the System directory as r/w:
su mount -o remount,rw /system
You'll soon learn which files you need to keep :-)
Q: How fast is this ROM?
Depends on what you consider fast! You can use Quadrant from the Market for a score but it's down to personal use and opinion. Standard Alex-V ROM score: 1530+ HD Alex-V ROM score: 2100+
Q: I get the following error (or similar) when installing the ROM, what is it?
E:Failure at line 11. copy_dir PACKAGE:data DATA: Installation aborted
This can occur when going from an a2sd based version of a ROM to d2sd etc version of the same ROM. A full wipe is needed via recovery and will resolve this issue (as long as you have a backup it's not a major hassle, just restore settings as detailed in above steps for TB and MB)
-Radio 32.44.00.32U_5.09.05.30_2 (Also works with latest 32.49.00.32U_5.11.05.27)
-Partition ext2, 3 or 4 wiped (for A2SD+ (or d2sd etc etc etc, Alex add in all your variants!) - Bashyuk)
Coming from a different ROM -> Full wipe/factory reset + Wipe Cache + Wipe Dalvik Cache + Wipe Battery Stats - This is the cleanest way to start and minimise the probability of issues.
Coming from a previous version of Alex-V -> Wipe the caches, don't do a factory reset. If no issues, cool, if issues, full wipe as above before asking questions as you will probably find the issue resolved.
Some have reported no problems with not doing a wipe, but it's a gamble. See my guide below on retaining settings and apps if this is an issue (use Nandroid settings restore and Titanium Backup or Mybackup).
Another Method To Install
(To be implemented when MD5 Checksum files become available)
A user recently reported an issue with a corrupted download causing the flash to fail and the phone to lock up on boot, requiring a re-flash. It is now recommended to perform a full integrity check on the ROM file before flashing.
MD5Sum file fingerprints
When you perform an md5 check, you are comparing the fingerprint from the files you downloaded to the fingerprint of the files on the server you downloaded from
Microsoft Windows users: md5sum program can be downloaded http://www.etree.org/md5com.html
Linux users already have this installed natively.
usage: md5sum <path-to-file\file>
In cmd prompt (Dos shell). (presuming you downloaded the Binary to your desktop and the ROM is on your desktop too)
If the file you downloaded matches the fingerprint in bold here or posted by Alex then you know it is correct.
More info http://en.wikipedia.org/wiki/Md5sum
Retaining Settings (Backup and Restore)
For those wishing to retain settings between flashes, I found the following helps using Titanium Backup:
NOTE: These steps should ideally only be followed when working within versions of Alex-V's ROM, if you are coming from a different Dev, it will v likely lead to issues. In theory, if it's another Sense based ROM you would think it would be fine. Sometimes it is. Sometimes!
1) Take a full backup and back that up on your PC just in case!
2) Take a full 'Nandroid' backup - Start your phone in recovery (vol.down + power) and select backup. [Or you can do it via ROM Manager if you have it installed.] - RM can cause confusion as it's a CM GUI so if a user is using AmonRA it won't be relevant - Bashyuk
3) WIPE MEMORY AND CACHE BEFORE FLASHING A ROM, every time [really?! - Bashyuk]
4) If in doubt, re-read Point 3
5) After it all settles down, reboot in to recovery, go to advanced backup settings and restore data (only) from your last Nandroid backup (just the data)
7) Reboot, run Titanium, restore all apps.
8) Run Market Doctor from Titanium to restore all Market links.
10) Move on with your life.
I've found with this, I can upgrade between ROM's no problem and retain all my settings, such as Locale which is an incredible pain to set back up again.
for My Backup
1. Download it from the Market
2. Backup (apk+data)
3. Backup Settings
4. maybe copy reware folder from sd to pc
5. flash new rom
6. Check in your google account
7. load My Backup from Market again
8. Restore all
It can be that some widgets don´t load....Drop it to Trash and load the new again
A2SD+ requires a Linux (EXT) partition (2, 3 or 4) to be created on your Micro SD card. Why? Because Android is based on Linux therefore EXT is the native Android filesystem.
How to create an EXT2/3 or 4 partition?
NOTE: The creation process wipes your SD Card so make sure it's backed up before starting!
- Via ROM Manager
- Via Linux with Gparted. Find this either on a Linux PC, a bootable Linux CD or DVD (most have this option, like Ubuntu, to boot off their installation CD), or the Gparted bootable CD.
NOTE 2: Always create the FAT32 partition first then the EXT 2/3 or 4 partition.
Regarding formatting under windows
EXT 2,3 and 4 are Linux file systems. Windows will not display EXT partitions, it will just show a 'blank' partition, and probably prompt you to format that too if you give it half a chance. Do not do that. Windows refuses to support EXT file systems so it will only end in tears.
If you have a second Linux partition (i.e. what you have now with a2sd+) Windows 'won't' see it so you can't do anything with it, unless you pull up Disk Manager and you will see a 'blank' partition that you can format as FAT32, but can't mount to access.
Seeing if a2sd+ is working
Quick System Info shows you the A2SD partition. Handy stuff. Remember that installing to your internal memory actually installs to your external A2SD+ partition now (still seen as internal memory by the phone) and installing to external memory installs to your FAT32 partition which is seen as external memory by your phone. To understand why you'd need to look up 'symbolic links' in the Linux world, I will spare you the details. It's all down to the magic of Linux. That's why the partition does not show up when you mount your phone in Windows, as Windows does not recognise Linux partitions, which the a2sd+ partition actually is, whereas a Linux PC will see it.
After doing the above, DO NOT manually move apps to the sd. They are already there even when the phone says they are not! If you want to go back to the standard way of doing things with apps, delete your ext partition and make your sd card all FAT32 again. Then cry as you run out of storage space again :-)
NOTE 3: Some app data will still be saved to the phone so you will see internal storage loss, just not as much as before. Other methods are available to combat this and will appear in time on this wiki.
Why Data2Sd was developed?
We all know of the Desire’s Internal memory limitations. It provides about 148 Mb of storage for your apps, which is frankly not enough. It fills far too quickly. Google themselves released A2SD which allows parts of some apps to moved to sd card. Their dalvik cache would however remain in Internal. Even with Froyo’s adaptation, memory was a serious problem. Then, some bright devs brought about APP2SD+, a code which allowed even the dalvik cache to be moved to Internal. However, even this would not be enough for huge programs. Then, Darkstrumn developed Data2sd, a method which moved the /data mount itself to Sdcard. It’s a much cleaner adaptation and provides almost limitless Internal Memory, which is limited only by the size of the card. Sibere ported Data2Sd to the Desire. How does Sibere’s Data2Sd work?
It transfers the /data which is used by all your apps to sd card. That way, instead of tricking the system, we do it the way it is intended to. We just request the system to know that /data resides in sdcard and not the phone. Data2sd essentially splits your sdcard into two partitions-One normal Fat32 partition for your normal needs (Storing music and vids etc), and another Fat32 partition which functions as the container for an ext file which acts as the mount location of /data (a folder which each and every app installed on your system
And now also data2whatever
Flashable All-in-one-data2sd-Solution which is the savest solution
For sure...a residual risk of data loose is always in Data2sd/whatever....melethron work on this to minimize this...thanks for all that work on this....
RW System Overlay
(Thanks to fllash 
Some roms still use the overlay because the it does not require the user to have S-OFF'd their Desire. If you have never needed to: - write to /system while inside android - use fastboot - use MetaMorph
then you probably don't need either the R/W overlay or S-Off
Changing / Migrating SD Cards
Thanks to dimcus
1. Backup your old card's FAT32 partition to your PC. In other words, whatever Windows shows you as being on the sd card as usual data.
2. Partition your new SD card so it has both fat32 and ext partitions.
2. Do a nandroid backup from recovery. This also backs up your EXT partition, which you will not have been able to do on your Windows PC
3. Copy all the FAT32 backup files from the PC to the new card
4. Place the new card into the phone
5. Go into recovery and restore. This will restore all files on your ext partition.
Verified to be working. Use Amon-Ra recovery or ROM Manager to partition your card if you don't have working linux / gparted installation in your machine (bluelavender)
Also verfied by Bashyuk - Note that ROM Manager only lets you partition a max of 512MB so you need GParted etc for larger partitions.
NOTE:Class 10 Micro-SD card (mine is 16gb from KingMax) seems not working with Sense Rom with Data2SD(EXT3), some people said it's software related, you take your own chance in trying it.(hongkongtom)
How To Take Screenshots
Use 'Screenshot' free in the Market
PicMe is a great application that creates a web server on your phone that you can pull up in a browser to take screen shots and send to your envious friends. Enjoy.
What is Undervolting?
Undervolting (a.k.a. UV) is a way of increasing battery life by reducing the amount of electrical power drawn by the processor. The downside of (excessive) undervolting is that there may not be enough power for the processor to remain stable.
Normally the processor may draw (say) 1.275 mV, but - due to a little 'engineering overdesign' by the manufacturer - it will often remain stable even if it is reduced to (say) 1.1 mV. Lower voltages reduce the draw on the battery, so that battery life is extended, with the added advantage that processor will not get as hot. Undervolting is particularly successful if the processor is also slowed down. Alternatively, when a processor is overclocked (i.e. the processor is made faster), it may require more electrical power (it is working harder, after all), and so they are also overvolted (and battery life is thereby reduced).
Of course the panacea is to undervolt and overclock so that the battery life is extended, and the system is faster overall; this is called undervolt-overclock (a.k.a. UVOC). Alternatively, there are some systems that attempt to adjust the voltage dynamically, so that the system is undervolted whenever possible (thereby increasing battery life), and overvolted when required (assuming the processor is able to increase its speed dynamically) - HAVS is one such system.
Note: Your success with undervolting and overclocking will vary not only between make/models of handsets, but even between instances of the same production run.
ALWAYS REMEMBER TO BACK UP YOUR ROM BEFORE FLASHING ANY ZIP FILES OF ANY KIND!
Q: Which themes can I install?
In theory, all that are designed to work with the ROM's base. 2.10, 2.29 etc
Q: Where can I search for themes that work with Alex's ROMs?
Q: How do I install a theme?
Flash it via recovery the same way you install a ROM
(detailed instructions in previous question)
Q: Is any wiping required?
Not usually when flashing a theme but if you have issues, a dalvik-cache wipe can help.
Q: How do I go back t the original ROM theme?
Q: Can I try out the UOT Kitchen? (full customization - notifications, icons, etc..) --Tiotempestade 10:44, 4 January 2011 (CST)
Sure! Try it: UOT KITCHEN
Just make sure you send the right framework-res.apk! The UOT kitchen supports Alex's ROMs (already have the file there) but with every new base (like from DHD v1.4 to v1.5) or certain changes you make to your theme there's a new framework-res.apk, so be sure to upload the right version..
For more info about theming with UOT look at the HOWTO