Database Info

HTC DESIRE S stuck at HTC White screen after flash Plese help!

Hi all,
I just tried flashing miui 2.4.20 to an HTC DESIRE S.
1)Before doing so, I unlocked the bootloader using HTC Dev tool
2)Rooted using superclick tool
3)Installed CWM Recovery using fastboot
and then flashed the rom....it won't go any further than the white HTC screen on reboot even though it looks like the flash is successful. I tried reflashing several times with no luck can someone please help?
EDIT:Just realised that I had to flash the boot.img using fastboot...problem solved.
Is there a way to make the Desire S completely unlocked so that I can flash using cwm without the need of fastboot?

lowrider82 said:
Hi all,
I just tried flashing miui 2.4.20 to an HTC DESIRE S.
1)Before doing so, I unlocked the bootloader using HTC Dev tool
2)Rooted using superclick tool
3)Installed CWM Recovery using fastboot
and then flashed the rom....it won't go any further than the white HTC screen on reboot even though it looks like the flash is successful. I tried reflashing several times with no luck can someone please help?
EDIT:Just realised that I had to flash the boot.img using fastboot...problem solved.
Is there a way to make the Desire S completely unlocked so that I can flash using cwm without the need of fastboot?
Click to expand...
Click to collapse
Yes. You need to downgrade your hboot, there are guides for this in the general section, you'll need to find a compatible ruu, get back to stock rom and then use revolutionary to S-Off
Sent from Purgatory - Still stuck between the One X and the SGS3.

How do i do the boot.img
Did it all on the exact same way you did
got the exact same problem at the moment.
Were do i find the boot.img and how do i go about getting it onto the phone
Im new to flashing

slugger7 said:
Did it all on the exact same way you did
got the exact same problem at the moment.
Were do i find the boot.img and how do i go about getting it onto the phone
Im new to flashing
Click to expand...
Click to collapse
I got a solution, but its a bit tricky: use the forum search
Sent from my HTC Desire S using xda app-developers app

Feel like an idiot lol
c.m.b said:
I got a solution, but its a bit tricky: use the forum search
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
Yep found out like now and it is working now. Thanx for teaching me the ways of the force

slugger7 said:
Yep found out like now and it is working now. Thanx for teaching me the ways of the force
Click to expand...
Click to collapse
No problem, but use it with caution
Sent from my HTC Desire S using xda app-developers app

help needed.
c.m.b said:
No problem, but use it with caution
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
hey.
please help me..
i flashed the pacman rom using clockmod recovery..
i downloaded it ,copied into my sd and then installed it..
i am still stuck on htc screen..
please help..
i dont know what to do!

jigi1993 said:
hey.
please help me..
i flashed the pacman rom using clockmod recovery..
i downloaded it ,copied into my sd and then installed it..
i am still stuck on htc screen..
please help..
i dont know what to do!
Click to expand...
Click to collapse
Are you htcdev unlocked?

lowrider82 said:
Hi all,
I just tried flashing miui 2.4.20 to an HTC DESIRE S.
1)Before doing so, I unlocked the bootloader using HTC Dev tool
2)Rooted using superclick tool
3)Installed CWM Recovery using fastboot
and then flashed the rom....it won't go any further than the white HTC screen on reboot even though it looks like the flash is successful. I tried reflashing several times with no luck can someone please help?
EDIT:Just realised that I had to flash the boot.img using fastboot...problem solved.
Click to expand...
Click to collapse
I have flashed many devices(Desire, Desire S, HD2, HD and One X) a hundred of times because I am a beta tester. So I know the ins and outs of flashing. But this time I need your help guys.
I have unlocked my Desire S (Hboot is 2.00.0002, S-ON, Radio 3822.10.50.24_M)
flashed TWRP recovery
flashed Viper Saga 2.1.3 JB
flashed boot.img
And the Rom booted and installed. All fine so far.
Now I want to install a different ROM.
Flashed the new PACman JB_2.2_v22 ROM, and boot.img. But this time I got stuck at white screen. So I tried CWM recovery and even 4EXT. Flashed Rom and its boot.img again. No luck. Stuck at white screen every time.
But now the weirdest. At the end I flashed TWRP recovery, Viper Rom and its boot.img again. And damn, I'm stuck at the white screen again.
Also weird is that I am not able to flash an official RUU after unlocking the bootloader again. When plugging in the device I can start the RUU installation proces. But during the sending firmware proces, the phone screen remains black with HTC on it for hours. So I had to remove the cable and boot the phone into bootloader again.
It looks like something is blocking these two processes.
Any ideas? I searched through XDA and on the internet. The only thing I can find to solve the white screen with green HTC is flashing boot.img. But that is not the issue.
The problem and sollution with the RUU installation, I haven't seen at all yet.
Hope somebody could point me in the right direction.

