[Q] Unable to Receive Phone Calls - One (M9) Q&A, Help & Troubleshooting

I've recently moved to Washington, D.C. for a summer internship as of last Friday. Ever since getting into the area, I have not been able to receive phone calls on my AT&T HTC One M9. I was curious to know if anyone else has had this issue? I am able to make phone calls, use the cellular internet (usually I have LTE service), send text messages, and anything else using the phone service, but the only time I know I get an incoming call is when my phone notifies me that I have a new voicemail message. It also doesn't matter if the phone is "awake" or not. I have had people call me when the phone screen is off and on, with the same result. I commute from Arlington, VA every day, and this issue happens regardless of where I am along my commute.
To further complicate things, if I am in phone conversation and someone calls me, Call Waiting shows up with the incoming call. So I am "able" to receive phone calls, but I do not receive them when I am not in a phone conversation.
Has anyone had a similar problem like this? I'm currently running Android Revolution 5.1 since the latest version has an issue for me where the phone restarts if I try to turn on the screen. Even then, that is not the issue because 8.1 has the same calling issue. I've talked with AT&T tech support and did everything they suggested, when I get home from work I plan on getting a new SIM card to see if that fixes things.
My gut tells me there is either something wrong with the SIM, or for some reason my out-of-state phone number (I have a central Ohio area code) has issues with the towers in the area.

I would reccommend that you try performing a manual roam, go to settings>mobile data>Network operators, let it scan for networks, select a network that is NOT your carrier then once it fails to register select your own carrier, this should update the Mobile HLR and hopefully allow you to receive calls again.
Hope this helps

