Database Info

Help with RUU'ing to 2.20

I've been running AOSP ROM's on my evita for a while now, but apparently with the 3.4 kernel you now need hboot 2.14 or higher and mine's at 1.09. My phone was unlocked with S-ON, but I did "fastboot oem lock" this morning because I read that it's necessary for an RUU. I downloaded the 2.20 RUU and tried to run the installer but I always get an Error [170] USB Connection Error. I have the HTC and adb drivers installed successfully and have tried to run the RUU as admin in both Sense and fastboot (bootloader). I'm a bit stumped and would really like to get AOSP back on my phone.

You need to S-off first.
Sent from my HTC One X using xda premium

tlazarus said:
You need to S-off first.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Should I use facepalm for that then?
EDIT
I got s-off, but still no go. Still the error 170.
I know on my old Incredible I was able to rename the rom.zip from the RUU as PB99IMG.zip and put it on the root of my sdcard. Then in hboot it would detect it and ask to flash it. This isn't happening on my evita though. Is there a way to do that, or is that only for older htc devices?

Put phone into fastboot and try again. Check error log to see if it fails to identify your phone.
Open command prompt and type adb devices, if it does not see it then try installing new drivers. If it does see it then enter " adb shell reboot oem-78" that will reboot your phone in to RUU ready fastboot. Open ruu and try running it again.
Sent from my HTC One X using xda premium

Venomtester said:
Put phone into fastboot and try again. Check error log to see if it fails to identify your phone.
Open command prompt and type adb devices, if it does not see it then try installing new drivers. If it does see it then enter " adb shell reboot oem-78" that will reboot your phone in to RUU ready fastboot. Open ruu and try running it again.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Where can I find this error log? It did see my device, I did that command (which ended at the black htc screen) and I ran the RUU again but I still get the error 170. I'm also using this RUU http://bugsylawson.com/index.php/fi...320911-2-101053225l-release-271865-signedexe/

Sounds like a bad download. Is it 568.22 mbs? Try roomyshare.com/ruu-evita-ul-cingular.html
You can find it in the list.
Sent from my HTC One X using xda premium