wanahave said:
I have flashed many devices(Desire, Desire S, HD2, HD and One X) a hundred of times because I am a beta tester. So I know the ins and outs of flashing. But this time I need your help guys.
I have unlocked my Desire S (Hboot is 2.00.0002, S-ON, Radio 3822.10.50.24_M)
flashed TWRP recovery
flashed Viper Saga 2.1.3 JB
flashed boot.img
And the Rom booted and installed. All fine so far.
Now I want to install a different ROM.
Flashed the new PACman JB_2.2_v22 ROM, and boot.img. But this time I got stuck at white screen. So I tried CWM recovery and even 4EXT. Flashed Rom and its boot.img again. No luck. Stuck at white screen every time.
But now the weirdest. At the end I flashed TWRP recovery, Viper Rom and its boot.img again. And damn, I'm stuck at the white screen again.
Also weird is that I am not able to flash an official RUU after unlocking the bootloader again. When plugging in the device I can start the RUU installation proces. But during the sending firmware proces, the phone screen remains black with HTC on it for hours. So I had to remove the cable and boot the phone into bootloader again.
It looks like something is blocking these two processes.
Any ideas? I searched through XDA and on the internet. The only thing I can find to solve the white screen with green HTC is flashing boot.img. But that is not the issue.
The problem and sollution with the RUU installation, I haven't seen at all yet.
Hope somebody could point me in the right direction.
Click to expand...
Click to collapse
To flash an ruu you need to lock your bootloader. As for the other issue do you know what panel your phone has, it's not an issue on sense roms and only becomes apparent in jb roms. Check http://forum.xda-developers.com/showthread.php?t=1943524
[OFF-TOPIC] Non-Sony screen panel DS users lounge I'd your not sure
The person who reads too much and uses his brain too little will fall into lazy habits of thinking.
—Albert Einstein

AW: HTC DESIRE S stuck at HTC White screen after flash Plese help!
And the problem with flashing ViperSAGA from TWRP is a different issue, TWRP is known to be problematic, I would recommend 4ext.

jugg1es said:
To flash an ruu you need to lock your bootloader. As for the other issue do you know what panel your phone has, it's not an issue on sense roms and only becomes apparent in jb roms. Check http://forum.xda-developers.com/showthread.php?t=1943524
[OFF-TOPIC] Non-Sony screen panel DS users lounge I'd your not sure
The person who reads too much and uses his brain too little will fall into lazy habits of thinking.
—Albert Einstein
Click to expand...
Click to collapse
Thanks for your reply.
Yes I've locked my phone again before installing the RUU. Made no sense. I've tried 2 WWE RUUs both with the same issue.
What panel I have I really don't know. Viper is sense. Worked om first flash. But after flashing PACman, the boot issues started. Now even Viper is not booting anymore.
I check the thread you posted. Will try the kernels. See what is happening.
EDIT: flashing these kernels do not work, because I'm S-ON. Need boot.image.
---------- Post added at 08:32 PM ---------- Previous post was at 08:31 PM ----------
teadrinker said:
And the problem with flashing ViperSAGA from TWRP is a different issue, TWRP is known to be problematic, I would recommend 4ext.
Click to expand...
Click to collapse
As I wrote. I've tried all of them. Am now on 4EXT. But still facing same issues. White screen with green logo.

