Develop Bugs

[Q] help!! cant get 3g to work after insalling new roms

Now i know theres hundreds of threads about 3G problems and im hoping this one doesnt get over looked . I recently in stalled two custom roms on my evo ( cyanogen 7.0.0 , and miui 1.1.25 ) wiped chaches factory resets etc. on first installations but for some reason my 3G is not being recognized or even showing up when i am using the custom roms. The only way i can use 3G is when i restore my phone back to my stock rom..... can anyone help me fixing the issue ....please. if i can get my 3G up and working while im running my custom roms it will make everything so much easier, instead of having to restore my stock rom when ever i want to do anything on my phone outside a wireless network
oh and kernals etc. are stocks that came with the roms.no customization has been done to the roms themselves.

has nothing to do with the kernels
you have to get msl reader and set your 3g up i think there is a thread in the developer section on it...let me see if i can find it
OK HERE IS THE FIX,
PHONE MUST BE ROOTED
PHONE MUST HAVE SENSE ROM ON IT TO FIX THE PROBLEM
download msl reader from market,
open msl reader,
write down msl code
open dialer
dial ##3282#
when asked for code or password enter the msl code you wrote down
select edit mode
select EVDO
select preferred mode,
set to automatic.
save exit reboot,
load rom of choice
and VIOLA YOU HAVE 3G
CHEERS AND GOOD LUCK

Well for CM7, are you sure you data is enabled? Sometimes tis off when you boot the rom. You can check in mobile data under wifi settings.

while that is true roxxors, since the OP stated two different roms giving him trouble and not having trouble with original load, the problem lies in how the roms read 3g...we all know that sprint roms LIE about 3g...and cyanogen actually reads actual signal...however until that EVDO change is done his phone will never get 3g on any of the cyanogen or miui or even aosp roms....

is the White different then the Black?

I have a black Epic 4G Touch rooted and running EuroSkank just fine. I actually haven't experienced any issues besides video camera with effects causes FC. But I have a friend who has the white Epic 4G Touch and we rooted it, got a custom recovery and all went smooth. The second we put on the ROM on his phone he now is unable to make/Receive Calls and send/receive text/mms messages. Is there a color specific ROM? I tried flashing all sorts of ROMs to the device to fix it, but to no avail can I get it to work.

i have a white one and it works well with all kinds of custom roms. i believe they are the same.