shark0807 said:
I've recently moved to Washington, D.C. for a summer internship as of last Friday. Ever since getting into the area, I have not been able to receive phone calls on my AT&T HTC One M9. I was curious to know if anyone else has had this issue? I am able to make phone calls, use the cellular internet (usually I have LTE service), send text messages, and anything else using the phone service, but the only time I know I get an incoming call is when my phone notifies me that I have a new voicemail message. It also doesn't matter if the phone is "awake" or not. I have had people call me when the phone screen is off and on, with the same result. I commute from Arlington, VA every day, and this issue happens regardless of where I am along my commute.
To further complicate things, if I am in phone conversation and someone calls me, Call Waiting shows up with the incoming call. So I am "able" to receive phone calls, but I do not receive them when I am not in a phone conversation.
Has anyone had a similar problem like this? I'm currently running Android Revolution 5.1 since the latest version has an issue for me where the phone restarts if I try to turn on the screen. Even then, that is not the issue because 8.1 has the same calling issue. I've talked with AT&T tech support and did everything they suggested, when I get home from work I plan on getting a new SIM card to see if that fixes things.
My gut tells me there is either something wrong with the SIM, or for some reason my out-of-state phone number (I have a central Ohio area code) has issues with the towers in the area.
Click to expand...
Click to collapse
I had this issue last week as well. It came on out of the blue and did all the usual AT&T troubleshooting and technical support. As of Monday, though, I think I have the issue fixed. I don't know if AT&T made a network modification that spurred the issue or if I changed something on my phone. Anyway, I'm not sure exactly what step along the way actually fixed my issue, but here's what I did.
1) Go into mobile data settings and see if turning off "Enhanced 4G LTE services" helps
2) I'm not sure if ARHD has this option, but if you can set your phone disable 4g in mobile data settings, turn 4g off and see if you can receive calls...I bet you can (so that's a temporary solution)
3) Alternatively, you can dial *#*#4636#*#* which will bring you into phone settings. Go into phone information, scroll down and on preferred network type, change that from GSM/WCDMA/LTE auto to GSM or GSM Auto (again this is just a temp fix because basically you're disabling LTE which is not desirable)
If any of those work, then check this file:
system\customize\ACC\default.xml
Scroll to the "Phone" app section
Look for a line "<item type="boolean" name="voLteEnabled">false</item>"
Change that to "true"
(If ARHD is compatible with AT&T, then it's probably already set to true)
If it was set to false, reboot and see if that works (to test, you'll have to undo any changes made in steps 1,2 or 3).
I did a lot of stuff before I did any of the above and Insert Coin (the custom ROM I use) already had the voLte setting set to true so the stuff below might actually be what fixed my issue. The next steps are just not as quick to accomplish as I ran the AT&T Ruu a few times and also flashed the developer ROM.
here's everything that i did...
Ran ATT 1.32.502.31 RUU to confirm that I can receive calls on 100% stock.
Flashed stock developer RUU and I could no longer receive calls.
Flashed custom rom (Insert Coin) and I could still not receive calls.
Ran ATT RUU again and calls suddenly worked again.
Re-flashed developer RUU.
Rooted it
installed root explorer (ES Files Explorer)
navigated to system\customize\ACC\default.xml and made the change explained above
rebooted the phone and I was again able to receive calls on the developer edition
Restored Insert Coin from a backup and i was STILL able to receive calls.
After restoring IC, i checked the default.xml file and noticed that not only was voLte set to true, ALL of the voLte options (there are like 5 of them) were set to true. Then I checked the IC zip file and opened the default.xml from what i was flashing and they were all set to true in the zip file. So I think they were all set to true when I began having problems. So I'm really not sure what fixed this for me. But, like I said, that's everything I did and it's working again.
If you go 100% stock by flashing the AT&T RUU (or if you're able to restore to stock using an untouched system image from TWRP) and still can't receive calls, then get on with AT&T support and have them verify your provisioning.
Sorry if this is not very well organized, but I started having this issue like last Friday and worked on it all weekend and Monday and finally got it resolved Monday night...so needless to say...I tried a lot of different things, but what I've written above is what I believe fixed the issue.
I think the problem is that your area supports voLte but maybe the ROM doesn't. Notice when you make a call that your 4G/LTE icon changes to 4G only. Well, the same is supposed to happen when you receive a call, but for some reason, something isn't allowing the phone to switch to 4g only.

jollywhitefoot said:
I had this issue last week as well. It came on out of the blue and did all the usual AT&T troubleshooting and technical support. As of Monday, though, I think I have the issue fixed. I don't know if AT&T made a network modification that spurred the issue or if I changed something on my phone. Anyway, I'm not sure exactly what step along the way actually fixed my issue, but here's what I did.
1) Go into mobile data settings and see if turning off "Enhanced 4G LTE services" helps
2) I'm not sure if ARHD has this option, but if you can set your phone disable 4g in mobile data settings, turn 4g off and see if you can receive calls...I bet you can (so that's a temporary solution)
3) Alternatively, you can dial *#*#4636#*#* which will bring you into phone settings. Go into phone information, scroll down and on preferred network type, change that from GSM/WCDMA/LTE auto to GSM or GSM Auto (again this is just a temp fix because basically you're disabling LTE which is not desirable)
If any of those work, then check this file:
system\customize\ACC\default.xml
Scroll to the "Phone" app section
Look for a line "<item type="boolean" name="voLteEnabled">false</item>"
Change that to "true"
(If ARHD is compatible with AT&T, then it's probably already set to true)
If it was set to false, reboot and see if that works (to test, you'll have to undo any changes made in steps 1,2 or 3).
I did a lot of stuff before I did any of the above and Insert Coin (the custom ROM I use) already had the voLte setting set to true so the stuff below might actually be what fixed my issue. The next steps are just not as quick to accomplish as I ran the AT&T Ruu a few times and also flashed the developer ROM.
here's everything that i did...
Ran ATT 1.32.502.31 RUU to confirm that I can receive calls on 100% stock.
Flashed stock developer RUU and I could no longer receive calls.
Flashed custom rom (Insert Coin) and I could still not receive calls.
Ran ATT RUU again and calls suddenly worked again.
Re-flashed developer RUU.
Rooted it
installed root explorer (ES Files Explorer)
navigated to system\customize\ACC\default.xml and made the change explained above
rebooted the phone and I was again able to receive calls on the developer edition
Restored Insert Coin from a backup and i was STILL able to receive calls.
After restoring IC, i checked the default.xml file and noticed that not only was voLte set to true, ALL of the voLte options (there are like 5 of them) were set to true. Then I checked the IC zip file and opened the default.xml from what i was flashing and they were all set to true in the zip file. So I think they were all set to true when I began having problems. So I'm really not sure what fixed this for me. But, like I said, that's everything I did and it's working again.
If you go 100% stock by flashing the AT&T RUU (or if you're able to restore to stock using an untouched system image from TWRP) and still can't receive calls, then get on with AT&T support and have them verify your provisioning.
Sorry if this is not very well organized, but I started having this issue like last Friday and worked on it all weekend and Monday and finally got it resolved Monday night...so needless to say...I tried a lot of different things, but what I've written above is what I believe fixed the issue.
I think the problem is that your area supports voLte but maybe the ROM doesn't. Notice when you make a call that your 4G/LTE icon changes to 4G only. Well, the same is supposed to happen when you receive a call, but for some reason, something isn't allowing the phone to switch to 4g only.
Click to expand...
Click to collapse
Friend, you win the internet, turning off 4G and turning it back on did the trick. Thank you!

shark0807 said:
Friend, you win the internet, turning off 4G and turning it back on did the trick.
Click to expand...
Click to collapse
Nice. Glad to hear it. Where did you turn 4G off? In mobile data settings?
shark0807 said:
Thank you!
Click to expand...
Click to collapse
There's a button for that

jollywhitefoot said:
Nice. Glad to hear it. Where did you turn 4G off? In mobile data settings?
There's a button for that
Click to expand...
Click to collapse
Yes, once off of 4G I was able to receive calls again. Now That I'm home I'm trying the .xml edit to see what happens.
EDIT: Tried the .xml edit, didn't work, I will flash the RUU tonight and see what happens.

shark0807 said:
Yes, once off of 4G I was able to receive calls again. Now That I'm home I'm trying the .xml edit to see what happens.
EDIT: Tried the .xml edit, didn't work, I will flash the RUU tonight and see what happens.
Click to expand...
Click to collapse
This happened to me with my M7 on T-Mobile after they added VoLTE and I was forced to toggle off LTE whenever I wanted to use the phone and I could never make it work properly again. Fortunately for you, the M9 supports it so it could be something like tower upgrades thus toggling it off then on made it grab on to different towers...possibly. I was running ViperROM then so it was a quick toggle however it would get frustrating to have to go into settings regularly. Hope you are all fixed for good

shark0807 said:
Yes, once off of 4G I was able to receive calls again. Now That I'm home I'm trying the .xml edit to see what happens.
EDIT: Tried the .xml edit, didn't work, I will flash the RUU tonight and see what happens.
Click to expand...
Click to collapse
Was the XML switch set to false? You could try changing all of the volte switches to true. Also maybe a different custom rom...maybe arhd doesn't support volte at all.

It was, and I did as you suggested, still nothing doing. I've now been trying to use the AT&T RUU to restore everything, but I'm running into problems with that as well. I haven't seen anyone discuss it on this forum, but fastboot and htc_fastboot crash while trying to flash the RUU. First I tried with the .exe of the RUU, which doesn't give me much information except that it crashes. If I do it through command prompt (and a RUU in .zip format), the RUU sends a "pre-update", crashes with an error code FAIL90, tries to do it again, then fastboot and htc_fastboot crash on the computer.
From previous HTC phone forums, it seems like this error happens on Windows 8 and 8.1 computers, but I'm not entirely convinced why my OS in this case would be the problem.
Fastboot error on computer:
Code:
Problem signature:
Problem Event Name: APPCRASH
Application Name: fastboot.exe
Application Version: 0.0.0.0
Application Timestamp: 54bfb0a1
Fault Module Name: ntdll.dll
Fault Module Version: 6.3.9600.17736
Fault Module Timestamp: 550f42c2
Exception Code: c0000005
Exception Offset: 0004248d
OS Version: 6.3.9600.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 5861
Additional Information 2: 5861822e1919d7c014bbb064c64908b2
Additional Information 3: a10f
Additional Information 4: a10ff7d2bb2516fdc753f9c34fc3b069
And for htc_fastboot:
Code:
Problem signature:
Problem Event Name: APPCRASH
Application Name: htc_fastboot.exe
Application Version: 0.0.0.0
Application Timestamp: 546e94d2
Fault Module Name: StackHash_79f3
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: PCH_27_FROM_htc_fastboot+0x00001215
OS Version: 6.3.9600.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 79f3
Additional Information 2: 79f3f37ca9651ef9bd47b0bfb55904f8
Additional Information 3: 86de
Additional Information 4: 86de0d14c4489f5d62365f6244178ece

shark0807 said:
It was, and I did as you suggested, still nothing doing. I've now been trying to use the AT&T RUU to restore everything, but I'm running into problems with that as well. I haven't seen anyone discuss it on this forum, but fastboot and htc_fastboot crash while trying to flash the RUU. First I tried with the .exe of the RUU, which doesn't give me much information except that it crashes. If I do it through command prompt (and a RUU in .zip format), the RUU sends a "pre-update", crashes with an error code FAIL90, tries to do it again, then fastboot and htc_fastboot crash on the computer.
From previous HTC phone forums, it seems like this error happens on Windows 8 and 8.1 computers, but I'm not entirely convinced why my OS in this case would be the problem.
Fastboot error on computer:
Code:
Problem signature:
Problem Event Name: APPCRASH
Application Name: fastboot.exe
Application Version: 0.0.0.0
Application Timestamp: 54bfb0a1
Fault Module Name: ntdll.dll
Fault Module Version: 6.3.9600.17736
Fault Module Timestamp: 550f42c2
Exception Code: c0000005
Exception Offset: 0004248d
OS Version: 6.3.9600.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 5861
Additional Information 2: 5861822e1919d7c014bbb064c64908b2
Additional Information 3: a10f
Additional Information 4: a10ff7d2bb2516fdc753f9c34fc3b069
And for htc_fastboot:
Code:
Problem signature:
Problem Event Name: APPCRASH
Application Name: htc_fastboot.exe
Application Version: 0.0.0.0
Application Timestamp: 546e94d2
Fault Module Name: StackHash_79f3
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: PCH_27_FROM_htc_fastboot+0x00001215
OS Version: 6.3.9600.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 79f3
Additional Information 2: 79f3f37ca9651ef9bd47b0bfb55904f8
Additional Information 3: 86de
Additional Information 4: 86de0d14c4489f5d62365f6244178ece
Click to expand...
Click to collapse
I'm on Windows 7, so I don't know about the Win 8/8.1 issues, but I've read a lot of people that have trouble using those operating systems with drivers.
Maybe try insert coin or another custom rom...I know IC supports AT&T, even thought that's the rom i was using when I started having problems.

Unfortunately I have very slow internet so it takes hours to download a ROM to test. I installed ViperROM, which I have been very happy with when I had my M7, and I can confirm that receiving calls works again. But I have the same problem I had with ARHD, that being that when the screen turns off, the phone turns off. So, the solution is "fixed" kind of, I just need to figure out why my phone is doing this standby issue, and fix that.

shark0807 said:
Unfortunately I have very slow internet so it takes hours to download a ROM to test. I installed ViperROM, which I have been very happy with when I had my M7, and I can confirm that receiving calls works again. But I have the same problem I had with ARHD, that being that when the screen turns off, the phone turns off. So, the solution is "fixed" kind of, I just need to figure out why my phone is doing this standby issue, and fix that.
Click to expand...
Click to collapse
That's because the version of Viper you're using is on the 1.40 base and you're on 1.32 firmware. Either upgrade firmware to 1.40 (requires s-off), flash a 1.32 version of Viper (if one is available...i'm sure one is), or you can try only flashing a 1.32 kernel (either the kernel found in the 1.32 viper rom, or you could try flashing Flar2's 0.3 version kernel in the Original Develpment section). I can confirm with insert coin that I'm able to run a 1.40 base rom on 1.32 base firmware by flashing a 1.32 base kernel...I can't guarantee the same will work with Viper, but it probably will. The easiest thing will be to just flash Flar's 0.3 version kernel because it's a small download. If that doesn't work, you probably should just download the entire 1.32 viper rom (or get s-off and flash the 1.40 firmware).
Actually, I forgot there's an option in Viper's aroma to install the old base kernel. Read here: http://venomroms.com/htc-one-m9/ (see the firmware requirements section)

@shark0807 your ADB and fastboot crash because they are not suitable for the M9 and buggy probably. I had such versions at the beginning of the M9 lifecycle. HTC has by now released their own version of fastboot which a.) doesn't crash anymore and b.) is capable of flashing RUU's larger than 2GB.
You can get my "Batch Tool" which includes the ARUWizard (the "RUU") from HTC as well as the updated htc_fastboot.exe and adb.exe (which I believe is just the generic Google adb.exe).
The Batch Tool comes as self-extracting rar archive and extracts to C:\Android - if you don't want to use it anymore, just delete that folder and its gone.
Batch Tool is here: http://forum.xda-developers.com/showpost.php?p=59783535&postcount=4
A procedure to have your stuff working on Windows 8/8.1:
1.) Go into Control Panel and remove everything that is or might be connected to HTC. First and foremost, HTC Sync Manager. Also every type of ADB/Fastboot drivers you see there.
2.) Download HTC Sync Manager from HERE and install it. Then remove it again (Sync Manager likes interfering with RUU flashes by blocking Fastboot and ADB for its own stupid purposes - better not have it run in the background. The drivers it installs will remain on your system anyway).
3.) Download my Batch Tool and use the "htc_fastboot.exe" instead of the generic Google fastboot.exe!
That should get you up and running. My Batch Tool additionally installs vcredist_x86_2008_SP1.exe - which is vital for a RUU to run properly. It is usually also installed by HTC Sync Manager but I have seen plenty of cases where that did not happen, so I included it into my Batch Tool setup.
Furthermore, DotNet in some version is required but usually already on most windows PC's - I haven't seen the necessity to separately install it. Just FYI.

