Hello,
I have a question about the latest RUUs. While wondering how I could put an end to the helicoptering issue without sending it back for the 2nd time (1st time, they just replaced the screen... and I don't know what else they did because it didn't happen for 2 months) as I currently have no acceptable replacement device to use while it's in repair, I checked if I had the latest radio and firmware installed because some users told me the latest versions made the helicoptering disappear for them.
I can see on AndroidRUU that the latest available JB RUU for Europe is 3.16.401.8, but I have a 3.16.401.9 firmware on my One S. Any idea where it comes from? Does everyone actually have this one now? 'cause I havent seen a RUU for that. Wouldn't it be weird that a supposedly newer firmware didn't solve an issue that the previous one solved?
Anyway, would it be safe to install the 3.16.401.8 RUU currently available to see if that really solves the helicoptering like it supposedly did for some? I still have a 100% stock device and don't want/have the time to do all the tasks to try Maximus and its newest radio for example (I'm also a bit afraid of not being able to revert it back to stock if that doesn't work either and I finally decide to send it back for repair after that).
PS: as for the radio, I have the same as everyone I guess (1.15.50.05.29_10.30.50.08L)
Related
OK, I rooted my t-bolt but haven't done any custom ROM flashing yet. I checked today for the s/ware update and when it found it I chose "reject" ... 2 questions..
First, will this sucker eventually push to my phone automatically via VZW?
Second, should I install another radio (and if so for what reason?). I do have some intermittent GPS weather issues (right now it says I'm in Vosu, which I think is near Finland somewhere --- I can assure you the phone is wrong) but IDK if this OTA (or leaked) update addresses that or something different.
I do plan on, one day, running a custom ROM I'm just not ready for that yet. I would update the radio though if it does something for service or whatever.
Advice, thank you.
The new radio is a piece of ****. Don't bother with it. I don't think that HTC pushes silent updates so I wouldn't worry about it. Just check your software version to make sure you're still running the stock radio.
everytime i have had a rooted phone, OTA updates did not succeed in installing itself, even if i agree to the update, and am not running custom roms
So, I guess if it asks me I'll just keep telling it 'reject' - it told me where I could find it if I needed it again, lol.
this will stop it from asking
http://forum.xda-developers.com/showthread.php?t=1077405
or showing up
and the OTA is the same the leak here by jcase and radio is also same as leak so if you flashed new mecha and flased new radio in hboot and ran this buildprop
you would be up to date like the rest just rooted atleast
Hey guys,
I´m new at this forum and I have a question
First I will show you some informations about my Phone:
-My Phone is S-OFF and rooted
-HBOOT 1.27.1100
-Radio 10.14.9035
-current Rom: CM9 alpha Rom
I used some different roms (first some Andorid 2.3.5 rom and later ICS Roms), but my Phone sometimes suddenly shutdown. Sometimes after a few hours, or sometimes after a few days.
It is still the same if I use the original Rom from HTC (with Android 2.3.4 with Sense 3.0).
I don´t know where the problem is ( maybe a hardware error? ), but I hope somebody can help .
I often resseted my phone, but it doesn´t take any effect. I hope there is any log on the phone which I can send you, but i don´t know where it could be
greets
Tobi
Do you use the original battery?
I got the same problems when I use an Anker battery:
http://forum.xda-developers.com/showthread.php?t=1515181
I still use the original battery...
Have you made sure the firmware is correct for each rom you experience problems with?
I assume you have updated it from original since boot = 1.27
Latest builds need 3.30
Most ics need 3.24/3.25
Some ics (now only older builds i think) and all gb run on 3.12
Check here for info:
http://forum.xda-developers.com/showthread.php?t=1412618
I think i flashed 3.30 on my Phone for the newest ICS, but the problem is, that the problem was still there when I used the original rom unrooted with the original bootloader...
Yes I think 3.30 = 1.27, I've not got round to flashing yet.
Maybe its overheating = rebooting?
It might be worth restoring to stock then sending for repair since issue was present in factory state.
stringer7 said:
Yes I think 3.30 = 1.27, I've not got round to flashing yet.
Maybe its overheating = rebooting?
It might be worth restoring to stock then sending for repair since issue was present in factory state.
Click to expand...
Click to collapse
Problem with that is that there is a chance the phone will work properly when they're going to test it... they will send it back unrepaired...
Niekjuh said:
Problem with that is that there is a chance the phone will work properly when they're going to test it... they will send it back unrepaired...
Click to expand...
Click to collapse
i don´t hope so...
It is true my phone is sometime hot, so I think it is overheating, but often it is still cold and suddenly shutdown. I think I flash it now to stock and write with amazon. Maybe I would have a bit more luck there.
Hello all,
Long time reader, just started posted recently. I bought my HTC One S when it first came out, and immediately rooted it and installed the ViperOneS Rom on it. I never got the chance to recieve the OTA updates for JellyBean or any of the other firmware updates. Now, as I was reading the CM10.1 thread, it said that certain firmware updates were required to install the new nightlies. I figured it was time to RUU my phone to stock with the newest firmware, and then re-root it so that I can take advantage of the 3.4.x kernel in the new CM 10.1 releases. Anyway, I went to www.shipped-roms.com and went to ville, and saw that the newest release appeared to be the :
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
....However, on my HTC One S news app, I looked back about two months, and it showed that Tmobile released a new RUU/OTA on June 24th, 2013. That build was labeled
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.17_Radio_1.13.50.05.31_10.30.50.08L_release_320836_ICS_2_JB.exe
Now, the one on Shipped-Roms has the 3.16.x build as opposed to the Tmobile's 3.14.x. But the Tmobile has a higher number after the "release" at the end of the exe, being 320836 as opposed to 301814 on the Shipped-Roms RUU.
So does anyone know which one is truly the most recent firmware for the HTC One S. I went and installed the Tmobile One, im going to play around with it for a day or two before I root it again. It was said one of the reasons TMobile released this was to address battery drain issues for jellybean users.
The entire article is available here : https://support.htc.com/en-us/080-H...HTC_One_S™_for_T-MOBILE_ROM_Update_|6.24.2013
I ran the RUU with no problems and am now running stock, until I decide to root again. I basically posted this to make people aware that their might be a newer firmware available than the one they are using, and it isn't on any of the RUU list such as Shipped-Roms. Anyway, if I experience any problems with it, I will post. Take care - dRedmentia
dredmentia said:
Hello all,
Long time reader, just started posted recently. I bought my HTC One S when it first came out, and immediately rooted it and installed the ViperOneS Rom on it. I never got the chance to recieve the OTA updates for JellyBean or any of the other firmware updates. Now, as I was reading the CM10.1 thread, it said that certain firmware updates were required to install the new nightlies. I figured it was time to RUU my phone to stock with the newest firmware, and then re-root it so that I can take advantage of the 3.4.x kernel in the new CM 10.1 releases. Anyway, I went to www.shipped-roms.com and went to ville, and saw that the newest release appeared to be the :
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
....However, on my HTC One S news app, I looked back about two months, and it showed that Tmobile released a new RUU/OTA on June 24th, 2013. That build was labeled
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.17_Radio_1.13.50.05.31_10.30.50.08L_release_320836_ICS_2_JB.exe
Now, the one on Shipped-Roms has the 3.16.x build as opposed to the Tmobile's 3.14.x. But the Tmobile has a higher number after the "release" at the end of the exe, being 320836 as opposed to 301814 on the Shipped-Roms RUU.
So does anyone know which one is truly the most recent firmware for the HTC One S. I went and installed the Tmobile One, im going to play around with it for a day or two before I root it again. It was said one of the reasons TMobile released this was to address battery drain issues for jellybean users.
The entire article is available here : https://support.htc.com/en-us/080-H...HTC_One_S™_for_T-MOBILE_ROM_Update_|6.24.2013
I ran the RUU with no problems and am now running stock, until I decide to root again. I basically posted this to make people aware that their might be a newer firmware available than the one they are using, and it isn't on any of the RUU list such as Shipped-Roms. Anyway, if I experience any problems with it, I will post. Take care - dRedmentia
Click to expand...
Click to collapse
higher numbers not always newer builded software, since jb for the unbranded was released several months sooner than the tmobile one the higer number is logical. However there has been a ota for the unbranded going to 3.16.401.9
watch out, many people got bricked wanting to update there already updated firmware to the newest.
if its already on jb firmware and works flawlessy leave it as is, or take the risk.
real187 said:
higher numbers not always newer builded software, since jb for the unbranded was released several months sooner than the tmobile one the higer number is logical. However there has been a ota for the unbranded going to 3.16.401.9
watch out, many people got bricked wanting to update there already updated firmware to the newest.
if its already on jb firmware and works flawlessy leave it as is, or take the risk.
Click to expand...
Click to collapse
I installed the Tmobile Jan 24th RUU no problem. As I said, I rooted my phone right when I got home from the Tmobile store, so it was still running the original firmware it came with. Now Its up to date, running CM 10.1 flawlessly with the 3.4 kernel, and overall seems quicker and more responsive. Now hopefully the battery life issue gets resolved, that was the only problem I was having before. Thank you though, from what I understand this will be the last firmware update from Tmobile, so I will never have to go through that process again. The HTC One S still holds its own as a great phone, I don't see any need to upgrade anytime soon.
are you dunning CM10.1 nightlies? is it stable? Any issues with camera/ bluetooth/ 4g?
Do we need s-off for that?
myechophone said:
are you dunning CM10.1 nightlies? is it stable? Any issues with camera/ bluetooth/ 4g?
Do we need s-off for that?
Click to expand...
Click to collapse
Actually I am running the August 13th CM10.1 Nightlie, and the camera works, bluetooth works, but my damn 4g is not connecting. All my mobile data settings keep getting stuck on Edge network or worse. It said it would have taken 10 hours to download a 150 mb file....I didn't notice until I left my house earlier today because it was my day off so I didn't use my phone for work. It was working flawlessly on wifi, thought everything was going good, and once I started driving around the service would go in and out, and never made it to 4g once, I think in one or two spots it hit 3g, but most of the time it was stuck on EDGE:2 in the Phone Settings. If I can't get this issue fixed I will go back to the stable CM10, which sucks because that doesn't use the new 3.4 kernel, or use a different ROM based on that kernel.
Hi all, kind of a newbie, but I've been rooting phones for a few years and have never had this issue. I wanted to upgrade my ROM to Maximus HD 10 and that was a big mistake because it involved going to SuperCID and S-Off. I was successful with both, but I ended up uninstalling due to not getting 3G/4G. Well, plenty of uninstalling and trying new ROMS and still I am left with 2G only. I have flashed the latest T-Mobile US Radio but it doesn't seem to do anything. I'm thinking it is a firmware issue, so I was wondering if there is a firmware I need to flash and do I need to fastboot flash it or recovery flash it? I am tempted to call T-Mobile and just order a new phone in the first place, but I would really like to have 3G/4G back. What firmware do I need and also does installing a new RUU overwrite the CID, firmware, and radio? I would love to back to the T-Mobile CID and the stock rom. Please help, thanks!!!
Keep soff and flash tmob ruu. All ruu contains firmware.zip, so if you flash tmob ruu you will downgrade your hboot and radio. Also make sure you'll wipe sd card from bootloader after ruu.
Sent from my HTC One S
hitzradio said:
Hi all, kind of a newbie, but I've been rooting phones for a few years and have never had this issue. I wanted to upgrade my ROM to Maximus HD 10 and that was a big mistake because it involved going to SuperCID and S-Off. I was successful with both, but I ended up uninstalling due to not getting 3G/4G. Well, plenty of uninstalling and trying new ROMS and still I am left with 2G only. I have flashed the latest T-Mobile US Radio but it doesn't seem to do anything. I'm thinking it is a firmware issue, so I was wondering if there is a firmware I need to flash and do I need to fastboot flash it or recovery flash it? I am tempted to call T-Mobile and just order a new phone in the first place, but I would really like to have 3G/4G back. What firmware do I need and also does installing a new RUU overwrite the CID, firmware, and radio? I would love to back to the T-Mobile CID and the stock rom. Please help, thanks!!!
Click to expand...
Click to collapse
should have searched and read some threads before uninstalling maximusHD. Tons of folks, myself included, had 3G/4G issues after installing MaximusHD. All fixed now.
rgrpark said:
should have searched and read some threads before uninstalling maximusHD. Tons of folks, myself included, had 3G/4G issues after installing MaximusHD. All fixed now.
Click to expand...
Click to collapse
I have drop signal issues, 3g and 4g seems normal but lose complete signal constantly.
i had home button issue when signal drops from 3g to 2g. home button activates itself sometimes when browsing internet and often drop action to homescreen. that must be radio related. and sometimes stock browser loose connection while chrome works. got tired of these things and everything all working perfectly when going back to Viper roms. any ideas ?
Sent from my HTC One S using Tapatalk 4
crazy touchscreen problem
After flashing a ROM my touchscreen x axis seems to have inverted itself, so right is left on the screen.
This problem happens during the recovery screen also
I have tried changing recovery's,Kernals,flashed ROM's that I know work
I have even returned the phone back to stock nothing fixed it.
I have even went as far as removing the motherboard and installing one out of a working phone and guess what it does the same thing.
So i ask all you knowledgeable people WTF wold cause this and how can I fix it ?
these are the last two ROM's I was trying out when all this happened
they both ran without a problem I just didn't like them
MokeeOS 44.2 24/12/2013 [UNOFFICIAL],
UNOFFICIAL AOKP][4.4.2] [S4] [12/26/13]
I'm in no way blaming the ROM developers for this issue I just need a little help
Strange problem. I think you should flash firmware, it is worth to try i guess
Sent from my One S using xda app-developers app
mines actually doing the same, and from what i've been reading, i believe it has to do with your hboot version and ics not being compatible with it. try flashing your original ruu if you can. that's what i'm trying to do as we speak. if i ever get my problem figured out, i'll let you know if it works.
HomieOneKinobi said:
mines actually doing the same, and from what i've been reading, i believe it has to do with your hboot version and ics not being compatible with it. try flashing your original ruu if you can. that's what i'm trying to do as we speak. if i ever get my problem figured out, i'll let you know if it works.
Click to expand...
Click to collapse
This was my test phone I had flashed just about everything you can think of before I would install it on the phone I use every day
I guess my luck ran out
I ended up flashing the phone back to the original firmware and OS version using the factory RUU without a problem
If I try to install anything over 4.04 it goes right back to the same crap
I tried different firmware, kernels, roms with sense/ no sense doesn't matter.
the phone is being sold as I type this and I'm leaving my other two One S phones alone for now on
Nobody should have to go through this much bull for newer OS version so I'm saving for a Nexus 5
Thank you for the suggestion