Database Info

Custom rom question.

I recently unlocked my bootloader and rooted my phone leaving s-on cos of my hboot being 2.0002 or whatever. And need a step by step to installing a custom rom with s-on. I have installed cwm recovery but cannot access it. I spent 4 hours searching on Saturday, can some kind person explain how to do it?
Sent from my HTC Desire S using XDA App

Put the ROM in SDcard. Turn off fastboot and switch your phone off. Then, hold Vol down button and without releasing it, press and hold power button. Hold till you see a white screen, You'll be in Bottloader mode. Press Vol down to highlight RECOVERY and press power to enter recovery. You'll be in CWM (if you flashed it correctly)
In CWM,
Backup your current (stock) ROM in Backup and restore > Backup. It's not necesary, but recommended, as you may want to come back later
Go to Wipe/Format
Wipe Cache
Wipe Dalvik Cache
Format System
Format Data
Wipe Data/Factory Reset
Then, go back and select Install ZIP from SD Card > Choose ZIP from SD Card and choose your ROM. The ROM is flashed.
Since you are hboot 2.00.002, you have to go through an additional step after that, you need to flash the kernel that came with the ROM, or you'll be stuck on the white HTC Screen. Extract the boot.img from the ROM and do this - http://forum.xda-developers.com/showpost.php?p=19071114&postcount=37
Reboot. You're done

shrome99 said:
Then, go back and select Install ZIP from SD Card > Choose ZIP from SD Card and choose your ROM. The ROM is flashed.
Since you are hboot 2.00.002, you have to go through an additional step after that, you need to flash the kernel that came with the ROM, or you'll be stuck on the white HTC Screen. Extract the boot.img from the ROM and do this - http://forum.xda-developers.com/showpost.php?p=19071114&postcount=37
Reboot. You're done
Click to expand...
Click to collapse
Excellent. Couldn't have put it better myself.

Thank you so much!
However I installed cwm recovery from the rom manager but it doesn't show up when I go into recovery, I get a red exclamation point, I press volume up and power and it says something about e something recovery not found?
Also where do I put that command? That kinda stumped me too lol. Sorry for being a noob
Sent from my HTC Desire S using XDA App

OK, first you need to setup adb and fastboot. Use this guide - http://forum.xda-developers.com/showthread.php?t=1272595
Next, get CWM recovery and instruction on how to flash it here - http://forum.xda-developers.com/showthread.php?t=1122694
You'll be flashing it via fastboot. Instructions are there in the second thread. The command will be in fastboot too, along the same lines.
Feel free to ask if you have any other doubt. Everyone is a noob at some point
Sent from my iPod touch using Tapatalk

Thank you so much. I will be doing this as soon as I can access my laptop again. Lol.
Sent from my HTC Desire S using XDA App

How'd it work out? Flashed succesfully?
Sent from my iPod touch using Tapatalk

Currently working at the other side of the country. I'll have to wait until thursday to flash it.
Thank you for the follow up though. It's very appreciated.
Sent from my HTC Desire S using XDA App

Sorted thanks guys.

