Database Info

[Q] One S Radio Upgrade?

Hey guys,
I'm running a One S (S4) on Virtuous RC1 and suffering from the phantom home button pressing.
I've read that this should be resolved in later radio updates - I'm currently on 1.06es.50.02.31_10.09a.50.04L
The issue, I'm guessing, is that my HBoot has been upgraded when the phone was in for warranty repair to 1.14. Recovery is currently TWRP 2.3.0.0
Anyone know what the best way to upgrade the radio is, or if this will even resolve the phantom home button pressing (which makes the phone VERY annoying to use)
Thanks
Russell

I have also hboot 1.13 and need to know how to upgrade
Sent from my HTC One S using xda app-developers app

There are 2 possibilities atm, use an AOSP based Rom like CM, AOKP, etc.
or downgrade your HBoot,
BE WARNED, this will brick your device, there is also explained how to unbrick your device,
ONLY DO THIS, if you really know what you are doing,
neither I or the creater of the guide will be responsible if you can`t unbrick your device,
you will do this on YOUR OWN RISK!
In both cases, you can use the Radio Installers from this Thread to install a new Radio

Thanks fr the info, that looks like a whole lot of work!
Does anyone know if the phantom home button pressing is definitely resolved by a later radio?
Are there any other options to install the radio (install RUU for example?)
Just need to weigh up my options before taking the plunge

I've re-locked and installed RUU to get back to stock, updated using the OTA and got latest radio.
Not had the home button issue since... still early days but signs are good.
Thanks to all for your help.

RadugaUK said:
I've re-locked and installed RUU to get back to stock, updated using the OTA and got latest radio.
Not had the home button issue since... still early days but signs are good.
Thanks to all for your help.
Click to expand...
Click to collapse
did you have to flash stock recovery?

PulpzillA said:
did you have to flash stock recovery?
Click to expand...
Click to collapse
If you going to run a RUU then you only need to lock the bootloader but a safe way would to flash stock recovery then lock it.

I did flash the stock recovery - almost everything I read seemed to think this was the safest way to get back to stock.

[Q] Phone not turning on after stock recovery flash

So, just to set the stage, I'm not a developer, but I'm fairly practiced at using ADB, unlocking bootloaders, rooting and unrooting, and installing custom recoveries and ROMs - that is to say, I know what I'm doing. I recently bought an HTC One, and in preparation for wanting to sell my One X on ebay, I wanted to return it to completely stock and make sure OTA updates were working properly.
I started by relocking the bootloading and installing the 2.20.502.7 RUU (I have an AT&T One X). That went fine and booted up properly, but I wasn't seeing the OTA updates, so I thought maybe the stock recovery hadn't been installed properly, and when I tried to boot into the recovery I couldn't get the menu to show (the initial image appeared, but holding Vol Up+Down didn't do anything, just made the error image appear after several seconds). So I downloaded the stock recovery image, reunlocked the bootloader, flashed the stock recovery...and then when I went to reboot the phone turned off and hasn't turned back on since.
Getting stuck in a bootloop or something I know how to deal with, but the phone is completely unresponsive, holding the power button for any length of time seems to have no effect, hoping you guys might have some ideas.
FYI My phone was on bootloader 1.09 before flashing the RUU, 1.14 after.

Requested moving to the AT&T One X forums

TToivanen said:
Requested moving to the AT&T One X forums
Click to expand...
Click to collapse
Ugh....thought that's where I was, evidently didn't look at the forum close enough...

bikeracer4487 said:
So I downloaded the stock recovery image, reunlocked the bootloader, flashed the stock recovery...and then when I went to reboot the phone turned off and hasn't turned back on since.
Click to expand...
Click to collapse
Where did you download from, and can you give link? Any charge light, when you connect the wall charger?

redpoint73 said:
Where did you download from, and can you give link? Any charge light, when you connect the wall charger?
Click to expand...
Click to collapse
Link to site of download link: http://onexroot.com/one-x-unroot/how-to-unroot-rooted-htc-one-x/
Download link: http://downloadandroidrom.com/file/HTCOneX/unroot/OneXUnroot.zip
Connecting charger shows blinking red notification light. As a side note, the phone was at 96% battery when I was working on it and I left it plugged in overnight, just in case.

That website doesn't make mention of the AT&T version. Not certain, but I'm inclined to believe its the recovery for the quad core version. Different hardware, with different partitions, so you might be hosed.
Take great care when you install mods from these kinds of websites (places other than XDA). They often do not clearly delineate between the dual core and quad core versions of the One X.

redpoint73 said:
That website doesn't make mention of the AT&T version. Not certain, but I'm inclined to believe its the recovery for the quad core version. Different hardware, with different partitions, so you might be hosed.
Take great care when you install mods from these kinds of websites (places other than XDA). They often do not clearly delineate between the dual core and quad core versions of the One X.
Click to expand...
Click to collapse
Yeah...that was dumb...I realized what you were getting at as I was getting the link for you... That said, I WAS able to get it turn on just now by holding down the Vol Down button and power for 10 seconds...although, didn't actually do anything, letting go of those buttons and simultaneously unplugging it from the charger made it turn on...not sure which or both of those things were actually the cause though. But once I was booted in I tried booting into recovery with "adb reboot recovery" but that got me to the HTC logo screen with the developer warning but it hung there. Luckily, I was able to boot into the bootloader, but again, trying to get into the recovery made it hand at the "quietly brilliant" screen. Do you know if the stock RUU's are supposed to flash the stock recovery, or do have a link to AT&T's stock recovery? I'm having a hard time finding one labeled properly.

Yes, RUU flashes stock recovery.
If the screen is coming on, that is usually a good sign. Try the RUU again.
BTW, do not not not install the 3.18 RUU if you are SuperCID and S-on. Or you will brick.

redpoint73 said:
Yes, RUU flashes stock recovery.
If the screen is coming on, that is usually a good sign. Try the RUU again.
BTW, do not not not install the 3.18 RUU if you are SuperCID and S-on. Or you will brick.
Click to expand...
Click to collapse
Okay, I'll try that, I still have the 2.20 RUU. Good to know on the 3.18 since I am def SuperCID. Will being SuperCID affect my ability to install OTA updates?

bikeracer4487 said:
Will being SuperCID affect my ability to install OTA updates?
Click to expand...
Click to collapse
Yes, SuperCID and S-on will also brick your phone, if you try to install 3.18 OTA.
You might consider doing s-off, or changing back to the AT&T CID. Even if you don't update using the 3.18 OTA, its very possible the buyer will.

redpoint73 said:
Yes, SuperCID and S-on will also brick your phone, if you try to install 3.18 OTA.
You might consider doing s-off, or changing back to the AT&T CID. Even if you don't update using the 3.18 OTA, its very possible the buyer will.
Click to expand...
Click to collapse
Good idea. Found a thread for S-OFF (http://forum.xda-developers.com/showthread.php?t=2155071) but not sure how to restore AT&T CID.
EDIT: Frick, wish I had though to do this BEFORE installing RUU and unrooting the phone.

[Q] No OS Installed - 3.18 Unlocked S=On

Followed the steps in Hassoon's toolkit, installed recovery, sideloaded CM, and now I have no OS. I can still access fastboot and recovery, see attached image for more info. Any more information needed, please let me know. This is pretty frustrating, no wonder I like Nexus devices.
(sorry for double posting, I also put this in Hassoon's thread, but felt it'd be more appropriate to post here)

first man... you'll only be able to use sense roms most likely, as the newer aosp roms dont mix with the upgraded touchscreen on the 3.18 firmware. so you can head to the original dev section to find the "downgrade touchscreen" thread to use aosp...
second, you have to fastboot flash the boot.img of every rom because the newer hboots dont allow it. easy solution to that is to go to original dev section and follow the s-off thread. if you can s-off you can say bye bye to fastboot for the most part

Also, you need to S-OFF to downgrade touchscreen firmware.
But yeah, if you can get into recovery just wipe everything and flash a rom.. (has to be sense until you s-off and downgrade touchscreen firmware)

exad said:
Also, you need to S-OFF to downgrade touchscreen firmware.
But yeah, if you can get into recovery just wipe everything and flash a rom.. (has to be sense until you s-off and downgrade touchscreen firmware)
Click to expand...
Click to collapse
Never thought I had to pull the boot image out, flash that through fastboot, THEN install the OS. Thanks for the help guys, I tested it out with the copy of CM I had (unofficial port on the threads) and sure enough, it booted up fine. Of course, as stated previously, I can't click anything b/c of the upgraded touchscreen, so I'm omw to flashing a sense rom and getting s-off and a downgraded touch screen. Thanks for the help guys!

Dolfan058 said:
Never thought I had to pull the boot image out, flash that through fastboot, THEN install the OS. Thanks for the help guys, I tested it out with the copy of CM I had (unofficial port on the threads) and sure enough, it booted up fine. Of course, as stated previously, I can't click anything b/c of the upgraded touchscreen, so I'm omw to flashing a sense rom and getting s-off and a downgraded touch screen. Thanks for the help guys!
Click to expand...
Click to collapse
Yea man its a pain to get everything going. But once you s-off, downgrade etc this phone really flies on aosp. There's also an (optional) thread in development section to rid the splash screen of the red text. Its a simple 3 step process that should only take 20 seconds. After that you're golden
Sent from my One X using Tapatalk 2

InflatedTitan said:
Yea man its a pain to get everything going. But once you s-off, downgrade etc this phone really flies on aosp. There's also an (optional) thread in development section to rid the splash screen of the red text. Its a simple 3 step process that should only take 20 seconds. After that you're golden
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I'll bet. Getting S-off to work is killing me though. Keep running into the 99 unknown error while flashing the RUU file. I've done complete wipes, made sure i have superCID, and still no luck. So close and yet so far...

Dolfan058 said:
I'll bet. Getting S-off to work is killing me though. Keep running into the 99 unknown error while flashing the RUU file. I've done complete wipes, made sure i have superCID, and still no luck. So close and yet so far...
Click to expand...
Click to collapse
are you using a sense rom or aosp?
you need to be on a sense rom since your hboot is 2.14 because aosp requires you change a setting to allow you to soff which you cant since the touchscreen doesnt work.
if you are already on a sense rom. simulate a battery pull by pressing and holding power on your phone till the capacative buttons blink a bunch of times and then it shuts off. then try again.

Dolfan058 said:
I'll bet. Getting S-off to work is killing me though. Keep running into the 99 unknown error while flashing the RUU file. I've done complete wipes, made sure i have superCID, and still no luck. So close and yet so far...
Click to expand...
Click to collapse
I feel bad, I see all these people having trouble getting s-off to work, and I did it today without any hassles at all.
Sent from my Evita using XDA Premium

exad said:
are you using a sense rom or aosp?
you need to be on a sense rom since your hboot is 2.14 because aosp requires you change a setting to allow you to soff which you cant since the touchscreen doesnt work.
if you are already on a sense rom. simulate a battery pull by pressing and holding power on your phone till the capacative buttons blink a bunch of times and then it shuts off. then try again.
Click to expand...
Click to collapse
Definitely a sense rom (http://forum.xda-developers.com/showthread.php?t=1868236), still trying to work through it. It's so annoying, I'm dying to get the unofficial CM build on here already.

Dolfan058 said:
Definitely a sense rom (http://forum.xda-developers.com/showthread.php?t=1868236), still trying to work through it. It's so annoying, I'm dying to get the unofficial CM build on here already.
Click to expand...
Click to collapse
if a simulated battery pull isnt working for you, you can paste your cmd prompt window in here and i can check if anything weird is going on.
usually it should work by the third try or so if not after the first simulated battery pull.

Htc One x defaults to speaker phone

Having an issue where calls default to speaker phone. Only major things I done have been update to 2.15, and flash 4.2 rome such as scotts clean rom, and viper rom. Happens in any rom regardless if you wipe out all partitions or not. The thing about it is that it doesn't happen at first when you install the rom. For example i went to sleep and the issue didn't happen after testing it a dozen times before sleep. I had fix it by doing a reset after installing the rom. After the phone is fully charged I noticed the issue came back this morning. Issue happens in safe mode as well.

Have you tried running an RUU?
Sent from my Evita

timmaaa said:
Have you tried running an RUU?
Sent from my Evita
Click to expand...
Click to collapse
No Which RUU should I use for htc one x? I always run my rom installations from Team Win Recovery. Is there a mod out there to disable the dock feature of the htc one x? I heard this can also be due to a bad dock connector. If it makes any sense I never had this issue in 4.1 at all.

An RUU isn't a ROM, nor is it installed like a ROM is. You'll find RUUs at androidruu.com, I'd strongly suggest getting s-off first though if you don't already have it.
Sent from my Evita

cessna784 said:
No Which RUU should I use for htc one x? I always run my rom installations from Team Win Recovery. Is there a mod out there to disable the dock feature of the htc one x? I heard this can also be due to a bad dock connector. If it makes any sense I never had this issue in 4.1 at all.
Click to expand...
Click to collapse
RUU links are listed on my Index thread, like everything else useful for our device: http://forum.xda-developers.com/showthread.php?t=1671237
If it shows up only on Sense 5 ROMs, its probably a software issue, not a hardware issue. I wouldn't assume the dock connector only, as there are other actions which also activate speaker phone, such as flipping the phone face down (possibly try to deactivate that feature in Settings to see if that helps).

timmaaa said:
Have you tried running an RUU?
Sent from my Evita
Click to expand...
Click to collapse
redpoint73 said:
RUU links are listed on my Index thread, like everything else useful for our device: http://forum.xda-developers.com/showthread.php?t=1671237
If it shows up only on Sense 5 ROMs, its probably a software issue, not a hardware issue. I wouldn't assume the dock connector only, as there are other actions which also activate speaker phone, such as flipping the phone face down (possibly try to deactivate that feature in Settings to see if that helps).
Click to expand...
Click to collapse
I have an HTC at&t version with 2.15, what RUU do your recommend running. The att one listed in the thread?

cessna784 said:
I have an HTC at&t version with 2.15, what RUU do your recommend running. The att one listed in the thread?
Click to expand...
Click to collapse
Are you s-off or s-on? With S-off, you can run any RUU meant for EVITA. I would start with the AT&T version. But be aware it will replace hboot with 2.14 as well as the radio and other modules. So you will need to flash 2.15 firmware again, if you want to use Sense 5 ROMs.
If S-on, do not flash any RUU until you are s-off. SuperCID (which I assume you have) and s-on will brick the phone if you run a Jellybean RUU.

redpoint73 said:
Are you s-off or s-on? With S-off, you can run any RUU meant for EVITA. I would start with the AT&T version. But be aware it will replace hboot with 2.14 as well as the radio and other modules. So you will need to flash 2.15 firmware again, if you want to use Sense 5 ROMs.
If S-on, do not flash any RUU until you are s-off. SuperCID (which I assume you have) and s-on will brick the phone if you run a Jellybean RUU.
Click to expand...
Click to collapse
I am S-OFF

redpoint73 said:
Are you s-off or s-on? With S-off, you can run any RUU meant for EVITA. I would start with the AT&T version. But be aware it will replace hboot with 2.14 as well as the radio and other modules. So you will need to flash 2.15 firmware again, if you want to use Sense 5 ROMs.
If S-on, do not flash any RUU until you are s-off. SuperCID (which I assume you have) and s-on will brick the phone if you run a Jellybean RUU.
Click to expand...
Click to collapse
Gonna run RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_ 0.24p.32.09.06_10.130.32.34_release_signed.exe

Device is stuck on landscape mode right away on the ruu that I installed. I put in the usb connector to charge and it goes back to normal. So it may mean that the micro usb port went bad and is causing my phone to get stuck in dock mode.

cessna784 said:
Device is stuck on landscape mode right away on the ruu that I installed. I put in the usb connector to charge and it goes back to normal. So it may mean that the micro usb port went bad and is causing my phone to get stuck in dock mode.
Click to expand...
Click to collapse
That would appear to be the case. There are apps available on the Play Store that disable dock mode, you can try and see if that helps.

redpoint73 said:
That would appear to be the case. There are apps available on the Play Store that disable dock mode, you can try and see if that helps.
Click to expand...
Click to collapse
any permanent way to disable dock mode without an app?

I don't think so, other than having it repaired.
Sent from my Evita

cessna784 said:
any permanent way to disable dock mode without an app?
Click to expand...
Click to collapse
With root, I would think so. But I don't know how to do it, off hand. Maybe try to freeze the process "Car" with Titanium?
Freezing with Titanium is my preferred way of tinkering with such things, as its easily reversible if you find it leads to undesirable wonky behavior.

Do you have a case on your phone? My daughter always drools on my phone and the pogo pins get wet and cause dock mode. Take your case off and check
Sent from my VENOMized HoxL

[Q] Newest MagioRom hanging

I finally got S-Off, and thought life was good. Installed the newest MagioRom (I had a much older version), but now the phone just hangs. The ROM attempts to load, goes through its splash screen, then the screen turns white with a green HTC in the center, and the buttons light up. After about a minute, the screen will darken. The screen buttons will make the phone vibrate, but they don't do anything. Occasionally, between the splash screen and the white screen, the taskbar will appear at the top. The phone shows no signal, but trying to pull the bar down does nothing. The ROM was a clean install with a full wipe. The power button will bring up the power menu, but selecting anything gets stuck and I have to do a hard reset. I powered it down through the bootloader. Any ideas?
I'm S-off (finally), CID 11111111, HBoot 2.16.0000 and radio 1.20.50.05.16
EDIT: And just found that the sdcard won't mount.

Here is a link to fix your sd-card:
http://forum.xda-developers.com/showthread.php?t=1630459&page=36

mannte said:
Here is a link to fix your sd-card
Click to expand...
Click to collapse
Thats what I was thinking it was. It did get worse before it got better. Trying to pull out of it gave the phone a bootloop at the white HTC screen. I finally quit trying to fix it per all the unmounted sdcard threads and tried an RUU. It boots now, but hangs as it is trying to load the sdcard. The OEM recovery can't see it either. I've even done the clear storage and factory reset in the bootloader to see if it would help. The only thing that I have got out of it is losing my "tampered" warning at the top.
Could my sdcard be dead?

It's not very likely that your sd-card is dead because it is just a partition, so if your sdcard is dead your phone probably wouldn't work at all.
Normally I should say that it would be a firmware, partition problem or a bad flash but the RUU should have fixed that.
I have two question if the answers are both yes than i have no other idea's and would advise you to return it for warranty and hope for the best.
1. Did you run an signed RUU.exe file. The filename should look like something like this: RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
2. Did the RUU run without any errors?
You could also try to run the RUU one's more or try another RUU, you should get the right one matching provider and country/region.
Here is a list of RUU's for the htc one s:
http://www.androidruu.com/index.php?developer=Ville
One last thing did you change your CID, that is also known to cause problems.
If you want to return it for warranty then I wrote a guide how to get your phone completely back to stock:
http://forum.xda-developers.com/showthread.php?t=2606312
You could also just relock it and then return it but they maybe let you pay then.

mannte said:
1. Did you run an signed RUU.exe file. The filename should look like something like this: RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
2. Did the RUU run without any errors?
Click to expand...
Click to collapse
I ran: RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501S.10L_release_263233_signed.exe
It ran without any problems.
mannte said:
Here is a list of RUU's for the htc one s:
http://www.androidruu.com/index.php?developer=Ville
One last thing did you change your CID, that is also known to cause problems.
Click to expand...
Click to collapse
That is where I picked this RUU up from.
I am CID: 11111111
mannte said:
If you want to return it for warranty then I wrote a guide how to get your phone completely back to stock:
Click to expand...
Click to collapse
I doubt it even still has one, I bought it a week after it made it to the US market.

I ran: RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501S.10L_release_263233_signed.exe
It ran without any problems.
Click to expand...
Click to collapse
Try this RUU it's a newer version:
http://www.androidruu.com/getdownlo..._10.30.50.08L_release_309489_signed_ICS_2.exe
I am CID: 11111111
Click to expand...
Click to collapse
If you're still S-OFF, try changing your CID back to the original, it's probably: T-MOB010
You can change your CID by typing: 'fastboot oem writecid yourCIDnumber' when you are in fastboot mode.
You can also use one of the HTC One S toolkits like Hasoon200 toolkit or the toolkit form squabbi.
I doubt it even still has one, I bought it a week after it made it to the US market.
Click to expand...
Click to collapse
In Europe you get 2 year's of warranty (In some countries even without a receipt), I don't know the US rules though.

ville
why my one s usually have some reboot????????