I'd start fresh, make sure your unlocked, check the drivers are installed correctly (are you on win 8, if so check post two of link in my sig) format all but sd in 4ext, flash rom (sense rom to start) flash kernel. Your obviously no noob but sometimes we miss the obvious. I'm around for a bit so report back
"We don't like their sound, and guitar music is on the way out."
- Decca Recording Co. rejecting the Beatles, 1962

Hi tried to flash AOKP_saga_unofficial using goomanager twrp recovery downloaded then flashed Rom in goomanager but on reboot got white screen HTC logo stuck scenario any ideas what went wrong
Desire s
Unlocked and rooted using all in one tool
S-on still
Hboot 2xxxx not downgraded
Sent from my HTC Desire S using xda app-developers app

gazzy21uk said:
Hi tried to flash AOKP_saga_unofficial using goomanager twrp recovery downloaded then flashed Rom in goomanager but on reboot got white screen HTC logo stuck scenario any ideas what went wrong
Desire s
Unlocked and rooted using all in one tool
S-on still
Hboot 2xxxx not downgraded
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
Did you flash boot.img?
"We don't like their sound, and guitar music is on the way out."
- Decca Recording Co. rejecting the Beatles, 1962

Hi first time have done it thru goomanager I don't remember ticking or seeing option to flash boot image would it be safe to do so and be necessary thanks
have to research a bit more I was a bit lax flashing rom
Sent from my HTC Desire S using xda app-developers app

Sorry my bad
Should have read up a bit more didn't flash bootloader sorry for wasting your time also wondering if I should flash ext4 recovery instead of using twrp seems every body using ext4 now
Sent from my HTC Desire S using xda app-developers app

gazzy21uk said:
Sorry my bad
Should have read up a bit more didn't flash bootloader sorry for wasting your time also wondering if I should flash ext4 recovery instead of using twrp seems every body using ext4 now
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
Don't worry about it, 4ext is the best recovery for our device. There seems to be a few issues with the other two.
"We don't like their sound, and guitar music is on the way out."
- Decca Recording Co. rejecting the Beatles, 1962

having a look round revolutionary Rom looks better prospect see you using it atlas this stock gb is running near perfect only trying to improve battery drain 18-20MA in sleep at mo revolutionary has under clock facility which is only way I can see but at what cost
This may I say is a really excellent thread filled by people like me not reading up enough before we tinker to our cost and thanks to you xda this is a casualty department for noobs
Sent from my HTC Desire S using xda app-developers app

gazzy21uk said:
having a look round revolutionary Rom looks better prospect see you using it atlas this stock gb is running near perfect only trying to improve battery drain 18-20MA in sleep at mo revolutionary has under clock facility which is only way I can see but at what cost
This may I say is a really excellent thread filled by people like me not reading up enough before we tinker to our cost and thanks to you xda this is a casualty department for noobs
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
The casualty department is located in the help Thread (follow link in my sig)
"We don't like their sound, and guitar music is on the way out."
- Decca Recording Co. rejecting the Beatles, 1962

Tip/warning rom manager recovery for htc one x (gsm)

I am creating this post as a tip and warning to everyone with an at&t htc one x (mostly noobs for help). If you have rom manager on your phone do not use it to flash the new recovery listed for the htc one x (gsm). I've been messing with android since 2009, but me seeing a new recovery for the one x with (gsm) next to it thought hey finally got an official clockwork recovery for our phones!!!!! Well i was wrong. Its for the international versions only not ours. The partition it writes the recovery to is on our bootloader partition, and flashing it will kill your phone. I flashed it, kept it on for hours but as soon as i rebooted the phone it turned off and would not turn on or charge. You'll pretty much be screwed and have to get a new phone unless you know how to run linux and ask for help fixing it which is harder than you think. Again do not flash the htc one x (gsm) recovery in rom manager!!!!!
Hope this helps some of you before hand and not after.
If this post isn't necessary i am sorry and please close it.

