Database Info

Major problems after trying to flash JB on HTC ONE X

Hello, I just tried to install the new JB insertcoin version on my HTC One X. Something went wrong and now I am completely stuck. After having searched the internet for a few hours to avoid asking the same question two times, I decided to finally ask for help here as my case seems to be unique.
I'm currently only have access to hboot and fastboot, when I try rebooting the phone I end up in an endless bootloop just as I reach the home screen.
- I can't flash any .img files whatsoever,
- I can't access "recovery" and I promptly receive a text "security warning" just under "RELOCKED".
- when I try entering hboot mode it says "Failed to open USB Master Mode".
- I have tried flashing RUU but it says I have <30% battery, which is not true as it's nearly full.
I have no idea what I should do from here, is my phone dead or is there still hope? Thanks in advance, I really appreciate any input I can get.
Update. I realize I need to download "recovery.img" and proceed with installing a stock rom. However, when I try flashing the recovery.img it says "FAILED" in cmd.
Update2. Dowloaded the stock rom but received error 140 midway through the installation. Probably has something to do with the "FAILED" I get when using the command "fastboot flash recovery recovery.img". Any help is appreciated, my batteries are probably at 50% now....

You say it says "relocked" in hboot? That means your bootloader isn't unlocked. You're gonna have to do that before you can do anything else.
Edit: also, are you sure insertcoin is for our one X and not the international (tegra 3) version? I quick skimmed through both our development sections and didn't see it.
Sent from my One X using xda premium

stnguyen09 said:
You say it says "relocked" in hboot? That means your bootloader isn't unlocked. You're gonna have to do that before you can do anything else.
Edit: also, are you sure insertcoin is for our one X and not the international (tegra 3) version? I quick skimmed through both our development sections and didn't see it.
Sent from my One X using xda premium
Click to expand...
Click to collapse
I have the EU version, my thread was moved here dunno why. Anyway, I unlocked bootloader and it now works to use the command "fastboot flash recovery recovery.img" and when I run the corresponding RUU I receive error 155 instead of error 140. I am now stuck in an endless bootloop where the phone restarts as soon as the home screen is reached.
Edit: Is there any way I can revert the 1.28 firmware for JB? It says HBOOT-1.28.0000 in the bootloader and maybe this is what's causing problem.

I remember one having to put the new hboot on there before they flashed it. Correct if I'm wrong

Update: I installed an older (ICS) version of insert coin and it worked. I won't touch jelly bean for a while....

This thread should probably get moved to the HTC One X forum though. I would give advice but don't know anything about the HTC Endeavor.

For them to run a jelly bean sense ROM they need to flash a updated hboot.
Hopefully that won't happen to us....
Sent from my Nexus 7 using Tapatalk 2

so you might as well run the ruu then to get jb for the endeavor then flash custom roms? can u still run ics roms afterwards? hopefully they dont have to flash boot.img in fastboot.

DvineLord said:
so you might as well run the ruu then to get jb for the endeavor then flash custom roms? can u still run ics roms afterwards? hopefully they dont have to flash boot.img in fastboot.
Click to expand...
Click to collapse
They have to fastboot flash kernels regardless since their kernel partition isn't writeable in recovery
And I believe they can only run jb roms from that point on
Sent from my HTC One XL using Tapatalk 2

[Q] One X (evita) not booting CM10/10.1

I have an HTC One X sitting here that I bought from somebody. It came rooted with an unlocked bootloader running CleanRom. I downloaded CM, wiped like usual and flashed the rom. I can't get it to boot now, it endlessly shows the CM boot logo (but doesn't appear to be restarting) and I was wondering if there was anything special I had to do to get CM working.

Fastboot flash boot boot.img......
Sent from my HTC One XL using Tapatalk 2

rpomponio said:
Fastboot flash boot boot.img......
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
I take the boot.img from the zip and flash that in fastboot?

driftkidd2323 said:
I take the boot.img from the zip and flash that in fastboot?
Click to expand...
Click to collapse
Yes sir. Depending on what version your hboot is, that might be your problem..
Sent from my HTC One XL using Tapatalk 2

