Database Info

Please Help!

Ok,
So I've used roms on my hd2 and one x, so I thought this would be simple on a friends sensation, oh how wrong was I.
I have unlocked the sensation via htcdev, installed clockworkmod and installed pyramids jellybean rom.
Now I have all sorts of issues, the rom boots then drops somehow straight to clockworkmod. I can't mount the sd card within clockworkmod to try a different rom and the phone is now useless, doh.
How can I fix this please guys?

Did you update the firmware? Are you s off or s on? If your s on you must flash boot image. Download 4 ext recovery, enable smart flash in 4ext. This way you can flash boot image. Please read flashing roms with s on. Also for that rom the firmware must also be upgraded. Let me link you to the guide to flashing roms with s on. This will help http://forum.xda-developers.com/showthread.php?t=1631861
Someone more knowledgeable than myself can give you step by step instructions to get you out of this pinch. But in the mean time read the link I posted about flashing with s on. It will help in the future. Best wishes not to worry I'm sure you can fix this.
Sent from my HTC Sensation using xda premium

daz1uk said:
Ok,
So I've used roms on my hd2 and one x, so I thought this would be simple on a friends sensation, oh how wrong was I.
I have unlocked the sensation via htcdev, installed clockworkmod and installed pyramids jellybean rom.
Now I have all sorts of issues, the rom boots then drops somehow straight to clockworkmod. I can't mount the sd card within clockworkmod to try a different rom and the phone is now useless, doh.
How can I fix this please guys?
Click to expand...
Click to collapse
HTC Dev doesn't really unlock it. It only partially unlocks it.
It doesn't s-off the device so you don't have access to the system partition, meaning you can't properly install a custom ROM without a few extra steps. And I don't think you can do it at all with clockworkmod. You need 4EXT Recovery which can flash a ROM with s-on. There's a few extra steps to doing it but it works.
You also have to make sure you have the correct firmware. So if the device was previously on a Gingerbread ROM and you didn't upgrade firmware, it won't work.
Now, the part where it boots then drops back into recovery is weird.
Tell us exactly what steps you did so we can better determine where something went flukely.
I'm CERTAIN it's fixable though.

realsis said:
Did you update the firmware? Are you s off or s on? If your s on you must flash boot image. Download 4 ext recovery, enable smart flash in 4ext. This way you can flash boot image. Please read flashing roms with s on. Also for that rom the firmware must also be upgraded. Let me link you to the guide to flashing roms with s on. This will help http://forum.xda-developers.com/showthread.php?t=1631861
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Thanks for responding.
I've got S-OFF and flashed boot.img with adb.
Will 4EXT allow me to mount the sd card?

Yes it should
Also some roms require 4ext it's a super easy touch recovery to use. You can download from here or the playstore.
Sent from my HTC Sensation using xda premium

Skipjacks said:
HTC Dev doesn't really unlock it. It only partially unlocks it.
It doesn't s-off the device so you don't have access to the system partition, meaning you can't properly install a custom ROM without a few extra steps. And I don't think you can do it at all with clockworkmod. You need 4EXT Recovery which can flash a ROM with s-on. There's a few extra steps to doing it but it works.
You also have to make sure you have the correct firmware. So if the device was previously on a Gingerbread ROM and you didn't upgrade firmware, it won't work.
Now, the part where it boots then drops back into recovery is weird.
Tell us exactly what steps you did so we can better determine where something went flukely.
I'm CERTAIN it's fixable though.
Click to expand...
Click to collapse
Yeah I'm certain it's fixable too , just not sure how, lol. I'll give 4EXT a shot. I have no idea how or why it drops straight to clockworkmod either, I would expect it to reboot to clockworkmod if anything, but it just kind of switches from the rom straight to it, very odd.
If you could point me to a firmware I might need I would be very grateful.

It is universal 3.33 let me get link also 3.32 will work on most ics roms but 3.33 is the newest I'm running jelly bean and use 3.33
http://forum.xda-developers.com/showthread.php?t=1459767
Sent from my HTC Sensation using xda premium

daz1uk said:
Thanks for responding.
I've got S-OFF and flashed boot.img with adb.
Will 4EXT allow me to mount the sd card?
Click to expand...
Click to collapse
If you are s-off you shouldn't have to flash boot.img separately. It will do all that with the ROM flash.
Maybe that's what's screwy. Though a borked up ROM still shouldn't affect SD card mounting in recovery...that is really weird. Do you have a card reader that you can use to check the card out in your computer? I'm wondering if somehow you screwed up the card when flashing the ROM. Maybe it wont' mount because the card isn't formatted properly anymore. Stuff like that has happened before.

daz1uk said:
Yeah I'm certain it's fixable too , just not sure how, lol. I'll give 4EXT a shot. I have no idea how or why it drops straight to clockworkmod either, I would expect it to reboot to clockworkmod if anything, but it just kind of switches from the rom straight to it, very odd.
If you could point me to a firmware I might need I would be very grateful.
Click to expand...
Click to collapse
Hi,
What does your bootloader say?
hboot etc.