Uppy said:
Hi again, i'm really sorry for being annoying but i dont get this bit.
I extracted android-win-tools to C and put the recovery image in the android-win-tools folder but what am i navigating to? c:\android-win-tools? Its specifically 4. that I'm stuck on.
This is slightly embarrassing!
this was so much easier on my Blade lol.
Click to expand...
Click to collapse
No need to be embarrassed buddy.
What point no. 4 means is that you need to move the file you want to flash (recovery.img in this case) to the folder that contains your adb files (android-win-tools, or whichever folder that you have extracted the android-win-tools that you downloaded). The rationale behind this is that when you enter the command fastboot flash recovery recovery.img, the fastboot will look for recovery.img in its default folder (android-win-tools, or whichever folder you've extracted the adb files to).
So here's what you need to do. For example, if you downloaded the adb files and extracted them to a folder named, let's say, xxxx, which is located in your C: then you need to take the recovery.img file and copy-paste it to the folder xxxx.
Before starting any of the procedures outlined here, first make sure adb can detect your device. (adb devices... sound familiar?)
Now boot phone into fastboot.
Now enter the following commands at the cmd prompt:
C:\Users\UPPY(or whatever)>cd\
Now you'll get the following:
C:\>
Next, you need to enter:
C:\>cd xxxx
You'll now get:
C:\xxxx>
Finally, enter the following:
C:\xxxx> fastboot flash recovery recovery.img
You should be done. I know the above looks over simplified... but i'm just trying to be extra nice here
I hope that clears your doubts.

Done! Thank you for all your help, you made it so much easier for me. its all up and running now.

Uppy said:
One last question though, where do i extract the boot image, do i put it in the root of my sd card and finally if thats the case what is the exact thing i type?
Click to expand...
Click to collapse
After you've flashed your custom recovery, boot into recovery and choose install from sd card, select zip from sd card, then navigate to your rom.zip file, and confirm to flash it using the recovery (on your phone)
But since you've unlocked using HTCDev, this will not flash the kernel as the boot is still locked. You have to bypass this by flashing the kernel manually using fastboot, otherwise you'll be stuck at the white HTC splash screen (Oh! how i hate that screen!!)
The kernel is contained in the boot.img.
The boot.img is contained within the zip file of the ROM you want to flash. So when you open up a ROM.zip (for example Reaper_v1.6.zip) with winrar, you'll see various files inside. Extract the one called boot.img. This is your kernel. Copy-paste this boot.img in your adb folder (like in the previous post)
To flash it, since you've already set up fastboot, just do what you did for flashing recovery.img, and follow the instructions i gave you exactly the same way, except the last part, where instead of recovery.img, you need to type:
fastboot flash boot boot.img
now type adb reboot, and boot into your shiny new custom ROM!!
You're done.

I'm getting an error when i try to connect to wi-fi, it just says error, what have I done wrong? grrr.
I think i didnt register the 3.4 boot image, will report back in a minute.
-edit- yeah i typed the command wrong thats all.

Uppy said:
Done! Thank you for all your help, you made it so much easier for me. its all up and running now.
Click to expand...
Click to collapse
Happy to help

shrome99 said:
Since you are hboot 2.00.002, you have to go through an additional step after that, you need to flash the kernel that came with the ROM, or you'll be stuck on the white HTC Screen.
Reboot. You're done
Click to expand...
Click to collapse
I have first read the install instructions from MIUI (saying: full wipe, flash rom) and now I have exactly what you have warned: Phone doesn't proceed, it ist stuck on the white HTC Screen.
UPDATE:
I was afraid of taking out the battery, as this may cause problems, and vol up + vol down + power just rebootet into white htc screen. The only way was indeed pulling the battery (after the vol up vol down power-reboot-gap). Then I could enter into the bootloader the regular way (vol down + power), and change to fastboot, and flash boot.img. Everything is fine now!!!

No-New-Phone said:
I have first read the install instructions from MIUI (saying: full wipe, flash rom) and now I have exactly what you have warned: Phone doesn't proceed, it ist stuck on the white HTC Screen.
UPDATE:
I was afraid of taking out the battery, as this may cause problems, and vol up + vol down + power just rebootet into white htc screen. The only way was indeed pulling the battery (after the vol up vol down power-reboot-gap). Then I could enter into the bootloader the regular way (vol down + power), and change to fastboot, and flash boot.img. Everything is fine now!!!
Click to expand...
Click to collapse
Was already typing a solution for you, but if you can solve a problem by yourself it's even better ;-)
Sent from my Desire S using XDA App

I'm glad this thread is helping more people than just myself. I'm not exactly a Technophobe but this was far more complicated than rooting my blade, Europa or racer or indeed writing the CSS files I used back on windows mobile 6.5 on my old touch 2.
I certainly needed my hand held through the first time doing this.
Sent from my HTC Desire S using XDA App

[Guide] How to root, install EXT4 recovery and custom ROM on HBOOT 2.00.0002

Hi, A short but effective guide for people who want to root their Desire S while keeping HBOOT 2.00.0002 and S-ON. This is what I did with my phone yesterday, but took me a lot of time to figure things out, so I'm writing this for myself and other people.
1) First of all set up ADB and Fastboot. [GUIDE] Easy and simple adb and fastboot setup for newbies (Windows only)
Also download the ROM you wish to install on your Desire S and put it on your microSD card. For this tutorial I choose Reaper v2.1 rom by lowveld.
2) You have to unlock your bootloader first via HTCdev so that you can install EXT4 recovery and custom roms. In the dropdown list select ''All other supported models'' and follow the instructions.
If you successfully finished the HTCdev unlock tutorial, your phone has a unlocked bootloader.
3) We're going to install EXT4 recovery. But first download ''4EXT_Recovery_v2.2.7_RC5.zip'' and extract the recovery.img file to the folder where you installed fastboot and adb. If you followed the tutorial in step 1 the folder will be ''C:\android-tools''
Now make sure Fast Boot is turned off on your phone. Go to ''Settings > Power > Fast Boot'' to turn it off. Unplug your phone from your computer, it's time to turn of your phone and boot into your bootloader.
Press Volume Down Button and Power Button at the same time to boot into recovery. Now connect your phone to your computer and select fastboot.
(Power button to select, Volume Down/Up to navigate)
Go to start->run-> type cmd and press enter. A command prompt will now appear.
Type:
cd c:\android-tools [press enter]
fastboot flash recovery recovery.img [press enter]
Click to expand...
Click to collapse
EXT4 recovery is now installed on your phone. Turn off your phone in bootloader menu.
4) Open the rom (.zip file) you downloaded in step 1 and put the ''boot.img'' file in ''C:\android-tools''
If you followed this tutorial correctly, you already copied your desired rom your onto your MicroSD card.
Now we boot into the bootloader again, this time we select recovery.
Go to: wipe | format>and select: wipe data/factory reset (this may take a while), then select wipe cache and wipe dalvik cache.
Go back to main menu in EXT4 recovery and select ''install from sdcard'' select ''Reaper_V2.1.ZIP''. After the rom is installed turn your phone off again.
Boot into recovery, connect your phone to your computer and select fastboot on your phone.
Go to start->run-> type cmd and press enter. A command prompt will now appear.
Type:
cd c:\android-tools [press enter]
fastboot flash boot boot.img [press enter]
Click to expand...
Click to collapse
After it's successfully installed, turn of your phone and just boot normally. It may take a while for your phone to boot up.
Your phone is unlocked,rooted and has a custom ROM.
Enjoy
Note: Some new ICS roms require different kind of HBOOT. I use Fallout v5.0.0 without any problems.
Just press the 'Thanks' button instead of saying thanks.
Changelog:
*03-03-2012 Updated guide
*14-03-2012 Updated guide
*12-09-2012 Added Notes/updated guide
Click to expand...
Click to collapse

