I have a weird situation. I bought a M9 (used). It activated fine and data and texting works perfect, but outgoing calls aren't working at all. The dialer just hangs. The Sprint Corporate store couldn't figure out the problem either. I've reprovisioned, updated the PRL, and did a factory reset multiple times.
What's going on?
BTW I know you all help out of kindness, but I'll reward anyone who successfully figures this out for w/ $20.00 via PayPal if they willingly accept it.
Is this phone s-off, unlocked, rooted? What happens when someone calls you? Under Settings - Call, what does it say for Preferred Network?
cmlusco said:
Is this phone s-off, unlocked, rooted? What happens when someone calls you? Under Settings - Call, what does it say for Preferred Network?
Click to expand...
Click to collapse
The phone isn't s-off or rooted (the bootloader is also still locked). I'm not sure how to check whether it's unlocked. Inbound calls seem to work fine.
simonstiph said:
The phone isn't s-off or rooted (the bootloader is also still locked). I'm not sure how to check whether it's unlocked. Inbound calls seem to work fine.
Click to expand...
Click to collapse
Boot into recovery or fastboot (not sure), and you will see the bootloader status. Relocked means that it was unlocked before. You can also see s off status here.
Skickat från min HTC One M9 via Tapatalk
Roobwz said:
Boot into recovery or fastboot (not sure), and you will see the bootloader status. Relocked means that it was unlocked before. You can also see s off status here.
Skickat från min HTC One M9 via Tapatalk
Click to expand...
Click to collapse
The top of the bootloader says ***LOCKED***
One odd thing to note is that everything (including outgoing calls) work when Wi-Fi calling is active.
Have you tried using a third party dialer app such as ExDialer from the market? If that works for outgoing calls, then at least you can rule out a hardware issue.You need to try to flash an RUU. The problem is, im sure the phone is already updated past the point of available ruu's. What software/build number is the phone on? You are probably going to have to find someone with a java card or xtc2 clip and get the phone s-off and unlocked. From there you can flash an older ruu (downgrade) and hopefully that fixes your issue. Other than that, with security on there isnt really anything you can do you havent already tried.
cmlusco said:
Have you tried using a third party dialer app such as ExDialer from the market? If that works for outgoing calls, then at least you can rule out a hardware issue.You need to try to flash an RUU. The problem is, im sure the phone is already updated past the point of available ruu's. What software/build number is the phone on? You are probably going to have to find someone with a java card or xtc2 clip and get the phone s-off and unlocked. From there you can flash an older ruu (downgrade) and hopefully that fixes your issue. Other than that, with security on there isnt really anything you can do you havent already tried.
Click to expand...
Click to collapse
That's a good idea, but I just tried ExDialer and it hangs on the exact same spot where it says "DIALING..." then says the call was lost. I'm at the most recently available RUU, but Marshmallow is on it's way for us any minute now. I'll investigate getting S-OFF.
You would think the verizon corporate store wouId have access to all the ruus, and would have tried reflashing it. I got s-off with a xtc2 clip. I met a guy from the java card thread who had one and lived fairley close. He did it for a small donation, it takes only minutes.
Do you use google voice integration?
I wish I stole my HTC M9.
shivadow said:
Do you use google voice integration?
I wish I stole my HTC M9.
Click to expand...
Click to collapse
I did have it active on the account, but I turned it off and had Sprint remove the [soc] tag from the line.
simonstiph said:
I did have it active on the account, but I turned it off and had Sprint remove the [soc] tag from the line.
Click to expand...
Click to collapse
Your phone is defective, Tell HTC (uh-oh protection) or Sprint to give you another phone.
clsA said:
Your phone is defective, Tell HTC (uh-oh protection) or Sprint to give you another phone.
Click to expand...
Click to collapse
I think you're right -- but I still wished I knew what the &%$# is actually the culprit. Even though I bought the phone second hand, HTC is to be willing to honor the warranty. At least my luck isn't that horrible.
Related
So today my Desire Z started to lose connection whenever the screen was locked for more than a few minutes. I would set it down and when I got back the lock screen would say "limited service". To get it back I would either have to restart my phone or enter than exit airplane mode. I have looked into the settings and I have mobile data always on.
Is there anyone else experiencing this?
Update: In small print under where it says "limited service" on the lock screen at also says "emergency calls only" as if my carrier is doing this and not my phone. It also seems to be more random than I thought because sometimes it happens when my screen is on and it doesn't always happen when my screen it locked for a few minutes.
I recently installed a data counter. Could that be conflicting with anything?
Any tips or advice is welcome.
What area are you in? I was experiencing something similar over this past weekend, but heard from up top that they were doing HSPA maintenance / work, they might be in your area now.
J.Coffey said:
Update: In small print under where it says "limited service" on the lock screen at also says "emergency calls only" as if my carrier is doing this and not my phone. It also seems to be more random than I thought because sometimes it happens when my screen is on and it doesn't always happen when my screen it locked for a few minutes.
I recently installed a data counter. Could that be conflicting with anything?
Any tips or advice is welcome.
Click to expand...
Click to collapse
Could it be your SIM card? Maybe clean the contacts and make sure it is in there good.
It does sound like something to do with the SIM card to me, e.g. dirty contacts on the SIM card, the SIM card sitting too loose in the holder, etc.
So I was at work when this started happening, then I went home and everything was fine, now I'm back at work and it's happening again. So I guess my signal isn't strong enough to maintain it while I'm here, I find this strange because I am getting the same speed as anywhere else while having the same amount of bars (3 or 4).
J.Coffey said:
So I was at work when this started happening, then I went home and everything was fine, now I'm back at work and it's happening again. So I guess my signal isn't strong enough to maintain it while I'm here, I find this strange because I am getting the same speed as anywhere else while having the same amount of bars (3 or 4).
Click to expand...
Click to collapse
I just got my bell desire Z, unlocked it and am having the same exact problem with Telus in Victoria, B.C.
I called Telus and they said there is no maintinence going on in the area. I have also S-OFF'd, rooted and installed cyanogen as well as other roms, with the same problem.
Any Ideas OP? did you solve your issue? I have reverted to stock, (still same problems) and am thinking of returning mine.
I will clean my SIM card and report back.
Edit: Yeah, no SIM card cleaning in the world could fix it. I think I am going to have to return it.
Have you both unlocked using codes?... and rooted and s-off using the old method?
.... wasn't there an issue with unlock codes. Revert back to stock then try the Gfree method for s-off and subsidy lock off I reckon.
Sent from my HTC Vision using XDA App
ddotpatel said:
Have you both unlocked using codes?... and rooted and s-off using the old method?
.... wasn't there an issue with unlock codes. Revert back to stock then try the Gfree method for s-off and subsidy lock off I reckon.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I had unlocked with a code, and then rooted and S-offed using the old method.
I can restore my stock nandroid, but I dont think there is a bell RUU that I can use. I will try again.
dash4g said:
I had unlocked with a code, and then rooted and S-offed using the old method.
I can restore my stock nandroid, but I dont think there is a bell RUU that I can use. I will try again.
Click to expand...
Click to collapse
Good call by ddotpatel there. As he said, there was a major issue with unlock codes, at least on the G2 side of things (I'm not clear if this affect the DZ). Don't use the old method to S-OFF, use gfree which will SIM unlock you too. It has even managed to repair some bricked G2's which got corrupted through unlock codes.
steviewevie said:
Good call by ddotpatel there. As he said, there was a major issue with unlock codes, at least on the G2 side of things (I'm not clear if this affect the DZ). Don't use the old method to S-OFF, use gfree which will SIM unlock you too. It has even managed to repair some bricked G2's which got corrupted through unlock codes.
Click to expand...
Click to collapse
OK, I applied the Tmobile RUU, and restored my Telus APN settings and got data back. After 5 minutes of sitting, I notice the same issues happening. I will try again in the morning with gfree, but not expecting much.
Thank you for the quick response and suggestion!
dash4g said:
OK, I applied the Tmobile RUU, and restored my Telus APN settings and got data back. After 5 minutes of sitting, I notice the same issues happening. I will try again in the morning with gfree, but not expecting much.
Click to expand...
Click to collapse
Don't worry, all gfree does is patch your radio configuration partition. Even if this went badly wrong and the partition was damaged/wipe (which won't happen), you could still boot your phone to repair it, it's just that the calling/data won't work without the radio config.
The guys on #G2ROOT have had success in getting a lot of G2's working again, after they started to have serious problems following unlocking codes.
same thing happened with me on the original telus desire. Change your sim card. Apparently they arent meant to last more than two years.
I had issues with my DZ on Telus after I used the gfree method to S-off. Since I was already unlocked and didn't seem to have any issues with my call quality until I S-offd..I assume it affected it somehow..but all's I did was replace my SIM and all was well again. I went from horrible call quality and data sending issues to a now perfect phone. For the $10 a new SIM is worth I'd suggest that.
Sent from my HTC Vision using XDA App
Rickroller said:
I had issues with my DZ on Telus after I used the gfree method to S-off. Since I was already unlocked and didn't seem to have any issues with my call quality until I S-offd..I assume it affected it somehow..but all's I did was replace my SIM and all was well again. I went from horrible call quality and data sending issues to a now perfect phone. For the $10 a new SIM is worth I'd suggest that.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Thanks for the input guys, but I just got real s-off with gfree and even bought a new SIM. Same issues.
I think I will bring it back on Monday, and swap for a new one.
Thanks for the help!
I am having the same issue on a DZ i just got from bell. I have full bars, then next thing I know i'm getting 'limited service' no idea why this happens? Guess i'll have to take it back to bell.
whistlerGreg said:
I am having the same issue on a DZ i just got from bell. I have full bars, then next thing I know i'm getting 'limited service' no idea why this happens? Guess i'll have to take it back to bell.
Click to expand...
Click to collapse
Have you rooted or modified it in any way? This is the EXACT same issue, but it would be nice to see if it is happening to stock phones as well.
I have been getting this issue too. I unlocked the phone via an online unlocking service then rooted and soff using gfree. The interesting thing is I would get this issue with my motorola milestone which was also carrier unlocked and rooted. I have a new sim and that hasn't resolved the issue. It only happens very rarely. I am running cyanogen rc1. The fact I was getting this issue on my milestone indicates its a network issue.
JPHCCFC said:
I have been getting this issue too. I unlocked the phone via an online unlocking service then rooted and soff using gfree. The interesting thing is I would get this issue with my motorola milestone which was also carrier unlocked and rooted. I have a new sim and that hasn't resolved the issue. It only happens very rarely. I am running cyanogen rc1. The fact I was getting this issue on my milestone indicates its a network issue.
Click to expand...
Click to collapse
Diff handsets + diff sim cards,... Gota be a network/reception problem no?
has anyone tried the data throttle thing to see if it makes a difference to you guys?
JPHCCFC said:
...The fact I was getting this issue on my milestone indicates its a network issue.
Click to expand...
Click to collapse
Funny that you should mention this, because now that I am at school, I am getting 1 bar, where in my old HTC Desire I would get no service.
At home, I would normally get very good reception with my old Desire, and now it fluctuates from 4 bars to no reception in a matter of minutes with the Z.
So it must be a network issue, but all the *****ing and complaining in the world wont get me anywhere with Telus I'm sure, as I am only 4 months into a 3 year contract. I am sure they will reverb something back like "not our phone, not our problem" Bah-humbug. I will get a replacement, but I also may just switch to Bell if they are going to be like that.
I just got a G2. perm rooted it. and everytime upon booting up it has signal for 1 second then literally just disappears and never comes back. can't choose mobile network or anything because it can't search for it. tried doing *#*#infor#*#* and it says GSM ONLY and everytime i try to change it to WCDMA PREFERRED it keeps reverting back as soon as i exit. the only way i've been able to get signal back so far is to connect to wifi and enable wifi calling, then after disconnecting i'm able to get signal and i'm able to check the WCDMA PREFERRED option but awhile ago i was on wifi calling then left my house and it was disconnected but wasn't able to get signal again.
can anyone help me with what i should do because although i might be able to get it back through wifi calling, this will be very problematic whenever i'm not near my normal wifi locations...
thanks for the help
Eh... I would try reinstalling a stock rooted rom.
Sent from my T-Mobile G2 running Cyanogenmod.
... also try a diff SIM.
EDIT..... Which method did you use to root?
ddotpatel said:
... also try a diff SIM.
EDIT..... Which method did you use to root?
Click to expand...
Click to collapse
I used the thread "temp to permanent root, using rage instead of visionary"
Sent from my T-Mobile G2 using XDA App
Is it factory unlocked? Have you used an unlock code? Have you tried the full radio s off, super Cid thing?
Sent from my HTC Vision using XDA App
I wonder if your SIM card is faulty, needs cleaning, or is just a bit loose in the socket.
steviewevie said:
I wonder if your SIM card is faulty, needs cleaning, or is just a bit loose in the socket.
Click to expand...
Click to collapse
This is what it sounds most like to me. Also try to install another rom since you have it rooted now and see if that fixes the issue. Make sure you do a Nandroid backup first though!
ddotpatel said:
Is it factory unlocked? Have you used an unlock code? Have you tried the full radio s off, super Cid thing?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I never put an unlock code and I'm still on tmobile. I called them and so far I haven't had trouble with signal as much but my number doesn't show up under status in about phone settings...it just says unknown. Its only on this phone though, my n1 shows my number with this sim.
Sent from my HTC Vision using XDA App
Just so we're clear.. Did this phone/sim combo work OK before your rooted the phone?
dadewy said:
Just so we're clear.. Did this phone/sim combo work OK before your rooted the phone?
Click to expand...
Click to collapse
No it wasn't. For the past couple of days since calling tmobile, its been significantly better but today I did randomly have that same problem of no connection, but mostly right now my problem is my g2 not being able to read my phone number in "status" under "about phone" settings but it does on my n1. When I called tmobile they tried sending my number ota 3 times with no luck...
Sent from my HTC Vision using XDA App
During the first 30 days you can go to a TMO store and get a new phone, pretty much "no questions asked". I'd go ahead and do that if I was you. Oh, go to a corporate store though, not a mall kiosk.
While you're there, get a new SIM, too. All free of charge.
If you still have the same problem after that, I'd try an exorcist
Is this problem solved now ? I got the same problem but have no chance to return it back.
If there is the way to solve it, could you please inform and share
Thx
hersam said:
Is this problem solved now ? I got the same problem but have no chance to return it back.
If there is the way to solve it, could you please inform and share
Thx
Click to expand...
Click to collapse
My signal problems seemed to be resolved, at least for the past week. It was resolved by calling tmobile customer support and they did some tests. However, my phone not recognizing my phone number under settings> about phone> status, is still a problem. Even tried getting a new sim and still didn't solve the problem. Did numerous OTAs with tmobile that didn't work. My number still shows up on caller id and stuff its just that menu thing. Sounds insignificant but some apps use that to determine your phone number. Also, when putting my sim back into my nexus one, it does show my number...
Sent from my HTC Vision using XDA App
Nevermind, my other problem was just resolved after reading a post in the cm6.1.1 thread. Settings-call settings-additional settings-my phone number.
Sent from my HTC Vision using XDA App
Hello everyone, this is my first post here, so be nice!
For starters, i have the European HTC One X. I've been having trouble rooting it, but I finally managed it! So, when it was rooted, I noticed that my phone didn't ask for my PIN code. I thought it had something to do with the SIM card not being correctly in place, but i checket it, and it was ok. I checked the Settings, and on Airplane mode, it says "turning off" without me turning it either on or off. I cant press anything there, and when i try to turn it off through holding down the power button, nothing is happening.
Its been a few hours, and I've tried to unroot, factory reset and other stuff. Tell me if you need more info, and I'll be thankful for all answers! I really need help here!
I think I have the same issue, could u check in setting about phone to see if your imei number and baseband is showing?.. mine shows as "unknown".. I have flashed multiple roms and run the ruu several times and I still have the same problem.
Sent from my HTC Wildfire using xda app-developers app
stout0_0 said:
I think I have the same issue, could u check in setting about phone to see if your imei number and baseband is showing?.. mine shows as "unknown".. I have flashed multiple roms and run the ruu several times and I still have the same problem.
Sent from my HTC Wildfire using xda app-developers app
Click to expand...
Click to collapse
Mine is saying unknown too. Any idea how to fix it?
Hope you haven't corrupted your IMEI
*#06#
Check it with your box.
Sent from my HTC One X using Tapatalk 2
chrisjcks said:
Hope you haven't corrupted your IMEI
*#06#
Check it with your box.
Click to expand...
Click to collapse
I tested, and it just says as headliner "IMEI", and lower down the option to say "ok". Nothing more, nothing less. What does it mean?
leonardie said:
I tested, and it just says as headliner "IMEI", and lower down the option to say "ok". Nothing more, nothing less. What does it mean?
Click to expand...
Click to collapse
A Box should pop up,
Saying IMEI in the top grey box, whilst showing a long number in the middle white box.
If you have nothing in the middle, no long number - sorry to say, but it's 'bricked'
You won't get a working sim on a corrupt IMEI, and it seems you have deleted yours.
I assume your attempts to root as corrupted & broken your IMEI, I would never recommend one root click programs - always best to just use a custom Rom.
Sent from my HTC One X using Tapatalk 2
The box is popping up, but no long number. Not any number at all.
Well.. since its bricked.. If i use a fabric restore, would anybody be able to see that i had it rooted?
And btw, i thought if it was bricked, i couldn't do anything at all?
Because i can still connect to Wifi, and download apps and stuff
leonardie said:
chrisjcks said:
A Box should pop up,
Saying IMEI in the top grey box, whilst showing a long number in the middle white box.
/QUOTE]
The box is popping up, but no long number. Not any number at all.
Click to expand...
Click to collapse
I believe your phone is bricked,
Unless you had a backup of your EFS folder which contains your IMEI, I don't think there is a way to restore it.
Because the IMEI is gone, no sim card will work, and you'll be limited to emergency calls only and wifi I think.
Maybe someone else can respond to verify this, but in my opinion - it doesn't look good for your phone (sorry to be the bearer of such bad news)
Hopefully someone will enter the thread to disagree with me, but that's just what I think.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Well, it is sad news indeed, but i really appreciate that you could give me the news. I have been googling like a maniac for a few days now, and noone could give me a clear answer. But do you think i will be able to return the phone if i turn it back to factory reset?
I've had this imei problem on my motorola defy (locked bootloader) and wasn't reading my sim after installing defy+ cm10 JB nightlies, but i recovered the phone to default using leaked radio flasher and it was fixed. Dunno if this could be fixed by an ruu flash but since its bricked what you got to lose ?
Hello again. I just found the receipt/bill (dunno in english) from when i bought the phone. There is a IMEI number there. Can i use it for something? For unbricking the phone, I mean.
Flashing the ruu doesn't fix the problem, I have done it many times and it still remains unknown. I believe the efs folder does not relate to HTC phones. It seems we are very much bricked! I tried sending it to HTC for warranty repair but because it has been unlocked they say the warranty is void..
Sent from my HTC Wildfire using xda app-developers app
Well f*ck. I bought insurance for it (when i bought it), and have reset to factory settings. Would anyone by ANY possibility be able to see that i messed with the software? And if they ask if i rooted it, or flashed ROMs, could i say "huh, what is that? How do i do it?"
I'm gonna try atleast. Update you later on the day
Yes I'm afraid.. they can tell the bootloader has been unlocked.. even if u re-lock it, it shows as re-locked....
Sent from my HTC Wildfire using xda app-developers app
Well, in that case.. I'll just deny it, and say i have no idea what a bootlocker, or loadbooter is..
leonardie said:
Well, in that case.. I'll just deny it, and say i have no idea what a bootlocker, or loadbooter is..
Click to expand...
Click to collapse
It's best to:
Relock your bootloader
Flash the RUU that you need to get a fully stock device
And take it to the shop you bought it from, do not send it directly to HTC yourself - you want to always go through a middle man of possible.
.... And just hope.
Basically, as I first noticed - it looks like your rooting procedures have corrupted your IMEI leaving you with an unrecoverable device.
In the future, stay clear from one click root apps - best way to root has always been to flash a kernel or Rom that includes it.
Good luck and hope they ain't too fussy to give you a working device.
Sent from my HTC One X using Tapatalk 2
permanent airplane mode
I have a similar problem with my htc one x. yesterday I saw that it disconnected my SIM card so I rebooted my phome. After reboot it didnt find my SIM and stuck in permanent airplane mode (it shows like it turns off but it doesnt). I checked that my IMEI is unknown. Tried hard reset few times but it didnt work. My phone wasnt ROOTED or anything. Is there a way to deal with this problem without sending the phone to warranty?
Hey - I've had 2 different Desire Eyes and they both have had incoming call issues. I didn't get a call all weekend into my phone, but I got lot of people saying they tried calling 2 or 3 times and got nothing. Anyone else having this issue?
I don't have any issues with my Desire. Have you tried putting your SIM in a different device for a little while to see if the issue persists? It could be your provider.
ShadowCodeGaming said:
I don't have any issues with my Desire. Have you tried putting your SIM in a different device for a little while to see if the issue persists? It could be your provider.
Click to expand...
Click to collapse
I haven't tried that, though I have tried multiple sim cards from my current provider and the backup Nokia 521 I was using while the warrenty was being processed worked perfectly (well, the calls did... It has Windows 10 on it, so the rest was a bit glitchy, haha).
Anything else you can think of that I should try? I could get AT&T to unlock the phone (since I purchased it off contract) and try another carrier, but I'm not too interested in setting up another service just to test to see if it's the phone.
mstrblueskys said:
I haven't tried that, though I have tried multiple sim cards from my current provider and the backup Nokia 521 I was using while the warrenty was being processed worked perfectly (well, the calls did... It has Windows 10 on it, so the rest was a bit glitchy, haha).
Anything else you can think of that I should try? I could get AT&T to unlock the phone (since I purchased it off contract) and try another carrier, but I'm not too interested in setting up another service just to test to see if it's the phone.
Click to expand...
Click to collapse
I do have exactly the same issue. I can make calls but cannot receive them. I've tried with both Skydragon v.2 and v.3 with stock kernel and with custom one v.004. I'm still investigating but so far not luck! Thanks.
Hey mstrblueskys, I had the same issue and after going to a long troubleshooting process with an AT&T representative, we figured out the issue. Hd voice service was causing this so they disabled it in my account and now I can receive calls without issues. How it helps you.
Thanks.
mstrblueskys said:
Hey - I've had 2 different Desire Eyes and they both have had incoming call issues. I didn't get a call all weekend into my phone, but I got lot of people saying they tried calling 2 or 3 times and got nothing. Anyone else having this issue?
Click to expand...
Click to collapse
sammor20 said:
Hey mstrblueskys, I had the same issue and after going to a long troubleshooting process with an AT&T representative, we figured out the issue. Hd voice service was causing this so they disabled it in my account and now I can receive calls without issues. How it helps you.
Thanks.
Click to expand...
Click to collapse
I just talked to them too. Turned off HD voice and bam - perfect.
Turning off HD Voice?
mstrblueskys said:
I just talked to them too. Turned off HD voice and bam - perfect.
Click to expand...
Click to collapse
I'm rooted with Skydragon 3.0, and having the same issue. Could you talk me through which menus you navigated through to get to HD Voice-off? Thanks in advance!!
redbullmed said:
I'm rooted with Skydragon 3.0, and having the same issue. Could you talk me through which menus you navigated through to get to HD Voice-off? Thanks in advance!!
Click to expand...
Click to collapse
You have to call in. That's the only option.
I was having receiving call issue after installing stock Sense 7 Marshmallow. Problem solved after HD voice is disabled.
Issue with volte on my M9. I saw the warnings and take responsibility for my actions.
When trying simultaneous voice and data I get the "data not available while on this call" popup. I verified Adv calling is turned on and my Verizon shows it activated also.
Since I'm not sure how to deal with Verizon on S-Off, custom recovery, custom rom I thought I'd start with the clever and helpful contributors on xda.
Any tips for preparing to deal with Verizon from those of you having gone through something similar?
************************ Edit
Viper 3.5 vzw FW 2.6.605 Don't have my hopes up but will try RUU to stock set up tonight
sidjohn said:
informationalIssue with volte on my M9. I saw the warnings and take responsibility for my actions.
When trying simultaneous voice and data I get the "data not available while on this call" popup. I verified Adv calling is turned on and my Verizon shows it activated also.
Since I'm not sure how to deal with Verizon on S-Off, custom recovery, custom rom I thought I'd start with the clever and helpful contributors on xda.
Any tips for preparing to deal with Verizon from those of you having gone through something similar?
************************ Edit
Viper 3.5 vzw FW 2.6.605 Don't have my hopes up but will try RUU to stock set up tonight
Click to expand...
Click to collapse
There have been both temporary and permanent hosings of volte. Ruu will cut to the chase and tell you right away if its ROM/app based.
I had one that had to be returned because of this. We can chat more after you ruu.
dottat said:
There have been both temporary and permanent hosings of volte. Ruu will cut to the chase and tell you right away if its ROM/app based.
I had one that had to be returned because of this. We can chat more after you ruu.
Click to expand...
Click to collapse
Thanks @dottat - Used your vzwM9_1.33_0PJAIMG.zip to ruu with htc_fastboot. Still not able to do voice and data simultaneously.
Just went back into recovery to wipe data/factory reset and noticed messages regarding missing bitmap oem_unlock_bg. Is that relevant? Saw somewhere that that is a toggle in developer options but cant find it
sidjohn said:
Thanks @dottat - Used your vzwM9_1.33_0PJAIMG.zip to ruu with htc_fastboot. Still not able to do voice and data simultaneously.
Just went back into recovery to wipe data/factory reset and noticed messages regarding missing bitmap oem_unlock_bg. Is that relevant? Saw somewhere that that is a toggle in developer options but cant find it
Click to expand...
Click to collapse
That message is normal.
If the issue stuck after ruu and you are in solid 4g service area you may need to get it swapped. Under settings-call is the video calling section greyed out permanently too?
Sent from my HTC6535LVW using Tapatalk
dottat said:
That message is normal.
If the issue stuck after ruu and you are in solid 4g service area you may need to get it swapped. Under settings-call is the video calling section greyed out permanently too?
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
South side of Minneapolis so I believe we have solid 4G and wife's iPhone 6 is capable of simultaneous data/voice.
Video calling is selected and grayed out.
Haven't tried toggling from My Verizon account yet.
sidjohn said:
South side of Minneapolis so I believe we have solid 4G and wife's iPhone 6 is capable of simultaneous data/voice.
Video calling is selected and grayed out.
Haven't tried toggling from My Verizon account yet.
Click to expand...
Click to collapse
Yours is exactly like mine was. I toggled from the account a few times. Had vzw support engineers look at multiple times and we finally gave up.
Any info you can offer up on flash history you might have? Did you browse the root directory of the phone and open some of the files etc?
Sent from my HTC6535LVW using Tapatalk
dottat said:
Yours is exactly like mine was. I toggled from the account a few times. Had vzw support engineers look at multiple times and we finally gave up.
Any info you can offer up on flash history you might have? Did you browse the root directory of the phone and open some of the files etc?
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
Not sure when this issue started for me but I didn't think to even check it until seeing some posts from others recently.
S-Off by Java Card in mid-May and bounced around between some of the more stable and popular roms on these forums staying with those that indicate support for verizon
No Red Text aboot, and updated firmware to 2.6. No unusual failures or hangups at either or while flashing any roms.
Other than deleting some files in DCIM, Downloads, and Pictures from my Win7 PC, I have not gone exploring in the root directory and haven't knowingly changed anything there.
sidjohn said:
Not sure when this issue started for me but I didn't think to even check it until seeing some posts from others recently.
S-Off by Java Card in mid-May and bounced around between some of the more stable and popular roms on these forums staying with those that indicate support for verizon
No Red Text aboot, and updated firmware to 2.6. No unusual failures or hangups at either or while flashing any roms.
Other than deleting some files in DCIM, Downloads, and Pictures from my Win7 PC, I have not gone exploring in the root directory and haven't knowingly changed anything there.
Click to expand...
Click to collapse
It possibly is just simply random. Sucks. Did you do a factory reset in stock recovery just to be sure?
Sent from my HTC6535LVW using Tapatalk
dottat said:
It possibly is just simply random. Sucks. Did you do a factory reset in stock recovery just to be sure?
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
Besides factory reset, if not already done, talk to Verizon Tech Suppport
and confirm that it is active. I had this same problem after activating the service,
and Tier 2 Support found that only one of the two lines was actually setup for HD Calling.
michaelbsheldon said:
Besides factory reset, if not already done, talk to Verizon Tech Suppport
and confirm that it is active. I had this same problem after activating the service,
and Tier 2 Support found that only one of the two lines was actually setup for HD Calling.
Click to expand...
Click to collapse
Thanks guys for helping - Never run out of thanks for the day before!
I think I will return cid to VZW__001, ruu again to confirm, factory reset from stock recovery, and toggle the adv calling setting from my verizon.
Do I have to remove all evidence of S-Off before contacting Verizon? Best to stop in a store to talk them into a new phone? Or go online for support?
sidjohn said:
Thanks guys for helping - Never run out of thanks for the day before!
I think I will return cid to VZW__001, ruu again to confirm, factory reset from stock recovery, and toggle the adv calling setting from my verizon.
Do I have to remove all evidence of S-Off before contacting Verizon? Best to stop in a store to talk them into a new phone? Or go online for support?
Click to expand...
Click to collapse
I'd recommend going back to S-on before going in to ask about this. If it does get fixed one way or another, just let me know and we can meet up again to get you back to S-Off.
bschram said:
I'd recommend going back to S-on before going in to ask about this. If it does get fixed one way or another, just let me know and we can meet up again to get you back to S-Off.
Click to expand...
Click to collapse
S-on regardless of whether I contact them online or in store?
sidjohn said:
S-on regardless of whether I contact them online or in store?
Click to expand...
Click to collapse
In the store probably. Online you shouldn't need to worry about it
I will update for those interested when resolved...thanks for your help
So I've seen things here and there about what (possibly) causes loss of Volte, but it's been scattered. Browsing or opening things on the root directory, was about the only thing that stands out... What are other ideas about what may cause the problem... Just out of curiosity
lordcheeto03 said:
So I've seen things here and there about what (possibly) causes loss of Volte, but it's been scattered. Browsing or opening things on the root directory, was about the only thing that stands out... What are other ideas about what may cause the problem... Just out of curiosity
Click to expand...
Click to collapse
That was only my theory but sidjohn said he didn't do anything like that. So who knows. Could have been a poor factory configuration too. My replacement has always been fine.
Sent from my HTC6535LVW using Tapatalk
dottat said:
That was only my theory but sidjohn said he didn't do anything like that. So who knows. Could have been a poor factory configuration too. My replacement has always been fine.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
I am not shy to explore but cautious about opening or changing anything I'm not fairly sure about. Doesn't rule out a bonehead move on my part but I've been comfortable rooting about since the T-Bolt days.
Still in protracted discussions with big red.
Appreciate the support from the xda community and will update as things progress.
sidjohn said:
I will update for those interested when resolved...thanks for your help
Click to expand...
Click to collapse
Expecting replacement - refurbished "Like New" - M9 July 31st. Will update once It's operational.
sidjohn said:
Expecting replacement - refurbished "Like New" - M9 July 31st. Will update once It's operational.
Click to expand...
Click to collapse
Glad to hear they are replacing it for you!
bschram said:
Glad to hear they are replacing it for you!
Click to expand...
Click to collapse
Not painless but I understand VZW's process I guess. Involved 2 online chats (3 if I count one disconnected after a couple of minutes), email support efforts, and several days of texts and phone calls with tech support engineers before they determined my phone was not accessing a particular APN which allows for Advanced Calling.
Got the impression from Tech that this is uncommon but coincidentally also just yesterday received a survey from verizon pertaining to my experience with my m9. One section asked whether I experienced any of a litany of issues reported by others - short battery life, bad camera, overheating, etc...and the inability to open a web browsing session while on a phone call - my exact problem. So maybe not so uncommon?
Received replacement today, looks and feels clean and "Like New" - Charged it but haven't fired up yet.
Just finished returning my original M9 to Stock, Locked, and S-On per @dottat 's easy to follow directions - thank you.
Now to get the replacement set up and think about S-Off again --- just a little nervous about that!
*****Edit to add link*****
Useful information. (Return to locked/S-on in Post #3)
http://forum.xda-developers.com/verizon-one-m9/general/official-ruu-1-33-605-15-t3137397