Database Info

Can't flash anything, RUU isn't working.

So, I used to be an Android expert and knew what was wrong just by the symptoms of the problem, having had an iPhone for about 4 months has changed all that. I'm still familiar with some of the stuff, fast boot, installing a recovery, mostly basic things, so I come here to the community I uses to help in.
Here's my issue: Viper ROM was installed, and I wanted to try out Rebel ROM. Downloaded it, but wouldn't connect to my computer through the ROM, so I booted to recovery to mount the internal storage.
It wouldn't flash, stating an error, tried CleanROM, same error. Now there's no OS on the phone, so I decided to RUU so I'd have something too work with.
Its on 2.20 so I downloaded that one, and program ran fine till it told me there was an error and so I can't even have a stock ROM.
TL;DR It can boot to recovery, fast boot, but can't flash a ROM or RUU. Any ideas? Thanks guys for your replies.
Sent from my Nexus 7 using Tapatalk 2

Did you try extracting the boot.IMG from the ROM, fastboot flash boot.img. if your on 1.14 Hboot you'll need to do this.
Sent from my HOX w/CM10.1 4.2.2 s-off

The error is because you didn't lock your bootloader before running the ruu fastboot oem lock

subarudroid said:
Did you try extracting the boot.IMG from the ROM, fastboot flash boot.img. if your on 1.14 Hboot you'll need to do this.
Sent from my HOX w/CM10.1 4.2.2 s-off
Click to expand...
Click to collapse
I am on hboot 1.14, can I use XsMagicals program? I'd rather use the ADB commands but I've forgotten them.

a box of kittens said:
The error is because you didn't lock your bootloader before running the ruu fastboot oem lock
Click to expand...
Click to collapse
Oh, thank you sir! I'll look up how to do that.
There's no way to downgrade the hboot, is there?

Flashing boot imgs can only be done through fastboot without s off(which I highly recommend you do) but tutorial on fastboot coming up!
---------- Post added at 10:48 PM ---------- Previous post was at 10:47 PM ----------
Flashing boot img through fastboot...
download the file in the link which above which will include adb and fastboot....put that on your computer somewhere you can find it.. now take the boot image out of the Rom zip and place it in that folder... Boot your phone into bootloader scroll down and select fastboot and now open a command prompt with in the fastbootbadb folder on your comp and type to command without the quotes "fastboot flash boot boot.img"...now go wipe in recovery and install the Rom it doesn't matter if you keep the boot img in the Rom zip or not

a box of kittens said:
Flashing boot imgs can only be done through fastboot without s off(which I highly recommend you do) but tutorial on fastboot coming up!
Click to expand...
Click to collapse
My device is S-ON, so I should S-OFF it?
And no way to downgrade the hboot? I know you can't RUU down to an earlier version because of this.

http://forum.xda-developers.com/attachment.php?attachmentid=1179735&d=1344782533 here is the download link
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
theking_13 said:
My device is S-ON, so I should S-OFF it?
And no way to downgrade the hboot? I know you can't RUU down to an earlier version because of this.
Click to expand...
Click to collapse
Yes s off makes things 100 x easier and without s off you can't downgrade hboot through ruu

Thank you sir! With S-OFF, I can RUU back to an earlier version? I tried searching through the dev section, I mostly found ROMs, and a couple mods.

http://forum.xda-developers.com/showthread.php?t=2155071 here is our s off thread very easy after that you can flash the ruu and it will downgrade your hboot... I recokmend you flash to viper than you do s off..but I'll link you to the ruu thread in a sec
---------- Post added at 10:57 PM ---------- Previous post was at 10:55 PM ----------
http://www.androidfiles.org/ruu/?dir=Evita all the ruus... Get the att 1.85 ruu

theking_13 said:
I am on hboot 1.14, can I use XsMagicals program? I'd rather use the ADB commands but I've forgotten them.
Click to expand...
Click to collapse
Yes you can. But I'd go with what kitten says. S-off = happiness with flashing ROMs to your hearts content.
Sent from my HOX w/CM10.1 4.2.2 s-off

I keep sending the boot.img to the HOX via ADB, but when I try to install it in TWRP, I still get that same error. What am I missing here guys?