Tx!
Was thinking about rooting/unlocking but wasnt really sure of myself doing it without bricking it. Most of this guide i already knew but it gives me confidence before making the jump
Sent from my HTC Desire S using xda premium

Why did you temp root at step 2? As soon as you restart your phone it'll be gone.

foX2delta said:
Why did you temp root at step 2? As soon as you restart your phone it'll be gone.
Click to expand...
Click to collapse
So it's not permanent? meaning step 2 is unnecessary?

@n0elite
Yeah, if your phone is locked (2. hboot) or s-on (0.98 hboot) if will just give you shell root, useful but not required for what you doing.

this looks promising, i think i'll try it someday
so i'll be root after i finished this procedure, or just temporary?

Finally. This was the missing link in this forum!
I had the intention do write one, but I am S-OFF and cannot verify the steps without going to Stock then doing the steps and then downgrade and S-OFF again. Too many things to do just in the name of a correct tutorial. Anyway thanks I am glad that somebody finally wrote it!
P. S. : please notify ben_pyett to include it in the Index thread
Sent from my Desire S using Tapatalk

foX2delta said:
@n0elite
Yeah, if your phone is locked (2. hboot) or s-on (0.98 hboot) if will just give you shell root, useful but not required for what you doing.
Click to expand...
Click to collapse
Wouldn't swapping step 2 and 3 fix that?
Sent from my HTC Desire S using xda premium

@dan-fish
Yip

Guide updated. Thanks for the comments

I've followed your Guide ... but i stuck on the bootscreen
i installed the ROM via recovery ... and then the phone restarted and started to boot, i just pulled out the battery to turn off the phone and then to flash "boot.img" via fastboot, but now i stuck on the bootscreen ... anybody knows what to do?

yxsunnyxy said:
I've followed your Guide ... but i stuck on the bootscreen
i installed the ROM via recovery ... and then the phone restarted and started to boot, i just pulled out the battery to turn off the phone and then to flash "boot.img" via fastboot, but now i stuck on the bootscreen ... anybody knows what to do?
Click to expand...
Click to collapse
Damn, where did you read to pull the battery? NEVER PULL BATTERY AT RUNNING OR BOOTING SYSTEM EXCEPT YOUR AWARE OF THE POSSIBILITY TO GET A PAPERWEIGHT AND DON'T MIND IT!!
Did really take a look at the recovery? What is written as last line?
Ok, but your phone is off now, if not reboot to bootloader with
adb reboot bootloader
at the command line.
Otherwise start it with vol down and power.
There use the fastboot command to flash the boot.img, if you're lucky it will work.
Swifted from my Desire S far away from my PC

Tectas said:
Damn, where did you read to pull the battery? NEVER PULL BATTERY AT RUNNING OR BOOTING SYSTEM EXCEPT YOUR AWARE OF THE POSSIBILITY TO GET A PAPERWEIGHT AND DON'T MIND IT!!
Did really take a look at the recovery? What is written as last line?
Ok, but your phone is off now, if not reboot to bootloader with
adb reboot bootloader
at the command line.
Otherwise start it with vol down and power.
There use the fastboot command to flash the boot.img, if you're lucky it will work.
Swifted from my Desire S far away from my PC
Click to expand...
Click to collapse
I tried it, but it will still stuck on the HTC Splash screen ...
When i'm flashing the ROM everything works and in the end it starts restarting ... and i have no chance to stop the restarting? Or i'm blind
Update: Found the solution ... noob mistake

yxsunnyxy said:
I tried it, but it will still stuck on the HTC Splash screen ...
When i'm flashing the ROM everything works and in the end it starts restarting ... and i have no chance to stop the restarting? Or i'm blind
Click to expand...
Click to collapse
What rom do you use? Maybe the recovery script forces a restart, sry, but anyways use vol down vol up and power or adb reboot bootloader to force a reboot.
If it's really needed only pull battery in between the small gap after shutdown and boot, but not at running system.
Try it the other way round, first flash the boot.img, afterwards flash the rom.
Swifted from my Desire S far away from my PC

Please help .
I am new to android and I did know a great stupidity, I removed the battery while charging the 4EXT Recovery image I thought was locked and now i do not know what to do, please teach me download it another rom as it related to furniture.

stroescu76 said:
I am new to android and I did know a great stupidity, I removed the battery while charging the 4EXT Recovery image I thought was locked and now i do not know what to do, please teach me download it another rom as it related to furniture.
Click to expand...
Click to collapse
So what is the problem? Phone doesn't boot or what?

