Database Info

Using fastboot without ENG or S-OFF

As many of you may know, you are locked out of using fastboot commands unless you have an engineering SPL. But I made a little discovery last night about how the HTC Rom Update Utility actually installs ROMs. Turns out it uses... fastboot!
Here's how it works:
With phone powered on, do "adb reboot bootloader" to enter fastboot.
-OR- With phone powered down, power on phone while holding VOL DOWN. From there press VOL UP to enter fastboot.
Run the command "fastboot oem rebootRUU"
Now you should see a black screen with a silver HTC logo. Look familiar? This is the screen you'll see when using the RUU.
From here you can re-flash an original HTC ZIP, with "fastboot flash zip filename.zip", where filename is the name of your signed HTC image.
As an added bonus, if your phone is S-OFF (even if you're not using the ENG SPL), you can flash ANY fastboot-compatible ZIP from here, signed or not.
When you're done, "fastboot reboot" will boot the device.
Found this by accident trying to help someone on IRC who had screwed up both their ROM and recovery somehow. All they could get into was fastboot/hboot, and they were S-ON.

Thankyou!
Just wanted to say I'm the guy that messed up his phone and needed Jason's help. He got me into a Sense ROM and was able to then get clockwork running again and restore my Nand. Really save my bacon.
Also, I've followed your advice. I now have a rooted AND S-off hero running Gingerbread.
Thanks again!

jasonmaloney said:
As many of you may know, you are locked out of using fastboot commands unless you have an engineering SPL. But I made a little discovery last night about how the HTC Rom Update Utility actually installs ROMs. Turns out it uses... fastboot!
Here's how it works:
With phone powered on, do "adb reboot bootloader" to enter fastboot.
-OR- With phone powered down, power on phone while holding VOL DOWN. From there press VOL UP to enter fastboot.
Run the command "fastboot oem rebootRUU"
Now you should see a black screen with a silver HTC logo. Look familiar? This is the screen you'll see when using the RUU.
From here you can re-flash an original HTC ZIP, with "fastboot flash zip filename.zip", where filename is the name of your signed HTC image.
As an added bonus, if your phone is S-OFF (even if you're not using the ENG SPL), you can flash ANY fastboot-compatible ZIP from here, signed or not.
When you're done, "fastboot reboot" will boot the device.
Found this by accident trying to help someone on IRC who had screwed up both their ROM and recovery somehow. All they could get into was fastboot/hboot, and they were S-ON.
Click to expand...
Click to collapse
Really? Thanks for the Info... Helpful, and Good to Know!!
Sent from my Hero using XDA App

wow, this is valuable information. couldnt this be put into the wiki or something? i tend to go to the wiki often, but i dont know how to properly edit a wiki.

jasonmaloney said:
As many of you may know, you are locked out of using fastboot commands unless you have an engineering SPL. But I made a little discovery last night about how the HTC Rom Update Utility actually installs ROMs. Turns out it uses... fastboot!
Here's how it works:
With phone powered on, do "adb reboot bootloader" to enter fastboot.
-OR- With phone powered down, power on phone while holding VOL DOWN. From there press VOL UP to enter fastboot.
Run the command "fastboot oem rebootRUU"
Now you should see a black screen with a silver HTC logo. Look familiar? This is the screen you'll see when using the RUU.
From here you can re-flash an original HTC ZIP, with "fastboot flash zip filename.zip", where filename is the name of your signed HTC image.
As an added bonus, if your phone is S-OFF (even if you're not using the ENG SPL), you can flash ANY fastboot-compatible ZIP from here, signed or not.
When you're done, "fastboot reboot" will boot the device.
Found this by accident trying to help someone on IRC who had screwed up both their ROM and recovery somehow. All they could get into was fastboot/hboot, and they were S-ON.
Click to expand...
Click to collapse
I have a similar problem with my CDMA hero. I tried the "Run the command "fastboot oem rebootRUU" and I get
<bootloader> [ERR] command error !!!
What am I doing wrong ? Probably everything.
Thanks.

Houndog101 said:
I have a similar problem with my CDMA hero. I tried the "Run the command "fastboot oem rebootRUU" and I get
<bootloader> [ERR] command error !!!
What am I doing wrong ? Probably everything.
Thanks.
Click to expand...
Click to collapse
Which bootloader version do you have, and where did you get the fastboot binary?

jasonmaloney said:
Which bootloader version do you have, and where did you get the fastboot binary?
Click to expand...
Click to collapse
HBOOT-1.47.0000 (HERO20000) is this what you mean ?
I got the fastboot off this site with SDK tools Android SDK updater ,revision 10. Is this what you need ?
Thanks for helping me..

hey Jason here's some background on his problem, I linked him this thread, hopefully you have more patience than me, but you know me, I don't really and I'm a dink http://forum.xda-developers.com/showthread.php?t=984688

Houndog101 said:
HBOOT-1.47.0000 (HERO20000) is this what you mean ?
I got the fastboot off this site with SDK tools Android SDK updater ,revision 10. Is this what you need ?
Thanks for helping me..
Click to expand...
Click to collapse
Not sure why it would be giving you issue. Make sure you're in fastboot mode and not hboot mode. You should see "Fastboot USB" on the screen if memory serves.
Alternatively, try the copy of fastboot.exe on my site. I pulled this directly from HTC's Rom Update Utility, so it might work better.

jasonmaloney said:
Not sure why it would be giving you issue. Make sure you're in fastboot mode and not hboot mode. You should see "Fastboot USB" on the screen if memory serves.
Alternatively, try the copy of fastboot.exe on my site. I pulled this directly from HTC's Rom Update Utility, so it might work better.
Click to expand...
Click to collapse
Jason, Thanks a million times, That was a problem, I d/l your fast.boot and it got me to the Black with silver htc screen. I'll see what I can do from here. Just want to get it to where I can boot into recovery.. Thanks again for helping me.

I've followed all the instructions but with a slightly different problem. I can't get to bootloader at all, but if I plug my hero to my pc and turn it on then it will say "fastboot usb" in a red rectangle at the top left, but is still otherwise the white HTC screen. when I do "fastboot oem rebootRUU" the terminal says okay, but the phone reboots into the same state instead of the black and silver screen I am hoping to see. Is it a brick or is there another option?

I get to where I want to load the image and it says "error: cannot load 'HERCIMG.zip'". Is this because it is not signed. I have the zip on the root of my sd card. I'm trying to install just a stock ROM and unroot so I can sell my phone.

beand1p said:
I get to where I want to load the image and it says "error: cannot load 'HERCIMG.zip'". Is this because it is not signed. I have the zip on the root of my sd card. I'm trying to install just a stock ROM and unroot so I can sell my phone.
Click to expand...
Click to collapse
If you look in the hero dev section you can find a thread called ruu in zip format. It will take you back to stock all the way no recovery no nothing just like fresh out the box. I've used it myself when I couldn't flash sense roms. And it works great. I would link you but I'm mobile. You might have to dig a little but its worth it. Good luck.
Yea It's Me Again With the
Modified Hero

laie1472 said:
If you look in the hero dev section you can find a thread called ruu in zip format. It will take you back to stock all the way no recovery no nothing just like fresh out the box. I've used it myself when I couldn't flash sense roms. And it works great. I would link you but I'm mobile. You might have to dig a little but its worth it. Good luck.
Click to expand...
Click to collapse
I get the same error even with that zip. I am S-OFF also. I have HBOOT-1.47 with radio 2.42.01.04.27.
I've tried almost everything to unroot and get back to stock. I am about ready to throw in the towel.

Why not just leave it rooted and put a stock rooted rom? Seems at that point you could remove superuser permissions somehow if It's that important for them to not have root. That would essentially take away root for all intensive purposes I would think. I'm just thinking out loud here and definitely you may want another opinion, but having root on the phone won't really cause them any real problems as long as they have a stock rom. They can still activate it, it still has the same menu options for a hard reset...maybe I'm missing the point other than you should be able to do what you're trying?
[dpeeps74]

dpeeps74 said:
Why not just leave it rooted and put a stock rooted rom? Seems at that point you could remove superuser permissions somehow if It's that important for them to not have root. That would essentially take away root for all intensive purposes I would think. I'm just thinking out loud here and definitely you may want another opinion, but having root on the phone won't really cause them any real problems as long as they have a stock rom. They can still activate it, it still has the same menu options for a hard reset...maybe I'm missing the point other than you should be able to do what you're trying?
[dpeeps74]
Click to expand...
Click to collapse
All the stock RUU's I have tried always give me the RUU Error [140]: BOOTLOADER VERSION ERROR
EDIT
I was able to RUU after using this method: http://forum.xda-developers.com/showthread.php?t=843544

I'm currently hitting a roadblock with this. Whenever i try the fastboot update zip command, and add the filename, i get an error saying that it cannot load said filename. i have no clue what i'm doing wrong.

zbach said:
I'm currently hitting a roadblock with this. Whenever i try the fastboot update zip command, and add the filename, i get an error saying that it cannot load said filename. i have no clue what i'm doing wrong.
Click to expand...
Click to collapse
The zip file should be on your computer, not your phone. Make sure to specify an absolute path for the zip file if the fastboot.exe file is not in the same folder as the zip file.

jasonmaloney said:
The zip file should be on your computer, not your phone. Make sure to specify an absolute path for the zip file if the fastboot.exe file is not in the same folder as the zip file.
Click to expand...
Click to collapse
I have the zip file in the android file along with the fastboot.exe program. I still get a "Cannot load" error message

thank you x100000.
I couldnt flash the original ruu because of the weird bootloader issue, but this worked like a charm and i was able to flash with a .zip of the ruu.
Thanks again.

[Q] Evo Shift Bricked Real Good? Stuck on HTC logo screen.

My first post here so go easy on me
Anyway, I got an Evo Shift, I do not know its history, but its stuck in some sort of a boot loop, on the white screen with green HTC logo.
Things I know:
****UNLOCKED****
SPEEDY XE SHIP S-ON
HBOOT -0.99.0001
RADIO - 1.08.01.0111
Clockwork Recovery v5.0.2.0
I did not get an SD card with it, no recovery image.
RUU says version is 2.77.651.3
I know the S-on is a problem.
I have tried all 4 of the RUU versions - failed.
Tried RUU with Gold Card - failed.
Tried rom.zip from each RUU renamed to PG06IMG.zip - failed.
I have tried custom roms of all sorts, every methoud I found - failed.
Where do I go from here? Is there a way of manually flashing all the partitions from a ROM.zip file via fastboot? Is there a way of disabling a version check in RUU? Or is there a way of disabling MD5 sum in Clockwork so I can try flashing a restore image from another Shift?
I have spent 3 days on this phone, and I would hate to admit defeat, so I am reaching out to the genius minds here. Thanks in advance!

Okay, I fixed it. did a write up on how I did it in case someone else fubars their phone.
Things you will need:
Android SDK
HTC Drivers
7-zip
RUU_Speedy_Sprint_WWE_1.17.651.1_Radio_1.07.00.112 9_NV_SPCS_1.52_1103_release_160079_signed.exe
On your computer, search for ROM.ZIP. Include system locations and hidden files.
Delete any instances of it that you may find.
Take the SD card out of the phone.
Put your Shift into fastboot (vol/down + power)
Run the RUU, let it get stuck.
On your computer, run a search for ROM.ZIP while the RUU is running. Its gonna show up in some temp folder.
Copy it to your desktop.
Use 7zip to extract it (for whatever reasons Windows can't extract it).
Open the extracted rom.zip folder.
Copy all files and place them in your SDKs platform tools folder.
Shut down the RUU, reboot the phone into recovery (vol/down + power).
Run CMD and change directories to your platform tools folder.
Type the command "fastboot flash recovery recovery.img" (without the quotes) - this gets rid of any custom recovery like Clockwork, etc.
Reboot the phone into recovery again, you should have a triangle with an ! next to it on black background.
Go back to CMD and your platform tools, and start flashing the following:
fastboot flash boot boot.img
fastboot flash dzdata dzdata.img
fastboot flash partition partition.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Reboot the phone.
After 30 seconds of white HTC screen, your phone should boot up fine and you will be in Android 2.2.
Let me know if it worked out for you, I just fixed mine less than an hour before writing this up.
Also, if anyone out there sees anything redundant, or can help me clean this process up a bit, I welcome your input.

gzetski said:
Okay, I fixed it. Please delete the thread. Unless someone wants me to do a write up on how I did it in case someone else fubars their phone.
Click to expand...
Click to collapse
Did you unlock the bootloader with htcdev tool?

The bootloader was already unlocked when I got the phone.

Thanks for this. I will test it and add it to my guide.

VICODAN said:
Thanks for this. I will test it and add it to my guide.
Click to expand...
Click to collapse
You're welcome... I figured I'd just go hard since it was bricked already.
Speaking of guides though, can I get a bit of clarification on something?
http://forum.xda-developers.com/showthread.php?t=1357157
2.3.4 step 15,
Place misc.img and PG06IMG.zip on sdcard using windows explorer or "adb push /sdcard/file.xxx" via usb
Click to expand...
Click to collapse
Where is the MISC.IMG coming from, and what is ( rom? which one? etc.)in the PG06IMG.zip?
Thanks!

And BTW, I am now rooted, but with S-ON... Grrr. Superuser works, rom manager works, pretty much anything requiring root access works. I have rebooted the thing like 20 times to see if it goes away, and its sticking just fine, but I am afraid of trying to flash a custom rom with the S-ON.
All attempts to flash ENG bootloader fail, both by flashing via fastboot (all my MD5 sums match, the process is flawless from start to finish, when I reboot, still same bootloader with S-ON), or using ShiftRR.
Any ideas?

gzetski said:
You're welcome... I figured I'd just go hard since it was bricked already.
Speaking of guides though, can I get a bit of clarification on something?
http://forum.xda-developers.com/showthread.php?t=1357157
2.3.4 step 15,
Where is the MISC.IMG coming from, and what is ( rom? which one? etc.)in the PG06IMG.zip?
Thanks!
Click to expand...
Click to collapse
shift-rootkit.rar
Read the prereqs.

Okay, got it.
Too many things floating through the intertubes with similar filenames.

gzetski said:
Okay, got it.
Too many things floating through the intertubes with similar filenames.
Click to expand...
Click to collapse
Yep, I've finally got the thread pinned, and I created 2 videos on how to do it the right way. They are uploading to youtube now.

S-off?
Did you ever figure out how to get S-Off? I seem to be right where you were a few days ago with the phone appearing to have root, but S-on still there. I'm also running HBOOT -0.99.0001 and unlocked via the HTC Dev tool. Is there anyway to downgrade to .93 or to turn S-Off. My ultimate goal is to get Cyanogenmod on this Shift.
Thanks in advance!

I have not messed with the phone for a few days. I am gonna try to go back to 2.3.4 then downgrade again. Most likely what I ended up having is a bunch of borked files, hopefully the latest RUU will fix that. This was really intended as a brick fix and not a legitimate 2.2 downgrade. When I mess with it, I will post the results for you though.

Omg thank you! I accidentally bricked one of my evo shifts and spent 3 hours trying to figure out how to fix it. I'm so glad I ran into this thread. Worked like a charm for me.

MTsol said:
Omg thank you! I accidentally bricked one of my evo shifts and spent 3 hours trying to figure out how to fix it. I'm so glad I ran into this thread. Worked like a charm for me.
Click to expand...
Click to collapse
Its not a brick if you can fix it... Bricked phones are permanent paperweights, nothing more, nothing less...
Sent from my PG06100 using Xparent Blue Tapatalk 2

drob311 said:
Its not a brick if you can fix it... Bricked phones are permanent paperweights, nothing more, nothing less...
Sent from my PG06100 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Yes Sir . Been there done that. Had a HERO that somehow got " water damaged " after it was BRICKED .

signature verify fail
gzetski said:
Okay, I fixed it. did a write up on how I did it in case someone else fubars their phone.
Things you will need:
Android SDK
HTC Drivers
7-zip
RUU_Speedy_Sprint_WWE_1.17.651.1_Radio_1.07.00.112 9_NV_SPCS_1.52_1103_release_160079_signed.exe
On your computer, search for ROM.ZIP. Include system locations and hidden files.
Delete any instances of it that you may find.
Take the SD card out of the phone.
Put your Shift into fastboot (vol/down + power)
Run the RUU, let it get stuck.
On your computer, run a search for ROM.ZIP while the RUU is running. Its gonna show up in some temp folder.
Copy it to your desktop.
Use 7zip to extract it (for whatever reasons Windows can't extract it).
Open the extracted rom.zip folder.
Copy all files and place them in your SDKs platform tools folder.
Shut down the RUU, reboot the phone into recovery (vol/down + power).
Run CMD and change directories to your platform tools folder.
Type the command "fastboot flash recovery recovery.img" (without the quotes) - this gets rid of any custom recovery like Clockwork, etc.
Reboot the phone into recovery again, you should have a triangle with an ! next to it on black background.
Go back to CMD and your platform tools, and start flashing the following:
fastboot flash boot boot.img
fastboot flash dzdata dzdata.img
fastboot flash partition partition.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Reboot the phone.
After 30 seconds of white HTC screen, your phone should boot up fine and you will be in Android 2.2.
Let me know if it worked out for you, I just fixed mine less than an hour before writing this up.
Also, if anyone out there sees anything redundant, or can help me clean this process up a bit, I welcome your input.
Click to expand...
Click to collapse
First, I want to thank you for posting this even though it hasn't yet worked for me. I'm in essentially the same position you started in. Phone will not boot past the green-on-white HTC logo. I boot to recovery and can get to fastboot mode with USB detected. I flashed recovery.img and boot.img with no problems, but trying to flash dzdata onwards gives me the same error every time: "(bootloader) signature checking... FAILED (remote: signature verify fail)" and will not flash the other components from ROM.ZIP.
Any thoughts on how to proceed? This thing is rapidly approaching permanent brick status.

You need to unlock your bootloader and then flash the rom. zip files through fastboot
The "failed" message means that your bootloader is locked

to get S-off the easiest method is to downgrade your device from 2.3.4 to 2.2 and then FOLLOW THE SAME INSTRUCTIONS AS OBTAINING S-OFF ON 2.3.4. i had the same issue when i first unlocked my Shift bootloader.

[Q] Problems with Leedroid 2.0

Hi,
i came to the screen install form zip on sdcard
but then it starts installation
and shows : installation aborted
now i cant start the phone i always get tothis screen
with the red text this build is for ....
what can i do?
edit: now i am again there where i can install zip from sdcard, but now it doesnt recognize the sdcard. What can I do, because i the phoen does not take a microsdcard where I could put a new rom.
how can i get access to the internela storage now wihtour a os?

How did this happen ? Selecting a ROM to flash in recovery cant really cause so much damage if it fails. They usually fail because of a md5 mismatch or something.
try to mount the sd card and you can use adb to push files to it..
you could also try a full wipe..

I did several things. I rooted and unlocked the device
and now it does not boot.
Everytime I tired to flash leedroid or stock rom with choosing install form zip
installation get aborted.
I am only able to get into the boolloader and into the recovery.
how can i restore the phone?
wipe and recovery is not possible i always end in this screen
with the red text.
edit: i think i try to get into booloader and copy another file version with adb to the sd card and hope it was a download error.
but why the hell then did both the leedroid 'AND the stock rom fail?

did you flash the boot.img BEFORE flashing leedroids ROM ??
If not i suggest trying that, If that fails, Just run an RUU and start from the beginning

Thanks for the Idea,
my problem is that i cant get access to the memory wihtout a working rom
on it And now i also dont get into the recovery CWMS.
I thouzhg power+vol up would do it but it doesnt work
I think i destroyed my brand new phone.
but thanks for helping.

It's not broken.
Try Power + Vol. down. Possibly you need to retry this several times to get into the bootloader.

its not destroyed dont worry..
Run an RUU and all will be good again. Whats your CID ?

That is the problem I cannot put up software on the device
so how should i run a ruu?
Where can i get the CID from wihtout starting the phone?
I hope you have a trick how I can save the device.

angeloski said:
That is the problem I cannot put up software on the device
so how should i run a ruu?
Click to expand...
Click to collapse
You run it from your Windows desktop. Download your appropriate RUU here for example (as it takes a loooooong time).
Connect your phone to your computer via USB.
Double Click the RUU-file.
Answer the Questions and the update will start.
Remember: Your device will be reset to factory default and your data on sd card will be gone so.
Edit: You will still have to start it with power + vol. down buttons pressed (as far as I remember).

angeloski said:
That is the problem I cannot put up software on the device
so how should i run a ruu?
Where can i get the CID from wihtout starting the phone?
I hope you have a trick how I can save the device.
Click to expand...
Click to collapse
To get into the bootloader try this.
Press and hold volume down, then power. Hold both down together for 5 secs, let go of the power button then press the power button several times. This always works for me.
If this works then your phone is easy to fix.

Maybe you could try to reflash the boot.img from leedroid via fastboot.
Then flash a proper recovery.img via fastboot (I use clockworkmod)
As I heard you could then push the rom.zip via Adb the sdcard while in recovery. Last step would be install zip from sdcard.
Sent from my HTC One S using XDA

Have you installed supersu via install ZIP from sdcard? I think this needs go be installed before installing the Rom. I Don't Know it exactly. But like this it worked for me when coming from stock rom. Thats how it worked for me:
1. Unlock bootloader via HTCDev
2. flash recovery image via fastboot
3. Install SuperSU from zipfile in recovery
4. Flash boot.img from Leedroid
5. Install Leedroid from sdcard
So maybe you missed one of the steps.
Sent from my HTC One S using XDA

to get CID go into fastboot and type in cmd window ''fastboot getvar cid''
If your phone is branded, you will need that branded RUU, So i assume you will need o2 Germany RUU

Reflash recovery in fastboot, should give you access to sdcard back.
Sent from my HTC One S using xda premium

i did the same thing to my one s yesterday... followed all the steps for leedroid n got same frustration u have...
theres a nandroid file in the dev section... fastboot the boot.img and the recovery.img
ya phone WILL boot back up

ok guys ty for cheeering me up.
i wil try it with a ruu, where can i find a ruu for my htc one s.
the link in the previuos post ist offline.
i think it was 1.78.407.x when i looked the last time in my handy.
thanks

so my cid is
C:\Android\android-sdk\platform-tools>fastboot.exe getvar cid
cid: O2___102
finished. total time: 0.003s
Like i said it is a O2 i hope this helps finding the ruu

well check the Shipped ROM thread.. If its not there you can ask the OP Football if he has it or can get it..
Some RUU's cost $13 so if you know someone else who wants it, you could split the cost ?

so far, now am in the recovery flash but it is the same
count mount /sdcard
how can i put a file onto the sdcard when i have no access?
partionoing sdcard doesn't help
i was looking for this boot.img and recovery.img which was posted before
i dont find it can someone link me to it if he knows what was meant?
thanks
edit: i was desperate and tried:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
but the second order was not successful
ist there another way to fix this usb brick
and to get access to /sdcard
new edit: now i write also in the help thread (noob friendly) i hope that is ok.

Did you already try this
http://forum.xda-developers.com/showthread.php?t=1667929
Or this
http://forum.xda-developers.com/showthread.php?t=1630459
Sent from my HTC One S using XDA

[Q] Help with Recovering my phone after an OTA update.

Hey, First post and it going to be about whether my phone is bricked for good or not. =/ I'd really appreciate some help as I've clearly not researched enough into this.
-My Rogers HTC One X had previously been rooted and unlocked to hboot 1.09 with cyanogenmod.
-I wanted to install Android Revolution HD, so i figure I needed an hboot update. I went ahead and flashed the phone with the 'firmware.zip' in 'OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.32.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl6j.zip' (HUGE MISTAKE)
-After flashing, I tried to install Android Revolution HD but it had crashed mid way.
-Im able to access hboot and Im also able to go into fastboot and recovery (recovery-clockwork-6.0.2.8-evita).
-Rebooting the phone results in a blank screen after the HTC loading screen. So no adb.
My hboot shows this:
UNLOCKED
EVITA PVT SHIP S-ON RL
HBOOT - 2.14.0000
RADIO - 23a.32.09.29
OPENDSP - v31.1.0.45.0815
eMMC-boot
Nov 26 2012,18:37:14:-1
I've tried locking it, flashing it with PJ83IMG.zip but it says: 'FAILED (remote: 44 hboot version check fail)'.
I've tried running 'RUU_Evita_UL_Rogers_WWE_1.94.631.3_Radio_0.18as.32.09.28L_10.103.32.24L_release_268972_signed.exe' but it gets half way and has Error 155.
Can anyone recommend a rom that will work in this configuration?
Any chance that I can still get S-off on the phone?
Any way to recover the phone at all? Just to be clear, I've flashed my Rogers phone with a Rogers OTA.
Thanks!

Dude you are ****ed! no way to recover from that!..
J/K
All joking aside.
Download TWRP 2.3.3.1 It is compatible with the most ROMS and isn't buggy. Check MD5 and fastboot flash recovery twrprecovery.zip <-- replace with actual zip file name.
then fastboot erase cache
Boot to recovery
Wipe cache dalvik system and factory reset and flash any ROM designed for evita.
Because you're S-ON and on an HBOOT >= 1.14, you'll also have to extract the boot.img from the rom and flash it separately "fastboot flash boot boot.img", unless otherwise indicated on the ROM's thread, usually in the OP.
As a side note, you shouldn't have rooted, you have a lot of reading to do.

Nevermind
Sent from my One XL using XDA Premium

Also that Rom is for the international HTC one x if the install hadn't crashed it would have bricked your phone
Sent from my HTC One X using Tapatalk 2

exad, Thanks for taking the time to write up the instructions for me. I've been able to get the phone to boot again. =) I do have some reading to do haha.
Given whats already done, did I put my phone in a situation where I've limited myself for future modding? What I'm really wondering is if I should be trying to get S-off so I can downgrade my firmware? Will I run into any issues with just running the phone as it is?

certitude said:
exad, Thanks for taking the time to write up the instructions for me. I've been able to get the phone to boot again. =) I do have some reading to do haha.
Given whats already done, did I put my phone in a situation where I've limited myself for future modding? What I'm really wondering is if I should be trying to get S-off so I can downgrade my firmware? Will I run into any issues with just running the phone as it is?
Click to expand...
Click to collapse
If you are going to s off, no need to really downgrade. This because you are turning security checks off. So it actually makes things a bit easier, and decreases the chances of bricking. I'm s off and on hboot 1.14 and was able to flash plenty of roms without a computer.
Sent from my Carbon-ize Evita using xda-developers app

You're not limited. You just need to fastboot flash boot boot.img any time you flash a ROM. If you're not a flashaholic like most of us, it's no big deal.
I wouldn't RUU with S-ON though, even though you didn't supercid, I bricked without supercid running an RUU after rooting.
So, if you don't plan to RUU you don't need to S-OFF either.
If you do intend to S-OFF, since you didn't need to supercid to unlock your bootloader, you would need to hex edit your CID to 11111111 if you wanted to S-OFF.
If you have any other questions, don't hesitate to ask but I suggest reading the stickies in all the sections. Good Luck

Thanks for the info everyone. I'll be keeping that in mind.

exad said:
Dude you are ****ed! no way to recover from that!..
J/K
All joking aside.
Download TWRP 2.3.3.1 It is compatible with the most ROMS and isn't buggy. Check MD5 and fastboot flash recovery twrprecovery.zip <-- replace with actual zip file name.
then fastboot erase cache
Boot to recovery
Wipe cache dalvik system and factory reset and flash any ROM designed for evita.
Because you're S-ON and on an HBOOT >= 1.14, you'll also have to extract the boot.img from the rom and flash it separately "fastboot flash boot boot.img", unless otherwise indicated on the ROM's thread, usually in the OP.
As a side note, you shouldn't have rooted, you have a lot of reading to do.
Click to expand...
Click to collapse
I got a Telus HTC one x yesterday. Spent all day reading about rooting etc and finally went ahead and did it. The unlocking part went without a hitch. I then went to install the clockwork recovery and I think I used an outdated one, because after I did it, it wouldn't boot into recovery. I could get into the bootloader, but checking anything else it wouldn't do anything. At that time I was still able to boot up my phone as normal. I then saw an updated clockwork recovery and tried that one, and it still wouldn't respond when I clicked on recovery. Now I can't do anything except get into the bootloader. My screen says the exact same thing as the original poster in terms of
UNLOCKED
EVITA PVT SHIP S-ON RL
HBOOT - 2.14.0000
RADIO - 23a.32.09.29
OPENDSP - v31.1.0.45.0815
eMMC-boot
Nov 26 2012,18:37:14:-1
I'm so upset right now. I read your instructions on what you suggested to the OP but theirs was Rogers and mines Telus, and I never did have a custom ROM on there, and I don't have a clear cache option, just a 'clear storage'
Even selecting the 'reset phone' doesn't work. I'm ready to cry lol. I don't want to touch anything without guidance so I don't screw it up even further. I know this is the rogers forum but it's what came up when doing a google search.
Please help me. Please tell me this can be fixed. :crying:

Don't use CWM, use TWRP instead. Find version 2.3.3.1 at goo.im (just Google TWRP 2.3.3.1 evita download). Check the md5 of the download is correct. I'm assuming you have fastboot on your pc.
Put the TWRP recovery.img in your fastboot folder
Boot phone into bootloader, wait for it to say "fastboot usb" on the screen of your phone
Open a command prompt in that folder on your pc
Type in the following command:
fastboot flash recovery openrecovery-TWRP-2.3.3.1-evita.img (whatever the name of the recovery image is, I think that's right)
It will now write the recovery to your phone, wait for it to finish, it should only take a few seconds
Now type the following command in:
fastboot erase cache
fastboot reboot-bootloader
Now you should be able to disconnect your phone and flash superuser.zip in your new recovery and have root access.
Sent from my HTC One XL using xda premium

omg!!!!! TY TY TY TY TY!!!!!!!!
It flashed into recovery!!!!!
I can't find where my superuser went...is there a way I can get it onto my phone? At this point I'm so nervous about screwing anything up that I'm afraid to play (which is rare for me as I'm normally quite good at all this stuff)
Do I really need the superuser? I'm planning on putting the ViperXL 3.2.7 rom on my phone. Can I just go straight to installing the rom?
I know where I went wrong now though. I used the international root instructions and not the AT&T ones as I assumed since I was Telus instead of Rogers or AT&T that that was the one I needed. Ugh! I feel like such an idiot!! I had android for quite a while then went to iphone for a little while (mistake) and had gotten so good at doing everything with those and forgot most of the steps involved with rooting android and the terminology. I'm happy to be back home with android!

You can just go ahead and flash ViperXL, that is pre-rooted so you'll be good to go. I just assumed you had a ROM running, so flashing the superuser zip would have just given that ROM root access.
Now, just make sure you stay here in the One XL (AT&T) forum. Make sure you only flash ROMs from here, because flashing one of the International ROMs can brick your phone, and we don't want that.
Sent from my HTC One XL using xda premium

I will be staying here!! lol
Just to be sure I have this correct...
I downloaded Viper and the boot img.
I'm going to go back to my cmd prompts, install the boot img
I'm getting hung up with understanding how to place the zip on my phone storage...My computer isn't showing it as being a separate drive.
I keep getting 'failed' errors with everything in TWRP. If I try to mount as USB storage, my computer says it needs to be formatted...
When I try to do anything else it shows up with failed.

Ok here's what you'll need to do:
Boot your phone into the bootloader (hold power and volume down key together, release power after a second but keep holding volume down until you're in bootloader)
Select recovery
Once recovery boots up, connect to pc with usb cable, select mount in recovery menu, then select mount storage
Your phone should now show up on your pc as a drive, copy the entire ROM zip to your phone
Once it's copied, do eject and safely remove the drive from your pc, and hit unmount on your phone screen
Hit the home button (little house on bottom left) in recovery
From main recovery select wipe, once in wipe menu you must wipe cache, dalvik cache, factory reset, and system
Once you've wiped all those, hit the home button again
Select install from the main recovery menu, then find the ROM you previously copied to your sd card and select it, then swipe to install, let the install finish (please note: if you're installing viper, it will have a few options to select during the install, select the ones you want. But right at the end of the install process there will be a checkbox for "reboot device now" and it will be checked, make sure you uncheck that before you hit finish/done)
Now you'll see two options, wipe cache/dalvik is one, do that, once that's done hit the home button again
From the main menu, hit reboot, and then bootloader, your phone will now boot back into the bootloader and fastboot usb should show up in red text on your screen if your usb cable is still connected
Now back to the pc, Copy the boot.img from the ROM zip and place it in your fastboot folder
Make sure you're connected with usb and fastboot usb is showing on your phone screen
Open a command prompt in your fastboot folder on pc and type in:
fastboot devices
You should see a device number return in the command prompt, if that shows up you're connected properly, so now type in the following command:
fastboot flash boot boot.img
This will flash the boot.img to your phone, let it finish
Once that's done you can reboot and you should be able to reboot into your new ROM
Sent from my Evita

It's not mounting...just keep getting a message from my computer that the drive needs to be formatted before I can use it...
btw, ty for all your help on this you've been amazingly helpful!

You may have corrupted your sd card. You'll have to format it, which means you'll lose all your data off it unfortunately. Do that first and then start again.
Sent from my Evita

It worked!!!!!! It booted up into Viper!!!!! TY a million times over!!!!!!!!!!

Awesome, so glad to see you got it going :thumbup:
And no problem at all, my pleasure, this is what XDA is all about.
Sent from my Evita

Help save my Sensation

I have an XE, HBOOT 1.27 Unlocked and S-ON and I flashed many ROMs, always enabling SmartFlash in 4Ext.
Yesterday I tried to flash Sebastian's ROM, Revelation, and now my phone is stuck at HTC Splash Screen.
First I did a nandroid to my current ROM, Pac 1.1, then format all(except SD Card), then flashed Revelation and something went wrong.
After flash complete I confirmed reboot and right before 4Ext closed, it showed a message saying something like : It has been detected a change in your boot partition, a backup of previous has been made in /sdcard/4Ext/boot.
It stays like that for a few seconds(I always had this message when flashed other ROMs) and soon after says something "there has been an error, report it" (never seen this message before) and reboots, but keeps showing Splash Screen for ~5 seconds, turns black, then Splash Screen again and so on until I remove the battery.
What can I do and how?
Someone told me to push via fastboot the ROM's boot.img but there is a problem.I have a PC where the phone has never been connected via USB cable, so I have no driver/tool anything.
When I connect it to PC, nothing shows up.
If I select FASTBOOT from the bootloader menu, still nothing shows up on PC.I tried from 4Ext menu Toggle usb connection, but still no trace on my PC.
I beg you, help me.
EDIT : I just found out that Sebastian messed up something in the installer, and all I have to do is to flash the boot.img through fastboot.

doublin said:
I have an XE, HBOOT 1.27 Unlocked and S-ON and I flashed many ROMs, always enabling SmartFlash in 4Ext.
Yesterday I tried to flash Sebastian's ROM, Revelation, and now my phone is stuck at HTC Splash Screen.
First I did a nandroid to my current ROM, Pac 1.1, then format all(except SD Card), then flashed Revelation and something went wrong.
After flash complete I confirmed reboot and right before 4Ext closed, it showed a message saying something like : It has been detected a change in your boot partition, a backup of previous has been made in /sdcard/4Ext/boot.
It stays like that for a few seconds(I always had this message when flashed other ROMs) and soon after says something "there has been an error, report it" (never seen this message before) and reboots, but keeps showing Splash Screen for ~5 seconds, turns black, then Splash Screen again and so on until I remove the battery.
What can I do and how?
Someone told me to push via fastboot the ROM's boot.img but there is a problem.I have a PC where the phone has never been connected via USB cable, so I have no driver/tool anything.
When I connect it to PC, nothing shows up.
If I select FASTBOOT from the bootloader menu, still nothing shows up on PC.I tried from 4Ext menu Toggle usb connection, but still no trace on my PC.
I beg you, help me.
Click to expand...
Click to collapse
Hi,
Try flashing a STOCK ROM
Choose the XE in the second post.
Otherwise you will have to setup your PC to run a RUU,and return everything back to square one.

The weird thing is that even if I try to flash another ROM, stil the same problem.
I format all except SD card,wipe cache+dalvik, mount SD card into PC and delete folder 4Ext/boot_backup.
Go back to 4Ext, enable SmartFlash and flash CM 10.1 by Albino . Reboot, I get the message about my boot partition has been modified, but not the error too, and when it reboots, stuck at splash screen.
I'm desperate.

doublin said:
The weird thing is that even if I try to flash another ROM, stil the same problem.
I format all except SD card,wipe cache+dalvik, mount SD card into PC and delete folder 4Ext/boot_backup.
Go back to 4Ext, enable SmartFlash and flash CM 10.1 by Albino . Reboot, I get the message about my boot partition has been modified, but not the error too, and when it reboots, stuck at splash screen.
I'm desperate.
Click to expand...
Click to collapse
Hi,
It looks like your only option to reconfigure your boot partition ,is to run a RUU.
Look HERE
Do you know the version-main of your phone?
But first you will also need to setup your PC for ADB.
Look HERE

malybru said:
Hi,
It looks like your only option to reconfigure your boot partition ,is to run a RUU.
Look HERE
Do you know the version-main of your phone?
But first you will also need to setup your PC for ADB.
Look HERE
Click to expand...
Click to collapse
Ok thank you for your links.
I'll try to do it tomorrow `cause right now I can't keep my concentration, too late and had a long day.

malybru said:
Hi,
It looks like your only option to reconfigure your boot partition ,is to run a RUU.
Look HERE
Do you know the version-main of your phone?
But first you will also need to setup your PC for ADB.
Look HERE
Click to expand...
Click to collapse
actually if he setup the pc with adb and fastboot files he will be able to flash the boot.img manually
so why the ruu.exe?

rzr86 said:
actually if he setup the pc with adb and fastboot files he will be able to flash the boot.img manually
so why the ruu.exe?
Click to expand...
Click to collapse
I tried that yesterday with the help of a guy, but no success.
I installed all necessary drivers, adb and fastboot, but I can't get my phone discovered on my PC.
If the boot partition would be screwed, why it doesn't work when I try to flash other ROM? Like CM 10.1 or the XE Stock that I've been suggested a few posts above. Flashing this ROMs, shouldn't the boot partition be written with the ROM's files, and everything should turn back as normal?

doublin said:
I tried that yesterday with the help of a guy, but no success.
I installed all necessary drivers, adb and fastboot, but I can't get my phone discovered on my PC.
If the boot partition would be screwed, why it doesn't work when I try to flash other ROM? Like CM 10.1 or the XE Stock that I've been suggested a few posts above. Flashing this ROMs, shouldn't the boot partition be written with the ROM's files, and everything should turn back as normal?
Click to expand...
Click to collapse
It should rewrite the boot partition. Are you sure 4ext says "a pending update to..." and the process completes?
First boot after a new flash can take as long a 10mins. Wait it out.
Anyway if it diesnt work, try another wipe (all except sdcard) flash another rom, and if you're still stuck, use an ruu.
Happy to help.

Far_SighT said:
It should rewrite the boot partition. Are you sure 4ext says "a pending update to..." and the process completes?
First boot after a new flash can take as long a 10mins. Wait it out.
Anyway if it diesnt work, try another wipe (all except sdcard) flash another rom, and if you're still stuck, use an ruu.
Happy to help.
Click to expand...
Click to collapse
I'm very sure 4ext says "a pending update to..." but only it doesn't completes as usual, instead show an error saying that the process couldn't be completed and the boot partition was reverted back as it was,report the problem. This happens when trying to flash Revelation.
I flashed CM 10.1 and says only " a pending update to..." no error , reboots and keeps turning off and on the splash screen.
I flashed a stock XE ROM, happens same thing as in CM 10.1 case.
I tried restoring from nandroid , happens same as CM 10.1 and stock XE ROM.
I wiped and flashed so many times in the last 2 days that I didn't do in the whole year that I had the phone.
I can't use a RUU, as I'm stuck at getting the phone discovered by PC.As I said, I installed all necessary drivers found on a topic here, but still can't see the phone.I tried HTC Sync also, as that pack installs the drivers too, but still no luck.
My last hope is to try connecting the phone on an older PC that I put it in a box and thrown it in the garage.That PC has all drivers and set-up for the phone, but they are outdated for sure.

doublin said:
I'm very sure 4ext says "a pending update to..." but only it doesn't completes as usual, instead show an error saying that the process couldn't be completed and the boot partition was reverted back as it was,report the problem. This happens when trying to flash Revelation.
I flashed CM 10.1 and says only " a pending update to..." no error , reboots and keeps turning off and on the splash screen.
I flashed a stock XE ROM, happens same thing as in CM 10.1 case.
I tried restoring from nandroid , happens same as CM 10.1 and stock XE ROM.
I wiped and flashed so many times in the last 2 days that I didn't do in the whole year that I had the phone.
I can't use a RUU, as I'm stuck at getting the phone discovered by PC.As I said, I installed all necessary drivers found on a topic here, but still can't see the phone.I tried HTC Sync also, as that pack installs the drivers too, but still no luck.
My last hope is to try connecting the phone on an older PC that I put it in a box and thrown it in the garage.That PC has all drivers and set-up for the phone, but they are outdated for sure.
Click to expand...
Click to collapse
There you go. The reason your phone is in a bootloop is that the correct boot.img is not written.
And something is not right with your recovery. It could be a bad flash (I'm not sure).
I don't think you need to use an ruu. Just get on a pc that recognizes your device, and flash the correct boot.img.
I would advise that you flash the recovery.img again.
EDIT: Change usb port to 2.0. Try all usb ports on your computer. It is quite common that fastboot recognizes devices on some usb ports and not on others.
Alternatively read this, point 4. This will surely work if you can't get another pc

doublin said:
I'm very sure 4ext says "a pending update to..." but only it doesn't completes as usual, instead show an error saying that the process couldn't be completed and the boot partition was reverted back as it was,report the problem. This happens when trying to flash Revelation.
I flashed CM 10.1 and says only " a pending update to..." no error , reboots and keeps turning off and on the splash screen.
I flashed a stock XE ROM, happens same thing as in CM 10.1 case.
I tried restoring from nandroid , happens same as CM 10.1 and stock XE ROM.
I wiped and flashed so many times in the last 2 days that I didn't do in the whole year that I had the phone.
I can't use a RUU, as I'm stuck at getting the phone discovered by PC.As I said, I installed all necessary drivers found on a topic here, but still can't see the phone.I tried HTC Sync also, as that pack installs the drivers too, but still no luck.
My last hope is to try connecting the phone on an older PC that I put it in a box and thrown it in the garage.That PC has all drivers and set-up for the phone, but they are outdated for sure.
Click to expand...
Click to collapse
Hi,
If you need windows 7 & 8 drivers, look HERE
If it worked on your old computer,then,it will still work now.

Far_SighT said:
There you go. The reason your phone is in a bootloop is that the correct boot.img is not written.
And something is not right with your recovery. It could be a bad flash (I'm not sure).
I don't think you need to use an ruu. Just get on a pc that recognizes your device, and flash the correct boot.img.
I would advise that you flash the recovery.img again.
EDIT: Change usb port to 2.0. Try all usb ports on your computer. It is quite common that fastboot recognizes devices on some usb ports and not on others.
Alternatively read this, point 4. This will surely work if you can't get another pc
Click to expand...
Click to collapse
I think this is the key to my problem. I checked the link you gave me and I think I might get it done using that method.
Gonna give it a try as soon as I get some free time later today.
PS : I tried all 3 usb ports on PC, ofc.
Thank you, I will keep this topic update with results.

I'm having a hard time finding the right RUU for my phone, as I don't have access to fastboot, which would make my job a lot easier.
I found a list with providers and CIDs and I suppose mine is HTC-ITA HTC__405 , since I bought it in Italy and it was unbranded.
But i can't get software version, as it asks me to go to setting/About phone . I can't do that.
I think the right RUU is RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.32.401.105_R2_Radio_11.69.3504.00U_11.22.3504, so now I'm downloading that and then move on step 4 on that tutorial.
Hope I just won't brick the phone.

doublin said:
I'm having a hard time finding the right RUU for my phone, as I don't have access to fastboot, which would make my job a lot easier.
I found a list with providers and CIDs and I suppose mine is HTC-ITA HTC__405 , since I bought it in Italy and it was unbranded.
But i can't get software version, as it asks me to go to setting/About phone . I can't do that.
I think the right RUU is RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.32.401.105_R2_Radio_11.69.3504.00U_11.22.3504, so now I'm downloading that and then move on step 4 on that tutorial.
Hope I just won't brick the phone.
Click to expand...
Click to collapse
You can flash only one particluar ruu. Just make sure it's pyramid le(sensation xe). You will not be able to flash a wrong one, so no need to worry.

Far_SighT said:
You can flash only one particluar ruu. Just make sure it's pyramid le(sensation xe). You will not be able to flash a wrong one, so no need to worry.
Click to expand...
Click to collapse
Yea I'm downloading right now RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.32.401.105_R2_Radio_11.69.3504.00U_11.22.3504
Says LE, so I should be fine.

Hi,
The RUU process will not work if the phone says "Unlocked"
You will need to relock the phone,according to the section 3 of the guide.
So,you will need a PC

did you check also if the bootloader screen says fastboot usb?

malybru said:
Hi,
The RUU process will not work if the phone says "Unlocked"
You will need to relock the phone,according to the section 3 of the guide.
So,you will need a PC
Click to expand...
Click to collapse
OOps, forgot that step (I flash ruu via ruu.exe)

malybru said:
Hi,
The RUU process will not work if the phone says "Unlocked"
You will need to relock the phone,according to the section 3 of the guide.
So,you will need a PC
Click to expand...
Click to collapse
But I'm gonna do the step 4 which says only to execute the RUU .exe but don't do anything, and in the temp folder on my pc I will find a file which then I'll have to move to the SD Card and flash straight from my recovery.
rzr86 said:
did you check also if the bootloader screen says fastboot usb?
Click to expand...
Click to collapse
When I vol down & power to get in bootloader I see :
FASTBOOT
RECOVERY
FACTORY RESET
SIM LOCK
IMAGE CRC
I don't know about fastboot usb...
Anyway, selecting FASTBOOT and connecting my phone to PC, nothing shows up, and running fastboot commands doesn't work, there's no link between pc and phone.

doublin said:
But I'm gonna do the step 4 which says only to execute the RUU .exe but don't do anything, and in the temp folder on my pc I will find a file which then I'll have to move to the SD Card and flash straight from my recovery.
When I vol down & power to get in bootloader I see :
FASTBOOT
RECOVERY
FACTORY RESET
SIM LOCK
IMAGE CRC
I don't know about fastboot usb...
Anyway, selecting FASTBOOT and connecting my phone to PC, nothing shows up, and running fastboot commands doesn't work, there's no link between pc and phone.
Click to expand...
Click to collapse
when you select fastboot does it say after that fastboot usb in bootloader screen?
actually have you enabled usb debugging mode from tettings?