Related
Hi Guys,
Finally after playing with a lot of roms I decided to go back to stock. I was flashing back to stock using the RUU exe from HTC and something went wrong. Phone is now stuck in RUU mode whenever you turn on. Have access to fastboot but when I try to boot recovery etc getting remote not allowed. Any suggestions other then paying $450 aus for new board?
Thanks
well if you got fastboot then you got hboot. which is good. i am pretty sure you can run a stock .nbh and get reverted allllll the way back to total stock just like removing root. im not to sure but look into those options. if you can do that then you should be able to reroot and not have a $450 shinny brick. i bet someone will respond with a better answer after this is posted lol!
I don't know if this is a standard solution, however I had the same problem for the past few day, and I tried everything and as I am updating from HTC RUU I held the action ( track ball ) button pressed and it did the upgrading . . . I'm not going to try again, but that is what happened.
Hope that helps.
Cheers,
Andre
Hello all,
Was just wondering if anyone can help me as I am trying to unroot the phone to send back for warranty reasons as main speaker is not working anymore.
First restored the original partition 7 from gfree and ran its unroot
it put back the 0.86.0000 hboot but still showing S-OFF though.
tried to flash the PD15IMG.zip for gingerbread and let it do all the updates and is still on s-off but showing 0.86.0005 now.
When booting it gives the normal first vibration then about a second or two later I get another vibration.
Has all the right software just seems like something is different and not running 100% stock yet.
Any ideas what I am missing?
Any help would be greatly appreciated.
M9x3mos said:
Hello all,
Was just wondering if anyone can help me as I am trying to unroot the phone to send back for warranty reasons as main speaker is not working anymore.
First restored the original partition 7 from gfree and ran its unroot
it put back the 0.86.0000 hboot but still showing S-OFF though.
tried to flash the PD15IMG.zip for gingerbread and let it do all the updates and is still on s-off but showing 0.86.0005 now.
When booting it gives the normal first vibration then about a second or two later I get another vibration.
Has all the right software just seems like something is different and not running 100% stock yet.
Any ideas what I am missing?
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Ive heard it can take a couple of tries of rooting and unrooting for it to show s-on. try rerooting it with the same method you used to root and then just get the stock pd15img to flash. Make sure you downgrade the bootloader first though if its now the gingerbread bootloader. Good Luck!
you mean the 0.86.0000 hboot?
M9x3mos said:
you mean the 0.86.0000 hboot?
Click to expand...
Click to collapse
0.86.000 is the stock hboot, you should be good to go.
yeah that is what I had didn't help
I assume should be engineering hboot
do gfree procedures
then put 0.86.0000
Hi Guys,
Apologies if this has been discussed before. I have looked for answers everywhere and i could not find any.
Ok, I have a Desire S which is branded to Telstra (Australia), I was sick of all the useless app that Telstra had put in and wanted to get rid of all those.
I used revolutionary method to get it s-off and install Generic Firmware. After that i was happy not having any of Telstra's bloatware on the phone. Then came the update of 2.3.5 and as usual downloaded the firmware and used RRU to Update. Big mistake on my part, i didn't read anything and just tried to push RRU on the phone, the result was White screen with HTC logo and nothing past that. Tried everything no luck, then looking for answers, i found a solution to remove revolutionary, I could see revolutionary gone in HBOOT but the phone would not start.
to solve this i went to telstra to send it to repair, warranty was there and when telstra asked what happened, i said i was updating an app and it went to this screen, Tech guys said this is the similar 3rd problem in a day. so after 5 days the phone got repaired, New IMEI number and logic board had to be replaced.
Now all over again i have bunch of telstra bloatware on the phone. I want to get Generic 2.3.5 with sense 3.0. what is the process to follow so that i don't make the same mistake again?
All i want to do is get it s-off and install generic Firmware, the easiest way possible something like revolutionary. I tried going with ADB but found a bit risky.
Any advice in getting Generic HTC Desire S (2.3.5 with Sense 3.0) the easiest way would be helpful. Thanks in advance.
HBOOT info:
SAGA PVT SHIP s-ON RL
HBOOT-0.98.0002
RADIO-3805.04.02.01_M
eMMC-boot
Mar 30 2011,17:29:31
Thanks
To get a generic firmware from some other area, you need to get Super CID. I don't know much about it, just that CID's like a region code, Super CID enables you to get generic ROMs from any region. Only XTC Clip can do that on a Desire S as far as i know. Flashing a custom ROM after Revolutionary S-OFF is a better option....
Listen, I really recommend you to use a Custom ROM based on the update if you are ready to S-OFF. Hyperion is much faster and has a lot more features. Hell, if you do S-OFF, why settle for Sense 3? Get Sense 3.5. I recommend endymion.
@shrome99: Thanks dude, correct me if i am wrong, to get a generic firmware onto the desire s there is no option but to go for s-off and customs roms are better than stock ones, the reason i am asking is i have not used custom roms and willing to stick to stock.
What is the easiest way to get the rom sorted, I know how to get the custom rom installed there are too many posts everywhere that you can read through and make a decision and find roms of your choice, but there seems to be nothing about stock roms, i am sure there are people who are willing to get stock rom and their carrier is not rolling out the update coz they want more junk to be added.
Steps on how to get generic stock rom would be really helpful.
Thanks again
zryvffn said:
@shrome99: Thanks dude, correct me if i am wrong, to get a generic firmware onto the desire s there is no option but to go for s-off and customs roms are better than stock ones, the reason i am asking is i have not used custom roms and willing to stick to stock.
What is the easiest way to get the rom sorted, I know how to get the custom rom installed there are too many posts everywhere that you can read through and make a decision and find roms of your choice, but there seems to be nothing about stock roms, i am sure there are people who are willing to get stock rom and their carrier is not rolling out the update coz they want more junk to be added.
Steps on how to get generic stock rom would be really helpful.
Thanks again
Click to expand...
Click to collapse
+1 to above
IMO, if you're considering making a change then put on a decent custom (see my sig) you won't regret it
ben_pyett said:
+1 to above
IMO, if you're considering making a change then put on a decent custom (see my sig) you won't regret it
Click to expand...
Click to collapse
Hey Ben, Thanks for this, I went ahead and got the ROM as you suggested. Installed the base verison, then the add-on and the update. I have been palying around with it and so far loving it.
Only problem tough, I cannot use Market. I can open market look for apps and download, but when it starts to install, the phone re-boots. any known issues with this and is there a workaround to sort this out.
Ok, so here is what i did, Flashed Base version again and market started working again with no issues. Another issue which is not so much of an issue but only at night, why does the soft keys don't lit up on Desire S?. any way to fix these. Thanks guys.
Sometimes firing up and signing into Google talk makes the market start working again
Sent from my HTC Desire S using xda premium
sadsac said:
Sometimes firing up and signing into Google talk makes the market start working again
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
Thanks for that, I did a search for the issue and did the same thing as you had advised, but didn't work. Then I flashed the base version again and then the update, which worked. Don't know what had happened there.
But yeah loving the new rom and i would say was a better move to be on a custom ROM and getting rid of Carrier's junk installed.
Cheers!
Ok, so instead of creating a new post i have decided to post it here since it is already been discussed.
I was happy with rooted phone and endymion Rom and was happy until my phone started heating up and restarted on its own as if it had a mind of its own, I called HTC and they advised to send it for repair, i had to unroot the phone and sent for repair. Got the phone back with updated version and i need help rooting the phone.
when i boot the phone in fast boot this is what i get:
****LOCKED****
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-BOOT
Aug 22 2011, 15:22:13
Android Version 2.3.5
HTC Sense Verison 3.0
Software Number: 2.14.841.4
Baseband Version: 2.14.841.4 CL 184593 Release-Keys
Now i need to Root the phone again so i can be another happy user of endymion.
I am looking at this guide and needed help.
http://forum.xda-developers.com/showthread.php?t=1443636&page=1
The oldest RUU i can find for my provider is RUU_Saga_Telstra_WWE_1.36.841.3_Radio_20.28d.30.0805U_3805.04.02.01_M_release_184558_signed.exe
I was reading the guide and this is where i am confused.
6.This command will gets you out of adb shell.. so we need to get back to adb shell and you will see "#" sign..meaning you are temp rooted and we can then proceed to changing MISC_VERSION:
Code:
adb shell
cd /data/local/tmp
./misc_version -s 1.27.405.6 .
./misc_version -s 1.27.405.6 do i change this to 1.36.841.3 or leave it as it is?
Any help will be greatly appreciated.
Thanks.
IMO you can leave it as it is. 1.27.xxx is older than your RUU version so I think it will work fine.
chninkel said:
IMO you can leave it as it is. 1.27.xxx is older than your RUU version so I think it will work fine.
Click to expand...
Click to collapse
Thanks for that, yes i did follow the guide, and then got stuck again. The problem i am facing is after pushing all the files as of the guide, i run tacoroot the phone restarts and all i get is a red triangle with exclamation mark in it and nothing else happens.
then to get rid of it, i pull out the battery and do a complete factory reset. I have done this about 5 times now but still the same.
Also tried using super one click but that dint work either and freezes on waiting for device.
anything i have missed or is there any other solutions, any GUI programs or video to help if i am missing something.
any help is appreciated.
Thanks
I believe that you have to boot the original recovery before using tacoroot to get it working ( I mean boot it once, then boot normally).
After using tacoroot --root, your phone will probably go in bootloop, don't worry about that and change your misc_version as described in the tutorial.
And please, stop pulling out the battery, you will brick your phone this way.
chninkel said:
And please, stop pulling out the battery, you will brick your phone this way.
Click to expand...
Click to collapse
+1
You can pull it out as often as you want..but at least you should know the risk.
Sent by my fingers to your head
chninkel said:
I believe that you have to boot the original recovery before using tacoroot to get it working ( I mean boot it once, then boot normally).
After using tacoroot --root, your phone will probably go in bootloop, don't worry about that and change your misc_version as described in the tutorial.
And please, stop pulling out the battery, you will brick your phone this way.
Click to expand...
Click to collapse
I don't understand,"boot into original recovery". To try i booted the phone in HBOOT and pressed recovery and same thing the triangle shows. am i missing something here.
EDIT: I went till the last step and this is what i get "Patching and backing up partition 17...
Error Opening backup file.
#"
any idea
zryvffn said:
To try i booted the phone in HBOOT and pressed recovery
Click to expand...
Click to collapse
That's what I meant.
You can try misc_version_universal to avoid error patching partition 17 (see attachment below).
chninkel said:
That's what I meant.
You can try misc_version_universal to avoid error patching partition 17 (see attachment below).
Click to expand...
Click to collapse
Thanks dude, this worked and going thru revolutionary. i did some changes in the steps and will update what i did in a while after i get a rom installed.
Thank you everyone for help and support. i was able to downgrade my HBOOT and install a custom ROM. It would not have been possible if you guys had not supported.
one thing i have learnt is the more you read the more you find things useful and you actually learn how ti weigh your risk and benefits and avoid ending up with an expensive paper weight.
so this is what i did.
after using universal misc version file i was getting 140 error in RUU, boot loader version error, tried 3 time but would not let me get past that, then out of frustration i thought about giving it a last try for good or for worse, in the misc version section i changed a bit.
adb shell
cd /data/local/tmp
./misc_version -s 1.36.841.3 (Same number as my RUU)
then RUU went fine and then revolutionary.
well, if any kind of newbie person in trying to root the phone i would suggest to read and if you think you have read enough, its probably you haven't.
special thanks to @chninkel, @eyahl. Thanks Guys for all the support.
Cheers!
I used HTC's official unlock and my phone is unlocked, but has S-On. Is there a benefit to S-Off now that mine is unlocked? What is the difference between how the unlocks are? Sorry if i'm not making much sense, I'm new to this place and Android in general... I just got my sensation last week.
Welcome to Sensation
Don't worry, everyone's a noob at some point, I'm pretty much still a noob myself but as far as I understand it:
To this point you have unlocked your bootloader which simply allows the phone to boot with third-party software installed. In your phone there is a form of security check and the level of security is determined by whether you are S-ON or S-OFF. It's a flag at the radio level of your phone that checks images before they are allowed to be written to the system memory. So when you gain S-OFF, you gain unrestricted access to the NAND flash memory on your device, also known as root. With S-ON you can get temporary root but it's not guaranteed, with S-OFF you can get permanent root no matter what you flash.
Essentially gaining S-OFF permits superuser access to the phone, giving you control over all aspects of software and hardware.
If you like your phone the way it comes to you, all filled up with bloatware and stuck using only the latest version of Android that your carrier releases OTA, with a boring/crappy splash screen and boot animation (and so on and so forth ) then you have no real reason to get S-OFF.
If however you have seen some of the shiny ROMs put together by the devs here at XDA, or have a sweet custom splash screen you'd love to see every time you boot up the phone, or just like the idea of having complete control over YOUR phone and flashing what-the-hell-ever ROM/firmware/radio/other stuff you damn well please, then you should definitely consider rooting.
The disclaimer to all this is that if you aren't careful and don't thoroughly research what you're doing BEFORE you do it, you could brick your phone and give yourself some serious grief. The fact you're even asking this now is a point in your favour, there are far too many 'help me' posts on here from people who did something without bothering to try and understand it first. Knowledge is power and there's buckets of knowledge on this forum and others.
I'd suggest reading here and here at the very least.
Hope that helps
s-off means you may do anything with your phone,
you will lose warrenty at s-off gain it at s-on
as the other guy said if u want a nice toutch to your rom s-off it and install, if u want it still legal dont
Thanks for the info. I've been considering using an ICS OTA file on my HTC Sensation 4G, but the guides i've seen only mention S-OFF and nothing about the unlocked S-ON. I just can't wait for the official release!
On the other hand though, I also want to remove bloatware from this phone and found a script for such... but i can't seem to get any temp root method working. I'm not ready to jump off the deep end yet, but i'm tired of the unnecessary stuff.
I also couldn't wait for the official ICS release so I s-off, rooted, super CID, and flashed an ICS firmware and went to android revolution. Honestly, it's one of the best decisions Ive ever made. If you think your stock phone is running good right now, you'll be amazed when you flash it, it will run absolutely faster I tell you.
Though there are alot of risks doing all of that, it might brick your phone completely. So be very careful, read and understand everything if you're going to do all of those stuff.
Sent from revolutionized HTC Sensation ICS
HTC sensation stuck at boot
Hey Guys Noob here,
I need help big time. I gone and mess with something I shouldn't have. I'm a first time android/touch screen user so bear with me.
I was trying to S-off my phone (alrady rooted- after several tries) but I downloaded the juopunutbear zip file on my phone. I mistakenly loaded it via the CWM recovery and now the screen is stuck on that juopunutbear image.
I have tried to flash my rom because I thought it was just a boot loop, but nothing happened. I NEED some advice please don't tell me I bricked it. :crying:
man+droid said:
Hey Guys Noob here,
I need help big time. I gone and mess with something I shouldn't have. I'm a first time android/touch screen user so bear with me.
I was trying to S-off my phone (alrady rooted- after several tries) but I downloaded the juopunutbear zip file on my phone. I mistakenly loaded it via the CWM recovery and now the screen is stuck on that juopunutbear image.
I have tried to flash my rom because I thought it was just a boot loop, but nothing happened. I NEED some advice please don't tell me I bricked it. :crying:
Click to expand...
Click to collapse
if you can boot into bootloader then you are not bricked
secondly what do you mean by juopunutbear.zip and from where?
edit:you said that you are already rooted
which means that you have unlocked bootloader from htcdev site am i right?
Yes it was already unlock from HTC dev, but I was trying to get S- off using the wire trick method. In reading the Jounutbear guide thread it directed u to a link which has the zip file which I should have run on my pc but I had mistakenly installed it from my sd card and now it isn't going furthuer than that screen. I now can't using the Jbear exe bcuz it not recogining it.
I don't really want to keep adding my nonsense to the thread how can I PM someone for help.
man+droid said:
Yes it was already unlock from HTC dev, but I was trying to get S- off using the wire trick method. In reading the Jounutbear guide thread it directed u to a link which has the zip file which I should have run on my pc but I had mistakenly installed it from my sd card and now it isn't going furthuer than that screen. I now can't using the Jbear exe bcuz it not recogining it.
I don't really want to keep adding my nonsense to the thread how can I PM someone for help.
Click to expand...
Click to collapse
do this
install 4ext recovery
enable smartflash from it
flash the rom
http://forum.xda-developers.com/showthread.php?t=1631861
I did all that but the phone keeps booting up with the Juoputnutbear image that point to the phone. It looks similar to when I was just rooting the phone but it just no picking up nothing but that.
man+droid said:
I did all that but the phone keeps booting up with the Juoputnutbear image that point to the phone. It looks similar to when I was just rooting the phone but it just no picking up nothing but that.
Click to expand...
Click to collapse
that's weird
did you perform a full wipe(from recovery) before flashing the rom?
also as long as you are on S-ON use 4ext recovery to flash the rom
and before flashing the rom enable smartflash from 4ext
if you have done all the above then use a ruu.exe to return to stock condition
http://forum.xda-developers.com/showthread.php?t=1672425
Well that thread seems to be a mouth full remember I'm a noob. But I will try and read that again to get what it really says. It seems though that it was a complex instruction how to get back to the stock rom? Isn't there a file for that I can download. I get to doing that RUU thing to see if it works tho
man+droid said:
Well that thread seems to be a mouth full remember I'm a noob. But I will try and read that again to get what it really says. It seems though that it was a complex instruction how to get back to the stock rom? Isn't there a file for that I can download. I get to doing that RUU thing to see if it works tho
Click to expand...
Click to collapse
i saw your post in the other thread
you managed to install 4ext
now try to flash a custom rom
before flashing the rom enable smartflash from 4ext
Hey guys good news
I finally got the phone to power on. I saw this thread that highlead my pro http://forum.xda-developers.com/showthread.php?t=2284273 but I was really got the details from another forum. I don't know if I'm allowed to post it so I won't, but I'll sum it up.
All I need to do was flash the boot image on my current rom (get this from the zip file) and also flash the recovery image from a backup I had and presto.
But I'll go and follow you guys instruction about enabling the 4ext smart flash from now on. What I want to know though is for some custom roms (eg cyanogenmod 10.1) do I needs to be S-off to install it?
If so I'm still gonna try and S-off this here thingy. Givethanks y'all
man+droid said:
Hey guys good news
I finally got the phone to power on. I saw this thread that highlead my pro http://forum.xda-developers.com/showthread.php?t=2284273 but I was really got the details from another forum. I don't know if I'm allowed to post it so I won't, but I'll sum it up.
All I need to do was flash the boot image on my current rom (get this from the zip file) and also flash the recovery image from a backup I had and presto.
But I'll go and follow you guys instruction about enabling the 4ext smart flash from now on. What I want to know though is for some custom roms (eg cyanogenmod 10.1) do I needs to be S-off to install it?
If so I'm still gonna try and S-off this here thingy. Givethanks y'all
Click to expand...
Click to collapse
any ICS/JB rom you can install via enabling smartflash in 4EXT before flashing the ROM
ganeshp said:
any ICS/JB rom you can install via enabling smartflash in 4EXT before flashing the ROM
Click to expand...
Click to collapse
Hey thanx for the heads up. So I'm finally s-off using the J-bear method but where unlocked use to be I'm now seeing the juopunutbear there so I got back into android but it was the old CWM that was on it how do I get back the 4ext and would that be a prob if that J name remains there tho?
man+droid said:
Hey thanx for the heads up. So I'm finally s-off using the J-bear method but where unlocked use to be I'm now seeing the juopunutbear there so I got back into android but it was the old CWM that was on it how do I get back the 4ext and would that be a prob if that J name remains there tho?
Click to expand...
Click to collapse
no you are fine now
there is no problem with juopunutbear because now you have patched hboot which is unlocked
you are fine also with cwm recovery
but if you still want 4ext do only step 2 from here
http://forum.xda-developers.com/showthread.php?t=1631861
man+droid said:
I did all that but the phone keeps booting up with the Juoputnutbear image that point to the phone. It looks similar to when I was just rooting the phone but it just no picking up nothing but that.
Click to expand...
Click to collapse
might be a bad dl. Download it again and reflash or try a different rom.
Earlier today I tried to update my HTC One X's firmware to 3.18 in order to install the latest cyanogenmod nightlies. First, I was confused at why the latest cyanogenmod nightly would not flash so after looking it up and figured out I needed to update the firmware but to do that I would have to relock the bootloader. Second, I had issues trying to relock the bootloader, eventually got that (did not know adb was updated). Third, after believing my nightmare was over, I quickly decided I would try to flash the latest evita ruu, which completed without any errors and I clicked finish. (RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed) straight from HTC's website. Finally, after a few minutes I noticed that my phone did not have a notification led, nor was it booted into the lovely (opinions may differ) HTC sense 4.1.
That is the story of how my phone got to the state it is in. The state being no lcd in any way, no notification led, but I can still hear the phone being plugged into windows and can hear it shut down and turn on (with the windows usb sounds) when holding the power button and pressing it as if it worked and I was doing a hard reboot(about a 10 second press to shut down and get the usb disconnected noise). (Tried both adb devices and fastboot devices neither showed a device). Never have I seen this before and if I can get it working hopefully I will never see it again. Hopefully XDA's member's genius can make up for my stupidity. (most likely my fault being too hasty and skipping a step :silly.
Any questions about what I did or how I did it. Please ask!
Hey bud,
sorry about your troubles. I myself have just updated to ruu 3.18 and hboot 2.14 in order to flash the xylon rom. I'm not an expert at this: I'm just another person trying to get the best (vanilla) experience from his phone! Here's a couple things I noticed in my 9 hour trial & tribulation in going from 3.17 ruu + 1.09 hboot to the latest updates:
my pc also did not read my phone on a couple of occasions. Some parts of the process, I believe you have to be on your regular screen and the phone will reset into fastboot on its own. Later on, I had relocked my bootloader before I was supposed to, and was unable to write much. I just went back to step 1 and re-did everything (had to dig up a thread on unlocking my bootloader via htcdev).
my best friend helping through this was the hold power + vol down button. i kept going to stock recovery & rebooting my phone OR into fastboot and see which place I was supposed to be at.
as for your LCD being completely dead...I haven't come across that issue. The closest thing was when I was in RUU mode and there was only an HTC logo on the screen.
if you'd like, pm me and I can msg you the xda threads I used to get through it. I'm not sure how to approach the dead LCD, but I hope it all pans out for you.
I just wanted to share my experience, as a non-dev nor extremely savvy techie, I feel your pain brother.
Its not that the lcd is dead (unless it died after the ruu flash finished along with the notification led), more like it just wont turn on, along with the notification led, Where it would usually be on when plugged in, it just no longer turns on. Anyway thanks for your sympathy, I managed to jam the nano sim into my HTC arias micro sim slot without an adaptor (cyanogenmod 7 is its latest), so yeah at least I have a phone for the time being XD.
You flashed 3.18 with supercid and s-on. If you have supercid you need s-off before ruu to 3.18.
Sent from my HTC One XL using xda app-developers app
In other words, if you RUU'd with SuperCID and s-on, you're probably bricked.
Sent from my Evita
So far, from what you guys have posted, i'm out of luck on fixing the brick by myself. I do not know if either of these are an option so, again, fix my stupidity. First, I found a hard brick repair (mobiletechvideos, can't post link yet :/) which I have seen mentioned on the website a few times so I want to know if it can fix my brick and if the repair is worth trying. Second, is replacement from at&t/ HTC an option? Of course if anyone wants to comment a fix on my first post please do .
Starfrog6 said:
So far, from what you guys have posted, i'm out of luck on fixing the brick by myself. I do not know if either of these are an option so, again, fix my stupidity. First, I found a hard brick repair (mobiletechvideos, can't post link yet :/) which I have seen mentioned on the website a few times so I want to know if it can fix my brick and if the repair is worth trying. Second, is replacement from at&t/ HTC an option? Of course if anyone wants to comment a fix on my first post please do .
Click to expand...
Click to collapse
Jtagg is probably the best option, if you're within a year you can try sending it to HTC, if they figure out how you bricked, which is possible, they will charge you ~$200USD to replace the board.
Good luck.
If you ran the RUU with SuperCID and S-on, its bricked. JTAG is likely your only option to get the phone running again. You can look into the unbricking thread in General, and the JET tool in Development. But to my knowledge, nobody has been able to unbrick from this condition (SuperCID + S-on + RUU or OTA), short of JTAG. Yes, Mobiletechvideos has been mentioned on here as on JTAG option. Can't vouch for them personally, but others on here might be able to.
If you phone is less than a year old, you can likely get a warranty replacement from AT&T. Ethically, its a bit of a gray area IMO. I'm usually not crazy about people making warranty claims for failure to read, and as a result of you having modded the phone (which SuperCID is). But in reality, it shouldn't typically be expected for RUU plus SuperCID to brick the phone (past RUUs have run fine with SuperCID).
HTC is typically less forgiving about warranty issues. So no reason to try with them over AT&T. AT&T will pretty much honor the warranty for anything but obvious physical damage. They don't care if the phone has been modded, or bootloader unlocked (not that they would even be able to tell in your phone's current condition).
http://forum.xda-developers.com/showthread.php?t=2181929
I was bricked too.
I tried to relocking my bootloader and flashing the offficial jellybean without doing S-OFF first and bricked mine. I tried everything here at XDA with no luck. I gave up and sent it back to HTC and they had it back to me running the official jellybean update in 2 weeks. and without any charge. I even got it back on my birthday. It is running smooth and fast with no lag at all.
HTC One X+ AT&T Version
Hello there,
I tried updating my phone from Android Version 4.1.1 to the latest Android 4.2.2
But after installing my phone has stuck in the HTC logo and its bricked.
Please advice me for further proceedings.
My phone details :
Updated ROM image from 1.15.502.1 to 2.15.502.1
***RELOCKED***
EVITARE_UL PVT SHIP S-OFF RL
CID-11111111
HBOOT-1.73.0000
CPLD-None
RADIO-SSD:2.21.5517.15
eMMC-bootmode: disabled
CPU-BOOTMODE: disabled
HW Secure boot: enabled
MODEM TYPE: MDM9215M
Sep 30 2013,17:16:15
I have installed the RUU file which you have shared in the link above.
Please help me I need my phone in the working condition.
You're in the wrong forum. This is the HTC One XL forum, you want the HTC One X+ forum.
But, have you actually attempted to run an RUU from this section? Any RUU you find in this section is not for your device.
Sent from my Evita