Turn off the md5 check before u flash the ROM zip
Sent from my HOX w/CM10.1 4.2.2 s-off

subarudroid said:
Turn off the md5 check before u flash the ROM zip
Sent from my HOX w/CM10.1 4.2.2 s-off
Click to expand...
Click to collapse
In the settings? Nothing is checked, and when I flash the ROM, the option that says "Zip file signature verification" is also unchecked.

Here's the error I get.
Code:
E: error in sdcard/CleanROM JL Beta 1.zip
(Status 1)
Error flashing zip 'sdcard/CleanROM JL Beta 1.zip'
Updating partition details...
[COLOR="Red"]Failed[/COLOR]

Nvm, fixed it! Thanks to both of you, couldn't have done it without your input.

[Q] help me HTC one s , reload 4.1.1

i tried to install maxsimus 10 sense 5, but i missed get s off and my mobile does not open,, i do unlocked and hboot 2.15.0000 and radio 1.15.50.05.29. and i only öpen bootloader... please help me thanks...

Ok, here we go. Good to see you're still on 2.15 bootloader and 1.15 radio. So nothing bad has happened.
Guess your phone doesn't boot behind the htc screen, so all your files on internal memory are deleted?
---------- Post added at 11:53 PM ---------- Previous post was at 11:38 PM ----------
You'll find an appropriate backup here.
Simply download the following files:
openrecovery-twrp-2.3.3.0-ville.img
blabla_htc_stock_3.16.401.8.zip
Boot into fastboot mode, fastboot flash twrp 2.3.3.0 by typing 'fastboot flash recovery openrecovery-twrp-2.3.3.0-ville.img' from your android working directory (usually the directory where fastboot.exe and adb.exe are stored).
Mount your internal sd card from twrp 2.3.3.0 copy the unzipped files into the right directory and restore. Done.

I'm in the same boat. hboot 2.15 and radio 1.13 here. S-OFF and SuperCID.
Tried your steps above, and while I get a little further with the stock restore images you provide (Rosie even comes up!), process system stops responding, and the phone reboots in a couple of minutes.
Any suggestions?

You can start from the beginning install RUU.
Appropriate RUU can be downloaded from androidruu com, you should be locked before run.
To lock a phone:
power off
power on with volume down
from pc run "fastboot oem lock"

Yes.
Also I'm not shure about relocking. I usually restore stock recovery without relocking my phone before running any RUU. It even stays unlocked after the process (S-OFF!). But relocking isn't a big thing so, even it's for just being on the right side.
I forgot a main thing in my above answer: You must run factory reset from bootloader before restoring. Thats the point the backup hangs with rosie after restore. Factory reset with twrp isn't enough.

rootrider said:
Yes.
Also I'm not shure about relocking. I usually restore stock recovery without relocking my phone before running any RUU. It even stays unlocked after the process (S-OFF!). But relocking isn't a big thing so, even it's for just being on the right side.
I forgot a main thing in my above answer: You must run factory reset from bootloader before restoring. Thats the point the backup hangs with rosie after restore. Factory reset with twrp isn't enough.
Click to expand...
Click to collapse
I ran factory reset and clear storage both before flashing TWRP and running the restore.
Process system isn't responding after awhile when starting up, and then it reboots a minute later
RUU restores don't work. They flash fine, but when booting, it hangs at white HTC screen with the "Preparing phone storage" message before rebooting. S-OFF usually bypasses relock requirement for RUUs.

Could you simply try HTC__001 as cid?
fastboot oem writecid HTC__001
And flash boot.img from the backup from fastboot?
fastboot flash boot boot.img
That new partition layout seems to mess everything up...
Which recovery are you using? You should use TWRP 2.3.3.0 for restoring.

rootrider said:
Could you simply try HTC__001 as cid?
fastboot oem writecid HTC__001
And flash boot.img from the backup from fastboot?
fastboot flash boot boot.img
That new partition layout seems to mess everything up...
Which recovery are you using? You should use TWRP 2.3.3.0 for restoring.
Click to expand...
Click to collapse
I'm using TWRP 2.3.3.0 for restoring, yes.
I've fastboot flash boot boot.img with no result. I can try the oem writecid.

