Oh how i loathe this POS phone
i have this as my work support phone. It wouldn't reliably stay powered up, any time I did turn it on it took 20+ minutes to acquire data/cell/3g signal. turning on maps crashed the phone. so i figured i'd install a new rom
I have lots of experience with sony ericsson, nexus 4, nexus 7 2012, 2013, acer 10.1 tab. i've done all this stuff before, but i cannot get cyanogen 10 or 11 to install properly, and now my phone sits with a spinning logo doing nothing
i:
unlocked the bootloader as per instructions at htc dev
setup ADB on the phone
first jsut copied the c11.zip to the sd card and tried to install that, same issue on with the HTC logo
used hansoon's kit to sideload c10. claims to have installd, now just spins the logo.
any help would be great.
simonsgray said:
Oh how i loathe this POS phone
i have this as my work support phone. It wouldn't reliably stay powered up, any time I did turn it on it took 20+ minutes to acquire data/cell/3g signal. turning on maps crashed the phone. so i figured i'd install a new rom
I have lots of experience with sony ericsson, nexus 4, nexus 7 2012, 2013, acer 10.1 tab. i've done all this stuff before, but i cannot get cyanogen 10 or 11 to install properly, and now my phone sits with a spinning logo doing nothing
i:
unlocked the bootloader as per instructions at htc dev
setup ADB on the phone
first jsut copied the c11.zip to the sd card and tried to install that, same issue on with the HTC logo
used hansoon's kit to sideload c10. claims to have installd, now just spins the logo.
any help would be great.
Click to expand...
Click to collapse
You give a lot of info in your sig, but nothing there or in your post if you're s-off or on and which recovery you're using. Since, you're Canadian you probably need s-off to flash the latest T-Mobile ruu for the radio. And ext4 seems to be the most trouble-free recovery for the amaze. If s-on you can probably still get CM working if you were already on ICS and flash with smart flash enabled in 4ext. If you're still having issues then try pushing the kernel with adb from hboot wth your pc.
I hope this helps.
Odysseus1962 said:
You give a lot of info in your sig, but nothing there or in your post if you're s-off or on and which recovery you're using. Since, you're Canadian you probably need s-off to flash the latest T-Mobile ruu for the radio. And ext4 seems to be the most trouble-free for the amaze. If s-on you can probably still get CM working if you were already on ICS and flash with smart flash enabled in 4ext. If you're still having issues then try pushing the kernel with adb from hboot wth your pc.
I hope this helps.
Click to expand...
Click to collapse
Thanks man. sig is a little out of date, i havent' needed xda as much since jumping to nexus. TWRP and i didn't do the s-off stuff. it says it needs a stock rom and i just havea spinning cyanogen mod. i will try install the 4ext and see if that changes the results.
Odysseus1962 said:
You give a lot of info in your sig, but nothing there or in your post if you're s-off or on and which recovery you're using. Since, you're Canadian you probably need s-off to flash the latest T-Mobile ruu for the radio. And ext4 seems to be the most trouble-free recovery for the amaze. If s-on you can probably still get CM working if you were already on ICS and flash with smart flash enabled in 4ext. If you're still having issues then try pushing the kernel with adb from hboot wth your pc.
I hope this helps.
Click to expand...
Click to collapse
Tried to install this RUU http://www.androidruu.com/getdownlo...1.41.661.3_release_258801lhwl8053lp8g5hcp.zip
but i get an error status 7 because the file_getprop assert fails.
was trying to install stock so i can do th s-off thing
simonsgray said:
Tried to install this RUU http://www.androidruu.com/getdownlo...1.41.661.3_release_258801lhwl8053lp8g5hcp.zip
but i get an error status 7 because the file_getprop assert fails.
was trying to install stock so i can do th s-off thing
Click to expand...
Click to collapse
If you want to flash back to the stock ICS image you need to first relock your bootloader. When you relock it will say relocked when in hboot. The procedure is to place the image in the root of your external SD card and select from hboot. It should recognize and flash back to stock, however everything other than your external SD gets wiped in the process. So you need to make sure you have a good recent backup. Also, you remember when you first HTC dev unlocked they sent you an image to push to unlock? Well, I hope you saved it, because you'll need it again to re-unlock the bootloader after flashing the firmware image, but before attaining s-off.
However, if you were already on your carrier's latest ICS firmware before you started flashing different ROMs, you probably already have their latest radio. If you install the latest 4ext and enable smart flash, you'll probably succeed in installing any of the source built ROMs (ASOP, CM, PACman, evervolv) without s-off, because ROMs built from the source don't have the CID flag in their binaries.
If you still decide to go back and attain s-off the procedure is as follows: 1) relock your bootloader 2) flash the latest stock firmware for the carrier that sold your device. 3) Unlock your bootloader again using the image and commands you previously did to HTC dev unlock the first time, 4) get s-off using the wire-trick 5) flash the hacked hboot (and another radio if you desire, but not required for most ROMs) 6) super CID to remove all carrier locked file / partition limitations and protections 7) Flash your preferred recovery. Because you're now s-off you can use TWRP, CWM, or 4ext since the protected partitions are no longer an issue. 8) Flash any ROM you want provided it's based on ICS or later (below won't work because the radio is incompatible).
Edit: One other thing to note before starting any of this make sure your battery is fully charged. Also, the first time you boot after installing CM or any ASOP based ROM it can take quite some time to go through the process before you get to the login screen. For me it usually takes a little under 10 mins. It may at first appear to be a little sluggish until the rom settles, usually about 10-15 mins.
I hope this helps
Related
I'm running clean-Rom standard ICS with s-on. I can't seem to flash any other roms with s-on without my phone rebooting constantly. I can't even make a backup of my phone successfully from recovery or Rom manager. I love the Rom and have root but would like to try other roms. How do I get s-off from where I am currently? Do I have to relock my boot loader through HTC and if so what order does this fall in the process to attaining s-off?
Use the toolkit from below link
http://forum.xda-developers.com/showthread.php?t=1696394
no need to relock bootloader and as follow instructions mentioned in that toolkit. You can select any item from list and click button below
Thanks I'll try that when I get home today
jenkies said:
I'm running clean-Rom standard ICS with s-on. I can't seem to flash any other roms with s-on without my phone rebooting constantly. I can't even make a backup of my phone successfully from recovery or Rom manager. I love the Rom and have root but would like to try other roms. How do I get s-off from where I am currently? Do I have to relock my boot loader through HTC and if so what order does this fall in the process to attaining s-off?
Click to expand...
Click to collapse
If you don't want to go s-off, your rebooting might be caused by failure to flash the GB firmware patch after flashing rom and boot.img. You didn't say, but if you are still on GB firmware (never flashed an ICS leak), you do have to flash the firmware patch each time you flash a rom.
The guide worked, little tricky with the wire thing and all. Wasnt expecting that and had to leave my phone plugged up and go to use someone else's internet to learn about that because the phone wouldn't complete the s off until I did...pretty interesting, but everything worked. I'm not sure if I should have but I also flashed the modified hboot at the end of the procedure.
jenkies said:
The guide worked, little tricky with the wire thing and all. Wasnt expecting that and had to leave my phone plugged up and go to use someone else's internet to learn about that because the phone wouldn't complete the s off until I did...pretty interesting, but everything worked. I'm not sure if I should have but I also flashed the modified hboot at the end of the procedure.
Click to expand...
Click to collapse
Yikes! Glad it all worked smoothly! The modified hboot is ok. Now, no need to unlock bootloader so leave it locked.
It sounds like (but you didn't say so) you are still on GB firmware. If you haven't flashed a leaked ICS RUU, that would be the case. If you flash ICS roms follow the directions because you'll also have to flash the GB/SD Card patch or else you'll have problems like you experienced. ICS uses different mount points on the SD card and the patch corrects that for those of you still on GB firmware.
I am an unfortunate rookie, and have made mistakes, hence the name. I want to return my phone to stock from htcdev unlock, s-on, hboot 1.5. with a boot loop on meanom ICS for the evo 3d. I have tried to use older ruu shooters. Relock with fastbot oem lock, and then pg86img. However with the bootloop I can not access anything unless I unlock again, and then go into recovery. This is all that I can think of at the moment that might help.
Kill the rookie!!! PLEASE HELP!!
I had much the same problem with my cdma, hboot 1.5, S-On shooter. When I was S-On none of the ICS roms would work. The all bootlooped on me. If you follow the rooting method found here on xda, it will get you back to a stock Rooted GB Rom.
go into hboot -> fastboot USB-> run command dos -> fastboot cwm-4.0.1.4-shooter.IMG -> flash the 2.17 firmware-> enjoy.
I had to S-off with Juopunutbear, then re-run that root/flash to get past the bootloops.
Sent from my Shooter using xda app-developers app
Unfortunately I have tried that and it still is not working.
My only suggestion would be to try it a few times, other then that, its above my head.
Sent from my shooter using xda app-developers app
rookiemistake said:
I am an unfortunate rookie, and have made mistakes, hence the name. I want to return my phone to stock from htcdev unlock, s-on, hboot 1.5. with a boot loop on meanom ICS for the evo 3d. I have tried to use older ruu shooters. Relock with fastbot oem lock, and then pg86img. However with the bootloop I can not access anything unless I unlock again, and then go into recovery. This is all that I can think of at the moment that might help.
Kill the rookie!!! PLEASE HELP!!
Click to expand...
Click to collapse
Have you tried one of the ruu exe files that you run from your computer? If you are trying to go stock, you should be able to relock the bootloader and run the ruu and that's it.
Sent from my ICS 3VO with Tapatalk 2
First of all I want to thank everyone that has been attempting to assist me with my problem. I have tried to relock since I am on htcdev unlock and then run an ruu force via my computer. I get an installation aborted error when trying to flash pg86img via recovery. I don't know what else to say.
You can't flash a bootloader zip from recovery. You have to flash it from hboot. Also make sure the zip is named correctly "PG86IMG.zip" without the quotes. Also make sure the zip is on the root of your sd as in not in any folders. Once you've named the zip correctly and placed it correctly then power off the phone. Hold down the volume down button and tap the power button. You should boot into the bootloader wait until the phone recognizes the zip and follow the on screen instructions. Hopefully this helps.
#Root-Hack_Mod*Always\=LTE
Thank you again. I tried your directions, it did recognize the pg86img. However it did not give me any instructions to follow. It did however allow me to be able to a partial stock state. My software version is still on the teamgenesis sense v2.9 cdma. Although I do like some of the features on this rom, I would still like to be able to get the OTA of ICS when it is released. Any suggestions?
rookiemistake said:
Thank you again. I tried your directions, it did recognize the pg86img. However it did not give me any instructions to follow. It did however allow me to be able to a partial stock state. My software version is still on the teamgenesis sense v2.9 cdma. Although I do like some of the features on this rom, I would still like to be able to get the OTA of ICS when it is released. Any suggestions?
Click to expand...
Click to collapse
To get the ota release (if it ever comes ) I do believe you will need to be locked and running the existing gingerbread rom. While I am not positive, I think the system uses the props file to determine if an update is applicable, and it will likely not recognize the teamgenesis rom version as being upgradeable.
Now I will likely get flames for saying this, but if you want to put the meanrom v2.4 of ICS on the phone, it can be done with s-on, you just need to follow the correct process. I ran that rom for a while, and it is very stock like, stable, and has a few enhancements that you will not find on a non-rooted stock rom. I never found anything wrong or not working with that rom.
To get it to load, first I downloaded flashimagegui from market, put the meanrom zip file on the sd card and made sure I had a recovery that I could get into. I am using TWRP v2.1.1, lots of folks talk about others like ext4, and I am only going to say use whichever you like, after all it is your phone.
Then with the phone unlocked via the htc method, I started the flashimage app, and browsed to the meanrom file. It extracted the kernel and flashed it. Once that was done, with clear cache buttons selected, rebooted to recovery, and used the install menu selection of TWRP to again flash the same rom file. Once it flashed the file, selected clear cache and dalvik just to be safe, selected reboot system, and it worked great.
Have a great weekend.
So, apparently I am still doing something wrong. I have put the pg86img on the root, relocked to the bootloader, and let it run it's course. However, it will get through with reading it and stops and does not finish anything with loading the system information. I have also tried to run the ruu via usb connection. I keep running into a c++ issue saying runtime error. I have wiped everything and thankfully I did make a backup of the rom and other information that I was runing so I can currently fall back on that.
I am on hboot 1.5, 2.17, and teamgenesis ICS rom for evo 3d.
Apparently there have been rumors that Sprint has finally released the ICS OTA, not that it really matters anymore, but I have run into a few interesting glitches, such as WIFI not staying connected while asleep or disconnecting.
If I have to I am willing to pay to do a netmeeing with someone in order to be able to fix this.
Sorry if it sounds like I am getting frustrated, but I have tried every walkthrough that I have found and have not had any luck with any of them.
Please help.
I forgot to say I am s-on
So, I tried rooting my device with the WinDroid tool. It all worked out fine until I got a custom recovery in.
I got the bootloader unlocked just fine. I'm not sure where I went wrong, but it wiped everything off my device (including the stock ROM. I was going to make a backup this time too... I usually forget).
So, I spent a heck of a long time just trying to get something on. The RUU for Telus is 1.5x and my current device is at 1.2.
I've pretty much resigned myself to waiting for the 1.2 RUU for telus to be released, but until then, is there a way that I can get at least a custom ROM on?
After some mucking I can finally get a .zip pushed to my SD and start to install it. My /system wouldn't mount for the longest time. I had to do a full wipe/format on all partitions to a) get access to my system partition and b) get access even to the internal memory.
I downloaded Elegancia 7.2 and I can get the installer to start and it seems to run just fine and it should be installed.
I fastboot'ed the boot.img. However I'm still just stuck at the white HTC screen.
What device info would you like besides what I've already stated? Am I just using the wrong ROM? If so, what roms are compatible with hboot 1.4?
My CID is TELUS001.
Also, when I try to reboot TWRP it's saying that there is no OS installed....
Rev.Tyler said:
So, I tried rooting my device with the WinDroid tool. It all worked out fine until I got a custom recovery in.
I got the bootloader unlocked just fine. I'm not sure where I went wrong, but it wiped everything off my device (including the stock ROM. I was going to make a backup this time too... I usually forget).
So, I spent a heck of a long time just trying to get something on. The RUU for Telus is 1.5x and my current device is at 1.2.
I've pretty much resigned myself to waiting for the 1.2 RUU for telus to be released, but until then, is there a way that I can get at least a custom ROM on?
After some mucking I can finally get a .zip pushed to my SD and start to install it. My /system wouldn't mount for the longest time. I had to do a full wipe/format on all partitions to a) get access to my system partition and b) get access even to the internal memory.
I downloaded Elegancia 7.2 and I can get the installer to start and it seems to run just fine and it should be installed.
I fastboot'ed the boot.img. However I'm still just stuck at the white HTC screen.
What device info would you like besides what I've already stated? Am I just using the wrong ROM? If so, what roms are compatible with hboot 1.4?
My CID is TELUS001.
Also, when I try to reboot TWRP it's saying that there is no OS installed....
Click to expand...
Click to collapse
Update -----------------
I'm a tool. I was using the international version of Elegancia.
So while in process of s-off once I got to the part when you "fastboot oem rebootRUU" that went through. But right after trying to flash a zip im stuck looking at the blk HTC screen. I was given a "<Failed <remote: 99 unknown fail>". Now its just stuck.
I've been trying to figure out what happened but just have no where else to turn. Please lend a hand.
I think I already know the answer to this question, but what version is your firmware? Just for your knowledge, there hasn't been an RUU since ICS, or maybe the first release of JB. So, odds are, you flashed the wrong RUU.
But good news, you *might* not be bricked. Have you tried rebooting? This really your only option, anyway. Try to get into the bootloader. Flash a new recovery if the RUU has already wiped it, and flash a compatible rom.
Please also list your bootloader info.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
aarsyl said:
I think I already know the answer to this question, but what version is your firmware? Just for your knowledge, there hasn't been an RUU since ICS, or maybe the first release of JB. So, odds are, you flashed the wrong RUU.
But good news, you *might* not be bricked. Have you tried rebooting? This really your only option, anyway. Try to get into the bootloader. Flash a new recovery if the RUU has already wiped it, and flash a compatible rom.
Please also list your bootloader info.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
Click to expand...
Click to collapse
It's not a full RUU in the normal sense. It's the one for Facepalm.
To the OP, did you gain SuperCID prior to running those commands? If not, then the process will fail. You should simply be able to hold the power button down & reboot your phone. Also, as stated above, list your device info so we can make sure you're using the right S-off exploit.
Sent from my HTC EVO 4G LTE
So I did get the phone into the bootloader. I was trying to do the rumrunner s-off but being I was so damn tired lastnight I ended up forgetting a step. I am currently unlocked and rooted. I also somehow deleted my backup like a idiot and wiped the os. So I'm stuck from this point where I need to go.
So where we stand as of now:
bootloader unlocked
rooted
twrp 2.6.3.0
firmware 3.17.651.4
hboot 2.09
radio 1.13.11.0830
z3r0t0l0rEnCe said:
So I did get the phone into the bootloader. I was trying to do the rumrunner s-off but being I was so damn tired lastnight I ended up forgetting a step. I am currently unlocked and rooted. I also somehow deleted my backup like a idiot and wiped the os. So I'm stuck from this point where I need to go.
So where we stand as of now:
bootloader unlocked
rooted
twrp 2.6.3.0
firmware 3.17.651.4
hboot 2.09
radio 1.13.11.0830
Click to expand...
Click to collapse
Happens to all of us. Don't worry about wiping the OS. Look for Captain Throwback's stock rooted rom, and flash a custom kernel along with it, like the Dirty MAC kernel or Arc reactor. Doesn't matter which one...rumrunner just needs a custom kernel.
Captain Throwback's stock 3.17 base
http://forum.xda-developers.com/showthread.php?t=2468418
Dirty MAC kernel
http://forum.xda-developers.com/showthread.php?t=2178307
Arc Reactor
http://forum.xda-developers.com/showthread.php?t=1873824
After you flash these, then reboot into Android, set your phone to stay awake during charge Settings-->Display and Buttons, and also set SuperSU to automatically grant root access (open the app, swipe right twice, and scroll down a little). This way, you don't have to touch your phone. If you touch it, the process will fail....even to unlock the phone to grant root access. And of course, turn on USB debugging in Developer Options.
After you do all of these, then run the exploit.
aarsyl said:
Happens to all of us. Don't worry about wiping the OS. Look for Captain Throwback's stock rooted rom, and flash a custom kernel along with it, like the Dirty MAC kernel or Arc reactor. Doesn't matter which one...rumrunner just needs a custom kernel.
Captain Throwback's stock 3.17 base
http://forum.xda-developers.com/showthread.php?t=2468418
Dirty MAC kernel
http://forum.xda-developers.com/showthread.php?t=2178307
Arc Reactor
http://forum.xda-developers.com/showthread.php?t=1873824
After you flash these, then reboot into Android, set your phone to stay awake during charge Settings-->Display and Buttons, and also set SuperSU to automatically grant root access (open the app, swipe right twice, and scroll down a little). This way, you don't have to touch your phone. If you touch it, the process will fail....even to unlock the phone to grant root access. And of course, turn on USB debugging in Developer Options.
After you do all of these, then run the exploit.
Click to expand...
Click to collapse
This is odd to me, because I ran rumrunner at least 3 times using just my stock ROM (no custom kernel or anything), and it worked fine every time. I guess the new version of rumrunner added some limitations to make it more generic.
whats bothering me is that even after i check the MD5, it keeps failing to install capt zip. think maybe i can just use adb to push the zip file? just not sure how to word the command right to get it to load
z3r0t0l0rEnCe said:
whats bothering me is that even after i check the MD5, it keeps failing to install capt zip. think maybe i can just use adb to push the zip file? just not sure how to word the command right to get it to load
Click to expand...
Click to collapse
No, don't. If it fails, don't force it. Reflash TWRP 2.6.3 (not the kit kat version), and try to flash again.
@Captain_Throwback: Yes, I didn't remember needing a custom kernel when I used Dirty Racun, but rumrunner needs it now. Keep in mind that rumrunner isn't for this device exclusively. Maybe that's the purpose of the custom kernel.
i'd wager you're trying to flash files that aren't recovery flashable, then lying to the people who are trying to help you.
i got it running again using capt stock rooted rom. attempting rumrunners s-off again now that i got this part working.
Are you using a custom kernel?
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
now s-off and updated rumrunners hboot. now onto flashing roms finally.
Thank you all that helped me with my stupidness and not reading directions.
Last post. I can't say it enough that you must read read read when it comes to directions. If I would of followed directions as directed I would of never ran into the issues I did. It was a learning experience.
One thing for sure that I took from this experience is adb and directions. I've learned a lot in the last 24hrs alone.
I'd like to thank Capain_throwback and everyone in the irc for the help and you all here that assisted me.
Sent from my EVO using XDA Premium 4 mobile app
i bought the m8 on att froma guy on craigslist i cant figure out how to unroot it ive tried installing skydragon a maximus but i cant get pass the htc boot screen ive tried updating the twrp to the newest and no i dont have a recovery ive even tried downgrading to an older one any help?? edit!! i cant get pass the boot screen i had cwm and tried installing stock att firmware please help
Jduncan312 said:
i bought the m8 on att froma guy on craigslist i cant figure out how to unroot it ive tried installing skydragon a maximus but i cant get pass the htc boot screen ive tried updating the twrp to the newest and no i dont have a recovery ive even tried downgrading to an older one any help?? edit!! i cant get pass the boot screen i had cwm and tried installing stock att firmware please help
Click to expand...
Click to collapse
What does your heart really want? Do you want to run custom ROMs and have root or not? It mostly sounds like you may want to return to stock due to lack of understanding and knowledge. That's okay if you want to do that. But kinda against the spirit of XDA!
Relock the bootloader and RUU will return the phone to stock and unrooted.
But it just sounds like you have mismatched firmware (results in long boot times with no boot animation, which some folks mistake for it not being booted).
Also, the newest TWRP require updated hboot, so that is probably the problem there.
If you want the phone rooted, and running a custom ROM: either run a ROM that corresponds with your firmware, or s-off and update your firmware.
What hboot and radio numbers? S-on or S-off?
redpoint73 said:
What does your heart really want? Do you want to run custom ROMs and have root or not? It mostly sounds like you may want to return to stock due to lack of understanding and knowledge. That's okay if you want to do that. But kinda against the spirit of XDA!
Relock the bootloader and RUU will return the phone to stock and unrooted.
But it just sounds like you have mismatched firmware (results in long boot times with no boot animation, which some folks mistake for it not being booted).
Also, the newest TWRP require updated hboot, so that is probably the problem there.
If you want the phone rooted, and running a custom ROM: either run a ROM that corresponds with your firmware, or s-off and update your firmware.
What hboot and radio numbers? S-on or S-off?
Click to expand...
Click to collapse
my hboot is 3.16.0 not sure about the s on and off thing but yeah iw ould love to run roms on it I tried downloading the skydragon 5.0.1 on it but it was stuck at the boot screen im using clockwork mod but I cant get twrp back on because I cant boot into the phone and ive tried everything to install the drivers and ive tried to manually install them also but no luck if you can email me or something to help me out it would be great!! [email protected]
Jduncan312 said:
my hboot is 3.16.0 not sure about the s on and off thing but yeah iw ould love to run roms on it I tried downloading the skydragon 5.0.1 on it but it was stuck at the boot screen im using clockwork mod but I cant get twrp back on because I cant boot into the phone and ive tried everything to install the drivers and ive tried to manually install them also but no luck if you can email me or something to help me out it would be great!! [email protected]
Click to expand...
Click to collapse
Holy run-on sentence! Seriously, please take the time to type a proper response with punctuation. Making it easier to read, makes it easier for me to help you. And that is what you want, isn't it???
I don't use my personal email for this type of support. That is what these forums are for.
Skydragon is probably not "stuck" but rather taking an extremely long time to boot (10+ minutes) with no boot animation, which often leads folks to believe its stuck altogether. If you leave it alone, it will probably boot eventually, but you may also find that WiFi is broken. Both are symptoms of the wrong firmware for the ROM you flashed.
Your hboot number also indicates that you don't have the right firmware installed, as firmware includes hboot as well as radio, WiFi, Bluetooth, and other modules.
On the AT&T variant, you will not have any "official" way to update the firmware to anything more up-to-date than 2.x firmware (hboot 3.17). You need 4.x firmware (hboot 3.19) to run the ROM you mentioned. Therefore you need s-off by sunshine (if not s-off already).
You can check s-on or s-off by booting into bootloader, and you will see it says one of the other near the top of the screen.
Alternately, if you don't s-off, you can flash a ROM that corresponds to your firmware. Try the following ROM, but putting the ROM zip on a removable SD card using a card reader connected to your computer (if you have those available). Then boot into recovery,navigate to the file and flash: http://forum.xda-developers.com/showthread.php?t=2705640
Aside from that, you should really get your USB connectivity issue sorted out. You can't do much without it. Verify no response when you type fastboot devices when the phone is in fastboot mode. If it doesn't respond (should return device ID) then try a different USB cable, and different USB port. If on Windows, try going to Device Manager, finding the phone, and pick the option to manually select the drivers, than pick the USB MTP drivers (not the HTC ones). This will often fix adb/fastboot connectivity issues.