Venomtester said:
Sounds like a bad download. Is it 568.22 mbs? Try roomyshare.com/ruu-evita-ul-cingular.html
You can find it in the list.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
It is that size, though I may try the link you gave.
EDIT
Okay, I think I found out what I've been doing wrong. I found this link http://forum.xda-developers.com/showthread.php?t=2119610 and it turns out that the file I've been trying does NOT include the 2.14 hboot that I need. The one I need is the latest JB release, but someone said that if you flash it with superCID and S-ON that it will brick your device. I have superCID but S-OFF, does anyone think that will brick my device? Should I flash the RUU with the 1.09 hboot (which I'm running) first, and then flash the newest RUU? Also, it looks like the link I provided offers flashable OTA's of each update. Would those work/be recommended for TWRP?

Change cid to cingular "cws_001" I think. Super cid can cause brick.
Sent from my HTC One X using xda premium

Venomtester said:
Change cid to cingular "cws_001" I think. Super cid can cause brick.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Well I didn't do that...haha. I read on another forum that TWRP doesn't support that cid check function or something and to just remove it from the updater-script so I tried that and flashed the latest OTA zip in TWRP and it failed after a few steps. I tried booting and it didn't get to the boot animation so I rebooted to recovery and restored my backup. I'm going to try a stock zip without the modified updater-script and restore my CID to normal and try again.
EDIT
Well, I restored the CID to CWS__001 and I still get that check_cid error

dshoe said:
Well I didn't do that...haha. I read on another forum that TWRP doesn't support that cid check function or something and to just remove it from the updater-script so I tried that and flashed the latest OTA zip in TWRP and it failed after a few steps. I tried booting and it didn't get to the boot animation so I rebooted to recovery and restored my backup. I'm going to try a stock zip without the modified updater-script and restore my CID to normal and try again.
EDIT
Well, I restored the CID to CWS__001 and I still get that check_cid error
Click to expand...
Click to collapse
To run a ota you need to flash stock recovery image.. and bootloader needs to be unlocked for that
Sent from my HTC One XL using xda premium

31ken31 said:
To run a ota you need to flash stock recovery image.. and bootloader needs to be unlocked for that
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Hm, okay then, let me ask another question. I'm on hboot 1.09 and I need 2.14 to run AOSP ROM's now. What's the best way to get there if I already have ROM's installed. Is it what I'm doing right now or should it be something else?
EDIT
The latest JB RUU is picking up my device now and offering the update, 2 seconds away from doing it....

dshoe said:
Hm, okay then, let me ask another question. I'm on hboot 1.09 and I need 2.14 to run AOSP ROM's now. What's the best way to get there if I already have ROM's installed. Is it what I'm doing right now or should it be something else?
EDIT
The latest JB RUU is picking up my device now and offering the update, 2 seconds away from doing it....
Click to expand...
Click to collapse
Just make sure you are s-off before running ruu or risk a brick..
Sent from my HTC One XL using xda premium

Hi. I am looking my update my hboot from 1.09 to 2.14. I am S-OFF now, also running the Sense 5 rom now(TWRP recovery).
I have downloaded the Latest JB 3.18 RUU from instructions here http://forum.xda-developers.com/showthread.php?t=2064621.
What else do I need to do before flashing the RUU to the device?

For what it's worth, I was on stock 2.20, got s-off and unlocked bootloader with superCID, and ran the 3.18 RUU with no problems. I didn't need to relock or anything.

knanda said:
Hi. I am looking my update my hboot from 1.09 to 2.14. I am S-OFF now, also running the Sense 5 rom now(TWRP recovery).
I have downloaded the Latest JB 3.18 RUU from instructions here http://forum.xda-developers.com/showthread.php?t=2064621.
What else do I need to do before flashing the RUU to the device?
Click to expand...
Click to collapse
You can go ahead and run the RUU. No real risk because you're s-off. Maybe make a backup though.
Sent from my Evita

[Q] Post root unable to access phone through ADB

AT&T HOX from Android 4.2.1, with 3.18 firmware. Attempting to get to CM 10.1
Rooted and flashed TWRP via http://forum.xda-developers.com/showpost.php?p=41830252&postcount=201
Moved on to Facepalm S-off http://forum.xda-developers.com/showthread.php?t=2155071, was getting error 99.
Used the Viper solution from ChongoDroid on page 17 http://forum.xda-developers.com/showpost.php?p=38186473&postcount=163 using viper from http://forum.xda-developers.com/showthread.php?t=2087443
Install Viper from TWRP, Viper install stops at 0.00%, will not progress. Hard restart via power button battery remove sim, attempted s-off again. At some point I ended up getting the correct error 92. Success! Run 'fastboot oem boot', get list of errors, wait for boot into Android. Boot stops at white HTC splash screen, android will not boot.
Panic, hard restart back into bootloader, and this is where things go hazy (it was 5 in the morning by now). At this point I'm sure I put in some commands I should not have via adb (don't remember which ones), and did a factory reset via hboot. Recovery now brings me back into the bootloader. Bootloader shows *** TAMPERED ***, ***RELOCKED *** and *** Security Warning ***. I'm still S-ON with hboot 2.14.0000.
When in fastboot, my phone will not list via 'adb devices'. FAQ Q16 (http://forum.xda-developers.com/showthread.php?t=2136172) says if I did a factory reset in hboot, my SD mem is wiped and i need to format it from device manager. Device Manager shows my phone as Android USB Devices > My HTC and options are Update Driver Software..., Disable, and Uninstall. Updating drivers gives me a drivers up to date notice. No option to format the SD
Word is that if it turns on, it isn't bricked, but if I can't get my adb to recognize my phone, what is there that I can do to fix it? I'm on 64 bit Windows 7.

alright, first off, you flashed a ROM for the international quad core One X and you're lucky not to have bricked your phone. Secondly, what you're gonna need to do is run the 3.18 ruu and restore your phone to factory settings with that. That's the only way to recover from factory reset in bootloader. Before you do, you need to be S-Off. Which you are, correct?
Edit: re-reading this, it appears you're not s-off. I'm gonna need to call in some help here because 3.18 ruu with SuperCID will brick you, but I don't think you can use a lower RUU since you're s-on. Anyone know what to do? If you are s-off and I just misread your post, then go ahead and run the ruu.
If it turns on, there's always a way to fix it!

Adb requires an os to work, since you can't boot to your os, no Adb
That being said, in bootloader, you should be able to access your phone with fastboot. Boot to bootloader/fastboot with your phone plugged in to your pc.
Do: fastboot devices and confirm that fastboot commands reach your phone, then we will move on to the next step.
Sent from my HTC One X using xda app-developers app

Correct, I am still s-off, and 'adb devices' gives an empty list, and does not list my phone. I cannot send commands to my phone via adb commands.

You just said in your first post you're still s-on......
These details are extremely important so please be sure of what you've typed prior to posting.
Sent from my HTC One X using xda app-developers app

exad said:
Adb requires an os to work, since you can't boot to your os, no Adb
That being said, in bootloader, you should be able to access your phone with fastboot. Boot to bootloader/fastboot with your phone plugged in to your pc.
Do: fastboot devices and confirm that fastboot commands reach your phone, then we will move on to the next step.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
exad said:
You just said in your first post you're still s-on......
These details are extremely important so please be sure of what you've typed prior to posting.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yes, sorry. I realized my mistake as soon as I posted, but since I'm a new member I can only edit or reply every 5 minutes.
Yes, I am S-ON. S-ON, not S-OFF.
And aha, yes. 'fastboot devices' does list my phone.

Good good. So first you'll want to unlock your bootloader again since it's relocked. Just flash the unlock_code.bin or whatever it's called again that you previously used.
Sometimes if you're relocked it does the unlock process like it's going to unlock but then leaves you relocked. If this happens press and hold power to simulate a battery pull and try again. It should work eventually. Might take several tries.
Sent from my HTC One X using xda app-developers app

Korad said:
Yes, sorry. I realized my mistake as soon as I posted, but since I'm a new member I can only edit or reply every 5 minutes.
Yes, I am S-ON. S-ON, not S-OFF.
And aha, yes. 'fastboot devices' does list my phone.
Click to expand...
Click to collapse
I'm assuming you have supercid already?
I would reflash twrp.. nothing higher that 2.3.3.1
Then load a sense Rom from this forum through twrp. Just to get a running os on the phone. Then you can s-off and run 3.18 ruu
Sent from my HTC One XL using xda premium

exad said:
Good good. So first you'll want to unlock your bootloader again since it's relocked. Just flash the unlock_code.bin or whatever it's called again that you previously used.
Sometimes if you're relocked it does the unlock process like it's going to unlock but then leaves you relocked. If this happens press and hold power to simulate a battery pull and try again. It should work eventually. Might take several tries.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Okay, flashed Unlock_code.bin on first try, now showing *** UNLOCKED ***

Korad said:
Okay, flashed Unlock_code.bin on first try, now showing *** UNLOCKED ***
Click to expand...
Click to collapse
Do as ken posted above though twrp 2.6 is supposedly stable and fine too.
Roms from here are safe to flash: http://forum.xda-developers.com/forumdisplay.php?f=1541
And... Here: http://forum.xda-developers.com/forumdisplay.php?f=1726
Sent from my HTC One X using xda app-developers app

exad said:
Do as ken posted above though twrp 2.6 is supposedly stable and fine too.
Roms from here are safe to flash: http://forum.xda-developers.com/forumdisplay.php?f=1541
And...:
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Have you flashed 2.6 yet? I've heard it works as well but was waiting for more input
Sent from my HTC One XL using xda premium

Not yet, going to when I get home. Jacobas92 said hes been using it though and I trust him.
Sent from my HTC One X using xda app-developers app

Well I'll take ur word for it. Gonna download and flash now and test the hell out of all options.
Sent from my HTC One XL using xda premium

31ken31 said:
I'm assuming you have supercid already?
I would reflash twrp.. nothing higher that 2.3.3.1
Then load a sense Rom from this forum through twrp. Just to get a running os on the phone. Then you can s-off and run 3.18 ruu
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
So I'm waiting on ViperXL to download (going very slowly), but if I'm looking to get to CM 10.1, and have root with TWRP, do I need to flash a ROM with TWRP first or can I do the Facepalm S-Off and move straight to CM 10.1 without flashing a middle-man ROM?

Korad said:
So I'm waiting on ViperXL to download (going very slowly), but if I'm looking to get to CM 10.1, and have root with TWRP, do I need to flash a ROM with TWRP first or can I do the Facepalm S-Off and move straight to CM 10.1 without flashing a middle-man ROM?
Click to expand...
Click to collapse
I believe you need to be on a rooted ROM to get s-off.

Korad said:
So I'm waiting on ViperXL to download (going very slowly), but if I'm looking to get to CM 10.1, and have root with TWRP, do I need to flash a ROM with TWRP first or can I do the Facepalm S-Off and move straight to CM 10.1 without flashing a middle-man ROM?
Click to expand...
Click to collapse
Viper xl will work fine that's what I used to s-off. Not with the new cm10.1 kernel you have to ruu up to 3.18 before you install it.
Sent from my HTC One XL using xda premium

31ken31 said:
Viper xl will work fine that's what I used to s-off. Not with the new cm10.1 kernel you have to ruu up to 3.18 before you install it.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
hes already on 3.18

If I'm using ViperXL as my ROM during S-Off, will I want to use ChongoDroid's extra steps when installing ViperXL or should I only need to do those if the Facepalm S-Off steps don't work by themselves?

Korad said:
If I'm using ViperXL as my ROM during S-Off, will I want to use ChongoDroid's extra steps when installing ViperXL or should I only need to do those if the Facepalm S-Off steps don't work by themselves?
Click to expand...
Click to collapse
You should be able to S-OFF with viperxl without any problems just by flashing viperxl and following the S-OFF thread right after.

So ViperXL finally finished downloading, and I've sent the command to push the .zip to /sdcard in prep to install it with TWRP, but it's been stuck there for 15+ minutes. Should I be worried? Should I restart?

Softbricked(?) Rogers

I recently tried to flash CM10 onto my Rogers One X through TWRP 2.3.3.1 but it's been stuck on the bootloader so now I don't have a working OS. I've been trying to figure out how to either fix that or go back to stock through RUU I can't find the correct RUU for that.
**Relocked**
Evita PVT SHIP S-ON RL
Hboot -2.14.0000
RADIO-0.23a.32.09.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
Nov 26
So far I've tried
Flashing TWRP 2.6 on, clearing cache/devlek/system then flashing CM10

Every phone is different. You should always read the stickies prior to doing anything even if you think you know what you're doing.
With 2.14 hboot and s-on you need to fastboot flash boot boot.img where the boot.IMG is extracted from the rom. This phone has a few quirks so I suggest reading more or you may find out the hard way.
Typically I ignore these questions but I was feeling nice today. Please also remember that the rules on xda are to search before asking so you are also in violation of xda rules.
Good luck.
Sent from my One X using xda app-developers app

I'll assume the attempted flash of TWRP 2.6 failed, since your bootloader is relocked.

redpoint73 said:
I'll assume the attempted flash of TWRP 2.6 failed, since your bootloader is relocked.
Click to expand...
Click to collapse
His last line shows that he flashed cm 10 in twrp 2.6 he relocked to try ruuing but there is no rogers ruu for that fw
Sent from my One X using xda app-developers app

SuperCID + S-Off. for unlocked bootloader Evita

Hi Guys
I am trying to get SuperCID, S-Off, then --> 3.18RUU and TWRP2.6.0.0 --> CM10.1 or 10.2
I have a phone that i Unlocked bootloader on HTCDev a long time ago. Rooted, TWRP2.6.0.0 running CM10.1 but because newer kernels require newer HBOOT so i am trying to get it.
I have TELST001 as CID
the phone in bootloader shows
****TAMPERED*****
****UNLOCKED****
EVITA PVT SHIP S-On RL
HBOOT-1.09.0000
Radio 0.20os.32.09.15
OpenDSP-V251.0.32.0405
eMMC-boot
Apr 2 2012,, 21:08:24
i have tried fastboot oem writecid 11111111 comes up with failed
I have also tried the oneclick SuperSID http://forum.xda-developers.com/showthread.php?t=1952038 - didn't work
any ideas whats the best step to take to get to the elusive cm10.2?
Thank you for your help!

You can try the hex edit method, which can be found here:
http://forum.xda-developers.com/showthread.php?t=2212737
Sent from my Evita

timmaaa said:
You can try the hex edit method, which can be found here:
http://forum.xda-developers.com/showthread.php?t=2212737
Sent from my Evita
Click to expand...
Click to collapse
This should work too:
Code:
adb shell
su
echo -ne "11111111" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20

Once you get Super CID, you can get S-Off using the method found here: http://forum.xda-developers.com/showthread.php?t=2155071
which worked wonderfully for me just this morning.
Then, once you've verified that you have S-Off, you can update your HBoot using this method: http://forum.xda-developers.com/showthread.php?t=2156686
I used the third zip listed, worked just fine.
If you do not have S-Off and you attempt this, the chance of bricking your phone is incredibly high.
When you get to green bar, as mentioned in the instructions, let it sit for a few seconds, and then move on to the next step without waiting for it to go away (because it won't...).
Once you're done with that, I would clear the cache using <fastboot erase cache>, flash your recovery software using <fastboot flash recovery "recovery software name here"> and then boot to that to flash your rom.
As I said, I just did this all this morning, and I'm happily running a rom that requires the updated HBoot. So best of luck!:good:

That's not entirely correct. It's not just the hboot you're meant to update. You really should run an RUU.
Sent from my Evita

Thank you all!
I have successfully superCID and S-Off then RUUed to the latest 3.18
now it says
*Unlocked*
EVITA PVT SHIP S-OFF RL
CID 11111111
HBoot 2.14.0000
Radio 0.24p.32.09.06
open DSP v34.1.0.45.1219
eMMC-Boot
Nov 26 2012 18:37:14:-1
but when i go into recovery it gives me a big exclamation mark
so presumably the TWRP is gone
So i used goomanager to install. that didn't work.
there's no root (after RUU) presumably normal
what is the best way to get TWRP on, then flash latest CM10.1
Many thanks for your help!

Download twrp and flash in fastboot.
Fastboot flash recovery recoveryfilename.img
Sent from my HTC One X using xda app-developers app

exad said:
Download twrp and flash in fastboot.
Fastboot flash recovery recoveryfilename.img
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Legendary.
Worked like a charm.
on latest CM10.1 nightly now.
Appreciate all of the above help!

Hello everyone..I would like to see if someone could help me..I have a one x with supercid, s-off, and bootloader unlocked..I want to flash a custom Rom like viper but wouldn't know where to start..would I ruu 3.18 or relock bootloader? Any help will be appreciated.
Sent from my HTC One X

xViiZe said:
Hello everyone..I would like to see if someone could help me..I have a one x with supercid, s-off, and bootloader unlocked..I want to flash a custom Rom like viper but wouldn't know where to start..would I ruu 3.18 or relock bootloader? Any help will be appreciated.
Sent from my HTC One X
Click to expand...
Click to collapse
All you need to do is flash the ROM from recovery....
Sent from my Evita

Ok so the hboot version wouldn't matter? I have ics 2.20 hboot 2.14. And viper xl is jb.
Sent from my HTC One X

No it doesn't matter.
Sent from my Evita

Alright thank you ..I appreciate it
Sent from my HTC One X
---------- Post added at 11:26 PM ---------- Previous post was at 11:08 PM ----------
ohh im sorry i was about to install the rom but then i checked my hboot version and it is 1.14 ..i read in a couple of threads that with 1.14 u need to install the boot img with the rom is this true? or would i need a hboot upgrade?

No, you're s-off so you don't need to do that.
Sent from my Evita

Ok let me try and I'll post results when I'm done
Sent from my HTC One X

So I flashed it and it did boot..thank you. So from now on if i would like to flash a different Rom, I would just got to twrp again right?
Sent from my HTC One X using xda app-developers app

xViiZe said:
So I flashed it and it did boot..thank you. So from now on if i would like to flash a different Rom, I would just got to twrp again right?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Correct
Sent from my HTC One XL using xda premium

Yeah just boot into TWRP, do a full wipe (cache/dalvik cache/system/factory reset), and flash your ROM (and gapps if it's an aosp ROM).
Sent from my Evita

Ok thank you guys..
Sent from my HTC One X using xda app-developers app

Heisenberg said:
Yeah just boot into TWRP, do a full wipe (cache/dalvik cache/system/factory reset), and flash your ROM (and gapps if it's an aosp ROM).
Click to expand...
Click to collapse
I accidentally flashed a ruu you while my phone was super CID. Now it won't boot. Is there a way that I could force my phone into fastboot? That is without having to do a j tag on it

HTC one X evita fails to boot in TWRP

i downloaded the lastest TRWP so i can check out the new kitkat on my evita and it will not boot in twrp u have no idea as to why.. i did have twrp 2.5 installed b4, even if i reboot from my phone into recovery it just restarts and stays at the HTC loading screen
EDIT " im using @jrior TWRP

quarterbreed said:
i downloaded the lastest TRWP so i can check out the new kitkat on my evita and it will not boot in twrp u have no idea as to why.. i did have twrp 2.5 installed b4, even if i reboot from my phone into recovery it just restarts and stays at the HTC loading screen
EDIT " im using @jrior TWRP
Click to expand...
Click to collapse
You have hardly provided enough information for an educated answer. Please try to include more details in the future.
For instance:
1. How did you install TWRP? What, exactly, did you do?
2. Please provide the top portion details of your bootloader (the top 5 lines)
3. etc, etc, etc...

Black!Jack said:
You have hardly provided enough information for an educated answer. Please try to include more details in the future.
For instance:
1. How did you install TWRP? What, exactly, did you do?
2. Please provide the top portion details of your bootloader (the top 5 lines)
3. etc, etc, etc...
Click to expand...
Click to collapse
Sorry about that, i didnt know that info would matter.. heres my top 5 lines in bootloader
EVITA PVT SHIP S-ON RL
HBOOT- 1.09.0000
RADIO- 0.16a.32.09.06
OpenDSP-v25.1.0.32.0405
eMMC-boot
then theres a date after that april,2,2012
and im running rootbox jb evita
hope this helps

quarterbreed said:
Sorry about that, i didnt know that info would matter.. heres my top 5 lines in bootloader
EVITA PVT SHIP S-ON RL
HBOOT- 1.09.0000
RADIO- 0.16a.32.09.06
OpenDSP-v25.1.0.32.0405
eMMC-boot
then theres a date after that april,2,2012
and im running rootbox jb evita
hope this helps
Click to expand...
Click to collapse
You need to update your firmware, that's your problem. You must do this by running the 3.18 RUU, but you must get s-off first. The Rumrunner s-off method is probably the easiest.
Sent from my Evita.

timmaaa said:
You need to update your firmware, that's your problem. You must do this by running the 3.18 RUU, but you must get s-off first. The Rumrunner s-off method is probably the easiest.
Sent from my Evita.
Click to expand...
Click to collapse
Thx ill try when i get home so i run the ruu after i get s-off

Yep, s-off then RUU. All up it should only take half an hour or so.
Sent from my Evita.

quarterbreed said:
Thx ill try when i get home so i run the ruu after i get s-off
Click to expand...
Click to collapse
Again, just for future reference, when someone else's post helps you, just hit the thanks button... That's what it's there for!
Sent from my One X using XDA Premium 4 mobile app

Black!Jack said:
Again, just for future reference, when someone else's post helps you, just hit the thanks button... That's what it's there for!
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
didnt notice the thanks button thx for the info.. 1 more question my HTC One X isnt coming up in device manager so im guessing thatas why runner isnt working. it says no adb connection to device.. hmm

quarterbreed said:
didnt notice the thanks button thx for the info.. 1 more question my HTC One X isnt coming up in device manager so im guessing thatas why runner isnt working. it says no adb connection to device.. hmm
Click to expand...
Click to collapse
Can you boot into your ROM at all? If so, ensure that USB debugging is enabled.
Do you have the HTC drivers installed on your computer for the phone?

Black!Jack said:
Can you boot into your ROM at all? If so, ensure that USB debugging is enabled.
Do you have the HTC drivers installed on your computer for the phone?
Click to expand...
Click to collapse
I can get in my rom, i do have debug enabled and installed the htc drivers, i hear the sound when i plug my phone in and it reconizes it when i turn on the storage mode to make it a hard drive, im running win 8 if that matters.
But for some reason it isnt comig up in device manager

Would anyone know as to why ADB isnt seeing my phone?

bump*

With the help of someone I was able to find out what the problem was. I had to install a earlier version of the HTC drivers and use the ADB RegFix driver for windows 8. And the reason why we couldn't get into recovery was because the version of TWRP I installed wouldnt work with the version of my HBoot. So I had to find the version of TWRP so I could then be able to use recovery. I hope this helps someone If they have the same issue sometime.