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
Related
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.
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.
I read that what the s-off does is basically buy you time so you dont have to flash the boot.img on your pc. The Maximus HD rom says you must have your s-off, but how about if I have my s-on, but flash the boot.img, will it be the same thing?
Thanks
Sent from my One S using xda app-developers app
elias.acab said:
I read that what the s-off does is basically buy you time so you dont have to flash the boot.img on your pc. The Maximus HD rom says you must have your s-off, but how about if I have my s-on, but flash the boot.img, will it be the same thing?
Thanks
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
No, the reason you need S-OFF for MaximusHD is because that ROM requires a leaked unsigned firmware, which you can only flash if you're S-OFF.
dr3amsINdigital said:
No, the reason you need S-OFF for MaximusHD is because that ROM requires a leaked unsigned firmware, which you can only flash if you're S-OFF.
Click to expand...
Click to collapse
Oh I see, thanks!
Sent from my One S using xda app-developers app
Hey, listen!
Please somebody help me. I have rooted and unlocked bootloader on my HTC One S. I want to install MaximusHD ROM on my phone, but I'm pretty sure I'm not S-off.
I have CM10.1 ROM installed on my phone.
Can somebody please tell me which guide should I follow so I can be S-off and install the desired ROM (MaximusHD)???
Also, with s-off the red letters disappear from splash screen? Thanks in advance. I really hope you can help me. I want sense 5 on my phone.
Sent from my One S using xda app-developers app
rolo143 said:
Hey, listen!
Please somebody help me. I have rooted and unlocked bootloader on my HTC One S. I want to install MaximusHD ROM on my phone, but I'm pretty sure I'm not S-off.
I have CM10.1 ROM installed on my phone.
Can somebody please tell me which guide should I follow so I can be S-off and install the desired ROM (MaximusHD)???
Also, with s-off the red letters disappear from splash screen? Thanks in advance. I really hope you can help me. I want sense 5 on my phone.
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Moonshine S-OFF: http://forum.xda-developers.com/showthread.php?t=2325590
or
Facepalm S-OFF: http://forum.xda-developers.com/showthread.php?t=2155135
Absolutely right.
And how to remove the red warning text you can find here.
Keep in mind that once you're s-off and want to return to s-on (warranty, whatever...) you'll need to reflash any stock bootloader. Else you'll definitely brick your phone. Best thing is to run any RUU before you set s-on flag on your phone then. It'll automatically restore the stock bootloader that comes with it.
S-off to install Maximus then S-on for final step. It's Ok.
I must do S-on because I get boot loops. Flashed Temporary radio 1.13 because it restarted auto.
hongha_222 said:
S-off to install Maximus then S-on for final step. It's Ok.
I must do S-on because I get boot loops. Flashed Temporary radio 1.13 because it restarted auto.
Click to expand...
Click to collapse
So it's very unstable with s-off?
I mean if I'm going to have WiFi trouble and radio and bootloops I guess is better with s-on?
Sent from my One S using xda app-developers app
rolo143 said:
So it's very unstable with s-off?
I mean if I'm going to have WiFi trouble and radio and bootloops I guess is better with s-on?
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Your device must have s-off without s-off you WON'T BE ABLE TO RUN ROM.
Click to expand...
Click to collapse
Try S-off first. Do it right way.
Then if you can't do anything to get it running or get boot loops, you should try S-on.
I feel it's perfect after 2 day and nothing worry about that.. Flash Temporary-Radio-Installer-V4 if your phone auto restart.
hongha_222 said:
Try S-off first. Do it right way.
Then if you can't do anything to get it running or get boot loops, you should try S-on.
I feel it's perfect after 2 day and nothing worry about that.. Flash Temporary-Radio-Installer-V4 if your phone auto restart.
Click to expand...
Click to collapse
I highly suggest AGAINST going S-ON with Maximus.
If you S-ON, you cannot flash an RUU to lower your hboot back down to hboot 2.15. This means you will be unable to revert back to an older rom or to use the current CM roms.
S-ON while on HBOOT 2.16 is a dead-end and you're forcing yourself to be on either Maximus or another rom that is compatible with 2.16 like Magio. Until someone figures out how to S-OFF while on hboot 2.16, you're stuck with it.
If you're S-OFF, installed Maximus, and you're experiencing bootloop problems and radio problems. Please look into the rcdata partition fix that me and many other HTC One S users were experiencing. Don't S-ON until you give this a try.
tsphan said:
I highly suggest AGAINST going S-ON with Maximus.
If you S-ON, you cannot flash an RUU to lower your hboot back down to hboot 2.15. This means you will be unable to revert back to an older rom or to use the current CM roms.
S-ON while on HBOOT 2.16 is a dead-end and you're forcing yourself to be on either Maximus or another rom that is compatible with 2.16 like Magio. Until someone figures out how to S-OFF while on hboot 2.16, you're stuck with it.
If you're S-OFF, installed Maximus, and you're experiencing bootloop problems and radio problems. Please look into the rcdata partition fix that me and many other HTC One S users were experiencing. Don't S-ON until you give this a try.
Click to expand...
Click to collapse
you're right but I don't see any problem when I try the rcdata fix.
b) Type "mount" to see a list of mounts. I saw that the data block (p35) was being mounted again in /sdcard, which should be (p36). Checking /etc/fstab shows that the /sdcard was commented out!
I can do S-Off with hboot 2.16.
flashed with s-on
I am very new to Android, having been converted from iOS. I had extensive experience with jailbreaking and all that.. flashing Windows Mobile with my HTC TyTn as well.
After having my One for almost 3 months I decided to root it and explore other ROMs. Rooting wasn't an issue and I flashed MaxiumusHD 14 which was replaced within 2 weeks with version 20. Everything went well and I've got battery life that certainly exceeds, by a long shot, versus stock battery consumption rate. (Juice Defender and Profile Scheduler definitely help there too). Original stock ROM consumed a lot of power with the HTCCheckIn service. Noticed that here in Brazil I believe my battery life is worse than when I purchased the phone in Canada, I believe it's due to poor service coverage areas (weak data signals, in particular).
As I learn more, I realize that I don't believe that any of the steps I performed to root and install Clockwork involved making S-OFF active. My bootloader shows S-ON. ROM works fine and I didn't get any errors in flashing. How is that possible?
Am I missing something obvious here?
Should I do moonshine S-OFF and flash again?
I've frozen the updater using Titanium Backup (purchased that, it's great) so that I don't keep getting pestered to update to Maximus 21. I just flashed 20! (and I see no issues and nothing in the change log seems to be a huge selling point).
Thanks for the assistance with this newbie.
Matt
mattdbr said:
I am very new to Android, having been converted from iOS. I had extensive experience with jailbreaking and all that.. flashing Windows Mobile with my HTC TyTn as well.
After having my One for almost 3 months I decided to root it and explore other ROMs. Rooting wasn't an issue and I flashed MaxiumusHD 14 which was replaced within 2 weeks with version 20. Everything went well and I've got battery life that certainly exceeds, by a long shot, versus stock battery consumption rate. (Juice Defender and Profile Scheduler definitely help there too). Original stock ROM consumed a lot of power with the HTCCheckIn service. Noticed that here in Brazil I believe my battery life is worse than when I purchased the phone in Canada, I believe it's due to poor service coverage areas (weak data signals, in particular).
As I learn more, I realize that I don't believe that any of the steps I performed to root and install Clockwork involved making S-OFF active. My bootloader shows S-ON. ROM works fine and I didn't get any errors in flashing. How is that possible?
Am I missing something obvious here?
Should I do moonshine S-OFF and flash again?
I've frozen the updater using Titanium Backup (purchased that, it's great) so that I don't keep getting pestered to update to Maximus 21. I just flashed 20! (and I see no issues and nothing in the change log seems to be a huge selling point).
Thanks for the assistance with this newbie.
Matt
Click to expand...
Click to collapse
I would post this question again in the HTC One section, this is the HTC One S section. They would most likely be able to help you.
tivofool said:
I would post this question again in the HTC One section, this is the HTC One S section. They would most likely be able to help you.
Click to expand...
Click to collapse
Ok, will do. Sorry I didn't notice the S. Thanks
Hey all, so i decided i wanted to try out some radios (was running viper xl)
and tried flashing a few different radios
from this thread and
http://forum.xda-developers.com/showthread.php?t=1694012
this section
"These are radios for flashing in Sense OR CM 10.x builds after 7/15 nightly!!!. They don't include the RIL files."
anyways, now i have been problems, phone randomly thinks sim card is being removed/inserted.
and having random reboots
tried flashing the 3.18 ruu
and flashed viper again,
and am still having these problems
so what else can i do?
any suggestions would be great
Well for the latest version of Viper you need to upgrade your firmware. Which build of Viper are your running?
Sent from my Evita
timmaaa said:
Well for the latest version of Viper you need to upgrade your firmware. Which build of Viper are your running?
Sent from my Evita
Click to expand...
Click to collapse
4.2.0
which firmware do i need to upgrade to ?
(i do belive my hboot was 2.15 before) but i cant seem to remember which ruu that would be
edit:
think i just found it
http://forum.xda-developers.com/showthread.php?t=2517148
is that the correct version?
Yeah that's the one you need.
Sent from my MID-1040
Thanks it had been forever since I'd run an ruu , completely forgot about the firmware upgrade
Sent from my HTC One XL using Tapatalk
No problems.
Sent from my MID-1040
timmaaa said:
No problems.
Sent from my MID-1040
Click to expand...
Click to collapse
To add to this thread so a new one doesnt need to be created, I to am having problems with my Sim card. I have tried flashing different radios, I have done the 2.15 firmware upgrade. I am about ready to give the 5.18 RUU a run and then go through the process of re-flahsing viper.
deepsouth06 said:
To add to this thread so a new one doesnt need to be created, I to am having problems with my Sim card. I have tried flashing different radios, I have done the 2.15 firmware upgrade. I am about ready to give the 5.18 RUU a run and then go through the process of re-flahsing viper.
Click to expand...
Click to collapse
Please post your bootloader details, your recovery version, your current ROM and kernel, and the exact problem you're facing.
Sent from my Evita
timmaaa said:
Please post your bootloader details, your recovery version, your current ROM and kerncontinuehe exact problem you're facing.
Sent from my Evita
Click to expand...
Click to collapse
Hboot details are in the screen shot. TWRP 2.7.0. Viper 4.2.0. Kernel is beastmode 3.4.10.
So my problem that I am having is that my phone continues to loose all data and voice service due to the phone telling me that there is no sim. I have tried different Radios with no differnce. sometimes the phone will start reading the sim if I toggle the phone into airplane mode.
I believe the radio is your problem, you need to make sure you have one of the radios that came bundled with Sense 5 releases installed. They'll be the ones that are 1.31 and upwards.
Sent from my Evita
timmaaa said:
I believe the radio is your problem, you need to make sure you have one of the radios that came bundled with Sense 5 releases installed. They'll be the ones that are 1.31 and upwards.
Sent from my Evita
Click to expand...
Click to collapse
Ok, I read something similar to what you are saying and I did flash a radio 1.31 from this link with is 2.15 firmware. http://forum.xda-developers.com/show....php?t=2517148. However the same problem was still happening. After flashing the current radio (from the above attachment), what I have noticed is that the No Sim icon only seems to happen when I have WiFi turned on for an extended time, this was just a brief observation from last night and this morning.
I am about to flash a stock RUU (possibly the 5.18) to 1) get the phone up to date with the latest firmware and 2) to see if this will help with my Sim Card problems. Or should I use a different RUU to start from Stock again?
Also When looking at the Radios thread I dont see any radios that are 1.31 and up for ATT. All of them seem to begin with 0.xx. The thread i am looking at is http://forum.xda-developers.com/showthread.php?t=1694012
The latest RUU is probably your best bet.
Sent from my Evita
timmaaa said:
The latest RUU is probably your best bet.
Sent from my Evita
Click to expand...
Click to collapse
With S-Off and my CID all 1s I wouldnt have to worry about doing the root again? After the RUU i should be able to install TWRP again and then a custom rom?
Your bootloader will remain unlocked, your CID will remain as 11111111, and your s-off status will survive the process. It's as simple as flashing TWRP afterwards and then the ROM of your choice.
Sent from my Evita
deepsouth06 said:
Hboot details are in the screen shot. TWRP 2.7.0. Viper 4.2.0. Kernel is beastmode 3.4.10.
So my problem that I am having is that my phone continues to loose all data and voice service due to the phone telling me that there is no sim. I have tried different Radios with no differnce. sometimes the phone will start reading the sim if I toggle the phone into airplane mode.
Click to expand...
Click to collapse
Did the issue start after flashing the ROM, or any other mods. Of did it just randomly start happening? Have you tried the stock kernel?'
Have you tried the trick of simply putting Scotch tape on the SIM (don't cover the contacts) to "fatten" it and force it to make better contact in the SIM tray? Loose SIM tray is known to cause the same issue.
timmaaa said:
Your bootloader will remain unlocked, your CID will remain as 11111111, and your s-off status will survive the process. It's as simple as flashing TWRP afterwards and then the ROM of your choice.
Sent from my Evita
Click to expand...
Click to collapse
Much thanks. I will be trying this out.
---------- Post added at 10:06 AM ---------- Previous post was at 10:04 AM ----------
redpoint73 said:
Did the issue start after flashing the ROM, or any other mods. Of did it just randomly start happening? Have you tried the stock kernel?'
Have you tried the trick of simply putting Scotch tape on the SIM (don't cover the contacts) to "fatten" it and force it to make better contact in the SIM tray? Loose SIM tray is known to cause the same issue.
Click to expand...
Click to collapse
To my best knowledge the issue started happening randomly. Phone was working fine for some time while I was one Viper. I believe but not 100% I started noticing this after a drop so a loose tray could very well be the problem. Also this issue was present with the stock kernel as well.
deepsouth06 said:
To my best knowledge the issue started happening randomly. Phone was working fine for some time while I was one Viper. I believe but not 100% I started noticing this after a drop so a loose tray could very well be the problem. Also this issue was present with the stock kernel as well.
Click to expand...
Click to collapse
Those answers (randomness, possible dropped phone) to me point to loose SIM tray. Also, have you tried taking the SIM out, and putting it back in, to make sure its seated properly (if dropped, it could have loosened it)?
If none of the suggestions work, you might also try to get a new SIM from your carrier.
redpoint73 said:
Those answers (randomness, possible dropped phone) to me point to loose SIM tray. Also, have you tried taking the SIM out, and putting it back in, to make sure its seated properly (if dropped, it could have loosened it)?
If none of the suggestions work, you might also try to get a new SIM from your carrier.
Click to expand...
Click to collapse
No i havent tried taking it out. I will try that out tonight. If all else fails I may end up going for a referb phone, but now with 5.18 I might hold off for as long as i can.
Thanks for your help as well.
To all, would disabling Google play services have any affect on the SIM card. I ask because after I flashed the 5.18 RUU I flashed a recovery and the flashed Viper. Phone was up and running about 1pm yesterday. Phone ran good with no problems the rest of day. This morning I unplug the phone from charger and within an hour or so I'm already at 87 percent battery. Looking up what is keeping the phone awake the culprit Google play services ( getting very annoyed of this app) so I force stop and disable play services and within one minute I get that icon of no SIM card. So with my story does google play services have any affect on the SIM cards? And how can I limit the wake locks of Google checkin.
Sorry for the long post.
deepsouth06 said:
To all, would disabling Google play services have any affect on the SIM card. I ask because after I flashed the 5.18 RUU I flashed a recovery and the flashed Viper. Phone was up and running about 1pm yesterday. Phone ran good with no problems the rest of day. This morning I unplug the phone from charger and within an hour or so I'm already at 87 percent battery. Looking up what is keeping the phone awake the culprit Google play services ( getting very annoyed of this app) so I force stop and disable play services and within one minute I get that icon of no SIM card. So with my story does google play services have any affect on the SIM cards? And how can I limit the wake locks of Google checkin.
Click to expand...
Click to collapse
I doubt that Google Play would have that effect on the SIM. I think its just a coincidence (red herring).
deepsouth06 said:
Sorry for the long post.
Click to expand...
Click to collapse
No need to be sorry. More detail is almost always better. Its the short posts that I have a problem with; where people ask for help and don't give any specifics or details. Makes it much harder to help.
So I needed to Unlock my HTC One X, and for that I needed to RUU, which I did without incident. But now, all my SD Card contents are gone? I thought I did enough research and everything I read said RUU doesn't mess with the SD card.
Turns out, it does, or am I missing something?
Appreciate the replies in advance. I'm very very buggered. I did a full Nandroid and everything, which is of course, gone.
An RUU doesn't usually wipe the sd card, but it has on rare occasions done so. More information required though, what are your bootloader details (before and after the RUU)? Which RUU did you run? What made you think you needed to RUU in order to unlock the bootloader?
Sent from my Evita
timmaaa said:
An RUU doesn't usually wipe the sd card, but it has on rare occasions done so. More information required though, what are your bootloader details (before and after the RUU)? Which RUU did you run? What made you think you needed to RUU in order to unlock the bootloader?
Sent from my Evita
Click to expand...
Click to collapse
I used
http://dl3.htc.com/application/HTC_One_X_RUU_5.18.502.1.exe
for the RUU.
I needed to be on a Stock Rom according to posts on XDA that I read in order to Unlock my phone for use with T-Mobile, switching over from AT&T.
I'm on 5.18 now, was on 3.14 if I remember correctly. Whatever I needed to be on to use CleanRom, I was on.
Ahh ok, you're talking about SIM unlocking. You didn't actually need to run an RUU, just flashing a Sense ROM would have been fine. There is no such firmware as 3.14, and it depends on which build of Cleanrom you were on. Either way, it looks as though you got unlucky because I've seen multiple people run the 5.18 RUU without any issues (apart from sometimes needing to run it twice to get it to work fully).
Out of interest, do you have SuperCID? Did you relock the bootloader prior to running the RUU? Do you have s-off?
Sent from my Evita
timmaaa said:
Ahh ok, you're talking about SIM unlocking. You didn't actually need to run an RUU, just flashing a Sense ROM would have been fine. There is no such firmware as 3.14, and it depends on which build of Cleanrom you were on. Either way, it looks as though you got unlucky because I've seen multiple people run the 5.18 RUU without any issues (apart from sometimes needing to run it twice to get it to work fully).
Out of interest, do you have SuperCID? Did you relock the bootloader prior to running the RUU? Do you have s-off?
Sent from my Evita
Click to expand...
Click to collapse
I was on a Sense ROM and it never asked me to insert my unlock code when I used a different sim. I was S-OFF before I ran RUU. Of course now I had to re-root the phone and that's where I've stopped. I may throw Viper on it, but I'm just deflated from losing all of my stuff.
Interesting. For future reference, because you were s-off you didn't need to relock your bootloader or anything to run the RUU, you could have just run it. Then afterwards you just flash TWRP recovery again and away you go.
Sent from my Evita