Related
* Unfortunately, I'm having the same problems with this ROM on HSDPA that I was having on aeroevan's ROM. GSM is found immediately on boot, however, HSDPA is very flakey. It will succeed in connecting every now and again, but then randomly drops the signal and won't reconnect. I thought maybe I just had a weak 3G signal where I was testing, but I have a BB Bold for work as well and that can easily maintain a 3G connection on the same network. I also had no problem way back in the day with CM7.2, but that ship has sailed .
Also, when the phone is in WCDMA preferred mode, after a while the phone will lose all connections (usually after a reboot but not always), including to GSM and when I go to reselect my network operator I get the message "Error while searching for networks". No matter how many times I reboot the phone or switch to "GSM Only" or "GSM/WCDMA auto" it never lets me again select my network provider.
As I said, I ran into the same problems with aero's port, so its not specific to this ROM.
* Situation are me after uproom (http://forum.xda-developers.com/showthread.php?t=1932573), spent two days lost wave, down to the original room (fullwipe finished down about 2.3.4). So lose the 3G network always in global mode (global), 3G users they will never be, but 2G ok (you spend vina sim and have installed APV vina). The physician who has experience helping hand factories. Thank a lot.
I don't known?
I do not understand.Specific guidance for me? please!
nabin229 said:
I do not understand.Specific guidance for me? please!
Click to expand...
Click to collapse
Aeroevan's rom? CM9, CM10? Is your radio outdated? What carrier are you on? More info = more help.
nabin229 said:
Situation are me after uproom (http://forum.xda-developers.com/show....php?t=1932573), spent two days lost wave, down to the original room (fullwipe finished down about 2.3.4). So lose the 3G network always in global mode (global), 3G users they will never be, but 2G ok (you spend vina sim and have installed APV vina). The physician who has experience helping hand factories. Thank a lot.
Click to expand...
Click to collapse
BTW, I don't understand this part.
I would suggest reading through the entire thread of Aeroevan's rom that you were describing as well as the Global CM9 thread. During your reading you may find and answer in there. I have found more answers that way than waiting on someone to direct me there anyway. That is all the advice I can provide with my limited knowledge.
Help me
ThePhantom97 said:
Aeroevan's rom? CM9, CM10? Is your radio outdated? What carrier are you on? More info = more help.
BTW, I don't understand this part.
I would suggest reading through the entire thread of Aeroevan's rom that you were describing as well as the Global CM9 thread. During your reading you may find and answer in there. I have found more answers that way than waiting on someone to direct me there anyway. That is all the advice I can provide with my limited knowledge.
Click to expand...
Click to collapse
I installed your room ( {Rom}{ICS} Official Global CM9), after 2 days my phone is not network. I reinstall the original room 2.3.4 but only use 2G when I used dataroaming; completely unusable 3G & network global mode always (I fullwipe data before reinstalling room 2.3.4 & APN properly installed).I then set your room again, but as I said above condition.Please help me how to be able to use 3G
because my phone is example:
Unfortunately, I'm having the same problems with this ROM on HSDPA that I was having on aeroevan's ROM. GSM is found immediately on boot, however, HSDPA is very flakey. It will succeed in connecting every now and again, but then randomly drops the signal and won't reconnect. I thought maybe I just had a weak 3G signal where I was testing, but I have a BB Bold for work as well and that can easily maintain a 3G connection on the same network. I also had no problem way back in the day with CM7.2, but that ship has sailed .
Also, when the phone is in WCDMA preferred mode, after a while the phone will lose all connections (usually after a reboot but not always), including to GSM and when I go to reselect my network operator I get the message "Error while searching for networks". No matter how many times I reboot the phone or switch to "GSM Only" or "GSM/WCDMA auto" it never lets me again select my network provider.
Ok, I don't know if anyone else is having the same problem as you. I hope I don't offend you but I am going to take a guess and say that english is not your first language as some of that is difficult for me to read and completely understand. From what I am gathering is you can connect to your carriers network but only on a temporary basis. Here are the steps I followed to connect to Verizon's network using {10-25-2012}{Rom}{ICS} Official Global CM9 - After a full wipe and clean install and after initial setup I went to (doing this from memory as I don't have it installed at the moment) Settings --> More --> Mobile Networks --> chose CDMA w/EVDO --> Exit out of settings and rebooted. When the phone booted up it recognized the Verizon network and all service and data was all working, I didn't have to change the APN settings at all. If you are still having trouble staying connected I suggest you check the version of radio you are using and consider updating it. Here is the radio thread: http://forum.xda-developers.com/showthread.php?t=1134451 I don't think I am the best person to assist you but just telling you what I would do if I were in your situation.
3G disconnect, only use 2G (GSM). Help me!
ThePhantom97 said:
Ok, I don't know if anyone else is having the same problem as you. I hope I don't offend you but I am going to take a guess and say that english is not your first language as some of that is difficult for me to read and completely understand. From what I am gathering is you can connect to your carriers network but only on a temporary basis. Here are the steps I followed to connect to Verizon's network using {10-25-2012}{Rom}{ICS} Official Global CM9 - After a full wipe and clean install and after initial setup I went to (doing this from memory as I don't have it installed at the moment) Settings --> More --> Mobile Networks --> chose CDMA w/EVDO --> Exit out of settings and rebooted. When the phone booted up it recognized the Verizon network and all service and data was all working, I didn't have to change the APN settings at all. If you are still having trouble staying connected I suggest you check the version of radio you are using and consider updating it. Here is the radio thread: http://forum.xda-developers.com/showthread.php?t=1134451 I don't think I am the best person to assist you but just telling you what I would do if I were in your situation.
Click to expand...
Click to collapse
my phone 3G is disconnect, only use 2G (GSM) , rom 2.3.4 Verizon, radio 1.09.01.0312. *I'm from Vietnam, I speak English not good, sorry.
nabin229 said:
my phone 3G is disconnect, only use 2G (GSM) , rom 2.3.4 Verizon, radio 1.09.01.0312. *I'm from Vietnam, I speak English not good, sorry.
Click to expand...
Click to collapse
No need to apologize m8. Hopefully someone more advanced than myself can assist you with your issue. I am sorry that I couldn't be of more assistance.
Trouble with wifi/3G
ThePhantom97 said:
Ok, I don't know if anyone else is having the same problem as you. I hope I don't offend you but I am going to take a guess and say that english is not your first language as some of that is difficult for me to read and completely understand. From what I am gathering is you can connect to your carriers network but only on a temporary basis. Here are the steps I followed to connect to Verizon's network using {10-25-2012}{Rom}{ICS} Official Global CM9 - After a full wipe and clean install and after initial setup I went to (doing this from memory as I don't have it installed at the moment) Settings --> More --> Mobile Networks --> chose CDMA w/EVDO --> Exit out of settings and rebooted. When the phone booted up it recognized the Verizon network and all service and data was all working, I didn't have to change the APN settings at all. If you are still having trouble staying connected I suggest you check the version of radio you are using and consider updating it. Here is the radio thread: http://forum.xda-developers.com/showthread.php?t=1134451 I don't think I am the best person to assist you but just telling you what I would do if I were in your situation.
Click to expand...
Click to collapse
I have been having the same problem. Flashed CM10 after full wipe, mobile network (for verizon) is CDMA w/EVDO, tried rebooting and switching and wiping and re-flashing but I have no wifi and bad 3G. When I revert to stock everything is fine. How can I fine the latest radio for CM10, I didn't see any JB in the thread link.
SS823 said:
I have been having the same problem. Flashed CM10 after full wipe, mobile network (for verizon) is CDMA w/EVDO, tried rebooting and switching and wiping and re-flashing but I have no wifi and bad 3G. When I revert to stock everything is fine. How can I fine the latest radio for CM10, I didn't see any JB in the thread link.
Click to expand...
Click to collapse
The latest is the ICS radio .320 it will work on JB roms as well.
Have you guys flashed the new ics firmware?
I'm so fresh you can suck my nits...
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.
Hello to everyone! I have Samsung Ace 2x (GT-S7560M) with Public Mobile, Canada. After the phone become incredibly lagging, I have decided to flash it with custom ROM, which I successfully did following instructions on this forum (http://forum.xda-developers.com/show...7#post50909757). I like my phone back again, the ROM is amazing.
BUT there are two huge issues - it is not connecting to Mobile Network and Bluetooth can not be enabled. (WiFi connects and working fine).
As I mentioned earlier I am with Public Mobile and able to make calls and recieve/send SMS messages with CM11. After every reboot there is message : "SIM card added. Restart your device to access the mobile network." , which can be easily bypassed by pressing right bottom button (not sure about the name, probably "Escape"). The phone indicates TELUS Network.
I read over the posts on this forum and tried to change settings in Prefered Network to GSM/CDMA auto(PRL). Also checked APN to Public Mobile (tried Telus as well) but no success in getting back 4g network.
Any suggestion? Really do not want to go back to official ROM
novice70 said:
Hello to everyone! I have Samsung Ace 2x (GT-S7560M) with Public Mobile, Canada. After the phone become incredibly lagging, I have decided to flash it with custom ROM, which I successfully did following instructions on this forum (http://forum.xda-developers.com/show...7#post50909757). I like my phone back again, the ROM is amazing.
BUT there are two huge issues - it is not connecting to Mobile Network and Bluetooth can not be enabled. (WiFi connects and working fine).
As I mentioned earlier I am with Public Mobile and able to make calls and recieve/send SMS messages with CM11. After every reboot there is message : "SIM card added. Restart your device to access the mobile network." , which can be easily bypassed by pressing right bottom button (not sure about the name, probably "Escape"). The phone indicates TELUS Network.
I read over the posts on this forum and tried to change settings in Prefered Network to GSM/CDMA auto(PRL). Also checked APN to Public Mobile (tried Telus as well) but no success in getting back 4g network.
Any suggestion? Really do not want to go back to official ROM
Click to expand...
Click to collapse
Unfortunately your issue with Bluetooth is super common with this phone and roms. In fact, as far as I'm aware there's not a single kitkat rom that doesn't disable Bluetooth. You might find a solution buried in one of the other threads pertaining to this phone, but I'm almost positive there's not a solution.
Just about every rom I've flashed for this phone gives me the sim card added message when I start it up, ignoring it is the best fix I've come across. Regarding your inability to connect to a network, it seems you've already tried everything I would have suggested. Which cm11 build did you flash, by the way?
If you can't get that sorted out you aren't stuck with going back to stock. There's also another cm11 build for the IIx/ Trend, as well as Omni 4.4.4, PAC 4.4.4, Beanatalk 4.4.3 and ALLEGEDLY SlimKat (I can't find the download link to save my life, but a few people have said someone ported slimrom to this phone).
Sorry I couldnt be of more help bru.
about my ROM
thank you for response, I am currently using CM11-20141114-UNOFFICIAL-kylessopen (240DPI) with gapps - kk -20140629-signed.
Hmm, the first time I flashed that same build I had quite a few issues and they rectified themselves when I flashed a different gapps. I think it was the January 2014 4.4.4 full package (when I've got some free time in an hour or so I'll let you know the exact one), which I found odd considering it was super out of date and yet cured what ailed me. Next time I flashed it the 20140629 package worked fine though, so who knows. You've tried redownloading that gapps package right? Sometimes an ever so slightly corrupted gapps zip can do this kind of stuff. Unfortunately I'm not super familiar with the ins and outs of this phone since its just to tide me over until I can afford to replace my Note 4 in earnest, so my ability to help here is mostly guesswork and drawing parallells. I hope you get this on the ropes dude. If you can't get it sussed out in the end I'd recommend going with Beanstalk. It doesn't have a working theme engine unfortunately and is ever so slightly more buggy (well, less buggy I. Your case I guess), but it's waaaaaaay more feature rich than either of the cm11 builds. If you value stability more than customization than Omnirom is your best bet. ALL of the roms for this phone are kinda glitchy, but I found Omnirom to be the least so.
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 .
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.