Nobody should ever use ROM Manager for anything, EVER.
Sorry for your loss.

Why would you flash a recovery for a different device and expect it to work?
When ROM manger is supported on your device its a great tool, like on the sgs2. If its not officilially supported on your device, don't mess with it.
Sent from my Nexus 7 using xda premium

nooomoto said:
Why would you flash a recovery for a different device and expect it to work?
When ROM manger is supported on your device its a great tool, like on the sgs2. If its not officilially supported on your device, don't mess with it.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
it was new on there at the time and with gsm next to i i figured it was for ours, anyway point is if i knew it wasnt for my phone i wouldnt have flashed it.

rob219 said:
it was new on there at the time and with gsm next to i i figured it was for ours, anyway point is if i knew it wasnt for my phone i wouldnt have flashed it.
Click to expand...
Click to collapse
in fact, it is not really that hard to fix. Just re-lock the phone via fastboot. then run RUU package from AT&T
It should set every thing back to original.
if your phone is not respond RUU, try reboot on RUU via fastboot.
By the way, The only recovery that works now is TWRP
Use this one only

sugeraddict said:
in fact, it is not really that hard to fix. Just re-lock the phone via fastboot. then run RUU package from AT&T
It should set every thing back to original.
if your phone is not respond RUU, try reboot on RUU via fastboot.
By the way, The only recovery that works now is TWRP
Use this one only
Click to expand...
Click to collapse
The ruu has to access the boot loader to verify your version. If you end up flashing a device and it writes certain partitions of your boot loader (ICJ).... Well your left with a permabrick, until someone finds a way to JTAG the One X(AT&T). I've heard that its already been done, but the person who has performed it has kept the pinout secret.
I'm not entirely sure which partitions your ROM manager has wrote to, if you can find that out you might be able to fix it... Depending on which ones have been written too.
Sent from my One X using xda app-developers app

Zombie thread alert!

Like many of us have said before. We are not the one x. We are the one XL.
Sent from my One X using xda app-developers app

_MetalHead_ said:
Nobody should ever use ROM Manager for anything, EVER.
Sorry for your loss.
Click to expand...
Click to collapse
Sorry, but I disagree!
I've had more problem locating backup files and restoring when in TWRP, than ROM manager!
Mike

MaverickCoast said:
Sorry, but I disagree!
I've had more problem locating backup files and restoring when in TWRP, than ROM manager!
Mike
Click to expand...
Click to collapse
You must be doing something wrong then. You don't even need to locate backups with TWRP, they're found automatically. Anyway, was it really necessary to revive an 18 month old thread just to say that?
Sent from my Evita

New to HTC need some help

Hey guys my s3 killed its self yesterday so I grabbed one of these beauties today and I'm really impressed so far(maybe its the custom ROM).
Now I got the phone off a guy, had it he unlocked the bootloader,rooted,and gave me the phone already running 4.1(dirty 1.8).no back ups to even a rooted stock.
Although I love jelly bean this battery is killing me and I would really like to have at least a stock zip I can flash in emergencies.
I am so unfamiliar with HTC(nexus one was the last one I owned)thank I really don't want to brick it.
OK so my questions are these
I have the rogers version of the Onex is there certain builds I need to look for or are they all just HTC one x?
With HTC is there a fallback like with samsung if things go wrong at least there's always download mode and Odin.
Do I need to have my boot loader unlocked?
Thanks in advance
And sorry for the noobness I just can't kill 2 phones in a week
Sent from my One X using xda app-developers app