muriani said:
I'm using TWRP 2.3.3.0 for restoring, yes.
I've fastboot flash boot boot.img with no result. I can try the oem writecid.
Click to expand...
Click to collapse
Sounds like a file or files in /system is messed up?
I'm guessing you can still access twrp/cwm recovery, if so could the following scripts help (deep cleanse your device)?
http://forum.xda-developers.com/showthread.php?t=2121584
Then you could just flash a custom_rom .zip ?
I'd run the Superwipe first, then again a second time then a third just to be on the safe side, that or I have OCD!
Then run the Kernel script, once all done reboot back into recovery then install the custom_rom .zip. If you don't have a custom_rom.zip on your internal just mount usb and transfer it across.
Hope that helps.

Sounds like a mess described in this thread.
@muriani: Have you been on MaximusHD before?
Maybe you should reinstall MaximusHD then and follow the procedure over there to fall back to a previous state. I'll try that myself tonight (UTC+2) as I need a working phone for today.

rootrider said:
Ok, here we go. Good to see you're still on 2.15 bootloader and 1.15 radio. So nothing bad has happened.
Guess your phone doesn't boot behind the htc screen, so all your files on internal memory are deleted?
---------- Post added at 11:53 PM ---------- Previous post was at 11:38 PM ----------
You'll find an appropriate backup here.
Simply download the following files:
openrecovery-twrp-2.3.3.0-ville.img
blabla_htc_stock_3.16.401.8.zip
Boot into fastboot mode, fastboot flash twrp 2.3.3.0 by typing 'fastboot flash recovery openrecovery-twrp-2.3.3.0-ville.img' from your android working directory (usually the directory where fastboot.exe and adb.exe are stored).
Mount your internal sd card from twrp 2.3.3.0 copy the unzipped files into the right directory and restore. Done.
Click to expand...
Click to collapse
ok thankyou for help but i did wrong things and my super user off, in recovery mode, i want to rebbot and start bootloader there is no OS is writen... i think its bad news for me(

super awesome
gilgamess said:
ok thankyou for help but i did wrong things and my super user off, in recovery mode, i want to rebbot and start bootloader there is no OS is writen... i think its bad news for me(
Click to expand...
Click to collapse
hey you are my man dute,, it works... i rescue my mobile thankyou very much...

rootrider said:
Sounds like a mess described in this thread.
@muriani: Have you been on MaximusHD before?
Maybe you should reinstall MaximusHD then and follow the procedure over there to fall back to a previous state. I'll try that myself tonight (UTC+2) as I need a working phone for today.
Click to expand...
Click to collapse
MaximusHD doesn't work for me at all.
I've wiped /system numerous times, I'll go back and try the superwipe as well though.
I've never had such trouble getting a freaking android phone to boot.

Nothing I've loaded seems to work. I've reset CID, factory reset after the restore, and all I get is "preparing phone storage", reboot, and then black screen with statusbar that eventually reboots.
I've nearly given up hope.

Well, as a last resort, I set CID to T-MOB010 (stock for my phone), ran the latest RUU for T-mobile, and same result.
I've given it up for lost.
EDIT: HOLY F*CKBALLS.
So, I didn't give up after all. Found a couple of other threads, and apparently yes, you have to relock, reset CID, AND go S-ON (fastboot oem writesecureflag 3) and then run the RUU.
I have a stock fresh TMOUS 4.1.1 One S now.

Well, if there is nothing else left, I think I'd have tried the same, because there is nothing to loose. Btw, which s-off did you do before: Moonshine or Facepalm?
Can/will you s-off your device again?

rootrider said:
Well, if there is nothing else left, I think I'd have tried the same, because there is nothing to loose. Btw, which s-off did you do before: Moonshine or Facepalm?
Can/will you s-off your device again?
Click to expand...
Click to collapse
I honestly don't remember which I used. I *think* it was Facepalm.
S-OFF will require SuperCID, which I really don't feel like going through again.
I tried just a basic update to the UnKnown JB 2.0 Sense rom and the thing didn't boot, so I think I may be stuck on stock+root for awhile.
Also, I'm noticing some pretty severe flakiness in the cell radio now. Full bars, I'd be trying to use data but there's just no traffic. Can't even play a 64kbps mp3 stream reliably with full bars 4G.

Hey i am using sense 5, rootroder helped me to rescue my mobile install 4.1.1 again, thank you very much...
And i use his advice doing super cid and s off and ite work... İ want to ask last thing, my htc is htc__102 from germany,, had i been needed to get supercid and s off with my mobile...
Sent from my HTC One S using xda app-developers app

rootrider said:
Ok, here we go. Good to see you're still on 2.15 bootloader and 1.15 radio. So nothing bad has happened.
Guess your phone doesn't boot behind the htc screen, so all your files on internal memory are deleted?
---------- Post added at 11:53 PM ---------- Previous post was at 11:38 PM ----------
You'll find an appropriate backup here.
Simply download the following files:
openrecovery-twrp-2.3.3.0-ville.img
blabla_htc_stock_3.16.401.8.zip
Boot into fastboot mode, fastboot flash twrp 2.3.3.0 by typing 'fastboot flash recovery openrecovery-twrp-2.3.3.0-ville.img' from your android working directory (usually the directory where fastboot.exe and adb.exe are stored).
Mount your internal sd card from twrp 2.3.3.0 copy the unzipped files into the right directory and restore. Done.
Click to expand...
Click to collapse
OK, What is the "right directory"

In your mobile phone's storege... Like 9.00 gb
Sent from my HTC One S using xda app-developers app

[Q] Can not access recovery

I have a HTC ONE X LTE - Rogers. I was running hboot 1.11 with Viper Custom ROM. I decided it was time to update my rom but I have not done any flashing in a while. I tried installing the newest Revolution HD ROM without any luck and realized it maybe because my hboot was out of date. So I tried to re-lock my bootloader and flash a newer RUU with JB but I feel like this is where I went wrong. I think I flashed the wrong RUU. I can no longer boot into Recovery. Even if I try flashing for it again I still can not boot into it.
Its status is currently UNLOCKED, hboot is 2.14. I don't want to mess this up, what do I do now?
Version-main 3.17.631.2
When I run fastboot and adb commands, fastboot works but it isn't recognized as a device for adb commands.
Windroid HTC One XL Toolkit:
Android Version: Not Found!
Sense Ver: Sense ROM not installed!
SU Version : Not Rooted!
Busybox: No Busybox Found
Carrier: Not found!

Revolution HD isn't for our phone, that's for the Endeavoru (HTC One X), you have the Evita (HTC One XL). You're lucky you didn't brick the phone.
After the RUU does the phone boot up into Android? Have you manually flashed TWRP recovery since you ran the RUU?
Sent from my Evita

timmaaa said:
Revolution HD isn't for our phone, that's for the Endeavoru (HTC One X), you have the Evita (HTC One XL). You're lucky you didn't brick the phone. Also, which RUU did you run?
Sent from my Evita
Click to expand...
Click to collapse
Yeah... I realize the differences now. Even posted asking for help on the wrong board till they redirected me to this one. Hmm I was on this thread
http://forum.xda-developers.com/showthread.php?t=1859714
and Im pretty sure I downloaded this file
http://www.androidruu.com/getdownlo...128.32.34a_release_299850qstr7rxdbfuofl6j.zip
and inside that I extracted the firmware.zip and flashed that onto my then RE-locked phone.
Everything was fine except I was following another thread that stated how and I just typed the commands. The guy said after it said "Okay" in the cmd window it was fine but on my phone the progress bar didn't go all the way and was actually stuck on the last bit for a good while so I thought since he said it was "okay" it was done and I restated my phone. Thats when the problems came.

That's a zip file so it's an OTA, not an RUU, an OTA will not work unless you already have the correct system already installed for it to build on. An RUU is an exe file. Go back to androidruu and download an RUU exe file then connect your phone in fastboot mode and run the exe program. Don't extract it, just run the program.
Sent from my Evita
---------- Post added at 04:12 PM ---------- Previous post was at 04:11 PM ----------
Also, that thread you linked to is in the wrong forum, you don't have that phone. Don't ever go to that forum (or any forum other than this one), stay in this forum that you're posting in now or you're gonna brick your phone.
Sent from my Evita

timmaaa said:
That's a zip file so it's an OTA, not an RUU, an OTA will not work unless you already have the correct system already installed for it to build on. An RUU is an exe file. Go back to androidruu and download an RUU exe file then connect your phone in fastboot mode and run the exe program. Don't extract it, just run the program.
Sent from my Evita
---------- Post added at 04:12 PM ---------- Previous post was at 04:11 PM ----------
Also, that thread you linked to is in the wrong forum, you don't have that phone. Don't ever go to that forum (or any forum other than this one), stay in this forum that you're posting in now or you're gonna brick your phone.
Sent from my Evita
Click to expand...
Click to collapse
Oh ok, cool. Is there a difference between Evita and EvitaRE? Is it ok if the RUU is a lower number(Im assuming a less up to date) firmware than the one I have right now? Then what should I do after? What Custom rom would you recommend? I was thinking a stable CM rom since I really like the look of AOSP. My only problem was I tried it before and my battery only lasted around 6 hours. With Viper I could get around 7-14 depending on usage.
When I run the RUU (1.0.6.2012) it says From :IMG V 3.17.631.2 To: Image V 1.94.631.3. Is this correct?

Evita and EvitaRE are two completely different phones. Only ever use ROMs/kernels/radios/RUUs that are for Evita specifically. You can't run an older RUU if you're s-on, are you s-on or s-off? Asking for a recommended ROM isn't allowed here, to say one is better infers that the others are inferior in some way. This isn't fair on the devs who spend their spare time bringing us great ROMs free of charge. You need to have a look through the ROMs on offer and find one you think you'll like. Also I asked you before if you've tried flashing TWRP recovery with fastboot? You never answered.
Sent from my Evita
---------- Post added at 04:34 PM ---------- Previous post was at 04:32 PM ----------
It looks like you're running an older RUU, are you s-off?
Sent from my Evita

timmaaa said:
Evita and EvitaRE are two completely different phones. Only ever use ROMs/kernels/radios/RUUs that are for Evita specifically. You can't run an older RUU if you're s-on, are you s-on or s-off? Asking for a recommended ROM isn't allowed here, to say one is better infers that the others are inferior in some way. This isn't fair on the devs who spend their spare time bringing us great ROMs free of charge. You need to have a look through the ROMs on offer and find one you think you'll like. Also I asked you before if you've tried flashing TWRP recovery with fastboot? You never answered.
Sent from my Evita
---------- Post added at 04:34 PM ---------- Previous post was at 04:32 PM ----------
It looks like you're running an older RUU, are you s-off?
Sent from my Evita
Click to expand...
Click to collapse
I am S-ON. Sorry about that, didn't realize. Yes I did try flashing TWRP recovery with fastboot but I am not able to acces it and I am not sure if I am flashing it correctly. I just put it into the folder with my fastboot files and cmd fastboot flash recovery recovery.img (I renamed it to recovery.img)
I downloaded RUU 1.0.6.2012 (it was the only exe in the list for my region) and I tried installing it. I get an Error 155:Unknown error. Telling me to get the correct RUU and try again.

Where did you download TWRP? Maybe we should start again to make sure you've got the right version. Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now hopefully you can enter recovery on your phone.
Sent from my Evita
---------- Post added at 04:44 PM ---------- Previous post was at 04:42 PM ----------
Forget about the RUU for the moment, I believe if we can successfully get TWRP on your phone you can flash an Evita ROM and you'll be fine.
Sent from my Evita

timmaaa said:
Where did you download TWRP? Maybe we should start again to make sure you've got the right version. Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now hopefully you can enter recovery on your phone.
Sent from my Evita
---------- Post added at 04:44 PM ---------- Previous post was at 04:42 PM ----------
Forget about the RUU for the moment, I believe if we can successfully get TWRP on your phone you can flash an Evita ROM and you'll be fine.
Sent from my Evita
Click to expand...
Click to collapse
Wonderful, I have successfully booted into recovery!:victory:

Cool. From now on just make sure you stay in our forum. You'll find the main page here:
http://forum.xda-developers.com/one-x-att
Bookmark that page. The two development sections are here:
http://forum.xda-developers.com/one-x-att/development (Sense ROMs)
http://forum.xda-developers.com/one-x-att/orig-development (aosp ROMs)
As long as you only download ROMs etc from those two development forums you can't really go wrong. Now just find a ROM you like and you can flash it. Remember if it's an aosp ROM you need to flash gapps as well. And don't forget to flash the boot.img afterwards too because you're s-on. If you have any further problems just ask here.
Sent from my Evita

timmaaa said:
Cool. From now on just make sure you stay in our forum. You'll find the main page here:
http://forum.xda-developers.com/one-x-att
Bookmark that page. The two development sections are here:
http://forum.xda-developers.com/one-x-att/development (Sense ROMs)
http://forum.xda-developers.com/one-x-att/orig-development (aosp ROMs)
As long as you only download ROMs etc from those two development forums you can't really go wrong. Now just find a ROM you like and you can flash it. Remember if it's an aosp ROM you need to flash gapps as well. And don't forget to flash the boot.img afterwards too because you're s-on. If you have any further problems just ask here.
Sent from my Evita
Click to expand...
Click to collapse
Cool, thanks for all the help! I think Im just going to do a quick install of cleanrom, make sure everything is stable and get S-OFF. After that I'll update my RUU to 3.18 and make a backup from there. Thank you again!

Well no I'm stuck again. I am trying to get S-OFF in order to get a clean RUU install so that the kernel isn't messed up like it is right now. Except The only two methods of getting S-OFF required either SuperCID or adb commands. The only way I can find to get SuperCID is through ADB commands so regardless I need to use adb commands. It isn't so bad except that my phone is not recognized when I try to run adb commands. Ive done everything to reinstalling multiple times yet nothing seems to work.

Try installing an Android 4.1 ROM, folks have had some trouble with adb on the Android 4.2.2 Sense 5 ROMs.
Sent from my Evita

timmaaa said:
Try installing an Android 4.1 ROM, folks have had some trouble with adb on the Android 4.2.2 Sense 5 ROMs.
Sent from my Evita
Click to expand...
Click to collapse
Im using CleanROM 6.5 and under software information it says android 4.1.1 and Sense 4+. Should I use an older one?

Ah ok, I thought you were using the latest version of CR which is an Android 4.2.2 ROM. So you've updated both your HTC drivers and adb/fastboot? What version of Windows are you using? Are you using the HTC usb cable that came with the phone? Are you using a front or rear usb port?
Sent from my Evita

timmaaa said:
Ah ok, I thought you were using the latest version of CR which is an Android 4.2.2 ROM. So you've updated both your HTC drivers and adb/fastboot? What version of Windows are you using? Are you using the HTC usb cable that came with the phone? Are you using a front or rear usb port?
Sent from my Evita
Click to expand...
Click to collapse
I'm pretty sure I have but just in case what should I exactly to update it? I am running windows 7-x64. No, the one that came with my phone is starting to not work so I am using one from a differ phone. On my laptop, on the left side. The side with more USB ports.

timmaaa said:
Ah ok, I thought you were using the latest version of CR which is an Android 4.2.2 ROM. So you've updated both your HTC drivers and adb/fastboot? What version of Windows are you using? Are you using the HTC usb cable that came with the phone? Are you using a front or rear usb port?
Sent from my Evita
Click to expand...
Click to collapse
Tested on my Desktop running Windows 7-x64 as well and all the drivers are fine except for the MTP drivers. They don't install correctly. Thats the problem with my laptop as well.

Is there anyway I can do a clean wipe or start over from scratch?

An RUU will start you over from scratch, the only problem is that you're s-on so you can run an older RUU and there isn't an RUU that's equal to or greater than your current firmware. Are you able to mount your sd card in TWRP?
Sent from my Evita

timmaaa said:
An RUU will start you over from scratch, the only problem is that you're s-on so you can run an older RUU and there isn't an RUU that's equal to or greater than your current firmware. Are you able to mount your sd card in TWRP?
Sent from my Evita
Click to expand...
Click to collapse
Yes I am

Cannot access Recovery

Hey guys,
My phone died from the dreaded "qhsusb_dload" issue, and since I cannot afford the replacement phone I really want, I bought another AT&T One X.
I had my previous one since March of last year and I have gotten everything done with no issues, including S-OFF, upgrading Firmware to 3.17 to use JB 4.2.2 and trying various Radios and Kernels, so I do have experience.
With this phone, completely stock, I unlocked the Bootloader, and at the top it shows TAMPERED and UNLOCKED. I now have two issues:
1. I cannot get into the Recovery. I flashed it manually from "Fastboot USB", as well as with EZ Toolkit Advanced (Evita) and WinDroidXL Tookit and it showed it was successful with each method, yet when I try to access it, I get the boot screen with the HTC logo for about 3 seconds then it just powers off completely.
I researched and tried TWRP 2.6 as well as CWM from WinDoidXL toolkit. I have also ran the "fastboot erase cache" command after installing the Recovery yet I still have the problem. I installed gapps to accomplish the same thing but I don't wanna use it just yet.
I am asking for help as I am afraid of bricking this phone as well. When it powers off after failing to access the Recovery, it stays off for a while, and Device Manager even shows "qhsusb_dload" I have to hold the power button for a long time (and multiple times in some instances) before it powers on and boots into the OS.
Please help me get this working as I am afraid to try it again with the fear of having it bricked.
I do not have root access (I need recovery to flash t he Super User zip file first, correct?) and my HBoot is 2.14 (can't remember what it was on my last phone). Do any of those play a part in the problem i'm having?
Thanks so much in advance

Does the phone boot up into the OS? What are your bootloader details?
Sent from my Evita

Hello again, timmaaa.
timmaaa said:
Does the phone boot up into the OS? What are your bootloader details?
Click to expand...
Click to collapse
badbwoydes said:
When it powers off after failing to access the Recovery, it stays off for a while, and Device Manager even shows "qhsusb_dload" I have to hold the power button for a long time (and multiple times in some instances) before it powers on and boots into the OS.
Click to expand...
Click to collapse
My phone works fine with stock ATT 4.1.1 that it came with, it's just the Recovery that won't launch, even though it appears to install fine when I flash it with fastboot.
My Bootloader shows:
TAMPERED
UNLOCKED
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012, 18:37:14-1
Thanks

Are you checking the md5 after downloading the recovery?
Sent from my Evita

timmaaa said:
Are you checking the md5 after downloading the recovery?
Sent from my Evita
Click to expand...
Click to collapse
No, but I have tried 2 different versions from here, the one I had on my previous Evita, and I have also used the ones embedded in the WinDroidXL and EZToolkit Advanced (Evita).
I've seen others saying their phone ends up booting normally after selecting Recovery from the Bootloader but mine just powers off when I select it and I can't find a previous thread with this issue.

It's possible your partitions are a bit funky. Running the 3.18 RUU might help.
Sent from my Evita
---------- Post added at 12:32 PM ---------- Previous post was at 12:31 PM ----------
We need to check your CID first.
Sent from my Evita

timmaaa said:
It's possible your partitions are a bit funky. Running the 3.18 RUU might help.
Sent from my Evita
---------- Post added at 12:32 PM ---------- Previous post was at 12:31 PM ----------
We need to check your CID first.
Sent from my Evita
Click to expand...
Click to collapse
Would this be what you're referring to? http://forum.xda-developers.com/showthread.php?t=2390405
And if so, I can try S-OFF even though I don't have root access?
My CID is all 1's
My HBOOT wouldn't cause this prob?

You can disregard all that. I ran the install for TWRP 2.6.3.0 from the EZToolkit Advanced (Evita) then cleared the cache with the automated option in the same Toolkit, which I have tried like 10 times a few hours ago and now it's working... I swear all I did differently was leave the phone idle and plugged in for a while.
I'd still like to get the S-OFF done at this time. When I run "fastboot getvar cid" it returns "cid: 11111111" which means I have SuperCID and I can go through with S-OFF?
Finally, I cannot find a S-OFF guide for HBOOT 2.14 and ATT Firmware 3.18. This is for my HBOOT but not my Firmware http://forum.xda-developers.com/showthread.php?p=42631876
I found this http://forum.xda-developers.com/showthread.php?t=2485865 which states it's for 3.18 Firmware but shows nothing for my HBOOT.
I also found this http://forum.xda-developers.com/showthread.php?t=2540232

S-off isn't specific to firmware, it works on all. Anyway, try Facepalm s-off.
http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my Evita

timmaaa said:
S-off isn't specific to firmware, it works on all. Anyway, try Facepalm s-off.
http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my Evita
Click to expand...
Click to collapse
You have no idea how terrified I am right now, modding a phone that is basically the same as the one that got bricked a few days ago.
Thank you for your assistance. I will indeed go with Facepalm as that's the one I used in the past

Flashed the kernel now computer can't load it

I flashed the kernel on my phone earlier today, now the computer keeps saying it can't find the driver for it. I'm on windows 7 and if I look under device manager I see HTC One X under "Other devices", I've tried different cable, different computer, uninstalling the driver and install the latest, but it still doesn't work. I can't boot the phone up all the way because the kernel isn't for the ROM I have. I can boot into recovery, which is ClockworkMod. I can't mount it, which is probably because the computer doesn't think the drivers are there. Anyone know how to fix this?
Oh, my phone is rooted and S-Offed.
Thanks.

You need to provide details when asking for assistance. Saying "the kernel" doesn't tell us anything, please tell us exactly which kernel you flashed. You also failed to mention which ROM you're on, your bootloader details, the version of CWM you're running, the os installed on your PC, and whether you have the HTC One X (Endeavoru) or the HTC One XL / at&t One X (Evita). All very crucial information, without which it's impossible to help you.
Sent from my Evita

The kernel was for the Cyanogenmod 11. The ROM I was running was a somewhat custom version of the original manufacture version, I don't remember which one exactly. I'm running CWM v6.0.4.6. The bootloader is the default I've never changed it. I'll give you what it says thought:
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-1.14.002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
I believe I mentioned I was run Windows 7 x64 and it's AT&T HTC One X (Evita)
Let me know if there's anything else.

So why not just flash the ROM again?
Sent from my Evita
---------- Post added at 12:01 PM ---------- Previous post was at 12:00 PM ----------
That will overwrite the bad kernel. Out of interest, if you knew the kernel wasn't compatible (aosp kernel with Sense ROM will never work) why did you flash it?
Sent from my Evita

timmaaa said:
So why not just flash the ROM again?
Sent from my Evita
---------- Post added at 12:01 PM ---------- Previous post was at 12:00 PM ----------
That will overwrite the bad kernel. Out of interest, if you knew the kernel wasn't compatible (aosp kernel with Sense ROM will never work) why did you flash it?
Sent from my Evita
Click to expand...
Click to collapse
I put an AOSP kernel on because I was trying to get Cyanogenmod on it.
The computer recognizes my phone when I'm in the bootloader and it says Fastboot usb, but the One X One Click utility doesn't recognize that my phone is connected. Is there another utility I should use?

You need the ROM on your phone before you can install the kernel. Forget the utility altogether and just use manual fastboot commands when you need to. Why do you need fastboot at the moment anyway? All you need to do is flash a ROM to get your phone booting again.
Sent from my Evita

timmaaa said:
You need the ROM on your phone before you can install the kernel. Forget the utility altogether and just use manual fastboot commands when you need to. Why do you need fastboot at the moment anyway? All you need to do is flash a ROM to get your phone booting again.
Sent from my Evita
Click to expand...
Click to collapse
Ok, this is gonna sound Noob-ish, but obviously the way I'm use to doing it doesn't work, how do I flash another ROM to it?

You're s-off so all you need to do is perform a wipe in recovery, and install the ROM zip (plus gapps zip if it's aosp). I have detailed instructions in my How-To Guide For Beginners thread, the link is in my signature.
Sent from my Evita

timmaaa said:
You're s-off so all you need to do is perform a wipe in recovery, and install the ROM zip (plus gapps zip if it's aosp). I have detailed instructions in my How-To Guide For Beginners thread, the link is in my signature.
Sent from my Evita
Click to expand...
Click to collapse
How do I get the Zip to it if I can't access the phone like a drive on my computer?

Can't you mount the sd card to the PC in CWM? If not, didn't you make a backup before messing with the phone? If you have a backup you can restore that. You should always keep a backup or a ROM zip on your phone at all times in case of situations like this. Or you can get fastboot working and flash TWRP 2.6 recovery instead of CWM and you'll be able to use the mount menu to mount usb storage, then it'll show up as a removable drive on your PC.
Sent from my Evita