rpomponio said:
Yes sir. Depending on what version your hboot is, that might be your problem..
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
cm10 booted right up, thanks!

driftkidd2323 said:
cm10 booted right up, thanks!
Click to expand...
Click to collapse
Your welcome, please hit the thanks button.
Sent from my HTC One XL using Tapatalk 2

Help
rpomponio said:
Yes sir. Depending on what version your hboot is, that might be your problem..
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Hello, I as well have a HTC one X Evita the HBoot curently is 1.14.0002 Do you belive that is the problem with mine as well? If so I do know how to use Fastboot and all but do i need to Install the ROM first then Flash the boot.img over or does it mater what order.

cassidyc123 said:
Hello, I as well have a HTC one X Evita the HBoot curently is 1.14.0002 Do you belive that is the problem with mine as well? If so I do know how to use Fastboot and all but do i need to Install the ROM first then Flash the boot.img over or does it mater what order.
Click to expand...
Click to collapse
If you are on hboot 1.14, and have flashed CM10, and not the boot.img, than yes, this almost certainly your problem.
It doesn't matter whether you flash boot.img over fastboot before or after the ROM.

Whats the diffence between the boot.img found in the 10.1 zipfile for htc one x and the one linked in download :
Boot.img (secure=0): http://d-h.st/vzF
Which one should I chose?
/ D

danishdaycare said:
Whats the diffence between the boot.img found in the 10.1 zipfile for htc one x and the one linked in download :
Boot.img (secure=0): http://d-h.st/vzF
Which one should I chose?
/ D
Click to expand...
Click to collapse
um http://d-h.st/vzF is for the endeavoru so NO one here would EVER flash it. do you have an evita or an endeavoru? this forum is for the evita.

DvineLord said:
um http://d-h.st/vzF is for the endeavoru so NO one here would EVER flash it. do you have an evita or an endeavoru? this forum is for the evita.
Click to expand...
Click to collapse
I accidentally flashed my evita with an endeavoru boot.img and now it's stuck in a splash screen boot loop. Is there any way to fix this? Thanks guys.

flint24 said:
I accidentally flashed my evita with an endeavoru boot.img and now it's stuck in a splash screen boot loop. Is there any way to fix this? Thanks guys.
Click to expand...
Click to collapse
Flash the evita boot.img?

exad said:
Flash the evita boot.img?
Click to expand...
Click to collapse
Sure but which one? Any one? I found this link by Googling but I hope I'm putting the right boot on my phone. I got my One XL from Germany around November 2012.
http://forum.xda-developers.com/showthread.php?t=2119610

flint24 said:
Sure but which one? Any one? I found this link by Googling but I hope I'm putting the right boot on my phone. I got my One XL from Germany around November 2012.
http://forum.xda-developers.com/showthread.php?t=2119610
Click to expand...
Click to collapse
If you bootloader says Evita, stay here. If not, run away... far, far away and never come back.
If it is evita go to a cm10/10.1 thread, grab the correct version and pull the boot.img from it. NEVER google for anything, now that you have found this forum. That's one of the quickest ways to break your phone.

Myrder said:
If you bootloader says Evita, stay here. If not, run away... far, far away and never come back.
If it is evita go to a cm10/10.1 thread, grab the correct version and pull the boot.img from it. NEVER google for anything, now that you have found this forum. That's one of the quickest ways to break your phone.
Click to expand...
Click to collapse
Thanks. I'm downloading it now from a reeeeaaaally slow connection so it'll take time to see if this works.
Also I've unlocked my bootloader but it also says "TAMPERED." Should I be worried about that?

flint24 said:
Thanks. I'm downloading it now from a reeeeaaaally slow connection so it'll take time to see if this works.
Also I've unlocked my bootloader but it also says "TAMPERED." Should I be worried about that?
Click to expand...
Click to collapse
Tampered is an indication that you unlocked the phone. You can remove it by RUUing after S-OFF if it bothers you.