Locked in HTC logo.
He remained in the HTC logo, and nothing happens, I would be very grateful if you help me, I think not uploaded image.: (

stroescu76 said:
He remained in the HTC logo, and nothing happens, I would be very grateful if you help me, I think not uploaded image.: (
Click to expand...
Click to collapse
What did you do before the phone wouldn't boot?

I followed your directions, I installed version Reaper_V2.1'''' I closed, I opened the phone and I gave in "Fastboot", give the command:
cd c: \ android-tools [press enter]
fastboot flash boot boot.img [press enter],
but it says "error: can not load boot.img", if I saw a video where I realize I'm wrong or my phone failed.

Put boot.img in c:\android-tools and then run the command again
Sent from my HTC Desire S using XDA

Cant boot into recovery...HTC screen only

I attempted to place a ROM on the phone using CWM recovery and something messed up. Now, I can boot into screen that says fastboot, recovery, etc. However, when I select recovery, nothing happens. Anyone point me in the right direction...im back to using my Blackberry!

From fastboot try and reflash recovery I would highly suggest twrp over cwm since twrp officially supports the one x.
Sent from my Nocturnalized Beast

E.Cadro said:
From fastboot try and reflash recovery I would highly suggest twrp over cwm since twrp officially supports the one x.
Sent from my Nocturnalized Beast
Click to expand...
Click to collapse
This is where I am stuck. Unfortunately, I'm not all that familiar with Fastboot. When connecting the phone to the PC with a USB, I see that the phone says Fatboot USB. From there I'm lost. I've not been able to find a guide that describes how to install a ROM using fastboot. Lots of posts says that it can be done, but none describing how its done. Anyone pointing me in the right direction?

http://forum.xda-developers.com/showthread.php?t=1754018

gunnyman said:
http://forum.xda-developers.com/showthread.php?t=1754018
Click to expand...
Click to collapse
Im still having difficulty loading a recovery via fastboot...
I get to the point where I enter the following line in command prompt...fastboot flash recovery twrp.img and the response I get is "error: cannot load 'twrp.img"
Any suggestions?

rpritch said:
Im still having difficulty loading a recovery via fastboot...
I get to the point where I enter the following line in command prompt...fastboot flash recovery twrp.img and the response I get is "error: cannot load 'twrp.img"
Any suggestions?
Click to expand...
Click to collapse
My Bad...didnt have the img file in the platform-tools folder.
So I've tried flashing the TRWP img and when I reboot into recover, I get the blue and black Teamwin splash screen. then it reboots and stays permanently on the HTC splash screen.
After I flash the clockwork img file and reboot into recovery, it reboots and stays permanetly on the HTC splash screen.
Any suggestions?

rpritch said:
My Bad...didnt have the img file in the platform-tools folder.
So I've tried flashing the TRWP img and when I reboot into recover, I get the blue and black Teamwin splash screen. then it reboots and stays permanently on the HTC splash screen.
After I flash the clockwork img file and reboot into recovery, it reboots and stays permanetly on the HTC splash screen.
Any suggestions?
Click to expand...
Click to collapse
I am having this same exact issue! Did you figure it out? I installed TWRP as well and now get the Teamwin screen before it reboots the the HTC screen with the legal disclaimer. Please help1

veritas2884 said:
I am having this same exact issue! Did you figure it out? I installed TWRP as well and now get the Teamwin screen before it reboots the the HTC screen with the legal disclaimer. Please help1
Click to expand...
Click to collapse
Sounds like a bad flash or corrupt recovery inage. Go to the play store and download goo manager and install twrp from goo manager instead. See if that fixes the problem.
Sent from my Nocturnalized Beast

E.Cadro said:
Sounds like a bad flash or corrupt recovery inage. Go to the play store and download goo manager and install twrp from goo manager instead. See if that fixes the problem.
Sent from my Nocturnalized Beast
Click to expand...
Click to collapse
Our devices will not boot. All we can get is either the white HTC Screen or get into the menu that allows fastboot/recover/ect...

Relock bootloader, run real stock ruu for your carrier, reunlock, reroot, reflash recovery. Flash your desired Rom. You will lose all data on phone!
Sent from my HTC One XL using xda app-developers app

c5satellite2 said:
Relock bootloader, run real stock ruu for your carrier, reunlock, reroot, reflash recovery. Flash your desired Rom. You will lose all data on phone!
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
That is what I am doing now. I did not relock the boot loader first it is in the process of running the RUU. Did I just fry my phone even more?
---------- Post added at 04:04 AM ---------- Previous post was at 03:56 AM ----------
Thanks c5satellite2 ,
For my AT&T One X I fixed it as you stated
Booted into fastboot
Used command window to relock bootloader:
fastboot devices <enter>
fastboot oem lock <enter>
Restarted and rebooted into fastboot again
Ran Stock Rom RUU Program from http://forum.xda-developers.com/showthread.php?t=1649658
Put me back to a working stock phone.
Re-rooted and re-unlocked bootloader
Installed TWRP this time! Thanks for the help! :good:

Recommended process for fixing strange issues like what you were experiencing. Glad it helped you guys out!
Sent from my HTC One XL using xda app-developers app

veritas2884 said:
That is what I am doing now. I did not relock the boot loader first it is in the process of running the RUU. Did I just fry my phone even more?
---------- Post added at 04:04 AM ---------- Previous post was at 03:56 AM ----------
Thanks c5satellite2 ,
For my AT&T One X I fixed it as you stated
Booted into fastboot
Used command window to relock bootloader:
fastboot devices <enter>
fastboot oem lock <enter>
Restarted and rebooted into fastboot again
Ran Stock Rom RUU Program from http://forum.xda-developers.com/showthread.php?t=1649658
Put me back to a working stock phone.
Re-rooted and re-unlocked bootloader
Installed TWRP this time! Thanks for the help! :good:
Click to expand...
Click to collapse
How exactly did you do this part "Ran Stock Rom RUU Program from http://forum.xda-developers.com/show....php?t=1649658"? What command did you use?

rpritch said:
How exactly did you do this part "Ran Stock Rom RUU Program from http://forum.xda-developers.com/show....php?t=1649658"? What command did you use?
Click to expand...
Click to collapse
It's just an exe. Boot your phone into fastboot mode. Your computer will recognize that it is plugged in in fast boot mode if you have the HTC driver installed. Then open the exe on your computer and follow the instructions on the screen. It will take about 15 mins for the whole process and your phone will reboot several times.
Also make sure you use twrp recovery instead of clockwork if you re-root!

veritas2884 said:
It's just an exe. Boot your phone into fastboot mode. Your computer will recognize that it is plugged in in fast boot mode if you have the HTC driver installed. Then open the exe on your computer and follow the instructions on the screen. It will take about 15 mins for the whole process and your phone will reboot several times.
Also make sure you use twrp recovery instead of clockwork if you re-root!
Click to expand...
Click to collapse
I cant seem to find a stock Rogers Ruu...will continue searching. Anyone out there have it?

http://http://forum.xda-developers.com/showthread.php?p=27882810#post27882810
Finally got it working...the above link is what worked. Here is the summary...
I was having this same problem and it took a while before I could get it to work. Try opening a command window in the same location of your adb tools.
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
Hopefully this helps you out!

Berserk87 said:
I'm stock right now (rooted) , but the updates keep failing, so i want to reflash stock rom.
I'm lost as to how to do this.
I downloaded ARUwizard and the stock rogers rom (PJ83IMG) but its still failing. I dont get all this adb tools stuff.
Click to expand...
Click to collapse
do this:
1.Put Rogers stock zip (keep it in zip form) in your platform-tools folder (you need to download Android SDK). This is the rogers file I downloaded...http://rapidlibrary.com/files/pj83i...elease-254934-signed-zip_ulc8eyefx8i89on.html
2. Boot phone into fastboot (hold power button and volume down key)
3. Used command window to relock bootloader by doing the following:
use command window to get to location on your computer where you have saved SDK stuff, continue with command window to the platform-tools folder then enter the following commands:
fastboot devices <enter>
fastboot oem lock <enter>
Phone will restart and reboot into fastboot again
4. type 'fastboot oem rebootRUU'.
5. Next, make sure you have the .zip RUU file in the same folder (see step 1) and type 'fastboot flash zip XXX.zip' (replace XXX with whatever the rogers stock zip is called, I changed it to "rogersstock.zip")
Phone will reboot to a HTC screen. If you see "re-flush image immediately", repeat fastboot flash zip XXX.zip command. You may have to do this 2 or 3 times.
After doing this, I was able to download and install the Rogers firmware update
BTW...I didn't discover any of this stuff on my own...I researched a bunch of different posts and put it together. Hopefully, someone else finds have all this in one post useful.

Hey guys, AT&T One X unlocked
I'm having a similar problem, been following the wiki exactly and when I flashed CWM recovery and it says it was successful:
F:\Users\Ryan\AppData\Local\Android\android-sdk\platform-tools>fastboot flash re
covery recovery-clockwork-touch-5.8.4.0-endeavoru.img
sending 'recovery' (5742 KB)...
OKAY [ 0.890s]
writing 'recovery'...
OKAY [ 1.480s]
finished. total time: 2.380s
When I select recovery it brings up the HTC logo and says in red text "This build is for development purposes only. Do not distribute without HTCs written permission... etc" after about 10 seconds the device boots up as normal.
Not sure what I'm doing wrong.

slash178 said:
Hey guys, AT&T One X unlocked
I'm having a similar problem, been following the wiki exactly and when I flashed CWM recovery and it says it was successful:
F:\Users\Ryan\AppData\Local\Android\android-sdk\platform-tools>fastboot flash re
covery recovery-clockwork-touch-5.8.4.0-endeavoru.img
sending 'recovery' (5742 KB)...
OKAY [ 0.890s]
writing 'recovery'...
OKAY [ 1.480s]
finished. total time: 2.380s
When I select recovery it brings up the HTC logo and says in red text "This build is for development purposes only. Do not distribute without HTCs written permission... etc" after about 10 seconds the device boots up as normal.
Not sure what I'm doing wrong.
Click to expand...
Click to collapse
What you are doing wrong is flashing the recovery for the wrong phone. Any file with "enveavoru" in it is for the international (Tegra3) version. Our phone is "evita".
Only install things in our Dev forum:
http://forum.xda-developers.com/forumdisplay.php?f=1541
To see everything in an organized list, go to my index: http://forum.xda-developers.com/showthread.php?t=1671237
Also, TWRP is recommended. CWM does not officially support our device, and therefore is just a port, and buggy. TWRP officially supports our device.

im getting the same error and im using the recovery ending on evita

Trying to install twrp recovery but failing...

I am trying to install twrp recovery to install CleanROM but it is failing. I have unlocked my bootloader via htc dev but the following fails:
c:\Android>fastboot flash recovery openrecovery-twrp-2.2.2.0-evita.img
sending 'recovery' (7428 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.011s
I am also doing this knowing I have the option of installing the script on Goo Manager but that only downloads, I get a toast saying successfully installed and cannot confirm if it has been installed as the device did not automatically restart and flash.
Please advise... Thanks.

If your running windows, just make sure all you files are in the same folder ie twrp, adb, fast boot then press shift + right click, open command prompt here. I've heard of have you virus protection on? can cause problems.
Sent from my One X using xda premium

Yes, adb.exe - fastboot.exe - AdbWinApi.dll and the twrp recovery image are all in the same folder.

My only other suggestions would be to make sure you have administrative permission s on you PC. I can't imagine why its doing that to you unless you downloaded a corrupt boot image. I've had that happen a few times.
Sent from my One X using xda premium

subarudroid said:
My only other suggestions would be to make sure you have administrative permission s on you PC. I can't imagine why its doing that to you unless you downloaded a corrupt boot image. I've had that happen a few times.
Sent from my One X using xda premium
Click to expand...
Click to collapse
For some reason I never got it installed via my pc either, just used goomanager an it was done pronto.
Just saying.
WR
Sent from my HTC One X

Is there anyway configurations prior to running Goo Manager? I have an unlocked bootloader, not sure what else is missing for it to not restart on it's own after downloading and 'installing'. Did the same thing happen for you?
Also note my phone is not rooted (stuck on Rogers' 1.94.x.x firmware after the OTA) -- could this be a problem? If so, how do I root my device otherwise..?

an_xda said:
Is there anyway configurations prior to running Goo Manager? I have an unlocked bootloader, not sure what else is missing for it to not restart on it's own after downloading and 'installing'. Did the same thing happen for you?
Also note my phone is not rooted (stuck on Rogers' 1.94.x.x firmware after the OTA) -- could this be a problem? If so, how do I root my device otherwise..?
Click to expand...
Click to collapse
Have you checked out the One click tool v 2.2.2.0 under the Index in the dev thread.
I was never able to get fastboot to flash it and this worked for me.
Its under the android development index thread under the heading recovery.

eak1080 said:
Have you checked out the One click tool v 2.2.2.0 under the Index in the dev thread.
I was never able to get fastboot to flash it and this worked for me.
Its under the android development index thread under the heading recovery.
Click to expand...
Click to collapse
Which tool are you referring to? I cannot find it. Any one click tool I see does not work for 1.94.x.x firmware...

I was on 1.94 too.
Just try goomanager again, download twrp, then in goomanager go to options and install open recovery.
Might want to make sure fastboot is off in options too before tryin to boot into recovery.
If that don't work its beyond me sorry.
WR
Sent from my HTC One X

How long does it usually take to flash twrp to the phone? The first time I execute the command, it fails the second time it sends but after 12 minutes nothing changes.

an_xda said:
How long does it usually take to flash twrp to the phone? The first time I execute the command, it fails the second time it sends but after 12 minutes nothing changes.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1777773
this is the thread

Yeah, I found it a few minutes ago as well. I gave up though, I cannot flash through fastboot and goo manager won't work. Guess this phone is not getting any custom roms.

your bootloader is unlocked though?

Yes, via htcdev (it also has the ***unlocked*** status in recovery).

Here's your full proof method.......
Boot up phone all the way, enable USB debugging
Download-
http://db.tt/sXmdepmX
Stick it on root of your internal sdcard.
Open up your command prompt and cd to your adb/fastboot directory.....type-
adb shell
su
dd if=/sdcard/twerp.img of=/dev/block/mmcblk0p22
Once it's done, do it again for good measure...
press up arrow, it rewrites last command, and press enter.
When done type
exit
exit
adb reboot recovery
There u go.......twrp recovery installed:beer:
Sent from my HTC One X using xda premium

18th.abn said:
Here's your full proof method.......
Boot up phone all the way, enable USB debugging
Download-
http://db.tt/sXmdepmX
Stick it on root of your internal sdcard.
Open up your command prompt and cd to your adb/fastboot directory.....type-
adb shell
su
dd if=/sdcard/twerp.img of=/dev/block/mmcblk0p22
Once it's done, do it again for good measure...
press up arrow, it rewrites last command, and press enter.
When done type
exit
exit
adb reboot recovery
There u go.......twrp recovery installed:beer:
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
What does of=/dev/block/mmcblk0p22 mean? This is going to work for the evita One XL right? I do this while my phone is booted up normally?
Trying this, I cannot get past the 'su' command and get: /system/bin/sh: su: not found

Well that's why goo isn't working either......goomanager and this both require root.
Sent from my HTC One X using xda premium
---------- Post added at 09:26 AM ---------- Previous post was at 09:23 AM ----------
are u on windows 8, or using USB 3.0 by chance??
Sent from my HTC One X using xda premium

Right, so that is why I am stuck in this dilemma. I am on 1.94.x.x firmware with the latest Rogers OTA and have no one click method to root and flashing twrp is failing.
I am on Windows 7 and have 2 USB 3.0 ports but currently not hooking up device to those ports.

With bootloader unlocked you should be able to flash a recovery. I see the error your getting when flashing twrp from bootloader and it looks like a communication error of some sort. It's not the phone blocking it......try all your USB ports when in bootloader, make sure your phone says fastboot USB also....if nothing else try a different pc, because it's not the phone, it's def. A pc issue I'd say
Sent from my HTC One X using xda premium
---------- Post added at 05:42 PM ---------- Previous post was at 05:34 PM ----------
Here's your problem....not rooted, goo won't work.....your missing files in your adb/fastboot folder
Download this-
http://db.tt/5ePa4XV5
Unzip and place files in your adb folder, overwrite the ones that are in there or delete them first, but leave your twrp.img and your unlock_code.bin
Boot phone all the way
Open cmd prompt and cd to your adb folder
Type
adb reboot bootloader
Once in bootloader
fastboot flash recovery nameofrecovery.img
Now do it a second time for good measure
On phone screen, select bootloader, then recovery.....done:beer:
Sent from my HTC One X using xda premium

Do what 18th.abn says.

[Q] Stuck at X screen

Obviously I'm a noob, so sorry if this is stupid or there is an obvious answer (I've spent a lot of time looking and couldn't find it though). I was having problems with my phone so decided to flash back to stock and relock it to 'start again'.
Maybe that wasn't a great idea because I've had lots of problems since then. When I try to flash back to stock using nexus root toolkit I get "failed (remote: invalid bootloader)" and the phone finishes still in bootloader. There was a suggestion to force flash, but given the warnings around that I'm pretty nervous about doing that. If I then start my phone up it stays on the google screen for quite a while and then gets stuck on the X screen (it isn't frozen because the animation keeps running, but nothing else happens, even if I leave it for an hour).
I did a bit more reading and tried wiping the dalvik cache and cache. It then said it was upgrading android, optimising apps etc, but then got stuck again. I tried resetting again and the phone now restarts when I push the off button and slowly goes through both the google screen and X screen.
This might be a stupid problem, but I'm stuck so any help would be great.

Flash the stock images manually rather than with a toolkit. You can find a guide stickied under the nexus 5 general section.
Sent using xda-developers app

http://forum.xda-developers.com/showthread.php?t=2513701
[TUTORIAL] How to flash a factory image | Return to stock | Unroot your Nexus 5
Follow this carefully step by step using method 2. Be extremely careful flashing the boot loader, in fact you can probably skip that part. As long as your boot loader is always in tact it's virtually impossible to brick. As of right now you're stuck in what's called a boot loop. Most likely, either your boot.img (not the same as boot loader) or system.img (aka ROM/firmware) is messed up and is causing it.
Welcome to modding, have fun, but be smart
Sent from my Nexus 5 using xda app-developers app

Chromium_ said:
Flash the stock images manually rather than with a toolkit. You can find a guide stickied under the nexus 5 general section.
Sent using xda-developers app
Click to expand...
Click to collapse
Thanks. Either a new problem or a related one - following the guide for setting up adb and fastboot, when i type adb devices into the command prompt nothing is listed (says "list of devices attached", but there isn't anything listed).

beshakey said:
Thanks. Either a new problem or a related one - following the guide for setting up adb and fastboot, when i type adb devices into the command prompt nothing is listed (says "list of devices attached", but there isn't anything listed).
Click to expand...
Click to collapse
Go into fastboot mode and run "fastboot devices". If the device shows up there, that's good enough.
Sent using xda-developers app

Chromium_ said:
Go into fastboot mode and run "fastboot devices". If the device shows up there, that's good enough.
Sent using xda-developers app
Click to expand...
Click to collapse
Thanks, that worked. But having done it when I reboot the phone it does the same thing (hangs of the Google screen for a long time then moves to the X screen and stays there). My phone is rooted and I have clockworkmod installed, so I selected fix root when asked, not sure if that is relevant?

Did you continue to follow the guide and flash the stock images in fastboot
Sent from my Nexus 5 using xda app-developers app

Yeah I did. I got the message "FAILED (remote:invalid bootloader image) and archive does not contain 'boot.sig' 'recovery.sig' and 'system.sig'. Everything else was OKAY. Put into recovery mode fine (with clockworkmod), wiped data and rebooted (fixing root when asked) but the problem described above remains.

More problems - tried doing it again, now it won't even boot up to the google/Android X screens. When I restart the screen lights up but nothing else. I can still reboot into the bootloader though. Arggh

beshakey said:
More problems - tried doing it again, now it won't even boot up to the google/Android X screens. When I restart the screen lights up but nothing else. I can still reboot into the bootloader though. Arggh
Click to expand...
Click to collapse
And you are following the factory image flashing guide that has been provided above?
Can you try going through the guide again, and tell us the specific errors that you are encountering.

And use method two, not the first one that talks about running the flash all script. You should be doing command's like "fastboot flash boot boot.img"
Sent from my Nexus 5 using xda app-developers app

beshakey said:
More problems - tried doing it again, now it won't even boot up to the google/Android X screens. When I restart the screen lights up but nothing else. I can still reboot into the bootloader though. Arggh
Click to expand...
Click to collapse
Don't worry, you'll get it, eventually. When you first start doing this kind of thing, it takes some getting used to because you have to read VERY carefully, and perform each step EXACTLY as stated. Computers are absolutely unforgiving of even the tiniest mistake, so you have to take your time, and be patient when you have to start all over. But, it's a challenge, and a learning process, and a lot of fun, once you get the hang of it.
Sent from my Nexus 5

OK, step by step. If you need more detail yell out.
1) I've downloaded ADB and Fastboot
2) If I put ADB devices into the command prompt I don't get any devices listed. But if I put in Fastboot devices I get the serial number of my phone
3) Previously I'd been using method one. So I now extract the image for hammerhead krt16m to my f:\ drive. I've also extracted radio-hammerhead-M8974A-1.0.25.0.17 and bootloader-hammerhead-HHZ11d to the same location and renamed them to radio.img and bootloader.img respectively
4) Phone is connected to computer and in fastboot (and detected by fastboot devices)
5) In command prompt when I type in fastboot flash bootloader f:/bootloader.img I get the error message FAILED (remoteL invalid bootloader image).
6) Flashed radio.img and rebooted bootloader and system.img (no reboot) without any errors (although they took a while)
7) Flashing userdata.img got the error 'FAILED (remote: flash write failure)
8) Performed all the remaining commands without any errors (when erasing the cache I got the message 'Did you mean to fastboot format this partition? erasing 'cache'... OKAY
9) Entered recovery mode. Earlier when I did this it was fine, but now (like when I try to start the phone) the screen lights up but no text etc appears
10) At this point I'm stuck, as I can't see the cwm text so can't select wipe data/factory data reset (although I did do this as part of earlier attempts)
From the 'on but no text' state, I can using the on button to restart into the same state or can enter fastboot (where text etc appears fine)

One at the boot loader you said you put f:/bootlaoder.img that was wrong, no drive letter. You do not need to flash your boot loader though anyways. Avoid doing that unless you have to, it is the only thing that will brick your phone.
You said system.img flashed fine, did not see any Menton of a boot.img or recovery.img. you need all three of these.
So, start over again. Make sure you flash a boot.img system.img and recovery.img separately. DO NOT flash the bootloader.img unless you have to (to update). Again, the boot loader is the one thing that will brick your phone if done wrong.
Sent from my Nexus 5 using xda app-developers app
---------- Post added at 07:31 AM ---------- Previous post was at 07:28 AM ----------
Sorry I just read through that tutorial and it does tell you to use drive letters. Im used to flashing with my files in the location of fastboot so I don't need to do that.
Sent from my Nexus 5 using xda app-developers app

@op why you are flashing 4.4 images?? it has a different bootloader then 4.4.2.
i guess your primary bootloader now is 11k and not 11d or 11a .....(since you took the ota out of the box)
bootloader version must match with the rest of images.
so download 4.4.2 images and flash them using 11k bootloader. (note that you have the old and new bootloaders on your device, volume down + power will take to the new bootloader 11k, and Volume down + volume up + power will take you to the old bootloader).
regarding adb command, it will not work in fastboot mode, it works when booting in os with usb debugging enabled, or in custom recovery mode

Good catch.
Sent from my Nexus 5 using xda app-developers app

samersh72 said:
@op why you are flashing 4.4 images?? it has a different bootloader then 4.4.2.
i guess your primary bootloader now is 11k and not 11d or 11a .....(since you took the ota out of the box)
bootloader version must match with the rest of images.
so download 4.4.2 images and flash them using 11k bootloader. (note that you have the old and new bootloaders on your device, volume down + power will take to the new bootloader 11k, and Volume down + volume up + power will take you to the old bootloader).
regarding adb command, it will not work in fastboot mode, it works when booting in os with usb debugging enabled, or in custom recovery mode
Click to expand...
Click to collapse
Thanks I'll try that. Is there any way for me to confirm on my phone what my primary bootloader is?

beshakey said:
Thanks I'll try that. Is there any way for me to confirm on my phone what my primary bootloader is?
Click to expand...
Click to collapse
Boot into it using power volume down and it will list the version
Sent from my Nexus 5 using xda app-developers app

travisjustin said:
Boot into it using power volume down and it will list the version
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Will try that, thanks.
I'm pretty sure I've done something stupid to cause this and I had a thought about what it might be - my phone was still at 4.3 for some reason. It would receive the update and install it, but the version wouldn't change to the new one. So should I try to track down the old 4.3.? bootloader?

beshakey said:
Will try that, thanks.
I'm pretty sure I've done something stupid to cause this and I had a thought about what it might be - my phone was still at 4.3 for some reason. It would receive the update and install it, but the version wouldn't change to the new one. So should I try to track down the old 4.3.? bootloader?
Click to expand...
Click to collapse
4.3? The nexus 5 ships with kitkat 4.4 ...there is no 4.3 for it.
Sent using xda-developers app