You have a lot of reading ahead of you, grasshopper, before you're ready to do anything to your phone:
http://forum.xda-developers.com/showthread.php?t=1671237
To answer your questions:
todorcim said:
I have the rogers version of the Onex is there certain builds I need to look for or are they all just HTC one x
Click to expand...
Click to collapse
No! It is wise of you to ask this, because there are two versions of the One X, the International (Tegra 3 quad-core) and the US/Rogers/Telstra (dual-core S4). Flashing stuff for the wrong version can permanently brick your phone (i.e., there is no current fix for some of these mistakes).
With HTC is there a fallback like with samsung if things go wrong at least there's always download mode and Odin.
Click to expand...
Click to collapse
Assuming you haven't flashed the wrong ROM, you can generally always get out of trouble by booting into bootloader, relocking, and running the RUU for your firmware. Most problems can be fixed by going back into recovery and re-flashing or flashing something else.
Note: Figure out what version of hboot you have before doing anything. With 1.09, modding is pretty straightforward. With 1.14, you have to take some extra steps and there are a few things you can't do at all.
Do I need to have my boot loader unlocked?
Click to expand...
Click to collapse
Yes. Leave it unlocked unless you need to RUU.

His hboot should be 1.11 which is the same as 1.09 as far as installing roms go.
If you're looking for a Sense ICS rom, I recommend ViperXL or CleanRom5. But there are other roms to try. As long as you stay in this forum and not the international forum you should be safe to flash anything you want.

Awesome thanks guys.
I check my boot loader and it is 1.11..
So that makes me happy cause all in all I'm addicted to flashing
One last question for you before I venture off on my own here..
With my nexus one I and the passimg I could flash through my bootloader in cause something went wrong or I just want to refresh my n1,is there something like that for this phone or are those days long gone?
Again thanks a bundle
Sent from my One X using xda app-developers app

Flash from TWRP recovery

todorcim said:
With my nexus one I and the passimg I could flash through my bootloader in cause something went wrong or I just want to refresh my n1,is there something like that for this phone or are those days long gone?
Click to expand...
Click to collapse
Correct, stick to TWRP. There is an app called GooManager that makes installing and updating TWRP close to effortless.
If you haven't already, reboot to recovery and see what you've got installed. Some people insist on using ClockworkMod recovery because they've used it on other phones, but it's not supported for this one and can cause issues with data getting corrupted. If you have CWM installed, all you need to do is download GooManager and select "Install openrecovery script" in settings and it will replace it with TWRP.

Ya I always use twrp have for a while but what I mean is if (can?) I soft brick my phone or something happens that I can't flash from recovery is there a passimg zip like we had for the n1 that could be flash through the boot loader?
You know just in case
I only ask cause its HTC thought maybe there was something like that...could have been a Google thing too not sure..
Sent from my One X using xda app-developers app

todorcim said:
Ya I always use twrp have for a while but what I mean is if (can?) I soft brick my phone or something happens that I can't flash from recovery is there a passimg zip like we had for the n1 that could be flash through the boot loader?
You know just in case
I only ask cause its HTC thought maybe there was something like that...could have been a Google thing too not sure.
Click to expand...
Click to collapse
Yes, you can still flash stuff through fastboot, if that's what you mean.

Ya that's what I mean
Thanks
Sent from my One X using xda app-developers app

[Q] Reboot get stuck in boot loop

So I've been more of a stalker of the XDA community for a while, never really needed to ask a question because I usually find the answers on the boards pretty handily or by some fluke things work for me without the need to post anything. But now that time has come to an end.
I had Jellybam 4.1.2 on my device flashed with whatever kernel came with it, and when my battery died yesterday the phone was stuck in a boot loop. Keep in mind that prior to that 1) It had never done this on a reboot and 2) the correct kernel had been flashed via fastboot. My hboot is 1.14. The reason I'm not posting this question in the Jellybam post in android development is because 1) I'm a n00b to posting on here and 2) this is now happening with any other rom I install (most recent is MIUI which I flashed late last night, started up normally, then got caught in a boot loop on a reboot).
I follow the normal steps of going into TWRP, flashing cache/davlik, factory wipe, system wipe, then installing, doing the gapps if necessary, or following the instructions on any aroma installers, then rebooting into fastboot and flashing the kernel so i don't get boot loops on the initial start up. I'm also doing this on a mac, but the command lines in terminal are pretty straight forward and i'm just doing normal ADB / fastboot commands.
I'm perplexed now and I can't figure out what changed or what I did differently that's causing this. Any help would be most appreciated and I apologize if this is somehow a cross or repeat post, but I couldn't find much like it.

