So I have a problem, my HOS is constantly disconnecting from the network. It'll only stay connected as long as I'm not browsing using the 4G network, on Wifi works fine, never disconnects.
At first I heard it was a problem with the TMO network and they were working on updates, so I waited; then I heard it was a problem with the HOS and the TMOB RUU version, and loading a HTC EU ROM would solve the problem; then I heard that it was a problem with the radio, but no one has a consistent method of flashing an updated radio with S-ON (some say OK to flash with Clockwork, others not so much luck, seen reports of soft bricks).
I havent seen anyone really find a solution for this problem. Seen folks say the build.prop needs to be updated (which I haven't tried), others have fixed with different ROMs, everyone has a different solution that only appears to work for them.
FWIW
HBOOT-1.09.0000
RADIO-0.16.31501S.16_2
Running TrickDroid 7.1.0
So my thought is that it's a problem with my device (I got it the first day it came out) so I assume it has to be a manufacturing defect that hopefully a warranty exchange would resolve.
I'm down for reloading stock, but as I recall the minute the bootloader is unlocked the disclaimer appeared. Anyone know how to lock the bootloader?
My other question is, has anyone done a warranty exchange or know if they care if the device is rooted since more than likely they'll just reflash it to stock and put it in the refurb stock. I've done warranty exchanges with G1, N1 and MT4G while rooted and no one seemed to care. But now that the bootloader has the disclaimer on boot, I fear I'll be on the hook for the device since it's rooted.
You can flash radio zips cuz you hboot is 1.09
Sent from my HTC One S using xda premium
randomnoob83 said:
You can flash radio zips cuz you hboot is 1.09
Click to expand...
Click to collapse
With clockwork or another method?
With TWRP. I had those disconnect issues with T-Mobile stock everything, but unlike you, I ran the RUU, so yes I got an update HBOOT but those issues are gone.
T-MobileUS HTC One S running Stock Rooted 2.21.
I flashed my radio with clockwork.
Sent from my HTC VLE_U using xda premium
thanks guys. very excited to hear that the new radio solved the issue. I was waffling between ditching the HOS for a GNexus but the camera on the HOS and the overall form factor kept keeping me near.
I'll try it as soon as I get back in town.
Please let us know if this works for you.
My girlfriend just bought a T-Mobile one s after seeing how nice my one x was, and she has been plagued with radio problems the entire time. I've ran the latest T-Mobile US RUU hoping it would fix the issues but it has not.
Obviously, I'd like to hold out as long as possible with rooting her phone incase she needs to return it. Anyway, let us know how it goes.
Related
Hello to Sensation world,
I've just arrived from Sony Ericsson x10 world and i'm new to htc, specially sensation.
I now that my warranty voids if I root my device. Is there any way to return it to stock state, unroot and with stock rom so I can send it to the service if I have any problem???
It's the only thing I wanna now, after that, all the doors are opened!
Thank's in advance
Everything you need to know about S-OFF, rooting, debranding and going back.
http://forum.xda-developers.com/showthread.php?t=1192300
I honestly think the Sensation is the first phone I've had that if you did a factory restore you'd still have to do some work to get S=On...I'd go to the above link to make sure you can do it before taking that risk.
I heard that RUU gives you back S-ON and probably warranty (not sure because I haven't tried it yet)
Oh, and RUU = Rom Update Utility. In case you didn't know because you are new
Swyped from my HTC Sensation
Even if you sent your phone back with S=OFF...do they check for that? I sent 2 mytouch 4g's back with S=OFF and it never prevented me from getting an exchange.
idavid_ said:
I heard that RUU gives you back S-ON and probably warranty (not sure because I haven't tried it yet)
Oh, and RUU = Rom Update Utility. In case you didn't know because you are new
Swyped from my HTC Sensation
Click to expand...
Click to collapse
I did RUU and it didn't give me S=ON...actually NOTHING I tried work. I wanted to restore my phone back to stock for a exchange because it was lagging terribly. I finally said, forget it..flashed Leedroids which I didn't like then flashed Android Revolution HD, phone stopped lagging after that so I kept it.
I"m pretty new at this so I think my terminology is backwards.
I already s-off and rooted it. Hope not to have any problems...
Sincerely I don't find any difference between the stock rom and the custom roms, and almost the same.
it would be nice to easily turn s-on as needed but honestly? I've returned several rooted phones. Never told I voided warranty...because I don't think they check!
Sent from my HTC Sensation 4G using XDA Premium App
A little late, but if you read the sticky in dev section, it says how to get S-ON back. You will need ADB
Swyped from my HTC Sensation
I had sudden unresponsive Sensation that apparently has been fixed / replaced by HTC. I still don't know if this is a hardware or software problem since there seem to be many incidents of these happening on the forum.
In any case, just want some advice...do we think these "unresponsive" issue is related to rooting/ROM...even though it seems to be happening with various ROM. I just wonder if I should try to reroot the repaired phone again.
Also, will the guide for rooting be still valid with maybe some newer firmware/Bootloader that HTC might have reinstalled onto the phone now? I am picking it up today...but I need to unlock the phone to use in Canada..which I did with the guide here before....but I am a little weary about doing it again after what happened!
newr said:
I had sudden unresponsive Sensation that apparently has been fixed / replaced by HTC. I still don't know if this is a hardware or software problem since there seem to be many incidents of these happening on the forum.
In any case, just want some advice...do we think these "unresponsive" issue is related to rooting/ROM...even though it seems to be happening with various ROM. I just wonder if I should try to reroot the repaired phone again.
Also, will the guide for rooting be still valid with maybe some newer firmware/Bootloader that HTC might have reinstalled onto the phone now? I am picking it up today...but I need to unlock the phone to use in Canada..which I did with the guide here before....but I am a little weary about doing it again after what happened!
Click to expand...
Click to collapse
Maybe it was the rom or some certain thing that you did causing the slow response. Rooting will never ever ever ever lag a phone, custom rims on the other hand usually don't but there's the new ones which still have work to be done. When you get your phone back, boot into bootloader and tell me the hboot version. If its ics I don't think that you can as I think juopuntbear only works on pre rooted phones.
It does seem like the phone itself had some problems.
Sent from my HTC Sensation Z710e using XDA
sensation lover said:
Maybe it was the rom or some certain thing that you did causing the slow response. Rooting will never ever ever ever lag a phone, custom rims on the other hand usually don't but there's the new ones which still have work to be done. When you get your phone back, boot into bootloader and tell me the hboot version. If its ics I don't think that you can as I think juopuntbear only works on pre rooted phones.
It does seem like the phone itself had some problems.
Sent from my HTC Sensation Z710e using XDA
Click to expand...
Click to collapse
Well.. the phone came back as HBOOT 1.18...I had to go through the rooting process as I needed to unlock the SIM. So my phone is S-off, rooted, clockwork 5.0.2.0, and super CID.
I am scared to try to install an ICS custom ROM on it now as I am not sure if that process caused the phone to die and there are many phones dying on here running that.
I am thinking maybe I should just update to the official update when it comes out. Hope it's possible with the phone being rooted and S-off etc..
newr said:
Well.. the phone came back as HBOOT 1.18...I had to go through the rooting process as I needed to unlock the SIM. So my phone is S-off, rooted, clockwork 5.0.2.0, and super CID.
I am scared to try to install an ICS custom ROM on it now as I am not sure if that process caused the phone to die and there are many phones dying on here running that.
I am thinking maybe I should just update to the official update when it comes out. Hope it's possible with the phone being rooted and S-off etc..
Click to expand...
Click to collapse
Ok, just tell what happened, what rom you flashed and how, I'll be able to tell you how to do it properly
Sent from my Sensation using XDA
i had plenty of battery life and was on 2.20 4.0.4 update prior to installing this OTA. now my phone wont even turn on after i did the update nor will it charge and have the light come on.. any ideas?
Let me guess. You had supercid??
Sent from my HTC One X using Tapatalk 2
if supercid gives problems on the at&t ota, then you should of been s-off cause i did ota fine with s-off and supercid.
idk i havent really heard of it but maybe. anyway to fix this now or ?
no fix
ps3kev said:
idk i havent really heard of it but maybe. anyway to fix this now or ?
Click to expand...
Click to collapse
SuperCID is when you changed the CID on your phone to 1111111 when/if you tried to root your phone. Here's a brief explanation by another XDA poster.
gol_n_dal said:
Certain things, e.g. RUUs, need to have the correct Carrier ID on the phone in order to install via the bootloader or recovery using the PG58IMG.zip process. The Latest Firmware packs for example are grouped together into sets, this is to allow you to install them if you don't have SuperCID. If you have got SuperCID you can install any of them as all the CID checks pass.
Another reason to change the CID if to allow you to install a generic RUU instead of the one that came with the phone, this allows you to remove the bloatware. For example I'm on Vodafone and I installed the generic Euro RUU purely to get rig of the Vodafone crap that came pre-installed.
The process to change it back is identical to the way you write the SuperCID just using your original CID (mine for example is VODAP001). IIRC HTC__01 is the generic CID
Click to expand...
Click to collapse
Unfortunately, I am on the same boat you are, I did not change my CID from 1's back to it's original and the update bricked my phone. It own't power on or boot into anything, I'm crossing my fingers that the AT&T store will believe me when I say "I don't know what happened, can you fix it?" and give me a new phone.
enduser76 said:
SuperCID is when you changed the CID on your phone to 1111111 when/if you tried to root your phone. Here's a brief explanation by another XDA poster.
Unfortunately, I am on the same boat you are, I did not change my CID from 1's back to it's original and the update bricked my phone. It own't power on or boot into anything, I'm crossing my fingers that the AT&T store will believe me when I say "I don't know what happened, can you fix it?" and give me a new phone.
Click to expand...
Click to collapse
It is not known if super-cid causes issues with doing an OTA! I have super-cid and s-off, and I applied the AT&T OTA without any problems after using the 2.20 RUU to go back to stock. It may be that super-cid causes issues if you are not s-off, but I don't think anyone really knows if it is definitely the presence of the super-cid that is causing the problems. It could be, but given that some people don't have any problems, it could be anything.
tlazarus said:
It is not known if super-cid causes issues with doing an OTA! I have super-cid and s-off, and I applied the AT&T OTA without any problems after using the 2.20 RUU to go back to stock. It may be that super-cid causes issues if you are not s-off, but I don't think anyone really knows if it is definitely the presence of the super-cid that is causing the problems.
Click to expand...
Click to collapse
S-off is precisely the reason you didn't brick. S-off by definition means that all security checks are bypassed, including CID check.
redpoint73 said:
S-off is precisely the reason you didn't brick. S-off by definition means that all security checks are bypassed, including CID check.
Click to expand...
Click to collapse
Hmm so if I had S-Off and Supercid and update via OTA sent directly from att not flashed any other way I will be ok?
romy134 said:
Hmm so if I had S-Off and Supercid and update via OTA sent directly from att not flashed any other way I will be ok?
Click to expand...
Click to collapse
If you were S-Off and SuperCID then the OTA should not affect you.
But. WHY are people wanting the stock OTA? It's causing issues because some people don't know if it's going to brick their phones. Please just wait until custom ROMs come based on the OTA. It's much much much easier
redpoint73 said:
S-off is precisely the reason you didn't brick. S-off by definition means that all security checks are bypassed, including CID check.
Click to expand...
Click to collapse
Yup, now I (and hopefully people who read this thread) know better for next time.
I'm happy to report that AT&T swapped out my HTC One X for a new one and 4.1.1 is pretty sweet! I'm going to wait a while before unlocking and next time I'll make sure to have S-off
I found this thread useful, in that it gave me "closure" after trying desperately to revive my bricked phone for an hour. Got some Z's and woke up to a new phone - they couldn't turn it on at the AT&T service center and gave me a few examples of what could've happen. One of them was "using third party rom's" but they didn't accuse me of anything, they replaced my phone and I was on my way.
I seriously don't get why anyone updates ota. We have a flashable rom typically with a day
Sent from my HTC One X using xda premium
The_Zodiac said:
I seriously don't get why anyone updates ota. We have a flashable rom typically with a day
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
for the other images other then system that get updated, and with s-off now we don't really get screwed by anything so you might as well see if latest gives any improvements.
enduser76 said:
Yup, now I (and hopefully people who read this thread) know better for next time.
I'm happy to report that AT&T swapped out my HTC One X for a new one and 4.1.1 is pretty sweet! I'm going to wait a while before unlocking and next time I'll make sure to have S-off
I found this thread useful, in that it gave me "closure" after trying desperately to revive my bricked phone for an hour. Got some Z's and woke up to a new phone - they couldn't turn it on at the AT&T service center and gave me a few examples of what could've happen. One of them was "using third party rom's" but they didn't accuse me of anything, they replaced my phone and I was on my way.
Click to expand...
Click to collapse
People never listen or read up till its to late
Sent from my HTC One X using xda premium
enduser76 said:
Yup, now I (and hopefully people who read this thread) know better for next time.
I'm happy to report that AT&T swapped out my HTC One X for a new one and 4.1.1 is pretty sweet! I'm going to wait a while before unlocking and next time I'll make sure to have S-off
I found this thread useful, in that it gave me "closure" after trying desperately to revive my bricked phone for an hour. Got some Z's and woke up to a new phone - they couldn't turn it on at the AT&T service center and gave me a few examples of what could've happen. One of them was "using third party rom's" but they didn't accuse me of anything, they replaced my phone and I was on my way.
Click to expand...
Click to collapse
were you honest or did you scam at&t cause that just makes at&t want to make security tougher and hurts other more preve people.
DvineLord said:
were you honest or did you scam at&t cause that just makes at&t want to make security tougher and hurts other more preve people.
Click to expand...
Click to collapse
The guy at the service station didn't really ask me anything other than "what's wrong with your phone?" and I replied "it's not turning on." he said ok and plugged it into his machines and said he was going to run some tests and to take a seat. Five minutes later he said it's not turning on and he's going to replace it, I asked him what could've happen and he gave a few examples (including third party roms, etc) but that it could have been anything from a corrupt file to dropping it on the floor.
The_Zodiac said:
I seriously don't get why anyone updates ota. We have a flashable rom typically with a day
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
For me personally, I couldn't get most of the ROM's to work properly, if at all. I kept getting errors like " com.google.process.gapps has stopped working" or something similar and I'd have no phone service (for example) which is why I went back to stock.
DvineLord said:
were you honest or did you scam at&t cause that just makes at&t want to make security tougher and hurts other more preve people.
Click to expand...
Click to collapse
Not true and they are the scammers btw.
Sent from the HOXL dimension of S-OFF
c5satellite2 said:
Not true and they are the scammers btw.
Sent from the HOXL dimension of S-OFF
Click to expand...
Click to collapse
at&t customer service and even technical support have been badass for me last few years only issue is 110 bucks for my phone bill which imo should ive me the right to do whatever i want with my service and my phone without having to pay for tethering or getting throttled ever imo and cheaper early upgrades.
I recently ran the bell ruu on my phone for my 1.08 hboot which reinstalled the stock Rom for my phone which worked well. I then did the ota update which updated my phone to 2.15 hboot and 3.16.666.9 version (jb) and now the signal keeps switching between no signal and near full strength. Please help.
Sent from my baked HTC One S
Fredfly said:
I recently ran the bell ruu on my phone for my 1.08 hboot which reinstalled the stock Rom for my phone which worked well. I then did the ota update which updated my phone to 2.15 hboot and 3.16.666.9 version (jb) and now the signal keeps switching between no signal and near full strength. Please help.
Sent from my baked HTC One S
Click to expand...
Click to collapse
Shouldn't pose a problem with stock OTA though.
Have you S-OFF'ed previously
Sent from my HTC One S using Tapatalk 4 Beta
I have not s-offer before. I only did the ota to acheieve moonshine s-off. Now I have done the s-off and tried several radios and Roms with no luck. If I pull the SIM card I can get signal back for a minute or two before it goes back to no service
Fredfly said:
I have not s-offer before. I only did the ota to acheieve moonshine s-off. Now I have done the s-off and tried several radios and Roms with no luck. If I pull the SIM card I can get signal back for a minute or two before it goes back to no service
Click to expand...
Click to collapse
Maybe the S-OFF has got something to do with it.
Sent from my HTC One S using Tapatalk 4 Beta
Well the problem appeared after the ota and I s-offed later thinking that I would be able to fix the problem with s-off. I have a feeling its my hboot being too high (2.15) but was reading that downgrade after the ota causes brick for some.
Sent from my baked HTC One S
Fredfly said:
Well the problem appeared after the ota and I s-offed later thinking that I would be able to fix the problem with s-off. I have a feeling its my hboot being too high (2.15) but was reading that downgrade after the ota causes brick for some.
Sent from my baked HTC One S
Click to expand...
Click to collapse
If you have applied Moonshine S-OFF, it installed HBOOT 2.15.4444 ... Don't know but it might be related to the signal issue. You can confirm from the relative thread.
did this problem ever get fixed?
Still haven't been able to figure it out. I have since tried ruu's and hboot downgrades and tried all radios and multiple roms. Broke down to calling Bell who told me to buy a new sim card. After using a strangers phone to activate the sim card because it my only phone, i got the sim activated but the phone kept dropping signal. I called back Bell and they said they will report it and then they gave me HTC's number. I called HTC and they asked me to go into recovery; having a custom recovery at the time made me have to admit that i had an unlocked bootloader. They suggested i send in the phone for repair. The guy on the phone told me to just relock the bootloader and flash the stock rom and they will still lock at it. He even remarked that they have fixed some phones with unlocked bootloaders and custom recovery's. I will report back when i hear from HTC about the repair estimate.
Got the estimate for the phone and it will cost 250$ to fix. They told me that the main board and the battery are broken. O have since denied the repair since I can't afford that. Now I am forced to use my old Samsung T746. Ps they did t care that I was s-offend.
Sent from my HTC One S using XDA Premium 4 mobile app
I had problems (even before rooting) where my wifi would simply not work. If I go into settings and try to switch it from On to Off, it would simply say there was an "Error". Earlier in 2013, I had rooted and installed a Cyanogenmod Rom on my phone (I forget which one exactly, but it was JB). After a while, I went back to stock. A week or so later, the problem happened again. I did a factory reset. It fixed the problem for a day. Then it happened again and not even a factory reset would fix it.
I got a Nexus 5 for Christmas, so I'm looking to sell this phone but want to fix the wifi before I do so. I've seen a couple of people with a similar problem but no fixes. Does anyone know what is the cause of this problem and how to fix it?
Thanks.
Um, how did you return to stock? Ruu or a backup?
Sent from my One Xl using xda premium
If it was happening while your phone was completely stock I don't think there's anything you can do that's going to be worth it. It'll likely have to go to a repair centre and the cost would be more than you can sell the phone for. You could list the phone on Swappa, there may be people who require only the display, motherboard etc.
You could try running an RUU as a last attempt saving though.
Sent from my Evita
magnetboard said:
Um, how did you return to stock? Ruu or a backup?
Click to expand...
Click to collapse
A nandroid is only going to put you back on the stock ROM, not stock recovery, etc. You may also have s-off, unlocked bootloader, SuperCID, etc. that would make the phone "not stock", but you have given zero details for us to answer your question.
Going back to stock should only be necessary for selling the device or returning for warranty (not necessary for AT&T).
Well, a nandroid, as stated by Tim, only gibes you the stock ROM. An ruu wipes anything that might have messed with anything.
Sent from my One Xl using xda premium
I used an RUU to go back to stock.
The details for my phone are:
S-Off
CID-11111111
HBoot-2.14.0000
If there is any other information that would be helpful, let me know and I can try to provide it. I'm planning on selling it on Swappa...my hope was to fix the wifi before doing so.
If you've done an RUU and still no WiFi then you've run out of options.
Sent from my Evita
Thanks. That's what I was expecting...just wanted to make sure.