Yes if your s off you simply flash from recovery without boot img. But do update your firmware.
Sent from my HTC Sensation using xda premium

malybru said:
Hi,
What does your bootloader say?
hboot etc.
Click to expand...
Click to collapse
Bootloader says:
S-ON

Ok, so I think I need to update the firmware?
I've installed EXT4, still cant mount sd, so can't revert to another rom.

daz1uk said:
Ok, so I think I need to update the firmware?
I've installed EXT4, still cant mount sd, so can't revert to another rom.
Click to expand...
Click to collapse
Hi,
If you are s-on,you cannot update your firmware.
What is your hboot?

malybru said:
Hi,
If you are s-on,you cannot update your firmware.
What is your hboot?
Click to expand...
Click to collapse
hboot 1.18.0000
Unlocked
S-ON
As far as I was aware S-ON just prevented the boot.img from being written via recovery, which can be done with adb. So the only reasons for these issues must be firmware version right?

daz1uk said:
hboot 1.18.0000
Unlocked
S-ON
Click to expand...
Click to collapse
Hi,
It is a pity you went to HTC to unlock your phone.
I wonder if you can still s-off using revolutionary.
You are going to need to run a RUU,and hopefully get a working phone again.
Try and find a RUU HERE that matches your area and carrier.

daz1uk said:
hboot 1.18.0000
Unlocked
S-ON
As far as I was aware S-ON just prevented the boot.img from being written via recovery, which can be done with adb. So the only reasons for these issues must be firmware version right?
Click to expand...
Click to collapse
Yup. If you have the 1.18 hboot you have Gingerbread firmware, which won't support Jellybean or ICS.
The good news is that you can flash a gingerbread rom and get the phone back to a working state right away if you need to get the phone back to the owner.
The RUU to restore is pretty simple. Then Revolutionary s-off proceedure is also extremely painless.
Reverting back to stock and starting over to s-off shouldn't take more than 15 minutes if you do it right. Then flashing the ICS/GB firmware (3.32 or 3.33) takes 3 minutes. Then the new rom takes 3 more minutes.
Just make sure you RUU to gingerbread and not to ICS. The ICS Hboots are harder to s-off. It's worth adding the extra step to flash the ICS/JB firmware later.

This is driving me nuts, tried 2 ruu's, both failed, if it was my phone it would be out the window!

daz1uk said:
This is driving me nuts, tried 2 ruu's, both failed, if it was my phone it would be out the window!
Click to expand...
Click to collapse
Hi,
Are you Sensation,or Sensation XE?

daz1uk said:
This is driving me nuts, tried 2 ruu's, both failed, if it was my phone it would be out the window!
Click to expand...
Click to collapse
Doh, my fault forgot to re-lock it, update is installing as I type, phew!
Sent from my HTC One X using Tapatalk 2

[Q] Does an RUU...

Delete everything on the root directory as i can see a lot of crap has built up there over time...
S-Off, 1.14 hboot (telstra), supercid
Do i need to relock the bootloader before running the RUU and is there anything else i need to do?
Sent from my One X using xda app-developers app

if you are s-off no need to relock bootloader

jerrycoffman45 said:
if you are s-off no need to relock bootloader
Click to expand...
Click to collapse
Cheers, still looking at an answer for the first q..

no need too ruu should wipe everything

jerrycoffman45 said:
no need too ruu should wipe everything
Click to expand...
Click to collapse
Uhhhh....... wha?

w0tha said:
Uhhhh....... wha?
Click to expand...
Click to collapse
Delete everything on the root directory as i can see a lot of crap has built up there over time...

jerrycoffman45 said:
Delete everything on the root directory as i can see a lot of crap has built up there over time...
Click to expand...
Click to collapse
Roger, makes sense now. Cheers for that!

if that wasnt first ? what was

jerrycoffman45 said:
if that wasnt first ? what was
Click to expand...
Click to collapse
It's all good I was reading your response the wrong way
Last one. Will my CID be returned to the default rather than SuperCID?

No supercid remains or at least it did on mine
Sent from my HTC One X using Tapatalk 2

If all you want to do is clean up your system there's an app for that
Sent from my One X using Xparent Green Tapatalk 2

A ruu will wipe your entire phone and return most things to bone stock.
The two things it won't affect are CID and s-off. Both of those have to be changed manually.

iElvis said:
A ruu will wipe your entire phone and return most things to bone stock.
The two things it won't affect are CID and s-off. Both of those have to be changed manually.
Click to expand...
Click to collapse
This might be a bit off topic but If I do RUU on a S-OFF HOXL device, the phone should be role back to stock excpet S-OFF and CID right, so if I want to flash a custom rom I shouldn't need to go through unlock bootloader, I can just flash the rom and it should work correct?
thanks

iElvis said:
A ruu will wipe your entire phone and return most things to bone stock.
Click to expand...
Click to collapse
Does RUU wipe the SD? I can't remember.