I ended up having this problem, just tried what was said and its working so far hopefully it stays working! never had this problem before I think the volte stuff was disabled from when I tried a different rom, im staying stock rooted at&t now

jollywhitefoot said:
I think the problem is that your area supports voLte but maybe the ROM doesn't. Notice when you make a call that your 4G/LTE icon changes to 4G only. Well, the same is supposed to happen when you receive a call, but for some reason, something isn't allowing the phone to switch to 4g only.
Click to expand...
Click to collapse
I think that's the case , for now what has work for me is using GSM auto prl, drains the battery faster , don't know why .
I have call att, I have them going nuts , they don't know what it is , I also enable all of the values, for volte, in the default.XML file, but didn't work .
I'm going to try changing roms, I'm thinking maximum HD
To point out, I haven't change firmwares , the phone still has the at&t one , I've kept in order to avoid this situations , I'll try another ROM

@ZeRo2o9
Where can I get the at&t ROM rooted ??

People I had the same issue , I've call at&t and told them I can only receive call on GSM mode , while on LTE , the phone wouldn't ring at all .
So the lady explain that LTE voice is not supported on all towers , that is the reason , so she opt me out , while it becomes available. Then unchecking the option under setting and reseting the phone the calls where working again .
Thanks for this forum for the help .

Related

[Q] Problem with Radio. URGENT