I followed Myrder's advice and loaded CM 10 for evita and it got me back into my phone but the touchscreen isn't working now

flint24 said:
I followed Myrder's advice and loaded CM 10 for evita and it got me back into my phone but the touchscreen isn't working now
Click to expand...
Click to collapse
If you have hboot 2.14 you need to downgrade your touchscreen firmware to get touchscreen working in AOSP ROMS

Sounds to me like you really need to do some reading. And really, reading should be done before attempting any of the things you're doing to your phone. You're lucky you haven't bricked it.
Sent from my Evita using XDA Premium

I'm kind of in a chicken before the egg situation. I found the files and commands needed to downgrade my touchscreen, however I think this requires the phone to have usb debugging on, which I can't select because the touchscreen doesn't work.
If that's not necessary because it's all in fastboot anyway, then I have to figure out why I'm getting a "remote 99 unknown fail" and a "status read fail too many links" error message when I try to run the commands for S-OFF and touchscreen downgrade in bootloader.

Couple Issues with UrDroid on HTC One XL 1.9

Hi everyone,
I don't quite have 10 posts yet, so I can't post in the UrDroid thread.
I had UrDroid 1.8, and it worked just fine, had some wifi issues (sometimes after turning the wifi off, it wouldn't turn on again unless I rebooted), so I upgraded to 1.9
Now I have a few issues:
It stays "connected" to a wifi network even after losing connection
Occasionally, after rebooting, my Beautiful Widgets go away and my default keyboard reverts to the stock keyboard (from swype)
occasionally I cannot turn the wifi back on after turning it off without a reboot
That's about it. If anyone has any ideas, please let me know. Thanks! :good:

Could be just bugs in the software. Recommend trying different ROMs
Sent from my Carbon-ize Evita using xda-developers app

I really wish I could try other roms, for some reason UrDroid is the only one that actually works, I have no idea why this is!
For instance, when flashing any verison of CM, after flashing and rebooting, it stays stuck on the loading screen, and doesn't go further, even after waiting a half an hour. AOKP and the others basically brick my phone. I think it has something to do with the UrDroid using Aroma Installer that seems to work well with my phone and twrp. I'm a bit of a n00b, so don't know for sure.
Was hoping someone else had these issues and could tell me how they fixed them.
Herc08 said:
Could be just bugs in the software. Recommend trying different ROMs
Sent from my Carbon-ize Evita using xda-developers app
Click to expand...
Click to collapse

What recovery are you using and version?
What hboot do you have?
Sent from my One X using xda app-developers app

Sorry for the late reply,I've had the darndest time getting into recovery since installing UrDroid 1.9!
I have HBOOT-1.14.002 and TWRP v. 2.3.1.0
Thanks for any help you could offer- I like UrDroid, but would like to try CM or the other ones!
exad said:
What recovery are you using and version?
What hboot do you have?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse

choeffe said:
Sorry for the late reply,I've had the darndest time getting into recovery since installing UrDroid 1.9!
I have HBOOT-1.14.002 and TWRP v. 2.3.1.0
Thanks for any help you could offer- I like UrDroid, but would like to try CM or the other ones!
Click to expand...
Click to collapse
Because of your hboot version you need to flash the boot.img seperately. It is possible that you are doing this but still encountering bootloops and the reason for that would be Hboot compatibility. I have noticed that some ROMs just do not play nice with certain hboots. The most compatible hboot that I've seen is 2.14 which seems to be the same accross all carrier phones.
That being said, my suggestion to you is to S-OFF if you aren't already, then, while keeping your bootloader unlocked, RUU up to 3.18 or 3.17 or whatever is the latest for your carrier which will update your hboot to 2.14 and then downgrade your touchscreen firmware which is super easy and there's a sticky for the process in the Original Android Development section.
After that, you should be able to run all roms without much issue AND you won't have to fastboot flash boot boot.img anymore.

That explains it- I literally have just been going into TWRP, installing the zip file, and then rebooting. I'm not even sure where I would find the boot.img, would that be inside the zip file?
So to S-OFF, should I follow the directions here: http://forum.xda-developers.com/showthread.php?t=2155071
I'm not sure how to RUU, any chance you or someone might have a link on instructions to do that? (I have an AT&T phone that I use on Straight Talk)
Thanks for your help, and if I'm asking for too much information, I'll keep doing some reasearch. I think the RUU is what kind of puzzles me (I'm clearly pretty green when it comes to rooting, I've only ever done it on this phone, not very successfully!
exad said:
Because of your hboot version you need to flash the boot.img seperately. It is possible that you are doing this but still encountering bootloops and the reason for that would be Hboot compatibility. I have noticed that some ROMs just do not play nice with certain hboots. The most compatible hboot that I've seen is 2.14 which seems to be the same accross all carrier phones.
That being said, my suggestion to you is to S-OFF if you aren't already, then, while keeping your bootloader unlocked, RUU up to 3.18 or 3.17 or whatever is the latest for your carrier which will update your hboot to 2.14 and then downgrade your touchscreen firmware which is super easy and there's a sticky for the process in the Original Android Development section.
After that, you should be able to run all roms without much issue AND you won't have to fastboot flash boot boot.img anymore.
Click to expand...
Click to collapse

choeffe said:
That explains it- I literally have just been going into TWRP, installing the zip file, and then rebooting. I'm not even sure where I would find the boot.img, would that be inside the zip file?
Click to expand...
Click to collapse
Yes it's in the zip. You extract it then fastboot flash boot boot.Img right before or after flashing the rom in recovery. Before flashing the rom and boot.img you should wipe cache, dalvik, system and factory reset. And only ever flash roms for the one xl or you risk bricking.
choeffe said:
So to S-OFF, should I follow the directions here: http://forum.xda-developers.com/showthread.php?t=2155071
Click to expand...
Click to collapse
Yes
choeffe said:
I'm not sure how to RUU, any chance you or someone might have a link on instructions to do that? (I have an AT&T phone that I use on Straight Talk)
Thanks for your help, and if I'm asking for too much information, I'll keep doing some reasearch. I think the RUU is what kind of puzzles me (I'm clearly pretty green when it comes to rooting, I've only ever done it on this phone, not very successfully!
Click to expand...
Click to collapse
To ruu, just download the ruu exe file and run it. But make sure you're s-off first or you'll brick.
Reading the stickies is suggested. You picked a ***** of a phone to be your first to root.
Sent from my One X using xda app-developers app

Thanks for your help thus far! I'm going to give it a try and see how it goes.
Yeah, I definitely wish I would have started with a Nexus or Sony device, but I changed from T-Mobile (worse decision of my life to go with them in the first place) to Straight Talk SIM with AT&T, and the HTC One X looked so pretty! Next phone is going to be a Nexus!
exad said:
Yes it's in the zip. You extract it then fastboot flash boot boot.Img right before or after flashing the rom in recovery. Before flashing the rom and boot.img you should wipe cache, dalvik, system and factory reset. And only ever flash roms for the one xl or you risk bricking.
Yes
To ruu, just download the ruu exe file and run it. But make sure you're s-off first or you'll brick.
Reading the stickies is suggested. You picked a ***** of a phone to be your first to root.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse

[Q] ATT htc one xl Suddenly gets stuck in boot loop after restarting phone

Hey Guys,
This is my first post, so excuse me if I sound like I don't know what I'm talking about.
a few days ago i tried to connect to my wifi at home and it was not picking it up although i was inside my own house. so i thought i should restart my phone. well after trying to restart it it got stuck in a boot loop. it would load the htc screen then start loading the venom logo then it shuts off and reboots the htc screen. i tried installing the back up, re installing the latest venom rom and even trying to put on a entire new rom but nothing has worked(it wont even let me install a new rom it errors out when i try) i doubt you will even get this but its my last effort Ive spent the entire day and all night looking for some way to fix this but i have yet to find anything. please if anyone one has any know how about this i could really used the help. i rooted my att htc one xl(evita) about 7 months ago using the method from onexroot.com and have never had an issue with this phone till now.
when i try to install a new rom via twerp it said install failed, im really stuck with this and could use some help thanks in advance.
just incase its not clear the phone is rooted running a custom rom(team venom) and im using twerp as my recovery program
evita pvt ship s-on rl
hboot-1.14.0002
radio-0.19as.32.09.11_2
opendep-v29.1.0.45.0622
emcc-boot
not sure if that helps at all

dtk0kai said:
Hey Guys,
This is my first post, so excuse me if I sound like I don't know what I'm talking about.
a few days ago i tried to connect to my wifi at home and it was not picking it up although i was inside my own house. so i thought i should restart my phone. well after trying to restart it it got stuck in a boot loop. it would load the htc screen then start loading the venom logo then it shuts off and reboots the htc screen. i tried installing the back up, re installing the latest venom rom and even trying to put on a entire new rom but nothing has worked(it wont even let me install a new rom it errors out when i try) i doubt you will even get this but its my last effort Ive spent the entire day and all night looking for some way to fix this but i have yet to find anything. please if anyone one has any know how about this i could really used the help. i rooted my att htc one xl(evita) about 7 months ago using the method from onexroot.com and have never had an issue with this phone till now.
when i try to install a new rom via twerp it said install failed, im really stuck with this and could use some help thanks in advance.
just incase its not clear the phone is rooted running a custom rom(team venom) and im using twerp as my recovery program
evita pvt ship s-on rl
hboot-1.14.0002
radio-0.19as.32.09.11_2
opendep-v29.1.0.45.0622
Click to expand...
Click to collapse
flash twrp 2.6 advanced wipe everything except sd card, reflash.
also since youre s-on you have to extract the boot.img from the rom zip and flash it with fastboot after flashing most roms. should not be the case with viper but i would do it anyway if vier doesn't boot after the above steps.
fastboot flash boot boot.img

reply
exad said:
flash twrp 2.6 advanced wipe everything except sd card, reflash.
Click to expand...
Click to collapse
this is going to sound bad but how do i do that again? i really dont remember how to flash twerp

dtk0kai said:
this is going to sound bad but how do i do that again? i really dont remember how to flash twerp
Click to expand...
Click to collapse
download: http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.6.0.0-evita.img
Place img in your fastboot folder
put phone in hboot/fastboot mode
open command prompt within fastboot folder (shift right click - open command prompt here)
fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
navigate to recovery in hboot menu, select recovery.

exad said:
download: http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.6.0.0-evita.img
Place img in your fastboot folder
put phone in hboot/fastboot mode
open command prompt within fastboot folder (shift right click - open command prompt here)
fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
navigate to recovery in hboot menu, select recovery.
Click to expand...
Click to collapse
ok im going to go try that ill post results

exad said:
download: http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.6.0.0-evita.img
Place img in your fastboot folder
put phone in hboot/fastboot mode
open command prompt within fastboot folder (shift right click - open command prompt here)
fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
navigate to recovery in hboot menu, select recovery.
Click to expand...
Click to collapse
when you say reflash you mean my rom right?

Yep
Sent from my HTC One XL using xda app-developers app

exad said:
Yep
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
when flashing my rom it said error kernal not installed but then it said new rom flashed successfully will that be a problem?(viperxl-3.2.7)

exad said:
Yep
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
well so far nothing has changed.

Like Exad said, you're s-on so you need to manually flash the boot.img from the ROM using fastboot.
Sent from my Evita

timmaaa said:
Like Exad said, you're s-on so you need to manually flash the boot.img from the ROM using fastboot.
Sent from my Evita
Click to expand...
Click to collapse
yea i tried that too nothing changed
off to bed still no luck loads part of the viper logo and then resets back to htc screen x.x

dtk0kai said:
yea i tried that too nothing changed
off to bed still no luck loads part of the viper logo and then resets back to htc screen x.x
Click to expand...
Click to collapse
Try running an RUU. This fault (or at least a very similar fault) happened with my fiance's phone and now there's only one ROM that will boot on it (an old build of cm10.1). You may be facing a hardware fault (that's what's wrong my fiance's phone), but I'd suggest running an RUU to see if that helps.
Sent from my Evita

You might brick if you ruu, I would try flashing other roms first. Make sure to check the md5 to make sure that the download isn't corrupt.
But
If you must ruu make sure it isn't 3.18. And you will have to change your cid back and relock.
Fastboot oem writecid CWS__001
To change your cid back.
If you ruu, you cannot ever the the 3.18+ ota until you reroot and achieve s-off
Sent from my HTC One XL using xda app-developers app

exad said:
Nononono he's s-on remember! He might brick of he RUUs
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Oh gosh, my bad, I'm having a weird day today.
Sent from my Evita

Well so long as it's not 3.18 it Should be OK I think?
Sent from my HTC One XL using xda app-developers app

exad said:
Well so long as it's not 3.18 it Should be OK I think?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
so i should just try a diffrent rom? when doing that i should flash the boot img using fastboot then install the rom and then do a cache whipe correct?

Did you Wipe system in advanced Wipe last time before flashing the rom?
For any rom you ever flash always follow the steps I layer out in my earlier post. It will not be different for any rom.
Sent from my HTC One XL using xda app-developers app

exad said:
Did you Wipe system in advanced Wipe last time before flashing the rom?
For any rom you ever flash always follow the steps I layer out in my earlier post. It will not be different for any rom.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
yes i did the entire wipe just like you said then installed the rom like you said and it started up and loaded the venom screen longer but then restarted, im going to try flashing the cm 10 and see if that dose anything

now cm10 is in a boot loop after i tried to flash gapps

Try flashing the 20130304 build from the get.cm/evita page.
Sent from my Evita

Can't S-Off for the life of me

Hey guys,
I have an HTC One X with the bootloader unlocked that has Venom Viper installed on it and I want to S-OFF the phone so that I can install the beast mode kernel. I want to do this because the phone has some issues like a dropping SIM card and random reboots. I have another friend with the same phone that I installed Viper on and she had the same issues. I over the phone talked her through the S-OFF method and once we finally got it and installed the kernel the phone worked perfectly.
One thing that was odd is that the method (FacePalm) wasn't working until we flashed the phone back to stock (not a backup but a stock release with a flashable SU bin that was on XDA somewhere). Once we did that the phone was S-OFF after rebooting into the bootloader.
This time around though I'm starting to wonder whether the fact it worked when we flashed back to stock was a coincidence because I did the SAME EXACT THING with this current phone, flashed to the same stock rom with the same method of SU, and it just won't work. I run through the whole process and get no errors (except when you are supposed to) and when I reboot into recovery it is not S-OFF. One thing I noticed though is that on another site it said "The last step is to confirm the SU request you get on your phone". I cannot remember if my friend got a popup but on this phone I never get one.
Therfore I am thinking the problem is with the flashable SU bin not working properly and was going to ask if anyone had their hands on a prerooted stock. There is a thread for one on here but the link is dead.
So basically does anyone have such a rom or know anything about the S-OFF method only working with stock or odex/deodex or something of that sort.
Thanks.

I got s-off with viper
Sent from my VENOMized HoxL

area51avenger said:
I got s-off with viper
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
I guess Ill just keep trying it. Did you use the files from xda?

Do you have the One X (Endeavoru) or the One XL (Evita)?
Sent from my Evita

timmaaa said:
Do you have the One X (Endeavoru) or the One XL (Evita)?
Sent from my Evita
Click to expand...
Click to collapse
Just the X (Endeavoru)

Ok you're in the wrong forum then, this is the One XL forum.
Sent from my Evita

timmaaa said:
Ok you're in the wrong forum then, this is the One XL forum.
Sent from my Evita
Click to expand...
Click to collapse
Actually it is the XL I just forget its not called that. Im sure because its black, from AT&T, and not the international version.

The colour is irrelevant, but if it's from at&t you have the Evita. Are you sure you have superuser installed and usb debugging is enabled in developer options? Which Android version is the ROM you're using?
Sent from my Evita

timmaaa said:
The colour is irrelevant, but if it's from at&t you have the Evita. Are you sure you have superuser installed and usb debugging is enabled in developer options? Which Android version is the ROM you're using?
Sent from my Evita
Click to expand...
Click to collapse
Ya both because i saw the SU app and I used adb so debugging is enabled.
Android ver 4.2.2

Downgrade to Android 4.0 or 4.1, people have had heaps of problems getting s-off while on a 4.2 ROM.
Sent from my Evita

timmaaa said:
Downgrade to Android 4.0 or 4.1, people have had heaps of problems getting s-off while on a 4.2 ROM.
Sent from my Evita
Click to expand...
Click to collapse
Ok thanks for the tip.

timmaaa said:
Downgrade to Android 4.0 or 4.1, people have had heaps of problems getting s-off while on a 4.2 ROM.
Sent from my Evita
Click to expand...
Click to collapse
Sigh. After trying to flash a 4.1.1 Rom the phone now boot loops and flashing any other rooms or restoring the TWRP backup (just system, boot, and data) that I had of viper have had no effect.

Did you flash the boot.img via fastboot?
Sent from my Evita

timmaaa said:
Did you flash the boot.img via fastboot?
Sent from my Evita
Click to expand...
Click to collapse
Not during the first boot, but after I realized my error I rebooted into fastboot and did it. Is it imperative that its done before booting?
EDIT:
OK so I just tried flashing the stock rom I tried for S-OFF before and even flashed the boot.img and its still boot looping.
It pisses me off that the security system has to be this obnoxious. I'm used to my own samsung phones where theres barely any security and bricking is practically impossible with Odin.

It isn't obnoxious if you know what you're doing. You're s-on so you must flash the boot.img for each ROM every time you flash a ROM. Install ROM, reboot to bootloader, flash boot.img, reboot to system. Once you have s-off you will no longer need to do this. Are you flashing the right boot.img?
Sent from my Evita

timmaaa said:
It isn't obnoxious if you know what you're doing. You're s-on so you must flash the boot.img for each ROM every time you flash a ROM. Install ROM, reboot to bootloader, flash boot.img, reboot to system. Once you have s-off you will no longer need to do this. Are you flashing the right boot.img?
Sent from my Evita
Click to expand...
Click to collapse
Ok well, I changed ONE simple thing that I would think wouldn't matter, but apparently it does. Instead of rebooting after the rom flashing and then during the boot loop holding vol down and power to get into bootloader again, AND THEN flashing the boot.img, I simply hit home in twrp after flashing the room and used the "reboot" function to go directly to boot loader and then flashed the boot.img
The phone now got past the developer warning screen and is showing the htc one beats audio screen. However it now seems to be frozen there :|
This is the rom I used: http://forum.xda-developers.com/showthread.php?t=2181891
It is a step further at least, and now that I see how to properly flash the boot.img I will try a few other roms and see if they work any better, unless you have any other suggestions.

It looks as though you've done it correctly. Which recovery version are you using?
Sent from my Evita

timmaaa said:
It looks as though you've done it correctly. Which recovery version are you using?
Sent from my Evita
Click to expand...
Click to collapse
2.6.3.0

Are you certain you're flashing the boot.img from the ROM you've just installed and not another one by mistake? TWRP 2.6.3 should be ok, but you could try 2.6 instead if you want to, I've seen a couple of bugs on 2.6.3 but I can't remember what they were.
Sent from my Evita

timmaaa said:
Are you certain you're flashing the boot.img from the ROM you've just installed and not another one by mistake? TWRP 2.6.3 should be ok, but you could try 2.6 instead if you want to, I've seen a couple of bugs on 2.6.3 but I can't remember what they were.
Sent from my Evita
Click to expand...
Click to collapse
Yes I am sure. Ill try a different ROM snd if that doesn't work ill downgrade TWRP