redpoint73 said:
Does RUU wipe the SD? I can't remember.
Click to expand...
Click to collapse
I don't think so, but it wipes /data. I can't remember if unlocking your boot loader on nexus 4 wipes your sdcard because mine was empty. On the hox the /sdcard should stay untouched
Sent from my Nexus 4

mirGantrophy said:
I don't think so, but it wipes /data. I can't remember if unlocking your boot loader on nexus 4 wipes your sdcard because mine was empty. On the hox the /sdcard should stay untouched
Sent from my Nexus 4
Click to expand...
Click to collapse
that is correct sdcard stays safe except for system files

redpoint73 said:
Does RUU wipe the SD? I can't remember.
Click to expand...
Click to collapse
When I did the 2.20, it wiped everything. But I was expecting this and had all my stuff backed up.
Edit: Now that I think of it, it might well have been unlocking that wiped it, not the ruu. At first it seemed like the files were all still there, then they were gone. I think in between that is when I unlocked.

Just back up anything you want to keep and factory reset?
Sent from my One X using xda premium

The_Zodiac said:
Just back up anything you want to keep and factory reset?
Click to expand...
Click to collapse
There's no need to factory reset, but you should always back up when you do something to your phone.

[Q] From ICS to JB

Hi, I have a HTC ONE XL for AT&T with S-OFF and unlocked bootloader. I have the nocturnal ROM based on ICS. Also HBOOT 1.01.0000.
I want to install a rom based on JB (This particular CleanROM 6.5 - ★ | Jellybean 4.1.1! |).
My question is with this hboot, can i flash a jb rom from ICS? Because I'm not sure if flash from recovery the zip of this rom bricked me.

It won't brick you. I'm not sure if you'll experience issues using such an old firmware with a ROM based on the latest softwate
Sent from my One X using xda app-developers app

Thanks. Is there any way to update the software?

Rafanjani said:
Thanks. Is there any way to update the software?
Click to expand...
Click to collapse
Yes install the Ruu, then push twrp, then install CR. This will give you the latest firmware. CR by itself does not so it, and some gave experienced random reboots with older wifi firmware. Just be aware that a small subset of HOXL phones do not work well with Maps/nav under JB

between ynelsol
GroovyGeek said:
Yes install the Ruu, then push twrp, then install CR. This will give you the latest firmware. CR by itself does not so it, and some gave experienced random reboots with older wifi firmware. Just be aware that a small subset of HOXL phones do not work well with Maps/nav under JB
Click to expand...
Click to collapse
thanks for reply! I did brick my phone when i try to install an official ruu 2 months ago, but i did fix this ($$$$). The problem is that I can not install because I have CID 111111 and CR root, bootloader unlocked etc

With s-off you won't brick running an ruu. Though my phone will no longer ruu properly but that's another story. I may post a thread about it in case others experience it so they know how to recover.
Sent from my HTC One X using xda app-developers app

exad said:
Though my phone will no longer ruu properly but that's another story. I may post a thread about it in case others experience it so they know how to recover.
Click to expand...
Click to collapse
I'm curious about this. What happened?
Sent from my HTC One

ECEXCURSION said:
I'm curious about this. What happened?
Sent from my HTC One
Click to expand...
Click to collapse
Something went wrong while RUUing and my hboot partition cannot be written over without clearing the cache first. So the RUU will get to the end and then fail. Everything flashed except the hboot. It's kind of funny because it looks like a brick when it happens but it remains in RUU mode so I can just fastboot flash the hboot seperately after and everything works but RUUs will no longer complete successfully Always half bricks.
How did it happen? Well I think it's because I was RUUing in a VM as I was running linux exclusively at the time. But during RUU the phone looses connection and I have to manually reconnect to my phone and I didn't realize so it interrupted the RUU. I'm just lucky I didn't end up with a full brick! ^_^

exad said:
Something went wrong while RUUing and my hboot partition cannot be written over without clearing the cache first. So the RUU will get to the end and then fail. Everything flashed except the hboot. It's kind of funny because it looks like a brick when it happens but it remains in RUU mode so I can just fastboot flash the hboot seperately after and everything works but RUUs will no longer complete successfully Always half bricks.
How did it happen? Well I think it's because I was RUUing in a VM as I was running linux exclusively at the time. But during RUU the phone looses connection and I have to manually reconnect to my phone and I didn't realize so it interrupted the RUU. I'm just lucky I didn't end up with a full brick! ^_^
Click to expand...
Click to collapse
how i can flash hboot using fastboot? I wish to have jb

Rafanjani said:
how i can flash hboot using fastboot? I wish to have jb
Click to expand...
Click to collapse
flashing hboot with fastboot won't give you JB......
Is your phone S-ON or S-OFF?
SuperCID? Yes or no?
Bootloader locked or unlocked?

exad said:
flashing hboot with fastboot won't give you JB......
Is your phone S-ON or S-OFF?
SuperCID? Yes or no?
Bootloader locked or unlocked?
Click to expand...
Click to collapse
I know! but it's the first step to upgrade to jb

Rafanjani said:
I know! but it's the first step to upgrade to jb
Click to expand...
Click to collapse
No it isn't

[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