After flashing the newest Paranoid Android and running for a few days I suddenly lost data. My phone states that my phone is roaming, so I tried turning data on and off and switching on airplane mode and then I settled on switching back to the ROM I was previously on, the latest MIUI and to my dismay saw that the same issue was occurring. So now my phone has no data on every rom I try and I dont know how to remedy this. If anyone has the same issue or anything to say that might help it would greatly appreciated. I still have 4 months to go on my contract and no money for Verizon's ETF or a replacement phone.
Sent from my HTC Incredible 2 using xda app-developers app
savtitan29 said:
After flashing the newest Paranoid Android and running for a few days I suddenly lost data. My phone states that my phone is roaming, so I tried turning data on and off and switching on airplane mode and then I settled on switching back to the ROM I was previously on, the latest MIUI and to my dismay saw that the same issue was occurring. So now my phone has no data on every rom I try and I dont know how to remedy this. If anyone has the same issue or anything to say that might help it would greatly appreciated. I still have 4 months to go on my contract and no money for Verizon's ETF or a replacement phone.
Sent from my HTC Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
Have you tried re-installing your PRL? Call *228 and press send, use option 2. That'll re-load the preferred roaming list.
What recovery are you using (CWM or TWRP - and ver. #) and is your DI2 S-Off ? Please post your current Bootloader information (HBoot) and whether you have Backups for your (previous) Roms on your mSD card?
Assuming that your device can still making voice calls (SMS ??) - does it work over WiFi ? And, you have already done *228 option 1 - as it sometimes help reset it?
It is sometimes necessary to call VZW and speak to tech support for smartphone and they need to reset things and power cycle your device while you are on the line with them on a different phone to get you out of roaming, depending on the "radio" that your device is now. Hopefully, you did not somehow flashed the leaked non-VZW radio/kernel from China Telecom.
Before calling VZW, it would be helpful if you can flash a Sense-based ROM, either one of the stock zip file or Andybone's tweaked Sense Rom based on OTA, or the SkyRaider's Zeus v1.3 Sense Rom - and, if your phone was Sim-unlocked, can you check to see if it will work in GSM mode for voice & data (borrow a known-working AT&T or T-Mobile Sim card) Remember to do a Master Reset, wipe dalvik/cache & system before flashing a different Rom.
And, you should read up the sticky posts written here about restoring the device back to stock - just in case. The steps are slow & delicate, but it can be done - relax & don't panic.
I cannot make the call because I have no data
Sent from my HTC Incredible 2 using xda app-developers app
Letitride said:
What recovery are you using (CWM or TWRP - and ver. #) and is your DI2 S-Off ? Please post your current Bootloader information (HBoot) and whether you have Backups for your (previous) Roms on your mSD card?
Assuming that your device can still making voice calls (SMS ??) - does it work over WiFi ? And, you have already done *228 option 1 - as it sometimes help reset it?
It is sometimes necessary to call VZW and speak to tech support for smartphone and they need to reset things and power cycle your device while you are on the line with them on a different phone to get you out of roaming, depending on the "radio" that your device is now. Hopefully, you did not somehow flashed the leaked non-VZW radio/kernel from China Telecom.
Before calling VZW, it would be helpful if you can flash a Sense-based ROM, either one of the stock zip file or Andybone's tweaked Sense Rom based on OTA, or the SkyRaider's Zeus v1.3 Sense Rom - and, if your phone was Sim-unlocked, can you check to see if it will work in GSM mode for voice & data (borrow a known-working AT&T or T-Mobile Sim card) Remember to do a Master Reset, wipe dalvik/cache & system before flashing a different Rom.
And, you should read up the sticky posts written here about restoring the device back to stock - just in case. The steps are slow & delicate, but it can be done - relax & don't panic.
Click to expand...
Click to collapse
I have done multiple AntiVenom wipes to no avail, and only WiFi is working for me. I have not yet attempted to flash an older sense based Rom so I will try that. My only question is can VZW access and get my phone out of permanent roaming with my phone having no data or 2G?
P.S. - I did not flash the Chinese radio/kernel. Just checked
Sent from my HTC Incredible 2 using xda app-developers app
savtitan29 said:
I have done multiple AntiVenom wipes to no avail, and only WiFi is working for me. I have not yet attempted to flash an older sense based Rom so I will try that. My only question is can VZW access and get my phone out of permanent roaming with my phone having no data or 2G? P.S. - I did not flash the Chinese radio/kernel. Just checked
Click to expand...
Click to collapse
I see, I've seen DI2 in similar situations but usually, VZW tech support can do some resetting of the stored info on their database to try to restore it, and the best way to make that easier is to restore/go back to a near/pure Sense-based ROM. Once you do that, and you are prompted to "activate your phone OTA" - try to make a call - if you can dail out but the call cannot go thru, you should hear an automated voice msg. that there is error processing your call, ask you to hang up, power down & restart - and try again after waiting 5 to 10 minutes. The msg. will ask you to call # **** - make sure you can call from a home/office/different wireless number as they will go thru the troubleshooting & power cycle/reset process - should take 10 or 15 minutes, and will have you make a test call & verify connectivity success at the end. Informed them that you've done a Master Reset. (FYI - This involved updating, re-generating the good old "A" security key(s) used to identify the phone and the ESN/MEID stored for each device - somehow, the flashing of some Roms & wipe/reset totally dumped clean all of that info, and it needed to be re-established. )
The next step is to re-flash a Sense-based Rom that's stock or close to it -
savtitan29 said:
I cannot make the call because I have no data
Click to expand...
Click to collapse
From the device's Settings - About Phone - look for your radio's info - is it .0312 or .0320 (ICS-based) or an older radio like 0.1111 - after you flashed the Sense Rom, please check it again, and if you could - follow the Sticky's to get the 0.312 radio or even the 0.1111 radio in a Zip file, copy/move to mSD card, restart into Bootloader & flash it - restart and see if it can make calls/use data. If not, VZW tech support is your best friend to reset those Android handshaking of the security keys as stored on their database ...
Letitride said:
I see, I've seen DI2 in similar situations but usually, VZW tech support can do some resetting of the stored info on their database to try to restore it, and the best way to make that easier is to restore/go back to a near/pure Sense-based ROM. Once you do that, and you are prompted to "activate your phone OTA" - try to make a call - if you can dail out but the call cannot go thru, you should hear an automated voice msg. that there is error processing your call, ask you to hang up, power down & restart - and try again after waiting 5 to 10 minutes. The msg. will ask you to call # **** - make sure you can call from a home/office/different wireless number as they will go thru the troubleshooting & power cycle/reset process - should take 10 or 15 minutes, and will have you make a test call & verify connectivity success at the end. Informed them that you've done a Master Reset. (FYI - This involved updating, re-generating the good old "A" security key(s) used to identify the phone and the ESN/MEID stored for each device - somehow, the flashing of some Roms & wipe/reset totally dumped clean all of that info, and it needed to be re-established. )
The next step is to re-flash a Sense-based Rom that's stock or close to it -
From the device's Settings - About Phone - look for your radio's info - is it .0312 or .0320 (ICS-based) or an older radio like 0.1111 - after you flashed the Sense Rom, please check it again, and if you could - follow the Sticky's to get the 0.312 radio or even the 0.1111 radio in a Zip file, copy/move to mSD card, restart into Bootloader & flash it - restart and see if it can make calls/use data. If not, VZW tech support is your best friend to reset those Android handshaking of the security keys as stored on their database ...
Click to expand...
Click to collapse
I will be doing all of these as soon as I get home from school. Thank you for all your help so far
Try dialing some of the *228 variants such as *22801, *22802, and so on. I had a similar issue where the radio got all messed up. Verizon store was so close to selling me a new phone, but when I made this suggestion the sales guy tried it and it cleared up my issue. My prl I think was totally hosed and needed to be reprogrammed ota.
Sent from my ADR6350 using Tapatalk 2
Letitride said:
I see, I've seen DI2 in similar situations but usually, VZW tech support can do some resetting of the stored info on their database to try to restore it, and the best way to make that easier is to restore/go back to a near/pure Sense-based ROM. Once you do that, and you are prompted to "activate your phone OTA" - try to make a call - if you can dail out but the call cannot go thru, you should hear an automated voice msg. that there is error processing your call, ask you to hang up, power down & restart - and try again after waiting 5 to 10 minutes. The msg. will ask you to call # **** - make sure you can call from a home/office/different wireless number as they will go thru the troubleshooting & power cycle/reset process - should take 10 or 15 minutes, and will have you make a test call & verify connectivity success at the end. Informed them that you've done a Master Reset. (FYI - This involved updating, re-generating the good old "A" security key(s) used to identify the phone and the ESN/MEID stored for each device - somehow, the flashing of some Roms & wipe/reset totally dumped clean all of that info, and it needed to be re-established. )
The next step is to re-flash a Sense-based Rom that's stock or close to it -
From the device's Settings - About Phone - look for your radio's info - is it .0312 or .0320 (ICS-based) or an older radio like 0.1111 - after you flashed the Sense Rom, please check it again, and if you could - follow the Sticky's to get the 0.312 radio or even the 0.1111 radio in a Zip file, copy/move to mSD card, restart into Bootloader & flash it - restart and see if it can make calls/use data. If not, VZW tech support is your best friend to reset those Android handshaking of the security keys as stored on their database ...
Click to expand...
Click to collapse
So I have moved back to stock Sense 2.3.3 with S-ON and there is still no working connection. At this point would I call VZW? and since i cannot call from my cell phone would i still call the *228 number or not? Is it possible for them to access my phone when it cannot connect?
savtitan29 said:
So I have moved back to stock Sense 2.3.3 with S-ON and there is still no working connection. At this point would I call VZW? and since i cannot call from my cell phone would i still call the *228 number or not? Is it possible for them to access my phone when it cannot connect?
Click to expand...
Click to collapse
Hmm, still no luck at all. Yeah, dial *228 first and does it dial out at all, or do you get any recorded msg. or nothing happened at all? Make a note of it - then, call VZW from another line (800) 922-0204, Monday-Sunday 6am-11pm - you want to reach smartphone / tech support - tell them you have the HTC DI2 and you are a customer. They will verify your personal info and then proceed to the next steps - and, try to find a way to communicate and/or re-establish communication with your device OTA. Make sure your device is at least 75% charged and at a good 3G signal area, and it's helpful to let them know that other VZW devices at the same physical location have coverage & working signal.
Let's see them go about resetting the system, etc. ...

[Q] Cannot call or receive calls, but can text and use 4G

Ok so I did a ton of stuff to my phone like rooting, flashing different ROMS, but in the end I want to get my phone back to stock, so I flashed the stock firmware with LG Flash Tool but now I can't call anyone and incoming comes don't come through. I just get a "out of service area" after a while whenever I try calling someone. Texting works and internet works, and so does Wifi. Also, my time is 3 hours fast when it's set to automatic in the settings. I don't know why it's doing this. And my IMEI is 0. Here are some pictures of my settings. One more thing. Since I flashed the stock, in my android devices, Google doesn't recognize my old device anymore. It treats this phone like a new device now. Weird... Anyone know how I can fix this problem?
Oh and when I try to update my phone it gives me this: "Your phone is not registered yet"
So many problems, I'm so sad
(these are the images uploaded online if the attachments don't work)
postimg (DOT) org/image/yc356c9el/
postimg (DOT) org/image/ipnwgre97/
Do you have a EFS backup? Your IMEI is 00000000000000.... That's NOT the way it should be. Maybe the network provider blocks you from using the network because of an invalid IMEI (don't know for sure) but since you reflashed Stock ROM i don't think it's modem related...
I think I fixed it! I just used the kdz method of going back to stock instead of the tot/dll method and it fixed my problems! I got it from this thread if anyone else has the same problem:
http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140

LTE modem issues on stock and custom based roms

Hi!
I am investigating an interesting (and potentially "deadly") issue with the Oppo modem, occuring on european netoworks, specifically Orange and Vodafone Romania. Orange has licences in the LTE FDD 800/1800/2600 mhz, Vodafone 800/1800 FDD and 2600 TDD. Where I live I can only get Orange on 1800/2600 and Vodafone on 800/1800 mhz. At first tried installing with a custon recovery both stock and custom firmwares, wich broke LTE on Orange and I was installing roms for 2 days fearing I messed up something. Actually, with stock recovery by installing stock fw, LTE started working again, but there was no way for it to work on AOSP roms. I then bought a Vodafone card and I figured that while LTE on Orange breaks, it works with Vodafone and vice-versa. On custom roms, only Vodafone works, but when I restore a twrp backup, it breaks for both Vodafone and Orange. Logcat does not show anything suspicious and I only get (while on LTE only) "emergency calls only" after the phone tried desperately to register on LTE for dozens of seconds. Since the way I flash roms does seem to have an effect sometimes, I realised it could be a filesystem bug, though I must admit further investigation is needed. I am not unified an I tried unbricking my phone twice (with the default version after unbricking, it works on Vdf, no Orange).
I would need a collaboration with more experienced developpers to further investigate this serious issue.
Strange But . . .
thank you for the heads-up, I've tried several ROMs already including the famous Chinese COS ROMs and have not experienced this issue, however, I have observed in the past that my LTE connection is functioning erratically. I am not sure if this is related but i believe it needs to be checked. I totally lost LTE connection from one of the 2 providers in my country where previously am getting strong signal. Am not suspecting anything of this sort until I came across this report. Hope an expert respond to this to clear this out.
Yes, it happened to me also, although the signal bars are there, the connection gets lost. At first I thought it was a network issue, but it happened once again after that. I realised that swiching data on/off sometimes solves the issue, sometimes not. Sometimes a reboot soles it, sometimes not.
But the fact that I have to flash another ROM to be able to use another netork, well, that's a big issue that almost makes me wanna change my phone. Too bad, because Oppo has geat signal strength where Samsung/ HTC normaly would loose connectivity.
I am waiting for the devs to suggest another thing to look for. I suppose that opening another thread on the stock rom area would be useless since this issue is specific to both stock and custom roms.
Maybe the mods would just post a shortcut there to this post, as this is a serious issue.
you need to enter engineering main page from the dialer enter *#36446337# Go to "Network Set" "RAT Mode"
Select what you need.. Go Back using Back button, go to "Band Mode" and select what you need, Then go to LTE Band Mode and do the same. That solved the issue for me.
that ussd code doesnt do anything on my v9077 however *#*#4664#*#* brings up a testing menu which enables setting radio to lte only this is handy if you are testing in bad reception are as phone will default to hspap if the signal is stronger
Unfortunately, none of the codes work, only *#*#4636#*#*
I suspect a RIL issue, since flashing stock modem instead of CM based, I get to see all networks, but I cannot conect to any of them with the proper tested SIM card.
In order to accomplish that, I must credit Flying_Bear with his thread http://forum.xda-developers.com/showthread.php?t=2496075 but also xpirt http://forum.xda-developers.com/and.../how-to-conver-lollipop-dat-files-to-t2978952
You basically need to exctract the telephony-common.jar and insert files from stock FW in order for it to comply with the stock modem that has been flashed. Only a combination of these 2 parts will make a good working phone.
The problem is that the files in stock ROM are odexed so you have 2 files, telephony-common.jar and telephony-common.odex. I tried deodexing them (thanks to sicopat http://forum.xda-developers.com/galaxy-s2/themes-apps/how-to-manually-deodex-odex-t1208320 )
Code:
java -jar baksmali.jar -x telephony-common.odex -o deodex
but I get
Code:
Error occured while loading boot class path files. Aborting.
org.jf.dexlib.Code.Analysis.ClassPath$ClassNotFoundException: Could not find superclass Landroid/app/Service;
at org.jf.dexlib.Code.Analysis.ClassPath$ClassDef.loadSuperclass(ClassPath.java:784)
at org.jf.dexlib.Code.Analysis.ClassPath$ClassDef.<init>(ClassPath.java:668)
at org.jf.dexlib.Code.Analysis.ClassPath.loadClassDef(ClassPath.java:280)
at org.jf.dexlib.Code.Analysis.ClassPath.initClassPath(ClassPath.java:163)
at org.jf.dexlib.Code.Analysis.ClassPath.InitializeClassPathFromOdex(ClassPath.java:110)
at org.jf.baksmali.baksmali.disassembleDexFile(baksmali.java:98)
at org.jf.baksmali.main.main(main.java:278)
Error while loading class Landroid/accessibilityservice/AccessibilityService; from file ./framework.zip
Error while loading ClassPath class Landroid/accessibilityservice/AccessibilityService;
If you are only *#*#4636#*#* can access. It means you are not in stock rom. (No engineer mode)
Use computer to flash back to stock first. Then try step by step.
http://www.oppoforums.com/threads/guide-how-to-recover-your-bricked-find-7-7a.23067/
Sent from my X9070

[Q] LTE issues after cm12 (virgin mobile a5_chl)

So as the title states I have the virgin mobile a5_chl variant and after flashing cm12 (build 05052015) I can no longer (or at least hardly ever) gain LTE signal back, no matter what ROM im on. It comes across saying I have no service and no signal and I can't text or call when trying to use LTE.
I have done the following to try and fix:
1. flash apn fix (obviously)
2. restore stock backup
3. try a different rom
4. completely RUU back to stock.
I believe the issue lies somewhere within the HtcOMADM_SPCS.apk but I'm not 100% sure about that. According to any thing i've found the HtcOMADM_SPCS.apk is the "vDM client" that allows for profile updates (when i try to do a profile update it either says vDM client has stopped responding or the the profile update could not be completed). I've tried uninstalling and reinstalling the HtcOMADM_SPCS.apk but that only provided a fix once and when i rebooted my phone I lost signal again.
I'm pretty much at a loss as to what to do as virgin mobile gives me the usual run around that they are "having tower issues" so I'm hoping maybe someone on here can help out. If you need any further information please ask and I'll provide, I tried to be thorough when creating this thread. Thanks for any help.
BUMP / Can someone from VM USA upload a copy of the HtcOMAD_SPCS.apk it can be found in system/app/HtcOMAD_SPCS. It would be very much appreciated if you could
Same exact issue
tsmith1223 said:
BUMP / Can someone from VM USA upload a copy of the HtcOMAD_SPCS.apk it can be found in system/app/HtcOMAD_SPCS. It would be very much appreciated if you could
Click to expand...
Click to collapse
Really weird been using cm12 worked well. Tried carbon worked perfectly! I went to bed and woke up no signal no data no anything . tried everything you did.
EDIT: just realized 3g also dose not work! in serious need of help. USA Virgin mobile phone. Rooted S-off. Currently back on carbon backups/new roms do not work. i get no service can only use wifi.
:crying::crying::crying:

Keep losing data connection and apn setting access

I picked up a Sprint prepaid HTC 816 recently and decided to flash this rom below
[ROM][UNOFFICIAL][CM12.1][5.1.1][VirginMobileUS][A5][single sim][1/1/2016 security]
That one
It installed great, had everything everything working after I added my Sprint APN settings. The phone still displayed it as Virgin Mobile and only 3g seemed to be working. But I was making and receiving calls, text messages and had mobile data.
Fast forward a couple of hours, I installed a custom theme from the Play store, rebooted and ever since then I lost the ability to pickup a network signal and access my APN settings.
If I re-seat the sim and toggle airplane mode it will pickup a network signal and I can regain apn setting access again but it drops within minutes.
Ive reflashed the rom, wiped everything reflashed again, same thing. Any ideas on what has happened?
Thanks and appreciate your time!
monsai83 said:
I picked up a Sprint prepaid HTC 816 recently and decided to flash this rom below
[ROM][UNOFFICIAL][CM12.1][5.1.1][VirginMobileUS][A5][single sim][1/1/2016 security]
That one
It installed great, had everything everything working after I added my Sprint APN settings. The phone still displayed it as Virgin Mobile and only 3g seemed to be working. But I was making and receiving calls, text messages and had mobile data.
Fast forward a couple of hours, I installed a custom theme from the Play store, rebooted and ever since then I lost the ability to pickup a network signal and access my APN settings.
If I re-seat the sim and toggle airplane mode it will pickup a network signal and I can regain apn setting access again but it drops within minutes.
Ive reflashed the rom, wiped everything reflashed again, same thing. Any ideas on what has happened?
Thanks and appreciate your time!
Click to expand...
Click to collapse
Are these the APN codes you used(poster corrected a mistake in green text)? Looks like there is a different APN for prepaid /postpaid.
http://androidforums.com/threads/working-sprint-prepaid-apn-settings.920752/
I indeed use the apn settings in the green from that post. They were working fine until I had a reboot. Then everything went to ****. It wont even let me access the apn settings and when I can its briefly and then I lose signal and apn access.
monsai83 said:
I indeed use the apn settings in the green from that post. They were working fine until I had a reboot. Then everything went to ****. It wont even let me access the apn settings and when I can its briefly and then I lose signal and apn access.
Click to expand...
Click to collapse
I had an issue with something on my Virgin mobile 816 a5_chl a while back and a member @wxppro was very knowledgeable about APN settings and their intricacies. He had a MVNO 816 at the time with an APN issue and I bet he could help you with this as that was my best suggestion for a fix and it didn't help you.
See if you can direct him here to this forum so that if he can help out the info is here to help others as well. Good luck.
Not sure how much I can help. APN is a tricky business. If your APN settings disappear after some time, it is generally because the cellular network the phone connects to does not match the APN's MCC/MNC numbers. Or it could be the phone is in 3G mode (CDMA EvDo mode).
You can try these things:
Switch network types, from LTE to 3G, wait a minute, and then back to LTE. APNs do not show up in 3G mode. They only show up in LTE (or global) mode.
When you have the APNs show up, check the parameters are correct, you can do a "Restore to default" and then add the new one following that post.
Hope this helps.
I'm having a similar issue as well (except on virgin mobile)
A month ago I flashed squid's version of CM 13 on my phone and everything was fine for a few days, until I completely lost LTE and access to APNs. I reverted to stock and still was unable to get LTE, although I could get a shaky 3g connection if I changed the network mode to CDMA only. I called virgin mobile and they walked me through the troubleshooting steps and eventually determined it was a network outage (even though two desires in my house belonging to other family members had LTE). I called again after they verified that the network was working again and they were still unable to fix the issue.
Recently, a friend upgraded from a desire to a different phone on a different network, and gave me his old phone. I plugged in my sim card and activated this new phone and I got LTE. Figuring everything was good, I decided to flash squid's ROM once again. The same issue happened, I got LTE for a day or two until it cut out service again. No access to APNs, not even any service in stock or on the official build of CM12 with the APN fix (I can't access APNs there either). I'm out of ideas and would appreciate if anyone had any input on my issues.
Techdude154 said:
I'm having a similar issue as well (except on virgin mobile)
A month ago I flashed squid's version of CM 13 on my phone and everything was fine for a few days, until I completely lost LTE and access to APNs. I reverted to stock and still was unable to get LTE, although I could get a shaky 3g connection if I changed the network mode to CDMA only. I called virgin mobile and they walked me through the troubleshooting steps and eventually determined it was a network outage (even though two desires in my house belonging to other family members had LTE). I called again after they verified that the network was working again and they were still unable to fix the issue.
Recently, a friend upgraded from a desire to a different phone on a different network, and gave me his old phone. I plugged in my sim card and activated this new phone and I got LTE. Figuring everything was good, I decided to flash squid's ROM once again. The same issue happened, I got LTE for a day or two until it cut out service again. No access to APNs, not even any service in stock or on the official build of CM12 with the APN fix (I can't access APNs there either). I'm out of ideas and would appreciate if anyone had any input on my issues.
Click to expand...
Click to collapse
I have this same phone a5_chl Virgin Mobile. Did you factory reset your device before flashing back to your stock rom? The other thing is and this is just my opinion not a statement of fact or a knock on the wonderful Bigsupersquid but that 13 CM ROM is nowhere close to being stable enough for me to risk flashing it to my daily driver phone. Just read all the posts and his candid responses. You were basically a beta tester .
I'm not an expert in APN's but if you can't get that fixed your last resort might have to be wiping your system and then flashing or running the executable RUU (rom utility upgrade) file found for our device on HTC/downloads . This is a last resort option and wiping your system will remove your existing firmware so have the correct RUU for your phone downloaded to your computer before attempting a wipe. If it's an exe, which I believe the U.S. Virgin Mobile one is ,you will hook up your phone fully charged in fastboot mode then from your computer run the exe RUU like any other exe executable program and wait. It will reformat all partitions and reinstall pure stock ROM. Hope someone else had an easier fix for your data issues and good luck.
EDIT: you will need your stock recovery flashed back and a relocked bootloader before flashing the RUU but I've read that some have flashed their RUU over a custom recovery with a locked bootloader and it wrote over the custom recovery with the stock recovery. I have never personally tried this just the first way I mentioned and that worked for me.
thoctor said:
I have this same phone a5_chl Virgin Mobile. Did you factory reset your device before flashing back to your stock rom? The other thing is and this is just my opinion not a statement of fact or a knock on the wonderful Supersquid but that 13 CM ROM is nowhere close to being stable enough for me to risk flashing it to my daily driver phone. Just read all the posts and his candid responses. You were basically a beta tester .
I'm not an expert in APN's but if you can't get that fixed your last resort might have to be wiping your system and then flashing or running the executable RUU (rom utility upgrade) file found for our device on HTC/downloads . This is a last resort option and wiping your system will remove your existing firmware so have the correct RUU for your phone downloaded to your computer before attempting a wipe. If it's an exe, which I believe the U.S. Virgin Mobile one is ,you will hook up your phone fully charged in fastboot mode then from your computer run the exe RUU like any other exe executable program and wait. It will reformat all partitions and reinstall pure stock ROM. Hope someone else had an easier fix for your data issues and good luck.
EDIT: you will need your stock recovery flashed back and a relocked bootloader before flashing the RUU but I've read that some have flashed their RUU over a custom recovery with a locked bootloader and it wrote over the custom recovery with the stock recovery. I have never personally tried this just the first way I mentioned and that worked for me.
Click to expand...
Click to collapse
I did try factory resetting and I am on stock after flashing the RUU. It makes no sense as the RUU should have reset everything. That perplexes me the most
Techdude154 said:
I did try factory resetting and I am on stock after flashing the RUU. It makes no sense as the RUU should have reset everything. That perplexes me the most
Click to expand...
Click to collapse
OK then you did get back to stock not from a nandroid backup but from flashing or running exe stock RUU? If that's the case then it replaced everything that might have been changed and your issues shouldn't be related to any APN changes. You also removed and reinserted your sim card as I believe, correct?
EDIT: that perplexes me as well my friend!
Techdude154 said:
I did try factory resetting and I am on stock after flashing the RUU. It makes no sense as the RUU should have reset everything. That perplexes me the most
Click to expand...
Click to collapse
i posted about my lte issues i had for nearly two weeks, running stock just to verify the data service problem wasn't my rom...
i had to install stock recovery, relock bootloader, download the ruu.exe from htc and extract the .img file in Wine, then rename it onto the sdcard and reboot into hboot so it'd flash. neither Wine nor virtualbox xp talk correctly to any of my phones over usb. and i wasn't about to native install Windoze.
factory reset stock didn't fix it, even trying activation, update profile, etc.
i learned i could get 3g data but switching to lte instead of cdma shut down data entirely.
virgin eventually directly escalated me to tier 2 tech support in my last call, they sent a couple service programming pushes to the phone that got my lte back online.
i tried the various service programming menu options repeatedly, with no results but the prl updated once; but the trigger to fix my lte seemed to come from upstream.
i tried various apns, in cm12, cm13, and stock lollipop. rebuilt init_a5.cpp with different mccmnc and adjusted apns. i really tried most tricks in the book plus a few more.
as far as alpha testing goes, at this point I'm just sharing something cool... i always enjoyed flashing latest greatest on my ov way before i was building.
not too many actual logs to really bug report for either rom.
bigsupersquid said:
i posted about my lte issues i had for nearly two weeks, running stock just to verify the data service problem wasn't my rom...
i had to install stock recovery, relock bootloader, download the ruu.exe from htc and extract the .img file in Wine, then rename it onto the sdcard and reboot into hboot so it'd flash. neither Wine nor virtualbox xp talk correctly to any of my phones over usb. and i wasn't about to native install Windoze.
factory reset stock didn't fix it, even trying activation, update profile, etc.
i learned i could get 3g data but switching to lte instead of cdma shut down data entirely.
virgin eventually directly escalated me to tier 2 tech support in my last call, they sent a couple service programming pushes to the phone that got my lte back online.
i tried the various service programming menu options repeatedly, with no results but the prl updated once; but the trigger to fix my lte seemed to come from upstream.
i tried various apns, in cm12, cm13, and stock lollipop. rebuilt init_a5.cpp with different mccmnc and adjusted apns. i really tried most tricks in the book plus a few more.
as far as alpha testing goes, at this point I'm just sharing something cool... i always enjoyed flashing latest greatest on my ov way before i was building.
not too many actual logs to really bug report for either rom.
Click to expand...
Click to collapse
Some of that was over my head but happily not all of it. Basically what your saying is the fix needs to come from the carrier and it's a reset issue on their end not a custom rom issue? By the way I'm a big fan of your work. Hell I might be on one of your older ROMs right now I've flashed so many I forget. Thanks for the education.
thoctor said:
OK then you did get back to stock not from a nandroid backup but from flashing or running exe stock RUU? If that's the case then it replaced everything that might have been changed and your issues shouldn't be related to any APN changes. You also removed and reinserted your sim card as I believe, correct?
EDIT: that perplexes me as well my friend!
Click to expand...
Click to collapse
The first time it happened, I flashed back to stock using the RUU.exe. I tried again but the second time I took out the SIM card before running the program, I still can't get LTE.
bigsupersquid said:
i posted about my lte issues i had for nearly two weeks, running stock just to verify the data service problem wasn't my rom...
i had to install stock recovery, relock bootloader, download the ruu.exe from htc and extract the .img file in Wine, then rename it onto the sdcard and reboot into hboot so it'd flash. neither Wine nor virtualbox xp talk correctly to any of my phones over usb. and i wasn't about to native install Windoze.
factory reset stock didn't fix it, even trying activation, update profile, etc.
i learned i could get 3g data but switching to lte instead of cdma shut down data entirely.
virgin eventually directly escalated me to tier 2 tech support in my last call, they sent a couple service programming pushes to the phone that got my lte back online.
i tried the various service programming menu options repeatedly, with no results but the prl updated once; but the trigger to fix my lte seemed to come from upstream.
i tried various apns, in cm12, cm13, and stock lollipop. rebuilt init_a5.cpp with different mccmnc and adjusted apns. i really tried most tricks in the book plus a few more.
as far as alpha testing goes, at this point I'm just sharing something cool... i always enjoyed flashing latest greatest on my ov way before i was building.
not too many actual logs to really bug report for either rom.
Click to expand...
Click to collapse
It does sound a lot like a carrier/account issue as I managed to kill 2 different 816s. I don't think it's the SIM card itself because I put it into a 3rd phone and got LTE, although since it was someone else's phone, I didn' t bother activating it.
I guess you got lucky with support, I tried talking to them and they tried the same thing with me. Although all I got was excuses saying they're logging a ticket with their "network engineers" and to call back in a few days. This continued on for a few weeks until they determined I needed a new phone, which I was also bounced around for another few weeks (I still don't have it).
I'm just completely lost now. I'm almost certain it's my account and it needs to be reset, but I can't get a tech who can help me. How did you manage to get someone in tier 2?
Techdude154 said:
The first time it happened, I flashed back to stock using the RUU.exe. I tried again but the second time I took out the SIM card before running the program, I still can't get LTE.
This is starting to scare me as well because I'm thinking of going back to stock once Marshmallow gets pushed to our phone to get my beats drivers back and this is making me think twice. Sorry your having so much trouble.
Click to expand...
Click to collapse
thoctor said:
Some of that was over my head but happily not all of it. Basically what your saying is the fix needs to come from the carrier and it's a reset issue on their end not a custom rom issue? By the way I'm a big fan of your work. Hell I might be on one of your older ROMs right now I've flashed so many I forget. Thanks for the education.
Click to expand...
Click to collapse
seemed that way.
i took radio logs before and after it worked, and worked only on 3g, and it looked to me like the sim card responded differently to the ril after things were running right again.
mine might've been a special case, though, it came from ebay with no sim, and virgin had to go to a little effort to get it programmed when i installed the sim initially.
they also claimed for several days that the local Sprint tower was down for lte service.
---------- Post added at 10:37 PM ---------- Previous post was at 10:32 PM ----------
Techdude154 said:
The first time it happened, I flashed back to stock using the RUU.exe. I tried again but the second time I took out the SIM card before running the program, I still can't get LTE.
It does sound a lot like a carrier/account issue as I managed to kill 2 different 816s. I don't think it's the SIM card itself because I put it into a 3rd phone and got LTE, although since it was someone else's phone, I didn' t bother activating it.
I guess you got lucky with support, I tried talking to them and they tried the same thing with me. Although all I got was excuses saying they're logging a ticket with their "network engineers" and to call back in a few days. This continued on for a few weeks until they determined I needed a new phone, which I was also bounced around for another few weeks (I still don't have it).
I'm just completely lost now. I'm almost certain it's my account and it needs to be reset, but I can't get a tech who can help me. How did you manage to get someone in tier 2?
Click to expand...
Click to collapse
tier 2 takes luck, time, many calls, and eventually you learn the answers to all the questions tier 1 outsourced from India asks so you can feed it to them so fast they want to shuffle you along. takes a couple of weeks to over a month to get to tier 2 and sometimes they have to be involved multiple times as well.
I've been dealing with virgin since 2009... replaced only two phones, eventually got the rest of the issues hammered out with persistence.
for a little while, twice, i had direct toll free numbers to American tier two even because my issues were so hard to solve. it didn't take too long for those numbers to be disconnected, though.

Categories

Resources