Do you have an Evita or Endeavour phone?
Sent from my HTC One XL using xda premium

It sounds like you are doing everything correct. Also seems like you have a good grasp of what to do. My thought is even if your initial install went though. Something in the bootimg may be corrupt. Perhaps try redownloading your preferred rom? And try again.
Sent from my One X using xda premium

ToxicWaste said:
Do you have an Evita or Endeavour phone?
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Evita

subarudroid said:
It sounds like you are doing everything correct. Also seems like you have a good grasp of what to do. My thought is even if your initial install went though. Something in the bootimg may be corrupt. Perhaps try redownloading your preferred rom? And try again.
Sent from my One X using xda premium
Click to expand...
Click to collapse
I've tried a couple times with the same result. I'll try again and see if anything different happens. Maybe just by some miracle I'll get it working again

I'm not sure how it works with safari for Mac. I do know that when I download ROMs with crome it some how downloads corrupt zips. On ei9 it works fine.
Sent from my One X using xda premium

uncledoobie said:
So I've been more of a stalker of the XDA community for a while, never really needed to ask a question because I usually find the answers on the boards pretty handily or by some fluke things work for me without the need to post anything. But now that time has come to an end.
I had Jellybam 4.1.2 on my device flashed with whatever kernel came with it, and when my battery died yesterday the phone was stuck in a boot loop. Keep in mind that prior to that 1) It had never done this on a reboot and 2) the correct kernel had been flashed via fastboot. My hboot is 1.14. The reason I'm not posting this question in the Jellybam post in android development is because 1) I'm a n00b to posting on here and 2) this is now happening with any other rom I install (most recent is MIUI which I flashed late last night, started up normally, then got caught in a boot loop on a reboot).
I follow the normal steps of going into TWRP, flashing cache/davlik, factory wipe, system wipe, then installing, doing the gapps if necessary, or following the instructions on any aroma installers, then rebooting into fastboot and flashing the kernel so i don't get boot loops on the initial start up. I'm also doing this on a mac, but the command lines in terminal are pretty straight forward and i'm just doing normal ADB / fastboot commands.
I'm perplexed now and I can't figure out what changed or what I did differently that's causing this. Any help would be most appreciated and I apologize if this is somehow a cross or repeat post, but I couldn't find much like it.
Click to expand...
Click to collapse
My phone did this once too. Never figured out why but the way I stopped it was to nandroid data, then wipe everything, reinstall the Rom and restore only data. After this it never bootlooped again.
Sent from my Venom1 XL using Xparent Red Tapatalk 2

ImagioX1 said:
My phone did this once too. Never figured out why but the way I stopped it was to nandroid data, then wipe everything, reinstall the Rom and restore only data. After this it never bootlooped again.
Sent from my Venom1 XL using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
Ok, I'll give that a shot. I installed CleanRom 5.1 today, ran some reboots and that seemed to clear it up. It might be a Jellybean thing, but who knows. Thanks for all the suggestions and quick responses!

Oh yea there is some discussion about a Rev-a or rev-b that is on your box having issues with 4.2 jb not working. I think its rev-b that everyone is having issues with.
Sent from my One X using xda premium

[Q] Not getting past HTC screen

I looked around and didn't see a solution to my problem. I might have missed it because I'm kind of panicked right now.
My HOXL was dying really fast. Within a few hours, it falls from 80% to 0%. I wanted to factory reset because I heard that it helps the battery life.
So I followed the process I always have (I'm unlocked, rooted, and had pacman's evita ROM installed) and did a factory reset, wiped cache and dalvik cache. Then I re-flashed pacman's ROM and the gapps. When I rebooted though, it went to the HTC screen and in a few seconds it just went black. I think it might have still been on or something, but nothing was happening for like 30 minutes. I tried it over and over again, flashing new ROMs and kernels, but now all that's happening is that it's stuck on that very first HTC screen.
I downloaded the latest JB RUU for evita to try it out. But if I can't get past that first screen, is there a way to connect it? I can still get into TWRP's recovery. My HBoot is 1.09. I'm really starting to feel nervous about having to buy a new phone, yet I feel like there should be a way to fix this. Could flashing the stock kernel be all I need? I tried to download from Viper's hub, but the download just stops at 99% and doesn't finish.
Please, I would really, really appreciate any help!

