Database Info

[RUU]RUU_SuperSonic_GB_Sprint_WWE_4.54.651.1_Radio_2.15 .00.0808_NV_2.15

Here the latest shipped RUU for SuperSonic
http://www.filefactory.com/file/cfe....15.00.0808_NV_2.15_release_220182_signed.exe
Enjoy!

As always, thanks
Sent from my PC36100 using xda premium

Nice! But just curious. How do you use this? Of all the things I know about rooting and whatnot this is the only thing I'm stumped on...
Sent from my PC36100 using XDA App

You run it on your pc. It returns your phone to stock
We're comin from a pure power source.

Football said:
Here the latest shipped RUU for SuperSonic
http://www.filefactory.com/file/cfe....15.00.0808_NV_2.15_release_220182_signed.exe
Enjoy!
Click to expand...
Click to collapse
Thank you Sir!

as always, thank you!!

exactly what I needed for my newly purchased evo 4G, big thanks!

I keep getting Error 170 when trying to run this... Running Win7 x64. Is there anything special I need to do to get this to work?

Drakhar said:
I keep getting Error 170 when trying to run this... Running Win7 x64. Is there anything special I need to do to get this to work?
Click to expand...
Click to collapse
That's what I am wondering. Every other RUU he uploaded were zip files that you just flashed through HBoot & this one is a exe file. How do you use this? This is a non-Rooted Rom right?

Drakhar said:
I keep getting Error 170 when trying to run this... Running Win7 x64. Is there anything special I need to do to get this to work?
Click to expand...
Click to collapse
Don't know exactly where you coming from and going to, 4.53 to 4.54? But something and that has been working and continued for me.
This ruu.exe is ran from the PC through usb debugging enabled, and having the correct drivers installed, I am on xp so I ran latest drivers maually, for higher o/s ver. its going to regonized the android and try to install autmatically....press stop/cancel you will need to configure it manually to have it install the correct drivers.
assuming you done this already, then enable settings>applic>develop>usb-deb and device powered on to home screen, from pc just double click the .exe and go through simple menu's and continue to process.
good luck and hope it helps..
latest Drivers
RUU4.54

Thank football!!!!

Anybody checked if stagefright libs were updated by HTC?

I have a custom slash screen on my EVO, will this put back on the oem Sprint one back on it? I just bought a E3D and am selling my EVO.

doeboy1984 said:
I have a custom slash screen on my EVO, will this put back on the oem Sprint one back on it? I just bought a E3D and am selling my EVO.
Click to expand...
Click to collapse
it should!!!

brad
my dilemma is that I have a rooted evo running a synergy rom on Hboot .79 and Radio 1.39
thing is that the s status is S-ON on this particular phone and unrevoked forever does not work on that radio version.
I've tried to upgrade the radio through clockwork recovery with the prepackaged zip yet when I reboot the phone still shows the old radio version.
I've tried installing an RUU from the PC but they all error out.
I'm looking for an RUU packaged in an install-able .zip that includes updated Radios Kernels Hboot and ROM in one. Is that even possible so i can fix this phone and get it some updated radios?!

brad560 said:
it should!!!
Click to expand...
Click to collapse
So I know you say it "should" but I don't want to RUU and then still have my batman logo as my splash screen, that would suck. I would ave to re-root it to try and find a splash .img, but I guess I will try it out and see if it works.

skunkd said:
brad
my dilemma is that I have a rooted evo running a synergy rom on Hboot .79 and Radio 1.39
thing is that the s status is S-ON on this particular phone and unrevoked forever does not work on that radio version.
I've tried to upgrade the radio through clockwork recovery with the prepackaged zip yet when I reboot the phone still shows the old radio version.
I've tried installing an RUU from the PC but they all error out.
I'm looking for an RUU packaged in an install-able .zip that includes updated Radios Kernels Hboot and ROM in one. Is that even possible so i can fix this phone and get it some updated radios?!
Click to expand...
Click to collapse
just saw you replied to me, sorry for the lateness. first of all, i would try aman ra for recovery, as many users have had problems with clockwork. as far as the ruu, how can you be s-on and still be rooted?

brad560 said:
just saw you replied to me, sorry for the lateness. first of all, i would try aman ra for recovery, as many users have had problems with clockwork. as far as the ruu, how can you be s-on and still be rooted?
Click to expand...
Click to collapse
I have the opposite issue. I have S-OFF (Revolutionary) but on stock unrooted (brought the phone to Sprint for a broken power button, and they ended up not fixing it, but flashed 4.53 stock rooted).
How the hell do I get this ROM rooted since Revolutionary doesn't want to root it because the bootloader is unlocked and I can't go to recovery because once I'm on the HTC white background fastboot screen, the volume button are locked and my power button is dead anyway...
I'm trying this Ruu .exe hoping it will give me S-ON but I'm doubtful it will happen...
EDIT: Just as I thought, I'm now on stock rooted 4.54 with S-OFF. And no power button

