Database Info

Noob - HTC One S on T-mobile stuck on edge with S-ON

I recently purchased a phone on ebay in great condition. It was locked, and was on stock rom. I decided I liked how my custom rom operated on my other phone so I unlocked, rooted, and added a custom rom (initally Cyanogenmod, then I tried PacMan) using this tutorial - http://forum.xda-developers.com/showthread.php?t=1583427.
Regardless of the ROM, I haven't been able to get anything over edge data speeds. I've checked the APN settings and they are correct. I have an unlimited data T-Mobile plan.
Here are some pieces of information that might prove helpful:
***TAMPERED***
***UNLOCKED***
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.13.50.05.31
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012, 17:10:57:-1
I was told that going back to stock ROM would fix this but that can't be the only way to get 4G...help?

The HTC One S
According to the seller, the phone's model is PJ40110.

My phone got stuck on EDGE after updating to the official JB OTA. I've tried a lot of things and have yet to find a fix. Might have to resort to sending it in for warranty, if possible. Looks like yours is on JB. Did you update it, or did you get it like that?
Here's my thread for reference: http://forum.xda-developers.com/showthread.php?t=2251286

dr3amsINdigital said:
My phone got stuck on EDGE after updating to the official JB OTA. I've tried a lot of things and have yet to find a fix. Might have to resort to sending it in for warranty, if possible. Looks like yours is on JB. Did you update it, or did you get it like that?
Here's my thread for reference: http://forum.xda-developers.com/showthread.php?t=2251286
Click to expand...
Click to collapse
I got it like that, then I updated it and still stuck on edge. Once I have tampered with the bootloader can I still use the warranty?