I would run the 3.18 RUU (which you can do in fastboot).

Try a complete wipe: Factory reset, system, cache and dalvik cache in twrp or if it is not wiping correctly due to twrp version " 2.3......" is best fro our phones, try downloading and installing twrp again or use adb commands to wipe and flash rom again.

I've tried a complete wipe, but I just noticed that my TWRP version is 2.2.0. I tried the wipe like five or more times and it didn't work. My PC isn't reading the HOXL in the adb command window. I rooted a Sero Pro 7 this way, so I think I should have the drivers installed for it... I'm going to try installing the HTC Sync drivers and seeing if I can send adb commands to my HOXL. If this doesn't work, I'm going to try the 3.18 RUU. I heard that some people have bricked their HOXL completely doing this, but I didn't change my SuperCID and s-on (?), so would I be fine? Or would it be safer to just use the latest ICS one (RUU_EVITA_UL_ICS_40_S_Cingular_US_2.20.502.7_Radio _0.19as.32.09.11_2_10.105.32.25L_release_271865_si gned.exe)?

So you have no way to flash boot image separately? I would definitely try to get device recognition so adb can be used before running ruu.
Sent from my HTC One X using xda premium

Yeah, I went through the noob way of unlocking and rooting this phone, so there was no need to use adb commands. I would have liked to try that first before running RUU, but I just want to have a working phone again, even if I have to go through the whole process of unlocking and rooting.
Sent from my Nexus 7 using XDA Premium HD app

I would still try to get a good adb environment. Sometimes panic is not a good thing. Just be careful and make sure you get the proper ruu and do not let the battery die while running it. Let me know if it works.
Sent from my HTC One X using xda premium

Venomtester said:
I would still try to get a good adb environment. Sometimes panic is not a good thing. Just be careful and make sure you get the proper ruu and do not let the battery die while running it. Let me know if it works.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
This is what I'm worried about:
SERooted wrote: Note to OP: You really should add to the 1st post that it is not wise to flash the 3.18 firmware over super cid and s-on.. its not a good thing for most people to have a qhsb_dload turn their phone into a paper weight before finding out that they shouldn't have used that file to begin with. i had to find out the hard way. i would have flashed the ics firmware on my phone but decided to go with the big JB only to find out that it turns it into a paperweight. I understand this is no fault but my own, however this would greatly help people when choosing which ruu to run.
http://forum.xda-developers.com/showthread.php?t=2191477

I know what you mean lol. I would only do that as a last resort. I would try and get adb working since the phone is not bricked. It just seems to have no Rom or boot image. Have you tried one with an aroma installer?
Sent from my HTC One X using xda premium

Venomtester said:
I know what you mean lol. I would only do that as a last resort. I would try and get adb working since the phone is not bricked. It just seems to have no Rom or boot image. Have you tried one with an aroma installer?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Huh...I just tried flashing the UrDroid ROM because of its aroma installer, but it didn't happen in recovery, like I thought it would. It said it was successful, so I rebooted the system. It got past the initial screen with an AT&T boot img and htc one img. Now I'll have to see if it actually loads past this.
EDIT: It worked! I'm going to have to try to see if I can load boot img some other way than just an aroma installer.

You can use Flash GUI from the market to install boot images or get Goo Manager to install a 2.3..... Version of twrp. That may solve your problems.
Sent from my HTC One X using xda premium

Venomtester said:
You can use Flash GUI from the market to install boot images or get Goo Manager to install a 2.3..... Version of twrp. That may solve your problems.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Second Flash GUI....works like a charm