Info"""" Reason to use TWRP -
CWM does not officially support our device, and its just a port. Due to this, CWM has some serious and known problems. As already mentioned, USB mount doesn't work. Also, it has been known in some cases to cause some major issues with dialer and other phone functionality after flashing a ROM. Problems that persist even if you try flashing another ROM or restoring a backup. These problems are difficult (although not impossible) to fix, and a big headache.

TWRP officially supports our device, gets regular updates. Its fully working, and its recommended by almost all (if not all) our developers." (Thanks to redpoint73) """""

2) Make sure the file you downloaded "openrecovery-twrp-2.2.1.0-evita.img (for example) should be in same folder where adb and fasboot present ( How to make sure = You need to copy the file in the folder where adb and fasboot present)

Example - If you downloaded android sdk then the downloaded file should be in "C:\android-sdk\platform-tools" folder.

Look at twrprecovery1 - image in the attachment

3) Then open command prompt in the same folder ( by pressing shift+right click and select "open command window" here) or open command window and type cd C:\android-sdk\platform-tools (or change to directory where adb and fastboot exists)

4) Then Run the following command fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img (openrecovery-twrp-2.3.1.0-evita.img is the file name which you downloaded) in command prompt

5) Then run the command fastboot reboot in the command prompt (phone will reboot, so do not panic)

6) Run the following command after the phone is rebooted adb reboot recovery

2) Once you downloaded the ROM of your choice, then extract the ROM.zip ( that mean you need to unzip it )

For example you downloaded CM10 -cm-10-20121012-NIGHTLY-evita and extracted it . Now you can see the boot.img in the folder you extracted. (( See the extract image in below ))

For example you downloaded Nocturnal Megre X rom and extracted it. Now you can see the boot.img in the folder you extracted. (( See the extract1 image in below ))

3) Now copy the boot.img from the extracted folder and paste in folder where fastboot and adb are present ( if you downloaded Android then paste it in C:\android-sdk\platform-tools )

Your folder where adb and fastboot present should now have boot.img of the ROM you extracted

4) Put phone into bootloader mode,

Either by opening command prompt in the same window where you placed boot.img (i.e where adb, fastboot is present) and running the command adb reboot bootloader in command prompt ( do not close the command prompt)

Or, since your phone is in recovery , select "Reboot" then Bootloader .

Note*- You always can get into bootloader by pressing power button + volume down for 10-15 sec. Also from there you can get into recovery by using volume keys to select recovery and pressing power button to enter into recovery

5) Once your phone is in bootloader mode, type the following command fastboot flash boot boot.img ( If command prompt is closed then open command prompt in the folder where boot.img, adb, fastboot are present . For example: C:\android-sdk\platform-tools - Same folder used in step 3)

5) Then run the following command adb reboot recovery

6) Your phone is in TWRP recovery

7) Select mount from recovery ( See mount - image in the attachments for example)

8) Copy the ROM.zip which you downloaded earlier to the SD card ( For example cm-10-20121012-NIGHTLY-evita.zip) ( Not the extracted folder but the actual zip file which you downloaded)

4) Copy the gapps into sd card ( you need to download gapps if you using CM10 or ASOP roms )

5) Unmount, then select Wipe and select Factory reset ( it is recommended to do a factory reset before flashing the new ROM. ) (See wipe, wipe1 images below )

1) If you keep getting htc red screen ( saying " This Build is for development only") then it does not mean you bricked your device. It means you forgot to flash boot.img or missed some step

2) if you are flashing similar ROMs ( having same kernel ).. there is no need to flash boot.img separately. But say if you wanna switch from sense to aosp you must do that as they have different kernels.

Again if you are just upgrading from older version to newer version of same ROM and if there are no kernel changes no need to flash it" (thanks kancherlapraneeth)

3) Another scenario, if you struck in boot for every long and you panicked and you did factory reset. After you can access only twrp recovery then do not worry, do the following

fastboot boot.img, then flash the Rom through twrp. Then your golden" (Thanks to InflatedTitan) ( Do not understand fastboot , boot.img then read above)

4) If you flashed an internation rom or rom which is not for our device and bricked your device then follow this link , the OP has similar problem and people helped him

[B]5)Which version of super user do I need to flash [/B

In above instructions, after you installed Custom recovery you flashed custom ROM then you already have it ( since you rooted) , so check the root with app called root checker.

"If your on stock with twrp installed then it was a temp root, so root is gone after you reboot, but it allowed for a permanent boot loader unlock. So you will need to flash an su binary package and then download a superuser app from the play store." (thanks to absolutelygrim) (Case where you did not unlock the bootloader but just rooted and rebooted. ) then download http://downloads.androidsu.com/super...arm-signed.zip (Superuser zip ) and flash in recovery ( same way we flash custom ROM or gapps.) then download supersu from the market and update the binaries

I find this a good idea.... I feel we should sticky things like this in the q/a and not have one hundred threads of the same problem...like this stickied... We could have different popular subjects stickied and so not so many threads would arise

Bro you did a damn good job on this. If a noob can't follow this, he doesn't need to be hacking anything. I mean for god sakes you've included pictures lol. Even though you've included steps and the fastboot commands, What about adding a link to gunnyman's quick anb dirty adb and fastboot tutorial? Rich in knowledge

Bro you did a damn good job on this. If a noob can't follow this, he doesn't need to be hacking anything. I mean for god sakes you've included pictures lol. Even though you've included steps and the fastboot commands, What about adding a link to gunnyman's quick anb dirty adb and fastboot tutorial? Rich in knowledge

I gotta say, I'm proud of our little community. I really haven't seen any harsh words or flaming of the recent wave of noobs, even though a lot of problems could have been easily avoidable on their part. Great job for those who have helped someone recently. I'm sure those in need appreciated it, even if they haven't hit the thanks button. They'll soon see how great the HOXLers are!

I gotta say, I'm proud of our little community. I really haven't seen any harsh words or flaming of the recent wave of noobs, even though a lot of problems could have been easily avoidable on their part. Great job for those who have helped someone recently. I'm sure those in need appreciated it, even if they haven't hit the thanks button. They'll soon see how great the HOXLers are!

I gotta say, I'm proud of our little community. I really haven't seen any harsh words or flaming of the recent wave of noobs, even though a lot of problems could have been easily avoidable on their part. Great job for those who have helped someone recently. I'm sure those in need appreciated it, even if they haven't hit the thanks button. They'll soon see how great the HOXLers are!

This probably is the most friendly community I've seen on xda..flaming only appears here when obviously deserved ...but holy critters I don't know how many bricked threads j saw when I woke up yesterday

XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality.Are you a developer?