doeboy1984 said:
So I know you say it "should" but I don't want to RUU and then still have my batman logo as my splash screen, that would suck. I would ave to re-root it to try and find a splash .img, but I guess I will try it out and see if it works.
Click to expand...
Click to collapse
They will always update the splash screen, it helps to identify the firmware and rom versions at a glance. During install the setup program will create a temp folder with PC36IMG.zip or update.zip look in this zip file and you should see a splash.img file or something like that (sorry haven't looked HTC updates since my Hero Days).
Sent from my PC36100 using xda premium

Any way to get this to be able to install through the bootloader because my usb port is broken on my phone and it won't stay connected to the computer and I need to get Unrooted, s-off, return to stock, stock hboot because I need to take my phone to Sprint to get phone replaced/fixed. Thanks.
Sent from my PC36100 using xda premium

[Q] Trouble installing most roms

Hi guys. Loving the forums - I've been a watcher for a while, but have only just joined.
I'm having trouble installing most ROMs. They all hang at the opening screen, or continually reboot depending on which one it is. I've tried flashing boot.img with no success. I've had luck with Stuart's ROM, but was really hoping to find a stable ROM with Jelly Bean.
I've read through the noob guides and FAQs, done a heap of searches but can't find the answer, yet I'm sure I'm not the first with this issue. It looks like this guy was having the same problems, but he posted in the wrong area and I can't find a follow up...
I've rooted and unlocked all ok, can access bootloader and TWRP without any issues.
Does anyone know what I could be doing wrong? Or know where this has been answered before? Thanks a mil.

http://forum.xda-developers.com/showthread.php?p=33303798
This is in the q&a stickies. See if this helps.
Sent from my One X using xda premium

itscoby said:
Hi guys. Loving the forums - I've been a watcher for a while, but have only just joined.
I'm having trouble installing most ROMs. They all hang at the opening screen, or continually reboot depending on which one it is. I've tried flashing boot.img with no success. I've had luck with Stuart's ROM, but was really hoping to find a stable ROM with Jelly Bean.
I've read through the noob guides and FAQs, done a heap of searches but can't find the answer, yet I'm sure I'm not the first with this issue. It looks like this guy was having the same problems, but he posted in the wrong area and I can't find a follow up...
I've rooted and unlocked all ok, can access bootloader and TWRP without any issues.
Does anyone know what I could be doing wrong? Or know where this has been answered before? Thanks a mil.
Click to expand...
Click to collapse
Give the members here more details. What exactly interests you in JB ROMS? What have you been trying to flash? What are you on right now?
If you wish to have a great Rom with no nonsense I'd suggest to you ViperXL. It's foolproof. I too asked questions after tons of research and tutorials. Asking questions is better than banging your head. And of course stick to this this forum for ROMS and you'll avoid a cool looking paperweight.
Jon
Sent from my HTC One XL using xda premium

subarudroid said:
http://forum.xda-developers.com/showthread.php?p=33303798
This is in the q&a stickies. See if this helps.
Click to expand...
Click to collapse
Thanks! I'd read through this one and had tried flashing the boot.img as it suggests for those experiencing my problem. Unfortunately it made no difference. It's a helpful guide though - unfortunately it came after I'd worked it all out for myself from other forums and posts!
ToxicWaste said:
What exactly interests you in JB ROMS? What have you been trying to flash? What are you on right now?
Click to expand...
Click to collapse
Thanks Jon. I'm after Jelly Bean primarily to check out Google Now. I head up digital customer experience for a big Aussie company and am interested to see how it might help our customers (READ: Really I want to know how it can help me!)
I was on a rooted stock Telstra ROM but couldn't get the OTA JB update to work. I tried ViperXL 3.0.0, CyanogenMOD 10 and Tachi91's v2.1 MOD. ViperXL is what I want to run ideally.
Currently on Scott's CleanROM 5.1. I'm running One XL with Firmware 2.20.502.7.

By all means download Viper and flash that bad boy. Firmware 2.20 and Viper are good friends. No need to flash .img separately. While you're at it, check out some kernels in the Venom Hub.
You came to the right place for help though. Never think you can't ask a quesrion hers if you think research hasn't answered it for you.
I've been trying Google Now but it's not doing much for me. Still playing with it.
ATT HOX Premium App--Stock is fine but modded is Creative

ToxicWaste said:
By all means download Viper and flash that bad boy. Firmware 2.20 and Viper are good friends. No need to flash .img separately. While you're at it, check out some kernels in the Venom Hub.
You came to the right place for help though. Never think you can't ask a quesrion hers if you think research hasn't answered it for you.
I've been trying Google Now but it's not doing much for me. Still playing with it.
ATT HOX Premium App--Stock is fine but modded is Creative
Click to expand...
Click to collapse
regarding Viper, I just downloaded 2.4.0 and honestly don't know what to do next. Do I just move the file to the phone while it's plugged in? I rooted and unlocked last night, and installed twrp. I didn't want to start a thread about this and am having trouble finding the answer. Any help is a big thanks.

In Flames said:
regarding Viper, I just downloaded 2.4.0 and honestly don't know what to do next. Do I just move the file to the phone while it's plugged in? I rooted and unlocked last night, and installed twrp. I didn't want to start a thread about this and am having trouble finding the answer. Any help is a big thanks.
Click to expand...
Click to collapse
First and foremost, go into recovery (twrp) and make a backup. The backup is just that, a backup in case something goes wrong.
Now that you have a backup, plug your phone into you pc (assuming that's what you have) and select your phone to be mounted as storage.
Next, open your file location for your phone.
Next, locate Viper Rom.
Now, copy Viper (just drag and drop) it into your phones sd card.
Ok. Now you should copy your backup you made in twrp previously. Now you have it backed up in two locations.
Let's get started:
Boot into recovery (twrp).
Select Wipe and do the next 4 steps INSIDE twrp!
Now wipe dalvick cache.
Now wipe cache.
Now wipe system.
Now do a factory reset.
Now Select Install in twrp.
Find your Viper folder zip.
Select it.
Swipe to flash!
Follow Aroma Installer options to your liking.
Please be patient as it takes a while. Also, when it first boots it takes a while.
Any more questions, just ask us
ATT HOX Premium App--Stock is fine but modded is Creative

Thanks a lot. Installing now.:good:

In Flames said:
Thanks a lot. Installing now.:good:
Click to expand...
Click to collapse
No prob, man. Let us know how it went.
ATT HOX Premium App--Stock is fine but modded is Creative

Install was flawless, only bad thing is I have to work and can't toy with it for 8 more hours Thanks again!

In Flames said:
Install was flawless, only bad thing is I have to work and can't toy with it for 8 more hours Thanks again!
Click to expand...
Click to collapse
That sucks but it will be fun to learn about all the tweaks and such. I would go back to the Venom thread and flash the 2.4.0-->::2.4.1 update. I did the ota reset file too. Same thing you did before by wiping but you don't do or need a factory reset. Just flash those files in twrp. All up to date then.
ATT HOX Premium App--Stock is fine but modded is Creative

ToxicWaste said:
By all means download Viper and flash that bad boy. Firmware 2.20 and Viper are good friends. No need to flash .img separately. While you're at it, check out some kernels in the Venom Hub.
Click to expand...
Click to collapse
Hmm. Viper 3.0.0 really did not work and I followed the instructions closely. Perhaps I will try Viper 2.4.0 and then, if successful, look at updating my kernel, and then updating to 3.0.0? Current kernel is 3.0.8-01558-g7f75e5b Could this be causing me problems?

itscoby said:
Hmm. Viper 3.0.0 really did not work and I followed the instructions closely. Perhaps I will try Viper 2.4.0 and then, if successful, look at updating my kernel, and then updating to 3.0.0? Current kernel is 3.0.8-01558-g7f75e5b Could this be causing me problems?
Click to expand...
Click to collapse
Before you started to install Viper 3.0.0, what we're you on?
Sure, if let's say you had-Viper 2.4.0 but wishing to go to 3.0.0, THEN you need to flash the boot img separate since its a JB Rom.
The directions I provided are fool proof and the other user had success. So I'm wondering what you started out on before you loaded the Rom.
--------------------
Also, Viper and CleanRom are identical in the fact you DON'T need to extract the boot.img from the Rom zip as long as its under 3.0.0 (if flashing Viper). It's basically pointing twrp to the Viper zip and swiping to goodness.
ATT HOX Premium App--Stock is fine but modded is Creative

ToxicWaste said:
Before you started to install Viper 3.0.0, what we're you on?
Sure, if let's say you had-Viper 2.4.0 but wishing to go to 3.0.0, THEN you need to flash the boot img separate since its a JB Rom.
The directions I provided are fool proof and the other user had success. So I'm wondering what you started out on before you loaded the Rom.
Click to expand...
Click to collapse
So I've finally had success! Installed both 3.0.0 and 2.4.1 - I realised that I was much better off on 2.4.1 with all the venom tweaks than on 3.0.0 for seemingly not much more OS-wise, especially since I want to bypass my corporate exchange security policy, and Google Now was available as a mod.
Turns out I was trying to install on top of ROMs that wouldn't boot, and when I was trying to install from working ROMs, I wouldn't think to go back in to make sure debugging was on and fast boot was off.
The key things I've learned (which I initially missed in my initial scan of pages and pages of forum posts):
You need to install from a stable ROM that will let you boot into it
...because having a stable ROM will allow you to make sure the fast boot setting in the Power settings is off and USB debugging is on in Developer tools
You may need to flash boot.img if you're running bootloader 1.13 or above - even if the ROM installer instructs you not to
boot.img must be flashed before the installation, not after
They might sound obvious now, but this might hopefully help anyone else in my situation.
Thanks for all your help guys!
PS - LOVING Viper.

itscoby said:
So I've finally had success! Installed both 3.0.0 and 2.4.1 - I realised that I was much better off on 2.4.1 with all the venom tweaks than on 3.0.0 for seemingly not much more OS-wise, especially since I want to bypass my corporate exchange security policy, and Google Now was available as a mod.
Turns out I was trying to install on top of ROMs that wouldn't boot, and when I was trying to install from working ROMs, I wouldn't think to go back in to make sure debugging was on and fast boot was off.
The key things I've learned (which I initially missed in my initial scan of pages and pages of forum posts):
You need to install from a stable ROM that will let you boot into it
...because having a stable ROM will allow you to make sure the fast boot setting in the Power settings is off and USB debugging is on in Developer tools
You may need to flash boot.img if you're running bootloader 1.13 or above - even if the ROM installer instructs you not to
boot.img must be flashed before the installation, not after
They might sound obvious now, but this might hopefully help anyone else in my situation.
Thanks for all your help guys!
PS - LOVING Viper.
Click to expand...
Click to collapse
Good to hear you got it up and running. Viper was recommended to me and man once I played with it and tweaked it I'm having a hard time wanting to flash anything else. If I do its going to be 3.0.0. The tweaks and ElementalX kernel are just unreal.
P.S. Hitting the Thanks button is a good way to show your appreciation.
Sent from my HTC One XL using xda premium

[Q] No OS Installed - 3.18 Unlocked S=On

Followed the steps in Hassoon's toolkit, installed recovery, sideloaded CM, and now I have no OS. I can still access fastboot and recovery, see attached image for more info. Any more information needed, please let me know. This is pretty frustrating, no wonder I like Nexus devices.
(sorry for double posting, I also put this in Hassoon's thread, but felt it'd be more appropriate to post here)

first man... you'll only be able to use sense roms most likely, as the newer aosp roms dont mix with the upgraded touchscreen on the 3.18 firmware. so you can head to the original dev section to find the "downgrade touchscreen" thread to use aosp...
second, you have to fastboot flash the boot.img of every rom because the newer hboots dont allow it. easy solution to that is to go to original dev section and follow the s-off thread. if you can s-off you can say bye bye to fastboot for the most part

Also, you need to S-OFF to downgrade touchscreen firmware.
But yeah, if you can get into recovery just wipe everything and flash a rom.. (has to be sense until you s-off and downgrade touchscreen firmware)

exad said:
Also, you need to S-OFF to downgrade touchscreen firmware.
But yeah, if you can get into recovery just wipe everything and flash a rom.. (has to be sense until you s-off and downgrade touchscreen firmware)
Click to expand...
Click to collapse
Never thought I had to pull the boot image out, flash that through fastboot, THEN install the OS. Thanks for the help guys, I tested it out with the copy of CM I had (unofficial port on the threads) and sure enough, it booted up fine. Of course, as stated previously, I can't click anything b/c of the upgraded touchscreen, so I'm omw to flashing a sense rom and getting s-off and a downgraded touch screen. Thanks for the help guys!

Dolfan058 said:
Never thought I had to pull the boot image out, flash that through fastboot, THEN install the OS. Thanks for the help guys, I tested it out with the copy of CM I had (unofficial port on the threads) and sure enough, it booted up fine. Of course, as stated previously, I can't click anything b/c of the upgraded touchscreen, so I'm omw to flashing a sense rom and getting s-off and a downgraded touch screen. Thanks for the help guys!
Click to expand...
Click to collapse
Yea man its a pain to get everything going. But once you s-off, downgrade etc this phone really flies on aosp. There's also an (optional) thread in development section to rid the splash screen of the red text. Its a simple 3 step process that should only take 20 seconds. After that you're golden
Sent from my One X using Tapatalk 2

InflatedTitan said:
Yea man its a pain to get everything going. But once you s-off, downgrade etc this phone really flies on aosp. There's also an (optional) thread in development section to rid the splash screen of the red text. Its a simple 3 step process that should only take 20 seconds. After that you're golden
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I'll bet. Getting S-off to work is killing me though. Keep running into the 99 unknown error while flashing the RUU file. I've done complete wipes, made sure i have superCID, and still no luck. So close and yet so far...

Dolfan058 said:
I'll bet. Getting S-off to work is killing me though. Keep running into the 99 unknown error while flashing the RUU file. I've done complete wipes, made sure i have superCID, and still no luck. So close and yet so far...
Click to expand...
Click to collapse
are you using a sense rom or aosp?
you need to be on a sense rom since your hboot is 2.14 because aosp requires you change a setting to allow you to soff which you cant since the touchscreen doesnt work.
if you are already on a sense rom. simulate a battery pull by pressing and holding power on your phone till the capacative buttons blink a bunch of times and then it shuts off. then try again.

Dolfan058 said:
I'll bet. Getting S-off to work is killing me though. Keep running into the 99 unknown error while flashing the RUU file. I've done complete wipes, made sure i have superCID, and still no luck. So close and yet so far...
Click to expand...
Click to collapse
I feel bad, I see all these people having trouble getting s-off to work, and I did it today without any hassles at all.
Sent from my Evita using XDA Premium

exad said:
are you using a sense rom or aosp?
you need to be on a sense rom since your hboot is 2.14 because aosp requires you change a setting to allow you to soff which you cant since the touchscreen doesnt work.
if you are already on a sense rom. simulate a battery pull by pressing and holding power on your phone till the capacative buttons blink a bunch of times and then it shuts off. then try again.
Click to expand...
Click to collapse
Definitely a sense rom (http://forum.xda-developers.com/showthread.php?t=1868236), still trying to work through it. It's so annoying, I'm dying to get the unofficial CM build on here already.

Dolfan058 said:
Definitely a sense rom (http://forum.xda-developers.com/showthread.php?t=1868236), still trying to work through it. It's so annoying, I'm dying to get the unofficial CM build on here already.
Click to expand...
Click to collapse
if a simulated battery pull isnt working for you, you can paste your cmd prompt window in here and i can check if anything weird is going on.
usually it should work by the third try or so if not after the first simulated battery pull.

[Q] AT&T HTC One X Soft Brick. Tried everything I could find. Suggestions?

So my AT&T HTC One X is bootloader unlocked, super CID and was rooted. I installed a copy of Viper XL 4.2.0 that had issues with the radio turning off so I thought I'd try Maximus HD. I flashed the boot.img and went to install the rom only to find that the rom was for the international version of the HTC One X only (this was conveniently overlooked in the thread). I backed out of installation, went to restore with my TWRP backup and it had been deleted. I reinstalled the Viper XL rom and my phone booted up to the HTC developers screen (red text) and went black. This now happens every time I try to boot the phone up.
I have access to fastboot and clockwork recovery. I can't get ADB to work as I don't have access to enable USB debugging. I have flashed a few roms since with their respective boot.img to no avail. The phone still just boots to the HTC screen and blacks out.
I don't have S-off and, from my research, I can't get it without ADB so I can't RUU and return to stock without bricking (apparently). I've been at this for about a month and this soft brick is starting to look a whole lot like a hard brick.
Any suggestions, or am I out of business?
Thanks in advance!

roycedavies said:
So my AT&T HTC One X is bootloader unlocked, super CID and was rooted. I installed a copy of Viper XL 4.2.0 that had issues with the radio turning off so I thought I'd try Maximus HD. I flashed the boot.img and went to install the rom only to find that the rom was for the international version of the HTC One X only (this was conveniently overlooked in the thread). I backed out of installation, went to restore with my TWRP backup and it had been deleted. I reinstalled the Viper XL rom and my phone booted up to the HTC developers screen (red text) and went black. This now happens every time I try to boot the phone up.
I have access to fastboot and clockwork recovery. I can't get ADB to work as I don't have access to enable USB debugging. I have flashed a few roms since with their respective boot.img to no avail. The phone still just boots to the HTC screen and blacks out.
I don't have S-off and, from my research, I can't get it without ADB so I can't RUU and return to stock without bricking (apparently). I've been at this for about a month and this soft brick is starting to look a whole lot like a hard brick.
Any suggestions, or am I out of business?
Thanks in advance!
Click to expand...
Click to collapse
Not sure if I can help you much but I did notice an important clue by what you said. It looks like you flashed the boot.img before flashing the Rom. This is backwards. You are supposed to flash the Rom first and then the boot.img. If you are not S-Off this will indeed cause problems. If you are still able and have the files on the phone, try flashing in that order and see if that clears it up. Oh and P.S. I'm sure you already are kicking yourself but yes, stick to Roms made for our phone in this forum.
Just noticed something else:
you said you had access to fastboot? Connect the phone and open a CMD prompt, navigate to your ADB/Fastboot folder (Where ever you keep your adb/fastboot tools) and then type "fastboot devices" to see if your computer is talking to your phone. If it is, you said you can flash Viper. you will just need to unzip the Viper zip and get the boot.img. Put that file in your ADB/Fastboot folder. open a CMD prompt again and navigate once again to you ADB/Fastboot folder, then type "fastboot flash boot boot.img and that should get you back on the road.
This is assuming you have a folder with the required ADB/Fastboot resources (if you don't I recommend you learn how) and knowledge on how to navigate to that folder with DOS commands.

roycedavies said:
So my AT&T HTC One X is bootloader unlocked, super CID and was rooted. I installed a copy of Viper XL 4.2.0 that had issues with the radio turning off so I thought I'd try Maximus HD. I flashed the boot.img and went to install the rom only to find that the rom was for the international version of the HTC One X only (this was conveniently overlooked in the thread). I backed out of installation, went to restore with my TWRP backup and it had been deleted. I reinstalled the Viper XL rom and my phone booted up to the HTC developers screen (red text) and went black. This now happens every time I try to boot the phone up.
I have access to fastboot and clockwork recovery. I can't get ADB to work as I don't have access to enable USB debugging. I have flashed a few roms since with their respective boot.img to no avail. The phone still just boots to the HTC screen and blacks out.
I don't have S-off and, from my research, I can't get it without ADB so I can't RUU and return to stock without bricking (apparently). I've been at this for about a month and this soft brick is starting to look a whole lot like a hard brick.
Any suggestions, or am I out of business?
Thanks in advance!
Click to expand...
Click to collapse
You said you flashed the boot.img from Maximus before flashing the ROM (which is ok, the previous member is incorrect in saying that it must be afterwards, it can be either), but did you flash the boot.img from the Viper XL ROM when you flashed that? If not your phone is trying to boot Viper while the Maximus boot.img is still installed, obviously this won't work.
One thing. The fact that Maximus ROM is only for the Endeavoru wasn't "conveniently overlooked" as you sarcastically put it. You were in the wrong forum. The ROM itself is in the Endeavoru forum and you have the Evita so you shouldn't be in the Endeavoru forum in the first place. The ROM is in the correct forum, it doesn't need to be labelled "Endeavoru only" because the user should be aware of which device they have and be aware of which forum they are in. The fact that you're bouncing around both forums is a bit of a worry. You have no reason to be in that forum.
Our forum is here:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Our two development sections are here:
http://forum.xda-developers.com/forumdisplay.php?f=1541
http://forum.xda-developers.com/forumdisplay.php?f=1726
Stay within our device forum, you don't ever need to be anywhere else. You're pretty lucky you haven't actually bricked your phone by flashing that ROM. By the way, there's no such thing as a soft brick. A brick is when your phone will not power on at all. It's either bricked or it isn't.
Sent from my Evita

timmaaa said:
You said you flashed the boot.img from Maximus before flashing the ROM (which is ok, the previous member is incorrect in saying that it must be afterwards, it can be either), but did you flash the boot.img from the Viper XL ROM when you flashed that? If not your phone is trying to boot Viper while the Maximus boot.img is still installed, obviously this won't work.
One thing. The fact that Maximus ROM is only for the Endeavoru wasn't "conveniently overlooked" as you sarcastically put it. You were in the wrong forum. The ROM itself is in the Endeavoru forum and you have the Evita so you shouldn't be in the Endeavoru forum in the first place. The ROM is in the correct forum, it doesn't need to be labelled "Endeavoru only" because the user should be aware of which device they have and be aware of which forum they are in. The fact that you're bouncing around both forums is a bit of a worry. You have no reason to be in that forum.
Our forum is here:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Our two development sections are here:
http://forum.xda-developers.com/forumdisplay.php?f=1541
http://forum.xda-developers.com/forumdisplay.php?f=1726
Stay within our device forum, you don't ever need to be anywhere else. You're pretty lucky you haven't actually bricked your phone by flashing that ROM. By the way, there's no such thing as a soft brick. A brick is when your phone will not power on at all. It's either bricked or it isn't.
Click to expand...
Click to collapse
Thanks for the reply. I believe the reason I'm not bricked is because I backed out of the installation of Maximus HD during the setup screen progression. The actual ROM was never flashed. However, I have flashed the boot.img and ROMs for Viper, Xylon, and Cyanogenmod with no success. The result is the same every time (HTC screen, then black). I extract the boot.img from each of the roms, flash it, and then flash the ROM. The ROM I flash is a copy of the the original with the boot.img still inside. Perhaps I should be removing the boot.img if I am going to flash it separately in fastboot? And I realize that the threads are specific for certain phones now. It's all kind of a mess to get into at first.

I understanding that it can be a bit confusing at first, especially with the phones betting similarly named. But you know now so you shouldn't have this problem again. I believe you will probably need to run an RUU to get out of this mess, but I'll need to see your bootloader details first, just the first five lines.
Sent from my Evita

Madcat8686 said:
Not sure if I can help you much but I did notice an important clue by what you said. It looks like you flashed the boot.img before flashing the Rom. This is backwards. You are supposed to flash the Rom first and then the boot.img. If you are not S-Off this will indeed cause problems. If you are still able and have the files on the phone, try flashing in that order and see if that clears it up. Oh and P.S. I'm sure you already are kicking yourself but yes, stick to Roms made for our phone in this forum.
Just noticed something else:
you said you had access to fastboot? Connect the phone and open a CMD prompt, navigate to your ADB/Fastboot folder (Where ever you keep your adb/fastboot tools) and then type "fastboot devices" to see if your computer is talking to your phone. If it is, you said you can flash Viper. you will just need to unzip the Viper zip and get the boot.img. Put that file in your ADB/Fastboot folder. open a CMD prompt again and navigate once again to you ADB/Fastboot folder, then type "fastboot flash boot boot.img and that should get you back on the road.
This is assuming you have a folder with the required ADB/Fastboot resources (if you don't I recommend you learn how) and knowledge on how to navigate to that folder with DOS commands.
Click to expand...
Click to collapse
Dude, you are a golden-freaking genius. Your suggestion to flash the boot.img second did the trick! I'm currently running Uxylon! Hopefully things continue to work. Thank you, thank you, thank you.

Oh, that's great. Usually it shouldn't matter which order you flash in, but at least it got you out of trouble this time.
Sent from my Evita

roycedavies said:
Dude, you are a golden-freaking genius. Your suggestion to flash the boot.img second did the trick! I'm currently running Uxylon! Hopefully things continue to work. Thank you, thank you, thank you.
Click to expand...
Click to collapse
Actually I can't take credit for this. Timmaaa pointed out something I didn't know. You can flash them in either order (mind blown!) I've only see it one way. I learn a ton every day. @timmaaa pointed out you had the Maximus boot.img loaded. I think you just flashed over it and now you have the correct boot.img for the Rom you are running. Glad everything worked out for you and I learned something in the process too. Cheers!

Madcat8686 said:
Actually I can't take credit for this. Timmaaa pointed out something I didn't know. You can flash them in either order (mind blown!) I've only see it one way. I learn a ton every day. @timmaaa pointed out you had the Maximus boot.img loaded. I think you just flashed over it and now you have the correct boot.img for the Rom you are running. Glad everything worked out for you and I learned something in the process too. Cheers!
Click to expand...
Click to collapse
Hey, you should take the credit, I believe flashing it afterwards was what got his phone booted :thumbup:
Sent from my Evita

Madcat8686 said:
Actually I can't take credit for this. Timmaaa pointed out something I didn't know. You can flash them in either order (mind blown!) I've only see it one way. I learn a ton every day. @timmaaa pointed out you had the Maximus boot.img loaded. I think you just flashed over it and now you have the correct boot.img for the Rom you are running. Glad everything worked out for you and I learned something in the process too. Cheers!
Click to expand...
Click to collapse
thanks again for your help and this might be a total shot in the dark but I am still having the boot to black issue after installing uxylon. the room is running well enough (4g won't turn on but one problem at a time) but every time I turn the phone off or rent I have to get into fastboot and flash the boot.img to get the phone on again. is that normal? the only other ROM I have ever had working is viper but I haven't seen any indication that having to use fastboot to turn the phone on every time is normal. is there a way to fix this possibly?

timmaaa said:
I understanding that it can be a bit confusing at first, especially with the phones betting similarly named. But you know now so you shouldn't have this problem again. I believe you will probably need to run an RUU to get out of this mess, but I'll need to see your bootloader details first, just the first five lines.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply! I will get the bootloader info ASAP bit don't I need to be s-of in order to RUU? from what I've read, if you don't have unlocked bootloader, root access, and s-off, you'll end up bricking your phone with RUU. I'd really like to do it but I have tried to get s-off to no avail.

No, that isn't normal at all, there's definitely something screwy there. I think you're gonna need to run an RUU, so you'll need to get s-off. Try this:
Http://Rumrunner.us
Sent from my Evita

roycedavies said:
thanks again for your help and this might be a total shot in the dark but I am still having the boot to black issue after installing uxylon. the room is running well enough (4g won't turn on but one problem at a time) but every time I turn the phone off or rent I have to get into fastboot and flash the boot.img to get the phone on again. is that normal? the only other ROM I have ever had working is viper but I haven't seen any indication that having to use fastboot to turn the phone on every time is normal. is there a way to fix this possibly?
Click to expand...
Click to collapse
Definitely not normal. A few recommendations:
1. Back up all your stuff, wipe everything except the SD card, Flash a fresh copy of the Rom, Flash the boot.img (you really should consider S-Off), Wipe the cache and DALVIK cache one more time, boot up the system.
2. Same as above except choose another Rom. There are plenty to choose from. The 4.4 Roms are getting a lot better now that the new Kernel fix got rid of the boot loops/reboots.
Sorry about the delay, it's been a heavy week at work. Hope things work out for you.

I don't think flashing another ROM is going to fix the problem at hand. There's very possibly something much deeper wrong here, which a ROM flash won't fix. I honestly think it's better to run an RUU which will bring everything back to the way it's meant to be and the user can start with a blank slate.
Sent from my One XL using XDA Premium 4 mobile app

timmaaa said:
No, that isn't normal at all, there's definitely something screwy there. I think you're gonna need to run an RUU, so you'll need to get s-off. Try this:
Http://Rumrunner.us
Sent from my Evita
Click to expand...
Click to collapse
Sometimes is pays to see if there is a page 2 to the thread...Sorry about that! lol
---------- Post added at 08:48 PM ---------- Previous post was at 08:45 PM ----------
timmaaa said:
I don't think flashing another ROM is going to fix the problem at hand. There's very possibly something much deeper wrong here, which a ROM flash won't fix. I honestly think it's better to run an RUU which will bring everything back to the way it's meant to be and the user can start with a blank slate.
Sent from my One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You have no idea how much I have vicariously learned from your posts. Thanks Timmaa! I keep thinking if more of these folks would go ahead and get S-Off they would have waaaaaaaaaay less issues.

Flashing another ROM could be worth a try, but the fact that the boot.img seems to be disappearing whenever the screen is off suggest something has gone wrong at a lower level.
I'm glad to help, I'm still learning something new just about every day too from XDA.
Sent from my One XL using XDA Premium 4 mobile app

timmaaa said:
Flashing another ROM could be worth a try, but the fact that the boot.img seems to be disappearing whenever the screen is off suggest something has gone wrong at a lower level.
I'm glad to help, I'm still learning something new just about every day too from XDA.
Sent from my One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I totally agree now because after rereading the post, there is a radio issue in addition to the boot issue. Is it possible that the Endeverou boot.img messed something up?

Yeah, that's exactly what I'm thinking. An RUU will hopefully fix that right up.
Sent from my Evita.

timmaaa said:
No, that isn't normal at all, there's definitely something screwy there. I think you're gonna need to run an RUU, so you'll need to get s-off. Try this:
Http://Rumrunner.us
Sent from my Evita
Click to expand...
Click to collapse
That sounds like a good plan. (I'm really appreciating all your input by the way! Thanks so much!) One question though, upon checking out the rumrunner website, there isn't specific mention of the HTC One X Evita. Call me paranoid, but after what I've been through I want to make 100% sure I'm compatible before moving forward. Have you or anyone used this specific method for S-Off on the One X Evita?

For the Evita you use the universal HTC method. I've created a thread for it if you want to make sure it's worked for other Evita owners.
http://forum.xda-developers.com/showthread.php?t=2540232
Sent from my Evita.

[Q&A] [ROM][JB][11.07] Team Venom presents: ViperOne S 3.2.1 - Welcome to the future

[Q&A] [ROM][JB][11.07] Team Venom presents: ViperOne S 3.2.1 - Welcome to the future
Q&A for [ROM][JB][11.07] Team Venom presents: ViperOne S 3.2.1 - Welcome to the future
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

App Shortcuts
axbog said:
I encounter a strange thing: Some of the app shortcuts disappear from the home screen after a reboot. I can still find them in the app drawer. I drag them again on the homescreens and after a reboot they are gone again. I've tried disabling Fastboot and it didn't work. I have also tried Fix Permissions and Zip Align just in case, but with no results. Anyone else encountered this? I found various explanations on the web. Most plausible was that it has something to do with the moving of the apps to the SD. But this wasn't a problem on Viper 3.1.3. Thanks.
Click to expand...
Click to collapse
Did anyone ever have the solution to this???? as I have been experiencing the sameee problem for a while now

i upgraded to 3.2.1 and the phone reboots randomly ,
today my phone rebooted twice (the aosp lockscreen is on )

Server problem
Hi there folks. I'm really looking forward to try this one, but i'm struggling with the DL whole morning with average speed of 20 - 30 kb /s. Of course my network provider supplies me with much more than that Is there any chance that any of you could upload the full ROM on different server. I would be very gratefull.
Greetings

The greatest!!! Thanks venom team for all the effort, and spectacular results. I'm more than happy

Google tasks won't sync
Hello everyone,
I installed this rom, and it is great! The only thing that is not working properly is the HTC tasks app. It works, but it doesn't sync with my google tasks account. Any idea how to fix it?

You don;t have to flash everything.Just flash the Update and that's it.

Anyone has a fix for "Play services" battery drain ? It's wasting more than 40% of my battery life, even when i'm not using the phone.
I'm S-OFF, running 3.2.1

Battery animation stuck on 99%
The battery animation is stuck on 99%.
Is this a common problem?

I love this rom. It runs more than 4 days without charging!
Will there come a newer version? maybe on lollipop?

Nighthawk_85 said:
I love this rom. It runs more than 4 days without charging!
Will there come a newer version? maybe on lollipop?
Click to expand...
Click to collapse
Did you ever touched your phone during those 4 days?
Sent from nowhere over the air...

Viper doesn't see my carrier (T-Mobile). No data, no calls
Installed without hitch. hboot2.15.
Wifi works fine, Google Play working... but no carrier whatsoever. Help? Setup stalled during first use.
EDIT: Bootloop, reinstalling. Setup stalled after first desktop.
EDIT 2: Saw card, but screen became black w/ no apps. Installed OTA update. "Starting Apps" for 10 minutes"

senselocke said:
Installed without hitch. hboot2.15.
Wifi works fine, Google Play working... but no carrier whatsoever. Help? Setup stalled during first use.
EDIT: Bootloop, reinstalling. Setup stalled after first desktop.
EDIT 2: Saw card, but screen became black w/ no apps. Installed OTA update. "Starting Apps" for 10 minutes"
Click to expand...
Click to collapse
Did you flash radio 1.20? (Which is actually only possible of your phone is S-OFF.) There might arise some problems with this rom if you are using a different radio version.

Flippy498 said:
Did you flash radio 1.20? (Which is actually only possible of your phone is S-OFF.) There might arise some problems with this rom if you are using a different radio version.
Click to expand...
Click to collapse
No. Actually installed Viper to get S-Off because another thread stated "install another close to stock ROM like Viper" to run rumrunner and achieve S-Off:
Rapier said:
Try with rumrunner. But first flash a close to stock ROM like Viper, then use rumrunner
Click to expand...
Click to collapse
Been trying S-Off for three, four days now. Rumrunner fails, Moonshine gets to test 3 then shows dots for hours.
Windows 7 64bit
Firewall off
Avast anti-virus shields off
Windows Defender off
Fastboot and ADB installed and working
HTC Sync utterly gone (only HTC drivers installed)
HTCDev unlocked
Rooted with SuperSU,
hboot 2.15,
HTC ROM 3.14.531.17 710RD
radio 1.16.50.05.31.
Viper was the latest attempt to get S-Off, but I couldn't get it to boot, so I never tried Rumrunner with Viper on it.

senselocke said:
No. Actually installed Viper to get S-Off because another thread stated "install another close to stock ROM like Viper" to run rumrunner and achieve S-Off:
Been trying S-Off for three, four days now. Rumrunner fails, Moonshine gets to test 3 then shows dots for hours.
Windows 7 64bit
Firewall off
Avast anti-virus shields off
Windows Defender off
Fastboot and ADB installed and working
HTC Sync utterly gone (only HTC drivers installed)
HTCDev unlocked
Rooted with SuperSU,
hboot 2.15,
HTC ROM 3.14.531.17 710RD
radio 1.16.50.05.31.
Viper was the latest attempt to get S-Off, but I couldn't get it to boot, so I never tried Rumrunner with Viper on it.
Click to expand...
Click to collapse
You flashed boot.img in fastboot after you flashed Viper?
Sent from nowhere over the air...

senselocke said:
No. Actually installed Viper to get S-Off because another thread stated "install another close to stock ROM like Viper" to run rumrunner and achieve S-Off:
Been trying S-Off for three, four days now. Rumrunner fails, Moonshine gets to test 3 then shows dots for hours.
Windows 7 64bit
Firewall off
Avast anti-virus shields off
Windows Defender off
Fastboot and ADB installed and working
HTC Sync utterly gone (only HTC drivers installed)
HTCDev unlocked
Rooted with SuperSU,
hboot 2.15,
HTC ROM 3.14.531.17 710RD
radio 1.16.50.05.31.
Viper was the latest attempt to get S-Off, but I couldn't get it to boot, so I never tried Rumrunner with Viper on it.
Click to expand...
Click to collapse
If you didn't forget flashing the boot.img I would recommend using Viper 2.1 or Viper 2.2 for getting S-OFF. Those versions do not depend on conditions you do not fulfill already. Besides I know that getting S-OFF is possible with them because I had been on Viper 2.2 when I got S-OFF.

Rapier said:
You flashed boot.img in fastboot after you flashed Viper?
Click to expand...
Click to collapse
Yes sir (or ma'am), I did. And it was the matching version (boot_hboot2.15.img) for my hboot as well (I believe we talked about this in a different thread? Or another user with a ferret image).
First time I installed 3.2.0 and the OTA in order, and Viper started up, but setup crashed, and there was no cell network. I rebooted and kept getting splash/reboot/splash/reboot/etc. So I re-installed, re-flashed boot, this time 3.2.0 alone. Setup still crashed, but the SIM card appeared, but then the "desktop" went black (menu and nav bar, but no home row or icons). Installing 3.2.1 did not fix this. So I went back to a TWRP backup of stock ROM.
Flippy498 said:
If you didn't forget flashing the boot.img I would recommend using Viper 2.1 or Viper 2.2 for getting S-OFF. Those versions do not depend on conditions you do not fulfill already. Besides I know that getting S-OFF is possible with them because I had been on Viper 2.2 when I got S-OFF.
Click to expand...
Click to collapse
Okay, I will give 2.2 a shot first. Thank you both for the ongoing feedback and help.

Flippy498 said:
If you didn't forget flashing the boot.img I would recommend using Viper 2.1 or Viper 2.2 for getting S-OFF. Those versions do not depend on conditions you do not fulfill already. Besides I know that getting S-OFF is possible with them because I had been on Viper 2.2 when I got S-OFF.
Click to expand...
Click to collapse
What version of which S-off program did you use? I just ran both Moonshine and Rumrunner with Viper 2.1 and both failed--but Rumrunner got much further than before (got to "pouring (8)" before telling me to pray and try again.

senselocke said:
What version of which S-off program did you use? I just ran both Moonshine and Rumrunner with Viper 2.1 and both failed--but Rumrunner got much further than before (got to "pouring (8)" before telling me to pray and try again.
Click to expand...
Click to collapse
I used facepalm. It's said that it does not to work on hboot 2.15 but somehow I got it working. Don't know why because all I did was following the instructions since no other method existed I could try back then. Be careful if you try to use facepalm. If you do not follow the instructions carefully you may get a fancy new paperweight. Besides in difference to other methods getting SuperCID is a prerequisite (step 12 isn't needed in your case) and not just optional after you got S-OFF.

Flippy498 said:
I used facepalm. It's said that it does not to work on hboot 2.15 but somehow I got it working. Don't know why because all I did was following the instructions since no other method existed I could try back then. Be careful if you try to use facepalm. If you do not follow the instructions carefully you may get a fancy new paperweight. Besides in difference to other methods getting SuperCID is a prerequisite (step 12 isn't needed in your case) and not just optional after you got S-OFF.
Click to expand...
Click to collapse
UGH oh my GOD< got it.
Viper 2.1 > OTA to 2.2
Install SuperSU from Play Store
SuperSU uninstalled default SU program
SuperSU > Access > Default Access: Grant
SuperSU > Access > Show Notifications: Off
SuperSU > Security > Enable su during boot: On
SuperSU > System > Trust system user: On
Then, ONLY THEN, did Rumrunner grant S-Off. Thank you for the suggestions and help, peoples. I do appreciate it.