(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.13.50.05.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: **************************
(bootloader) imei: **************************
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4168mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Going to try downloading the appropriate RUU to see if that fixes it.

Have you tried forcing it to WCDMA only in *#*#4636#*#*?

There is no RUU yet for t-mobile JB, not that I know of.
Sent from my HTC VLE_U using xda app-developers app

usaff22 said:
Have you tried forcing it to WCDMA only in *#*#4636#*#*?
Click to expand...
Click to collapse
See attachment - when I do WCDMA only I get no data...

I'm beginning to wonder if it was a hardware issue...perhaps a bad antenna?

goosemon said:
I'm beginning to wonder if it was a hardware issue...perhaps a bad antenna?
Click to expand...
Click to collapse
Doubt this will help, but have you thought about trying to S-Off and then running an old RUU (ICS)? It sounds like it could be a hardware issue, though, as you mentioned.

npiper05 said:
Doubt this will help, but have you thought about trying to S-Off and then running an old RUU (ICS)? It sounds like it could be a hardware issue, though, as you mentioned.
Click to expand...
Click to collapse
I'm working on that now, currently getting error: device not found once I type adb shell to get SUPERCID. Looking at other posts to figure out how to get this to work. Phone connected to computer and showing FASTBOOT USB so the computer sees that it is connected. Once I get SUPERCID then I can get S-Off and try going back to ICS.

With adb shell, am I supposed to have my device driver files in the "platform tools" folder so the adb server can identify my phone? HTC Sense and drivers are already installed and work fine.

goosemon said:
With adb shell, am I supposed to have my device driver files in the "platform tools" folder so the adb server can identify my phone? HTC Sense and drivers are already installed and work fine.
Click to expand...
Click to collapse
Nope, just need HTC Sync, then uninstall it (so you're left with only the drivers) and get adb and fastboot files.
Edit: I don't think adb works in fastboot, works while booted only.
Sent from my HTC One S using Tapatalk 2

I've read that people that updated to the T-Mobile JB OTA can't get super CID, which means they can't get S-OFF. Let us know if it works out for you though.

dr3amsINdigital said:
I've read that people that updated to the T-Mobile JB OTA can't get super CID, which means they can't get S-OFF. Let us know if it works out for you though.
Click to expand...
Click to collapse
So I gotta go back to ICS to get SUPERCID...giving that a shot. At this point my sdcard can't be mounted, trying a fix from http://forum.xda-developers.com/showthread.php?t=1630459&page=25

goosemon said:
So I gotta go back to ICS to get SUPERCID...giving that a shot. At this point my sdcard can't be mounted, trying a fix from http://forum.xda-developers.com/showthread.php?t=1630459&page=25
Click to expand...
Click to collapse
I know you mentioned ADB not working when in fastboot. As a poster mentioned before, ADB only works when phone is booted up, not in fastboot. Make sure you have Debugging checked in developer options in the settings menue. I'm almost certain when you SuperCID, you start off with a booted up phone, not in fastboot, so that my be where you are running into an issue.
Also, do you have a custom recovery installed at this point? Just curios. Will your sd not mount in recovery, or just in general.
Keep working. You'll sort it out and learn a ton in the process. That's why I love XDA. Super helpful community.
Nick

npiper05 said:
I know you mentioned ADB not working when in fastboot. As a poster mentioned before, ADB only works when phone is booted up, not in fastboot. Make sure you have Debugging checked in developer options in the settings menue. I'm almost certain when you SuperCID, you start off with a booted up phone, not in fastboot, so that my be where you are running into an issue.
Also, do you have a custom recovery installed at this point? Just curios. Will your sd not mount in recovery, or just in general.
Keep working. You'll sort it out and learn a ton in the process. That's why I love XDA. Super helpful community.
Nick
Click to expand...
Click to collapse
I'll try ADB in regular bootup once I get sdcard to mount. This is in recovery...the latest clockworkmod recovery, I tried running Viperones rom and it happened sometime around 2 this morning, the details are a little fuzzy, I'm pretty sure I saw red and starting hitting my head against the wall and collapsed in tears and anguish

goosemon said:
I'll try ADB in regular bootup once I get sdcard to mount. This is in recovery...the latest clockworkmod recovery, I tried running Viperones rom and it happened sometime around 2 this morning, the details are a little fuzzy, I'm pretty sure I saw red and starting hitting my head against the wall and collapsed in tears and anguish
Click to expand...
Click to collapse
Been there and definitely understand. It can be frustrating, but I feel like most issues can be sorted out. Have you tried a different USB cord or port on your computer. Seems silly, but I've had similar issues, search high and low on xda, and someone suggested to try to different cord and it mounted. These phones can be moody.
Good luck and report back if you need more help.
Nick

Once I can find and flash stock recovery I think I'll be one step close to accessing my sdcard, and from there stock ROM or ICS ROM so I can get superCID, and then S-OFF.

goosemon said:
Once I can find and flash stock recovery I think I'll be one step close to accessing my sdcard, and from there stock ROM or ICS ROM so I can get superCID, and then S-OFF.
Click to expand...
Click to collapse
The first post in this thread has a link for the stock recovery http://forum.xda-developers.com/showthread.php?t=2250573

[Q] WiFi Problem, tried everything!

I've read numerous threads extensively about flashing, wifi problems, etc, still no WiFi, Unable to Scan for Network and turns itself on and off.
Tried a bunch of things, different ROMs like ARHD, ViperS, Codename Lungo CM9, CM10, CM10.1... here's the latest in order:
ARHD 7.2, firmware 3.32, flashed boot.img from zip inside the ROM, no WiFi, just keeps turning off and on back and forth.
Code:
fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.27.1100
INFOversion-baseband: N/A
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 9.99.999.999
INFOserialno: SH16JV602626
INFOimei: 356441045026925
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5811000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 4071mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 617f0a98
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.491s
Decided to go back to stock, Canadian Bell customer, flashed RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed.exe
Code:
fastboot oem lock
... INFODevice was already locked!
OKAY [ 0.008s]
finished. total time: 0.008s
Flashed RUU for 1.45, this is the getvar after:
Code:
INFOversion: 0.5
INFOversion-bootloader: 1.18.0000
INFOversion-baseband: N/A
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.45.666.5
INFOserialno: SH16JV602626
INFOimei: 356441045026925
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5811000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 3961mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 9d24123f
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.500s
Booted successfully, still no WiFi, Unable to Scan for Network and just turns back and forth.
Installed OTA_3.32.666.13_R-1.45.666.5_P1_signed_releasewxi5zuxsepds1lu0.zip from stock recovery, then took firmware.zip from inside the OTA update, renamed to PG58IMG.zip and flashed from bootloader, no errors.
Gets stuck at boot, stays at the HTC logo forever and doesn't go anywhere.
So gave up, flashed back to 1.45 RUU, bootloader says locked again, unlocked with Revolutionary, fastboot flash 4ext recovery, installed firmware 3.33 for ARHD, then flashed ARHD 7.2.
WiFi problem still persists, turning on WiFi just shows Unable to scan for network, then turns itself off, turns itself back on again, etc. Flashed back to 3.32 Universal firmware, still nothing, gets stuck at Turning Wi-Fi on... and doesn't go anywhere.
Stock kernel on ARHD, wiped cache + dalvik, made sure Radio and RIL matches, no SIM inside phone, also tried deleting /data/misc/wifi/wpa_supplicant.conf, no joy. Tried WiFix, nothing. Even tried to play with the brass pins above the camera.
So full flash back to stock and still doesn't work, I'm out of ideas. At one point I was able to connect to WiFi after flashing a European 1.45 RUU and then flashed the Bell 1.45 RUU, that's how I was able to install the OTA update. Installed OTA update from inside Android after downloading and got stuck at boot, so flashed back to Bell 1.45 RUU, and has never been able to get WiFi back again. Since I've tried so many things before and after the European RUU, it's impossible to reproduce the exact steps I did, but I've also tried flashing to the same European RUU again, and still no WiFi either.
Any help would be greatly appreciated!

Kwokinator said:
Any help would be greatly appreciated!
Click to expand...
Click to collapse
I'm taking a complete shot in the dark here.....but check to make sure your Wifi region is properly selected.
Go to settings>wifi>hit menu button>select advanced>wifi region code
Pick your country from that list.
If you flashed the RUU for the country you live it that SHOULD be correct already. But it won't hurt to check it.

I`m having the same problem
I tried many roms now and still - the wifi is unactivatable.
First the problem occurs to me, when i flashed the updates from cm10.1 with the goo mananger and the auto script for flashing.
Bach there, it was easy to solve this problem by wiping cache/dalvik cache and flashing the old version.
Now nothing solves that issue.
My next idea is to restore an older backup, i will give report here...

Skipjacks said:
I'm taking a complete shot in the dark here.....but check to make sure your Wifi region is properly selected.
Go to settings>wifi>hit menu button>select advanced>wifi region code
Pick your country from that list.
If you flashed the RUU for the country you live it that SHOULD be correct already. But it won't hurt to check it.
Click to expand...
Click to collapse
I'm on ARHD 7.2 now, there's no region code selection. In the Advanced menu there's Network Notification, Keep Wi-Fi on during sleep, Best WiFi Performance, MAC address, IP address, DLNA auto-IP.
Both MAC address and IP address shows as Unavailable.

Kwokinator said:
I'm on ARHD 7.2 now, there's no region code selection. In the Advanced menu there's Network Notification, Keep Wi-Fi on during sleep, Best WiFi Performance, MAC address, IP address, DLNA auto-IP.
Both MAC address and IP address shows as Unavailable.
Click to expand...
Click to collapse
Oh...that's a bummer. I didn't realize Sense based roms didn't have that option.
Try this, just for an experiment. Backup ARHD so you can go back to it. Then do a full wipe, install Albino's 4.2.2 AOSP based CM10.1 ROM. See if the wifi works in that one. If it does't work on boot, then look at the wifi settings where I showed you to see if changing the region code helps. More importantly, check to see what the region code is for you after boot before you change it.
If you can get it working using another ROM entirely, then we'll have at least eliminated hardware as the problem. If you have the exact same problem on a completely different ROM, different version, not sense, etc...then I'd starting leaning toward hardware issues.

Skipjacks said:
Oh...that's a bummer. I didn't realize Sense based roms didn't have that option.
Try this, just for an experiment. Backup ARHD so you can go back to it. Then do a full wipe, install Albino's 4.2.2 AOSP based CM10.1 ROM. See if the wifi works in that one. If it does't work on boot, then look at the wifi settings where I showed you to see if changing the region code helps. More importantly, check to see what the region code is for you after boot before you change it.
If you can get it working using another ROM entirely, then we'll have at least eliminated hardware as the problem. If you have the exact same problem on a completely different ROM, different version, not sense, etc...then I'd starting leaning toward hardware issues.
Click to expand...
Click to collapse
The phone boots up to MAC address and IP address still unavailable, region code is defaulted to Europe. Changed to Canada, Taiwan, then if I press the back button to go back out, WiFi is still trying to turn on, call up the region code again, it's back to Europe again so changes don't get saved. Then after a few minutes the phone will just reboot by itself, then after it boots up again the outcome is still the same.

Kwokinator said:
The phone boots up to MAC address and IP address still unavailable, region code is defaulted to Europe. Changed to Canada, Taiwan, then if I press the back button to go back out, WiFi is still trying to turn on, call up the region code again, it's back to Europe again so changes don't get saved. Then after a few minutes the phone will just reboot by itself, then after it boots up again the outcome is still the same.
Click to expand...
Click to collapse
This may sound stupid
But try this
Change the cid to standard one instead of supercid like HTC__001 for eg
Then reflash whatever rom you are using then check wifi
Btw cid changing command
fastboot oem writecid HTC__001
It will be better if you change back to your original cid
Sent from my HTC Sensation 4G using xda premium
---------- Post added at 07:41 PM ---------- Previous post was at 07:38 PM ----------
Also try Wifix Manager app if you haven't yet
Sent from my HTC Sensation 4G using xda premium

ganeshp said:
This may sound stupid
But try this
Change the cid to standard one instead of supercid like HTC__001 for eg
Then reflash whatever rom you are using then check wifi
Btw cid changing command
fastboot oem writecid HTC__001
It will be better if you change back to your original cid
Sent from my HTC Sensation 4G using xda premium
---------- Post added at 07:41 PM ---------- Previous post was at 07:38 PM ----------
Also try Wifix Manager app if you haven't yet
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
Changed the CID to HTC__001 and flashed the ARHD 7.2 zip again, still no go.
Tried WiFix already, doesn't work either.
Is it a hardware issue?

Kwokinator said:
Changed the CID to HTC__001 and flashed the ARHD 7.2 zip again, still no go.
Tried WiFix already, doesn't work either.
Is it a hardware issue?
Click to expand...
Click to collapse
seems like it check bluetooth too
also ..lift up the pins a little bit to have better contact on the back of phone ..just above the camera and see

I have Problem with wifi i use albino Kang 17.5.2013 aLogcat say failed to load driver and Supplicant not running, cannot connect

Kwokinator said:
Changed the CID to HTC__001 and flashed the ARHD 7.2 zip again, still no go.
Tried WiFix already, doesn't work either.
Is it a hardware issue?
Click to expand...
Click to collapse
Hi!! I'm having the same issues tried everything, switching firmwares even radio and nothing, both WIFI and Bluetooth not working is it a hardware thing? have you been able to fix it?
Thanks

Arquimercyless said:
Hi!! I'm having the same issues tried everything, switching firmwares even radio and nothing, both WIFI and Bluetooth not working is it a hardware thing? have you been able to fix it?
Thanks
Click to expand...
Click to collapse
did you try this guide?
http://forum.xda-developers.com/showthread.php?t=2085009

[SOLVED][Q] Phone is freezing after few seconds only. Even in Recovery.

Hello everyone,
My brother bought HTC One X+ so I got his Sensation very recently (though I helped him to Unlock, Root and ViperS it first time)
As a first time HTC user curiously I flashed couple of ROMs and finally settled on ViperS 3.1.2 (full wipe) yesterday
Problem started right after that. Phone started freezing every few seconds. I need to screen off the device for 1-2 minutes and then it will work for another few seconds and then freeze again completely.
Same thing happened in Recovery too. It took 8 battery pulls to flash ViperS again.
Since it is happening in both the Recovery and OS I narrowed it down to either of them
1. Bad SDCard
2. NAND problem
3. Some other hardware problem
Plz advise me as to what I should do to resolve this issue ?
(My brother will laugh at me that I could not handle HTC even for a day )
Thank you so much in advance !!!
UPDATE:
Seemingly re-flashing 4ext Recovery again and re-flashing ROM with full wipe solved the issue.
Thanks to both friends who helped me all the way especially rzr86
UPDATE 2:
Problem came back again. This time even worse
UPDATE 3:
My SDCard was the culprit. So if anyone has same issues first try another card.

try to format sdcard
then reflash vipers rom with full wipe
see how it goes
ddi you try with another sdcard?

rzr86 said:
try to format sdcard
then reflash vipers rom with full wipe
see how it goes
ddi you try with another sdcard?
Click to expand...
Click to collapse
Unfortunately I don't have another SDCard here with me. And Sensation does not have any internal memory or atleast I did not find any.
Should I buy a new SDCard ?

silentvisitor said:
Unfortunately I don't have another SDCard here with me. And Sensation does not have any internal memory or atleast I did not find any.
Should I buy a new SDCard ?
Click to expand...
Click to collapse
no need to buy yet a new sdcard
we didn't even know if it is sdcard's fault
try to format the current one

rzr86 said:
no need to buy yet a new sdcard
we didn't even know if it is sdcard's fault
try to format the current one
Click to expand...
Click to collapse
Ok. Doing a full format now.
Should I re-flash ViperS or try formatted SDCard for sometime ?
Thanks !

silentvisitor said:
Ok. Doing a full format now.
Should I re-flash ViperS or try formatted SDCard for sometime ?
Thanks !
Click to expand...
Click to collapse
Format it once and then put the rom zip in the sdcard and flash it from recovery
Sent from my HTC Sensation Z710e using xda premium

Nice.....!!!!!!!
It seems working fine for now.
Let see.
Thanks rzr86

It froze again now

silentvisitor said:
It froze again now
Click to expand...
Click to collapse
i suggest to use a ruu.exe to return to stock
if you are on S-OFF dont worry you won't lose it
http://forum.xda-developers.com/showthread.php?t=1672425
see if it freezes again

rzr86 said:
i suggest to use a ruu.exe to return to stock
if you are on S-OFF dont worry you won't lose it
http://forum.xda-developers.com/showthread.php?t=1672425
see if it freezes again
Click to expand...
Click to collapse
I'm S-ON and this whole stuff looked quite complicated
Whole phone is working fine except touch screen sometimes, randomly.
Any other ideas/suggestions apart from RUU ?
Thanks !

silentvisitor said:
I'm S-ON and this whole stuff looked quite complicated
Whole phone is working fine except touch screen sometimes, randomly.
Any other ideas/suggestions apart from RUU ?
Thanks !
Click to expand...
Click to collapse
Your phone gets hang or only touch screen becomes unresponsive? I guess you should give a try to touch screen recalibration tool. You can found it in the development section.
Sent from my HTC Sensation Z710e

silentvisitor said:
I'm S-ON and this whole stuff looked quite complicated
Whole phone is working fine except touch screen sometimes, randomly.
Any other ideas/suggestions apart from RUU ?
Thanks !
Click to expand...
Click to collapse
using an ruu we will see if it is a hardware problem
if you still have freezes after ruu then probably it is a hardware issue
once you are on S-ON just relock the bootloader by using the fastboot command
then run the ruu.exe from pc
another suggestion is go to venom tweaks->misc tab->lcd density and change to 250
see how it goes

I flashed ViperS again today morning without wiping and since then it hasn't frozen except once when I was playing music in the background and editing id3 tags of few songs. After few seconds keyboard started typing random letters on its own. Screen off and on and it was good for another few seconds. Except this it has been good all day

Hmm...started again. Keyboard is typing on its own. Otherwise its normal. Virus ?
Which recalibration tool ? Is that safe ?
Is there any way to completely format all the partitions to eliminate any low (system) level virus issue ?
Thanks !

silentvisitor said:
Hmm...started again. Keyboard is typing on its own. Otherwise its normal. Virus ?
Which recalibration tool ? Is that safe ?
Is there any way to completely format all the partitions to eliminate any low (system) level virus issue ?
Thanks !
Click to expand...
Click to collapse
Search the forum where someone succeded to zeroing all partitions
I don't remember the thread unfortunately
But I suggest also to use the ruu
Sent from my HTC Sensation Z710e using xda premium

So after RUUing I will have to re-unlock my bootloader through HTCDev or old token will work ?
Btw, what is this Quick launch thing in Venom Tweaks under Statusbar tab ? What it does ? Found no difference anywhere.
Thanks !

silentvisitor said:
Hmm...started again. Keyboard is typing on its own. Otherwise its normal. Virus ?
Which recalibration tool ? Is that safe ?
Is there any way to completely format all the partitions to eliminate any low (system) level virus issue ?
Thanks !
Click to expand...
Click to collapse
Use this tool to recalibrate your touch screen.
http://forum.xda-developers.com/showthread.php?t=2437293.
It will erase your data to it is advised to make a backup first. Hope this solve your issue.
Sent from my HTC Sensation Z710e

Hey, thanks for the link. Checking it.
I doubt its a screen issue as after this keyboard thing phone hangs too but becomes normal after screen on-off.
@rzr86 Hi, my software version is 3.33 and there is no RUU with this version. What to do?
Thanks guys !

silentvisitor said:
Hey, thanks for the link. Checking it.
I doubt its a screen issue as after this keyboard thing phone hangs too but becomes normal after screen on-off.
@rzr86 Hi, my software version is 3.33 and there is no RUU with this version. What to do?
Thanks guys !
Click to expand...
Click to collapse
No need to follow again the procedure from htcdev site
Only use the unlock code.bin
Post the output from this command
fastboot getvar all
Sent from my HTC Sensation Z710e using xda premium

Here it is :
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.720.6
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4180mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
My local friend here suggested me to try ViperS 1.6.3 to see if it is some issue with ViperS 3.1.2

[Q] Sensation xe continuesly restarts, restart loop, help

htc sensation XE
Hi to all, I’m a newbie to the site and therefore apologies in advance if I’m asking or going to ask simple, newbie questions. I hope someone can help me, many thanks in advance
I went on holiday - whilst abroad I used my phone extensively to take pics, vibers calls, whats app and gps tracking without the SIM. on return when I touched home soil and placed my SIM into the phone it started rebooting in a constant loop i.e. I’m powering the device and it loads up to the home page and then restarts.
What I have done so far, very reluctantly: wiped the cache and restored factory setting with out the SIM card and the SD card - result = NO JOY
Can anyone help me please??? I keep reading that the phone may require flashing, can someone give me step by step instructions.
Much appreciated

gixxer600k6 said:
htc sensation XE
Hi to all, I’m a newbie to the site and therefore apologies in advance if I’m asking or going to ask simple, newbie questions. I hope someone can help me, many thanks in advance
I went on holiday - whilst abroad I used my phone extensively to take pics, vibers calls, whats app and gps tracking without the SIM. on return when I touched home soil and placed my SIM into the phone it started rebooting in a constant loop i.e. I’m powering the device and it loads up to the home page and then restarts.
What I have done so far, very reluctantly: wiped the cache and restored factory setting with out the SIM card and the SD card - result = NO JOY
Can anyone help me please??? I keep reading that the phone may require flashing, can someone give me step by step instructions.
Much appreciated
Click to expand...
Click to collapse
Seems like a loose battery problem. Just try putting a piece of paper between battery and body to make battery fit tight. I guess issue will be resolved after this. Try and report back.
Sent from my HTC Sensation Z710e

thanks, i tried this method and no result.
MrJukeHardbane said:
Seems like a loose battery problem. Just try putting a piece of paper between battery and body to make battery fit tight. I guess issue will be resolved after this. Try and report back.
Sent from my HTC Sensation Z710e
Click to expand...
Click to collapse

gixxer600k6 said:
thanks, i tried this method and no result.
Click to expand...
Click to collapse
Go to fastboot mode, and run
Code:
fastboot getvar all
Post the results (remove imei, serial)

how do i do that? i can get to the bootloader i.e. by holding the volume button down and power on.
i see the fastboot option, i can select this via the power button and thereafter i get 4 options :
1bootloader
2reboot
3reboot boatloader
4power down
appreciate the help,
Far_SighT said:
Go to fastboot mode, and run
Code:
fastboot getvar all
Post the results (remove imei, serial)
Click to expand...
Click to collapse

Can you confirm if the following is correct - just been reading a little about fastboot - am i correct in understanding that i have to download SDK to my pc/laptop and then connect my phone via usb thereafter, i need to go into bootloader of the phone and select fastboot, and then issue the command via the PC. What does the command do? many thanks
gixxer600k6 said:
how do i do that? i can get to the bootloader i.e. by holding the volume button down and power on.
i see the fastboot option, i can select this via the power button and thereafter i get 4 options :
1bootloader
2reboot
3reboot boatloader
4power down
appreciate the help,
Click to expand...
Click to collapse

gixxer600k6 said:
Can you confirm if the following is correct - just been reading a little about fastboot - am i correct in understanding that i have to download SDK to my pc/laptop and then connect my phone via usb thereafter, i need to go into bootloader of the phone and select fastboot, and then issue the command via the PC. What does the command do? many thanks
Click to expand...
Click to collapse
Correct. The command gives information about the board (the phone itself). Some of it is firmware version and many more. For security reasons when you post it to anywhere, remove the IMEI number and Serial.
Also, There is an issue when connecting to 2G networks on some devices that the device reboots. Can you try locking it to 3G only? (On the dialer Type *#*#4636#*#*, then choose "phone information", and there there will be a drop down list of network modes, choose WCDMA Only).

many thanks, i need some guidance, can you point me to a step by step guide if there is one available?
astar26 said:
Correct. The command gives information about the board (the phone itself). Some of it is firmware version and many more. For security reasons when you post it to anywhere, remove the IMEI number and Serial.
Also, There is an issue when connecting to 2G networks on some devices that the device reboots. Can you try locking it to 3G only? (On the dialer Type *#*#4636#*#*, then choose "phone information", and there there will be a drop down list of network modes, choose WCDMA Only).
Click to expand...
Click to collapse

ok managed to load the SDK and pull off the info as per previous post, what next ?? many thanks in advance
C:\AndroidSDK\sdk\tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.29.0000
(bootloader) version-baseband: 11.24A.3504.31_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.153
(bootloader) serialno: SH1____________
(bootloader) imei: 3591____________
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813001
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4113mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 705f86f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.500s
gixxer600k6 said:
many thanks, i need some guidance, can you point me to a step by step guide if there is one available?
Click to expand...
Click to collapse

gixxer600k6 said:
ok managed to load the SDK and pull off the info as per previous post, what next ?? many thanks in advance
C:\AndroidSDK\sdk\tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.29.0000
(bootloader) version-baseband: 11.24A.3504.31_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.153
(bootloader) serialno: SH1____________
(bootloader) imei: 3591____________
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813001
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4113mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 705f86f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.500s
Click to expand...
Click to collapse
This is for general information and I don't know what Far_Sight had in mind for this, but did you try my suggestion (of locking your device to 3g only?) I provided instuctions for that on my previous comment.

astar26 said:
This is for general information and I don't know what Far_Sight had in mind for this, but did you try my suggestion (of locking your device to 3g only?) I provided instuctions for that on my previous comment.
Click to expand...
Click to collapse
@astar26 I asked him to post this so that it is clear what we're dealing with.
Before going into flashing, make sure you have tried all the obvious ways like battery connections, change of SIM card etc.
The easiest way would be to do an ruu. It will reflash all your partitions and can help you out. See http://forum.xda-developers.com/showthread.php?t=1672425
Alternative is to unlock your device and flash custom Rom. Since you did a factory reset already follow http://forum.xda-developers.com/showthread.php?t=1631861 to unlock your bootloader and flash a custom recovery. Then either flash the ahrd Rom (link in the thread) or the stock one again
THESE METHODS WILL MAKE YOU FORMAT YOUR PHONE AGAIN (YOU'LL LOOSE YOUR DATA).
Happy to help.

many thanks again for the reply
I can’t get that far i.e. to the keypad, the phone starts, I see the htc logo and then it seems normal for maybe 2/3 seconds and then reboots. I have to remove the battery to power it down otherwise it continues the restart boot loop over and over again. I can get to the bootloader if there is a way to do it from there please provide newbie instructions.
Also the bootloader is unlocked - the previous owner unlocked it (I have had the phone like this since it was 4 months old and has been absolutely fine)
I’m thinking if it’s not a hardware issue then to flash the ROM and see if it resolves it. Now my issue is that I haven’t done anything like this before and when I Google for info it’s a bit like opening up a can of worms lol.
Am I correct, please confirm the following and put me right please

1:As the bootloaders unlocked can I download htc syn to my laptop, then download the correct RUU to the laptop, thereafter connect the phone via usb and boot into the bootloader and select fastboot, after selecting the fastboot option it should change to fastboot usb. Once this is done I can run the RUU and job done. (Is this correct)
2:According to an article I read my phone has a codename, is the codename for my phone Pyramid?
3nce I know the correct codename I can download the RUU from ‘shipped roms’ (http://www.shipped-roms.com/?category=android), Also at this stage when I select Pyramid I get a load of options for various RUU’s – which one is the correct one? And how do I know?
astar26 said:
This is for general information and I don't know what Far_Sight had in mind for this, but did you try my suggestion (of locking your device to 3g only?) I provided instuctions for that on my previous comment.
Click to expand...
Click to collapse

gixxer600k6 said:
many thanks again for the reply
I can’t get that far i.e. to the keypad, the phone starts, I see the htc logo and then it seems normal for maybe 2/3 seconds and then reboots. I have to remove the battery to power it down otherwise it continues the restart boot loop over and over again. I can get to the bootloader if there is a way to do it from there please provide newbie instructions.
Also the bootloader is unlocked - the previous owner unlocked it (I have had the phone like this since it was 4 months old and has been absolutely fine)
I’m thinking if it’s not a hardware issue then to flash the ROM and see if it resolves it. Now my issue is that I haven’t done anything like this before and when I Google for info it’s a bit like opening up a can of worms lol.
Am I correct, please confirm the following and put me right please

1:As the bootloaders unlocked can I download htc syn to my laptop, then download the correct RUU to the laptop, thereafter connect the phone via usb and boot into the bootloader and select fastboot, after selecting the fastboot option it should change to fastboot usb. Once this is done I can run the RUU and job done. (Is this correct)
2:According to an article I read my phone has a codename, is the codename for my phone Pyramid?
3nce I know the correct codename I can download the RUU from ‘shipped roms’ (http://www.shipped-roms.com/?category=android), Also at this stage when I select Pyramid I get a load of options for various RUU’s – which one is the correct one? And how do I know?
Click to expand...
Click to collapse
1) Bootloader unlocked means you can flash custom ROMs, but not firmware (only via RUU).
2) Yes, it is Pyramid
3) Since you are not S-Off, you need the exact RUU for your CID, which is HTC__001 in your case, which means you need a WWE one (good for you, as this one is easily found).

gixxer600k6 said:
many thanks again for the reply
I can’t get that far i.e. to the keypad, the phone starts, I see the htc logo and then it seems normal for maybe 2/3 seconds and then reboots. I have to remove the battery to power it down otherwise it continues the restart boot loop over and over again. I can get to the bootloader if there is a way to do it from there please provide newbie instructions.
Also the bootloader is unlocked - the previous owner unlocked it (I have had the phone like this since it was 4 months old and has been absolutely fine)
I’m thinking if it’s not a hardware issue then to flash the ROM and see if it resolves it. Now my issue is that I haven’t done anything like this before and when I Google for info it’s a bit like opening up a can of worms lol.
Am I correct, please confirm the following and put me right please

1:As the bootloaders unlocked can I download htc syn to my laptop, then download the correct RUU to the laptop, thereafter connect the phone via usb and boot into the bootloader and select fastboot, after selecting the fastboot option it should change to fastboot usb. Once this is done I can run the RUU and job done. (Is this correct)
2:According to an article I read my phone has a codename, is the codename for my phone Pyramid?
3nce I know the correct codename I can download the RUU from ‘shipped roms’ (http://www.shipped-roms.com/?category=android), Also at this stage when I select Pyramid I get a load of options for various RUU’s – which one is the correct one? And how do I know?
Click to expand...
Click to collapse
1)you are correct:good:
but i think you don't need htc sync(i am not sure for that)
2)sensation/xe/4G's codename is pyramid
3)the ruu have to correspond with your region(same firmware or higher) and your cid
you can also see Far_SighT's post for RUU
but i suggest to flash first the stock rom from recovery
if you don't have a custom recovery flash 4ext(again from Far_SighT's post on how to flash it,only step 2)
then from recovery :
nandroid backup just in case
format all partitions except sdcard
enable smartflash
flash the rom
done

Many thanks to all that have replied and viewed with the intent to help
I have managed to resolve the phone using the guide provided. I downloaded an RUU.
It was quite interesting doing all this 
I flashed the phone with an identical ROM i.e. version 3.33.401.153 – so I’m guessing whilst on holiday something happened which caused the software to get corrupt!
Next question, is it possible to flash the ROM again but with maybe the latest firmware – if yes can someone recommend an RUU.
many thanks

gixxer600k6 said:
Many thanks to all that have replied and viewed with the intent to help
I have managed to resolve the phone using the guide provided. I downloaded an RUU.
It was quite interesting doing all this 
I flashed the phone with an identical ROM i.e. version 3.33.401.153 – so I’m guessing whilst on holiday something happened which caused the software to get corrupt!
Next question, is it possible to flash the ROM again but with maybe the latest firmware – if yes can someone recommend an RUU.
many thanks
Click to expand...
Click to collapse
if you used a RUU with 3.33 firmware then you have the latest

@astar26 has the right idea. I had this issue for a long time, and after my own investigation I concluded that it was either the phones connection to 2g was resetting it, or I damaged the cpu by heavy overclocking. But the fix for the former helped me very much. One thing to note, if you can power up the device and have it perfectly without your SIM card in it. Or you can power it up with the phone in aeroplane mode then it tends to help the rebooting stop for a little while when your simcard is reactivated
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2

[Q] Phone stuck on 'quietly brilliant' screen

Hi all,
For no reason - overnight - my phone just stopped working. It displays the 'quietly brilliant' screen forever. It is HTC One X ATT version, unlocked and runs on t-mobile. I already bought it unlocked on Amazon and never 'tampered' with it nor anything.
I tired to obtain help from HTC support - they told me to hold the power button for 3 minutes, then all buttons for 2 minutes - nothing helped. Before I send it for repair I thought I would ask here.
I am able to boot into HBOOT by holding the volume- button. Then if I go into FASTBOOT and connect the phone (all drivers installed) the mode changes to FASTBOOT USB. I've downloaded the 3.07 RUU from HTC and tried that. It recognizes the phone while in the ".. USB" mode and does the 1st step: reboot. The phone boots into 'quietly brilliant' screen and the connection times out.
Next, I downloaded the android SDK and tried to connect with fastboot manually - I am able to connect, but unable to flash anything - signature not matching, etc. Clearing cache didn't help either - that was about all I could do with my skill level.
My HBOOT screen shows the following:
*** LOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.09.0000
RADIO-0.17.32.09.12
OpenDSP-v28.1.0.32.0504
eMCC-boot
Apr 2 2012,21:08:24
I've tried many tips from this forum but wasn't able to get anything to work. Help please!

mfigrs said:
Hi all,
For no reason - overnight - my phone just stopped working. It displays the 'quietly brilliant' screen forever. It is HTC One X ATT version, unlocked and runs on t-mobile. I already bought it unlocked on Amazon and never 'tampered' with it nor anything.
I tired to obtain help from HTC support - they told me to hold the power button for 3 minutes, then all buttons for 2 minutes - nothing helped. Before I send it for repair I thought I would ask here.
I am able to boot into HBOOT by holding the volume- button. Then if I go into FASTBOOT and connect the phone (all drivers installed) the mode changes to FASTBOOT USB. I've downloaded the 3.07 RUU from HTC and tried that. It recognizes the phone while in the ".. USB" mode and does the 1st step: reboot. The phone boots into 'quietly brilliant' screen and the connection times out.
Next, I downloaded the android SDK and tried to connect with fastboot manually - I am able to connect, but unable to flash anything - signature not matching, etc. Clearing cache didn't help either - that was about all I could do with my skill level.
My HBOOT screen shows the following:
*** LOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.09.0000
RADIO-0.17.32.09.12
OpenDSP-v28.1.0.32.0504
eMCC-boot
Apr 2 2012,21:08:24
I've tried many tips from this forum but wasn't able to get anything to work. Help please!
Click to expand...
Click to collapse
Anybody feel free to correct me if I am wrong, but you phones HBOOT should say this,
Since you are not rooted ignore whatever is in parenthesis.
(***TAMPERED***)
(***UNLOCKED***)
EVITA PVT SHIP (S-OFF) RL
(CID-11111111)
HBOOT-2.14.0000
RADIO-0.24P.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012, 18:37:14:-1
Now if I am right, the problem should be that your RUU needs updating. You also seem to be running an old radio version. Your OpenDSP is outdated as well. I would suggest updating your RUU and radio version, I think your OpenDSP should be updated with the RUU. @Madcat8686 would probably be better at explaining everything and being able to give you links, but I think that is the main issue.

The trick is, the phone doesn't take the RUU update - at least not the recent one from HTC website. I have tried other updates though, and they didn't work either. After the 1st reboot the phone gets stuck on 'quietly brilliant' screen and is never recognized again by the computer, so it just times out.
Besides, I really don't care how much it is outdated as long as it works. Meanwhile - it doesn't, and that is the problem I am trying to fix. Factory reset and recovery didn't work either...

mfigrs said:
The trick is, the phone doesn't take the RUU update - at least not the recent one from HTC website. I have tried other updates though, and they didn't work either. After the 1st reboot the phone gets stuck on 'quietly brilliant' screen and is never recognized again by the computer, so it just times out.
Besides, I really don't care how much it is outdated as long as it works. Meanwhile - it doesn't, and that is the problem I am trying to fix. Factory reset and recovery didn't work either...
Click to expand...
Click to collapse
Do you know if it was running the Android 4.1.1 update or the original android 4.0.4?

ChadMan097 said:
Anybody feel free to correct me if I am wrong, but you phones HBOOT should say this,
Since you are not rooted ignore whatever is in parenthesis.
(***TAMPERED***)
(***UNLOCKED***)
EVITA PVT SHIP (S-OFF) RL
(CID-11111111)
HBOOT-2.14.0000
RADIO-0.24P.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012, 18:37:14:-1
Now if I am right, the problem should be that your RUU needs updating. You also seem to be running an old radio version. Your OpenDSP is outdated as well. I would suggest updating your RUU and radio version, I think your OpenDSP should be updated with the RUU. @Madcat8686 would probably be better at explaining everything and being able to give you links, but I think that is the main issue.
Click to expand...
Click to collapse
Not exactly true. It should say what the user had first posted. The reason his radio is old is because you can't change radio on an unmodified phone. Nothing really needs updating as you put it, but an RUU should at least get the phone booting.
Sent from my Evita.
---------- Post added at 09:59 AM ---------- Previous post was at 09:58 AM ----------
mfigrs said:
The trick is, the phone doesn't take the RUU update - at least not the recent one from HTC website. I have tried other updates though, and they didn't work either. After the 1st reboot the phone gets stuck on 'quietly brilliant' screen and is never recognized again by the computer, so it just times out.
Besides, I really don't care how much it is outdated as long as it works. Meanwhile - it doesn't, and that is the problem I am trying to fix. Factory reset and recovery didn't work either...
Click to expand...
Click to collapse
That 3.07 RUU doesn't exist for our device, that's why it didn't work. Go to androidruu.com and navigate to the Evita section, there you'll find RUU's for our phone. Find one that is at&t/Cingular and try again.
Sent from my Evita.

mfigrs said:
Hi all,
For no reason - overnight - my phone just stopped working. It displays the 'quietly brilliant' screen forever. It is HTC One X ATT version, unlocked and runs on t-mobile. I already bought it unlocked on Amazon and never 'tampered' with it nor anything.
I tired to obtain help from HTC support - they told me to hold the power button for 3 minutes, then all buttons for 2 minutes - nothing helped. Before I send it for repair I thought I would ask here.
I am able to boot into HBOOT by holding the volume- button. Then if I go into FASTBOOT and connect the phone (all drivers installed) the mode changes to FASTBOOT USB. I've downloaded the 3.07 RUU from HTC and tried that. It recognizes the phone while in the ".. USB" mode and does the 1st step: reboot. The phone boots into 'quietly brilliant' screen and the connection times out.
Next, I downloaded the android SDK and tried to connect with fastboot manually - I am able to connect, but unable to flash anything - signature not matching, etc. Clearing cache didn't help either - that was about all I could do with my skill level.
My HBOOT screen shows the following:
*** LOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.09.0000
RADIO-0.17.32.09.12
OpenDSP-v28.1.0.32.0504
eMCC-boot
Apr 2 2012,21:08:24
I've tried many tips from this forum but wasn't able to get anything to work. Help please!
Click to expand...
Click to collapse
In fastboot mode (bootloader) with a command prompt type: fastboot getvar all
Post those details and then we can see the bigger picture. Please edit out your IMEI live when posting.
Edit - (just on the off chance you have superCID)

timmaaa said:
Not exactly true. It should say what the user had first posted. The reason his radio is old is because you can't change radio on an unmodified phone. Nothing really needs updating as you put it, but an RUU should at least get the phone booting.
Sent from my Evita.
---------- Post added at 09:59 AM ---------- Previous post was at 09:58 AM ----------
That 3.07 RUU doesn't exist for our device, that's why it didn't work. Go to androidruu.com and navigate to the Evita section, there you'll find RUU's for our phone. Find one that is at&t/Cingular and try again.
Sent from my Evita.
Click to expand...
Click to collapse
Right, but wouldn't that be the latest update for the device. He most likely got the international RUU update.

He can run any Evita RUU later than his current firmware version, it doesn't have to be the latest.
Sent from my Evita.

Hello everyone,
The results of 'getvar all':
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.17.32.09.12
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.85.502.3
(bootloader) serialno: HT246W30???? [last 4 digits obscured]
(bootloader) imei: ---
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4126mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: e964c535
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.094s
Responding to other questions - I think the RUU 3.07 that I downloaded from HTC suport page for ATT phone should normally work. In the filename it says Cingular, however I also tried other RUUs (at least one) that I downloaded from somewhere, and it didn't work as well. I tried flashing just 'boot_signed.img' from one of those ruus - result: failed - because of signature or something like that.
Regards,

Dude, I like I already said, that 3.07 RUU is not for our device, it's for the HTC One. Just because it says Cingular in the filename doesn't mean it's for our device, it just means it's an at&t RUU. Stop trying RUU's from random places, go to this site:
http://androidruu.com/?developer=Evita
That's where you'll find RUU's for Evita.
Sent from my Evita.

Guys, please - that's not the point!
timmaaa said:
Stop trying RUU's from random places, go to this site: (... it doesn't let me keep the link ...)
Click to expand...
Click to collapse
That's exactly the site I got my other RUU from. The first one that I tried was from HTC website and had this filename: "RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial.exe". It says "EVITA" as plainly as it could. I am aware of that.
The thing is: both didn't work. OK, I'm going to try another one just for the sake of completeness, but with two previous attempts the story was the same:
1) Turn on the phone holding volume-
2) Select FASTBOOT
3) Connect to USB
4) Launch RUU
5) Click through dialogs, agree to everything
6) Message appears "Verifying information..."
7) New dialog pops up allowing me to select the 3.18.502.6 update
8) I click Next -> Next -> ...
9) The dialog opens with a message that the phone is being "prepared" for update and it will be rebooted to bootloader
10) Phone reboots and goes to the 'quietly brilliant' screen (or more recently - just black screen)
11) Computer shows message "Waiting for bootloader"
12) Computer times out -> the only available option is Exit.
End of story for me. Is there a way to somehow fix that? I'm OK with doing stuff from cmd - it's just that none of the tips I found in this forum actually worked. For example, adb always ends up with error 'device not found' and fastboot only works while the phone is in the fastboot menu, but does not let me flash anything.
Thanks.

Ok, but the only RUU you specifically mentioned up until this point was one that isn't for this device (3.07), which is why I posted that. Maybe you got it from androidruu, but you definitely didn't get it from the Evita section. There's no need to get narky at me for trying to make sure you don't brick your phone after you've already run at least one RUU that isn't for your device.
Perhaps you need to try the 2.20 at&t RUU.
Sent from my Evita.

You could try putting it into RUU mode to try and force it to flash. I had to do that to mine about 5 hours ago. Just go to fastboot, type "fastboot OEM rebootRUU" and try running the RUU from there.
Sent from my HTC One X using xda app-developers app

My apologies for the confusion - the RUU I was mentioning as 3.07 is actually 3.07.2012 - this way it's being referred to on the HTC website, but the software version in it is 3.18. I'm not allowed to post links yet, so it's kind of hard to explain...
I have tried the 'rebootRUU' trick - it didn't do anything. After some experiments I found that letter sizes do matter - when I entered "fastboot oem rebootRUU" the phone actually rebooted. However, it went straight into the 'quietly brilliant' screen and I wasn't even able to go past the "Verifying information" pop-up on the computer - it ended up in 'usb connection timed out' error.
Anyway, I will try 2.20 - if that one doesn't work, I guess I'll have to send it for service.
Thank you all for trying to help.

timmaaa said:
Ok, but the only RUU you specifically mentioned up until this point was one that isn't for this device (3.07), which is why I posted that. Maybe you got it from androidruu, but you definitely didn't get it from the Evita section. There's no need to get narky at me for trying to make sure you don't brick your phone after you've already run at least one RUU that isn't for your device.
Perhaps you need to try the 2.20 at&t RUU.
Sent from my Evita.
Click to expand...
Click to collapse
http :// www htc com /us/support/htc-one-x-att/news (sorry can't post links)
I think the op might be talking about this RUU which i can confirm does indeed work for the One X. If not, try this RUU! You said it was 3.07.2012 but this is 3.07.2013 not sure if just a typo but here's hoping!
As for the phone, if the RUU doesn't work then it might be a hardware issue not letting the phone boot. It's happened to me on the EVO 4G and no amount of software flashing would fix that.
Also, this probably won't make a difference, but make sure to run the RUU as administrator

mfigrs said:
My apologies for the confusion - the RUU I was mentioning as 3.07 is actually 3.07.2012 - this way it's being referred to on the HTC website, but the software version in it is 3.18.
Click to expand...
Click to collapse
3.07.2013 (its not 2012) is neither the RUU number nor the software version, its the date the RUU was posted to the HTC website (March 7, 2013).
The software/RUU number is 3.18.502.6
The software/RUU number is always in the file name.