feyerbrand said:
I have a black Epic 4G Touch rooted and running EuroSkank just fine. I actually haven't experienced any issues besides video camera with effects causes FC. But I have a friend who has the white Epic 4G Touch and we rooted it, got a custom recovery and all went smooth. The second we put on the ROM on his phone he now is unable to make/Receive Calls and send/receive text/mms messages. Is there a color specific ROM? I tried flashing all sorts of ROMs to the device to fix it, but to no avail can I get it to work.
Click to expand...
Click to collapse
White and black are essentiall the same phone.
Sounds like a network issue.
You could try a complete Stock+Root with an OTA build from sfhub http://forum.xda-developers.com/showthread.php?t=1721229 .
This should set everything right.
OR
You could try reseting the network settings. You'll need your MSL and a stock dialer.
Hands Free Activation/Network Reset:
Open dialer then ##72786# (factory reset on network settings)
Enter your MSL and hit OK
On the SCRTN screen select yes
Phone will auto reboot and take you to Hands Free Activation
If you have an SD card, media scanner will do its thing first.
Re-activation will initiate, let it run (DO NOT TOUCH THE SCREEN, no need to Press OK it will continue on its own)
Phone will then update Profile, then PRL, (you can select cancel when it searches for Firmware update if you want)
Phone will reboot again.
To get you MSL (if you're rooted)
1. Download "Terminal Emulator" from the app market.
2. Open Terminal Emulator.
3. type in getprop ril.MSL (make sure the .MSL is capitalized)
4. Press enter and poof, you have your MSL
Good luck

alright I found the problem. It wasn't the ROM at all, it wasn't the RIL, it wasn't anything to do with the custom ROM. It was actually his line that was having problems with the switch. We got it all figured out and the phone works great now. Thank you for your responses on getting it back up and working. We put a test line on the phone and it called just fine, so we found the issue was actually on his number. Phone fixed, and we are rocking the custom Jelly Bean again. Thank you everyone!

feyerbrand said:
alright I found the problem. It wasn't the ROM at all, it wasn't the RIL, it wasn't anything to do with the custom ROM. It was actually his line that was having problems with the switch. We got it all figured out and the phone works great now. Thank you for your responses on getting it back up and working. We put a test line on the phone and it called just fine, so we found the issue was actually on his number. Phone fixed, and we are rocking the custom Jelly Bean again. Thank you everyone!
Click to expand...
Click to collapse
Thanks for posting back the resolution. It always helps the community when we know what happened.

[Q] Can't Get 4G Working on Any ROM/Radio except stock EC05

Hey everyone,
So I've been flashing ROMs on my Epic for about 2 years now, and I'm very VERY used to troubleshooting issues and solving them by either browsing the forums or doing it myself. However, I CANNOT get 4G to work on this phone except for stock EC05. I am currently running 4.3 with the latest gapps on the new Carbon Unofficial epicmtd ROM, with deodexed FC09 radio. I get **** service and can't connect to 4G. This happens consistently with all the ROM's I've used as well as the radios for anything past CM7. Does anyone know what I can do to remedy this situation? I would really like to not have to flash it over to another carrier due to sprint being horrible service providers.
tl;dr how do I get 4G working on FC09

Dr_Lapdog said:
Hey everyone,
So I've been flashing ROMs on my Epic for about 2 years now, and I'm very VERY used to troubleshooting issues and solving them by either browsing the forums or doing it myself. However, I CANNOT get 4G to work on this phone except for stock EC05. I am currently running 4.3 with the latest gapps on the new Carbon Unofficial epicmtd ROM, with deodexed FC09 radio. I get **** service and can't connect to 4G. This happens consistently with all the ROM's I've used as well as the radios for anything past CM7. Does anyone know what I can do to remedy this situation? I would really like to not have to flash it over to another carrier due to sprint being horrible service providers.
tl;dr how do I get 4G working on FC09
Click to expand...
Click to collapse
I offer this suggestion with much caution....
Ever consider using EFS Clear within Odin? You'll have to setup your phone again, but it could help.
WARNING: This will completely delete your phone identification and you won't be able to reconnect to Sprint's network until you set it up manually again. Write down all your pertinent information, such as MEID #, phone number, etc..
From stock FC09, I recall having to do the following to enter the information:
Enter in the dialpad: ##785468#
Press Edit
Touch the number area to input your phone number.
Input your phone like: 5551112222 (Where you have area code and then phone with no dashes, spaces or parenthesis)
Hit return
Input your phone number like before in the next field
Hit return
Hit done
Manually update your profile in Settings > About Phone > Status
You can always just call up customer care and ask them the steps on how to reconnect your phone to the network. I just said a little cousin starting hitting buttons and when I grabbed the phone it refused to allow calls, text and data.

nikon120 said:
I offer this suggestion with much caution....
Ever consider using EFS Clear within Odin? You'll have to setup your phone again, but it could help.
WARNING: This will completely delete your phone identification and you won't be able to reconnect to Sprint's network until you set it up manually again. Write down all your pertinent information, such as MEID #, phone number, etc..
From stock FC09, I recall having to do the following to enter the information:
Enter in the dialpad: ##785468#
Press Edit
Touch the number area to input your phone number.
Input your phone like: 5551112222 (Where you have area code and then phone with no dashes, spaces or parenthesis)
Hit return
Input your phone number like before in the next field
Hit return
Hit done
Manually update your profile in Settings > About Phone > Status
You can always just call up customer care and ask them the steps on how to reconnect your phone to the network. I just said a little cousin starting hitting buttons and when I grabbed the phone it refused to allow calls, text and data.
Click to expand...
Click to collapse
Nevermind, I understand now. How much success have you had with this process? And do I just need the phone's status splash screen information or am I manually entering EVERYTHING?

[Q] CM11.0, 20140608, M7 Snapshot - Unable to get signal from radio

I started to experiment with different custom ROMs available for the d2att (now, apparently called the d2lte). My phone is using TeamWin 2.6.3.1 for recovery, I have been using it for everything. So far I have only been familiar with two certain ROMs: Cyanogenmod and CarbonROM. I have not flashed anything except for the recovery.
I complete the installation of my new ROM by first wiping cache, dalvik, data and system. My ROMs are stored on an external SD.
CarbonROM was the first one to be installed, but I found it quite buggy and unstable. I have since been using different snapshots of CM to test functionality and stability...since I plan to hang up my LG G2 and start using my SGS3 w/7200mAh battery as my daily phone. So it needs to be very reliable. I also enjoy picking with settings so the more settings the better.
So, question number #1:
When I install CM the normal way, add my APN, and select the proper mobile network mode, how come I cannot get a signal, no matter what I try? I have searched around many forums for the answer to this...many have nothing to do with my problem or are using different phones. I can confirm my SIM card works, as it was used in my LG G2. Carrier is Virgin Mobile Canada. Network mode is GSM/WCDMA Auto. It does not work with any other modes including Global.
Q #2:
If I plan on using custom KK (4.4.2) ROMs, is there anything extra I need to flash to the phone in order for the cell radio to work successfully? When I researched this, I found lots of people talking about flashing a custom bootloader, but I could not find an exact answer to my question. I would rather not brick my phone by attempting this blindly.
Q #3:
Since I am looking for a reliable custom ROM, is CM the best developer to choose? Is there a more reliable ROM out there?
Mike
EDIT: I did more reaseach on bootloaders and modem firmware and found that my bootloader is already at the most recent version. I did find however that my modem firmware was out of date, so I updated from UEMK5 to UEND3. This however did not solve my problem as I still have no service...
I am contemplating now about starting from scratch and wiping my internal storage... will this help or is it unnecessary?

For question # 1, do you have a proper imei after installing CM11? You can check it in the dialer by typing in *#06#.
For question #2, the modem must be compatible with the bootloader. Custom ROMs will only install if the phone has a compatible bootloader.
For question #2, I prefer Validus which is an AOSP-based ROM.

audit13 said:
For question # 1, do you have a proper imei after installing CM11? You can check it in the dialer by typing in *#06#.
For question #2, the modem must be compatible with the bootloader. Custom ROMs will only install if the phone has a compatible bootloader.
For question #2, I prefer Validus which is an AOSP-based ROM.
Click to expand...
Click to collapse
I have an IMEI number. That is what has me kind of confused...everything is there to show signal, it's just that it will not pick up a tower. When I throw a SIM card in it recognizes it. One thing to also mention is it pins the signal at 0, -1, or 258692378... or another outrageous number.

First things first have you followed the method of going back to a stock TW ROM, obtaining a GPS lock, and then flashed your Custom KitKat rom?
Sent from Mission Control

UnknownTroll1 said:
First things first have you followed the method of going back to a stock TW ROM, obtaining a GPS lock, and then flashed your Custom KitKat rom?
Sent from Mission Control
Click to expand...
Click to collapse
I am now on stock 4.3 firmware. I have obtained a GPS lock.
No service at all.
But... I had a funny feeling, so I went into stock android recovery and wiped cache...and voila, service!
Only problem is, I'm losing it almost constantly. The only way to fix it is by wiping the cache, but I can't keep doing that whenever I lose service.
Will I be okay to flash the custom recovery and custom ROM at this point?

Do you have the latest modem installed?

mpelley92 said:
I am now on stock 4.3 firmware. I have obtained a GPS lock.
No service at all.
But... I had a funny feeling, so I went into stock android recovery and wiped cache...and voila, service!
Only problem is, I'm losing it almost constantly. The only way to fix it is by wiping the cache, but I can't keep doing that whenever I lose service.
Will I be okay to flash the custom recovery and custom ROM at this point?
Click to expand...
Click to collapse
If you are still on the Stock TW ROM here is a method to try. It will clear most of your mobile data problems.
1. Enter the Samsung service mode by typing this code into the dial pad *#197328640#
2. Then go to Mainmenu>UMTS>Common>NV REBUILD>NV REBUILD> (Important: don't exit the menu yet!)
3. Wait 30+ sec
4. Long press power button and select "Restart / Reboot"
5. Now check your GPS from any software that may use GPS like "Maps" or "GPS Status"
Credit: S3Rx ROM Development Thread.
EDIT: Afterwards you should be good to go on your custom ROM. This issue seems to have arisen when a d2lte build broke most people's LTE/Mobile data.
Sent from Mission Control

UnknownTroll1 said:
If you are still on the Stock TW ROM here is a method to try. It will clear most of your mobile data problems.
1. Enter the Samsung service mode by typing this code into the dial pad *#197328640#
2. Then go to Mainmenu>UMTS>Common>NV REBUILD>NV REBUILD> (Important: don't exit the menu yet!)
3. Wait 30+ sec
4. Long press power button and select "Restart / Reboot"
5. Now check your GPS from any software that may use GPS like "Maps" or "GPS Status"
Credit: S3Rx ROM Development Thread.
EDIT: Afterwards you should be good to go on your custom ROM. This issue seems to have arisen when a d2lte build broke most people's LTE/Mobile data.
Sent from Mission Control
Click to expand...
Click to collapse
I am still unable to get service. This time it is pinned at -113. I am although, registered on a network. Not able to make calls or text.

mpelley92 said:
I am still unable to get service. This time it is pinned at -113. I am although, registered on a network. Not able to make calls or text.
Click to expand...
Click to collapse
Yea at this point I am stumped. I guess its a hardware issue. But before calling quits what is your baseband and boot loader?
Sent from Mission Control

UnknownTroll1 said:
Yea at this point I am stumped. I guess its a hardware issue. But before calling quits what is your baseband and boot loader?
Sent from Mission Control
Click to expand...
Click to collapse
Bootloader and baseband: I747MVLUEMK5

mpelley92 said:
Bootloader and baseband: I747MVLUEMK5
Click to expand...
Click to collapse
You're running the most recent release so I'm not sure what's causing the issue.

audit13 said:
You're running the most recent release so I'm not sure what's causing the issue.
Click to expand...
Click to collapse
I have found the problem with the service. I live in an area where signal is not too great. My LG G2 has a tendency to pick up the correct tower for my area, but my Galaxy S3 does not choose the same tower... It looks for one in a completely different direction.
Forgive me, this thread is going to take a bit of a turn.
Is there any way to choose which cell tower the phone connects to? In my area there is one directly east and the other is directly west. I need the western tower in order to make/receive calls/text and in order to get any data reception. Right now where my phone sits, it does not connect to the western tower so I cannot use it. I used OpenSignal to observe which tower both phones connect to.
The other issue I found is my extended battery (Anker 7200) also interferes with reception quite a bit. In town, it's not noticeable. But out on my acreage it stops my phone from getting any signal. I compared it to my LG G2 and my Galaxy S3 with the old 2100mAh battery. The G2 hovers around -95, S3 w/OEM battery at -101 and the S3 w/Anker battery at -113 (no service).
Mike

mpelley92 said:
Is there any way to choose which cell tower the phone connects to? In my area there is one directly east and the other is directly west. I need the western tower in order to make/receive calls/text and in order to get any data reception. Right now where my phone sits, it does not connect to the western tower so I cannot use it. I used OpenSignal to observe which tower both phones connect to.
Mike
Click to expand...
Click to collapse
Try changing the mode to LTE only under your settings. This may force the stronger connection.

x0ne215 said:
Try changing the mode to LTE only under your settings. This may force the stronger connection.
Click to expand...
Click to collapse
Unfortunately that won't work either. In my area I can only pick up HSPA....

mpelley92 said:
Unfortunately that won't work either. In my area I can only pick up HSPA....
Click to expand...
Click to collapse
Hmm. Out of curiosity, have you tried a different ROM on 4.4.2? I've had weird issues with ROMs and signal, ie MIUI caused me to have my signal cut in and out at random intervals. Worth a shot at least. I've been using SlimKat if you want one for reference (probably the quickest download due to size).
Unfortunately all I can suggest is trying to play with tasker and seeing if you can get it to skip over the crap tower, but to my knowledge there's no way to prevent connection to said tower.
I guess if you wanna get into a gray area you could modify said tower....but I claim no responsibility for your actions with that

x0ne215 said:
Hmm. Out of curiosity, have you tried a different ROM on 4.4.2? I've had weird issues with ROMs and signal, ie MIUI caused me to have my signal cut in and out at random intervals. Worth a shot at least. I've been using SlimKat if you want one for reference (probably the quickest download due to size).
Unfortunately all I can suggest is trying to play with tasker and seeing if you can get it to skip over the crap tower, but to my knowledge there's no way to prevent connection to said tower.
I guess if you wanna get into a gray area you could modify said tower....but I claim no responsibility for your actions with that
Click to expand...
Click to collapse
I've been using Liquidsmooth the past few nights and am losing signal more than ever.
Would the OS control how the modem is used? I would think that it's hardware only that changes how and when you get service.
I'm going to try the UEND3 modem firmware and see if that makes a difference. Also going to try SlimKat like you suggested.

[Q] Unable to Receive Phone Calls

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 .