I apologize if this topic has been covered already, however I am not thoroughly acquainted with smartphones and most of the terminology associated with this topic I do not fully understand yet and am therefore unable to extract the information I need from existing forums. I have a Verizon Rezound that I want to use on the GCI prepaid network. I have followed the instructions in a Youtube video by click4geek called Use any Carrier with HTC Rezound (sorry new user, can't post links) and have also unlocked the bootloader via the HTC website. I now can use the phone over the GCI network for calls and text messaging. I have a twofold question: first, what do I do next--root the phone with a ROM (I read this is the best option for phone functionality and the overheating problem)??? If I do this which ROM would most fit my needs (basic user, just need phone calls, sms/mms messaging, and data)? And second, I have set two APN's via GCI protocol (one for data and one for MMS), the problem is I can access data yet I cannot send picture messages. Any thoughts? Thank you for your help!!!!
mdugger said:
I apologize if this topic has been covered already, however I am not thoroughly acquainted with smartphones and most of the terminology associated with this topic I do not fully understand yet and am therefore unable to extract the information I need from existing forums. I have a Verizon Rezound that I want to use on the GCI prepaid network. I have followed the instructions in a Youtube video by click4geek called Use any Carrier with HTC Rezound (sorry new user, can't post links) and have also unlocked the bootloader via the HTC website. I now can use the phone over the GCI network for calls and text messaging. I have a twofold question: first, what do I do next--root the phone with a ROM (I read this is the best option for phone functionality and the overheating problem)??? If I do this which ROM would most fit my needs (basic user, just need phone calls, sms/mms messaging, and data)? And second, I have set two APN's via GCI protocol (one for data and one for MMS), the problem is I can access data yet I cannot send picture messages. Any thoughts? Thank you for your help!!!!
Click to expand...
Click to collapse
I can put some input on the ROM, and somewhat possibly on the APN.
First from what you've said, the over heating problem. That's just a known fact with the rezzy.. look on the bright side, you have a great hand warmer for winter! But, Plain-Andy, CM, or Liquid Smooth would probably suit your needs the best of hand. Do you have a custom recovery yet? You haven't gone S-OFF yet have you? So if you do flash a custom ROM, you will have to extract and flash the boot.img manually from the zip, unless otherwise stated in the OP of ROM.
APN, I don't know very much about.. But I know the rezound got global capabilities with the 4.0.3 ICS update, therefore, if you flash any ROM with the latest update, you should be able to apply them again, but I'm not sure if they would work...
Sent from my HTC One M8 Running Paranoid Android. S-OFF.
pball52998 said:
I can put some input on the ROM, and somewhat possibly on the APN.
First from what you've said, the over heating problem. That's just a known fact with the rezzy.. look on the bright side, you have a great hand warmer for winter! But, Plain-Andy, CM, or Liquid Smooth would probably suit your needs the best of hand. Do you have a custom recovery yet? You haven't gone S-OFF yet have you? So if you do flash a custom ROM, you will have to extract and flash the boot.img manually from the zip, unless otherwise stated in the OP of ROM.
APN, I don't know very much about.. But I know the rezound got global capabilities with the 4.0.3 ICS update, therefore, if you flash any ROM with the latest update, you should be able to apply them again, but I'm not sure if they would work...
Sent from my HTC One M8 Running Paranoid Android. S-OFF.
Click to expand...
Click to collapse
You're correct, I do not have a custom recovery or S-OFF. How would I go about doing those, and are they both necessary?
Thank you very much for your assistance!!!!
mdugger said:
You're correct, I do not have a custom recovery or S-OFF. How would I go about doing those, and are they both necessary?
Thank you very much for your assistance!!!!
Click to expand...
Click to collapse
A custom recovery is needed to flash any ROM. Or just let alone any rooting/modding. If you have the boot loader unlocked, you should just be able to flash a recovery via fastboot using
fastboot flash recovery (name_of_recovery).img
S-OFF (turns off all security flags) can be achieved via rumrunner. http://rumrunner.us although. Its suggested by a couple of devs, mostly Snuzzo to have a minimum 3 or 4 flashes from fastboot. That's also known for boot images (kernels) and recoveries.
From a custom ROM with S-ON you have to flash the kernel from fastboot. Once you flash the zip in recovery, you have to extract the zip on your computer, but the boot.img needs to go into your fastboot folder. Then flash, similar to flashing the recovery but
fastboot flash boot (name of kernel).img
As for the APN thing though.. All I can say about that is, most AOSP ROMS support different services such as GSM and other companies. It'd probably be specific to the ROM that was flashed. Be helpful to possibly flash and ask OP.
Sent from my HTC One M8 Running Paranoid Android. S-OFF.
pball52998 said:
A custom recovery is needed to flash any ROM. Or just let alone any rooting/modding. If you have the boot loader unlocked, you should just be able to flash a recovery via fastboot using
fastboot flash recovery (name_of_recovery).img
S-OFF (turns off all security flags) can be achieved via rumrunner. although. Its suggested by a couple of devs, mostly Snuzzo to have a minimum 3 or 4 flashes from fastboot. That's also known for boot images (kernels) and recoveries.
From a custom ROM with S-ON you have to flash the kernel from fastboot. Once you flash the zip in recovery, you have to extract the zip on your computer, but the boot.img needs to go into your fastboot folder. Then flash, similar to flashing the recovery but
fastboot flash boot (name of kernel).img
As for the APN thing though.. All I can say about that is, most AOSP ROMS support different services such as GSM and other companies. It'd probably be specific to the ROM that was flashed. Be helpful to possibly flash and ask OP.
Sent from my HTC One M8 Running Paranoid Android. S-OFF.
Click to expand...
Click to collapse
thank you for your help. I definitely need more though *sigh*. I followed the directions for "How to Root the HTC Rezound" on the unlockr website. It included flashing an Amon Ra Rezound recovery and installed a Superuser App on my phone. After I followed this guy's directions, I looked at the comments below the process and apparently Superuser and su apps don't work simultaneously on the Rezound and its apparently not rooted, according to the comments anyway. I think in order to flash a custom ROM I will need a "dummies" guide with all steps laid out for me (with S-on). Is there any such guide? Please excuse my naivety. I know it is very taxing explaining everything at an elementary level.
mdugger said:
thank you for your help. I definitely need more though *sigh*. I followed the directions for "How to Root the HTC Rezound" on the unlockr website. It included flashing an Amon Ra Rezound recovery and installed a Superuser App on my phone. After I followed this guy's directions, I looked at the comments below the process and apparently Superuser and su apps don't work simultaneously on the Rezound and its apparently not rooted, according to the comments anyway. I think in order to flash a custom ROM I will need a "dummies" guide with all steps laid out for me (with S-on). Is there any such guide? Please excuse my naivety. I know it is very taxing explaining everything at an elementary level.
Click to expand...
Click to collapse
I wrote a giant 30 step guide once.... Let me see if I can find it. But one, you don't want amon ra recovery... That's for ICS. Newer ROMs need TWRP at least 2.6.X.X but preferred 2.7 or above
Edit: Aha! Found it! This has every single step, step by step. http://forum.xda-developers.com/showthread.php?p=51742399
Start at step 11,12 or 13. Can't really say lol. Or, read the whole post. That's about as clear as it gets. Literally lol
Feel free to ask if there is a misunderstanding.
Sent from my HTC One M8 Running Paranoid Android. S-OFF.
pball52998 said:
I wrote a giant 30 step guide once.... Let me see if I can find it. But one, you don't want amon ra recovery... That's for ICS. Newer ROMs need TWRP at least 2.6.X.X but preferred 2.7 or above
Edit: Aha! Found it! This has every single step, step by step. http://forum.xda-developers.com/showthread.php?p=51742399
Start at step 11,12 or 13. Can't really say lol. Or, read the whole post. That's about as clear as it gets. Literally lol
Feel free to ask if there is a misunderstanding.
Sent from my HTC One M8 Running Paranoid Android. S-OFF.
Click to expand...
Click to collapse
Awesome!!! Thank you for your help!!! I'll let you know how it goes--if you hear a primal scream it may be me!!
Ok so I flashed both the CM and LiquidSmooth ROMS with success, but had no service with CM and had some service with LS, but couldn't send sms messages or get data. What did I do wrong?
pball52998 said:
I wrote a giant 30 step guide once.... Let me see if I can find it. But one, you don't want amon ra recovery... That's for ICS. Newer ROMs need TWRP at least 2.6.X.X but preferred 2.7 or above
Edit: Aha! Found it! This has every single step, step by step. http://forum.xda-developers.com/showthread.php?p=51742399
Start at step 11,12 or 13. Can't really say lol. Or, read the whole post. That's about as clear as it gets. Literally lol
Feel free to ask if there is a misunderstanding.
Sent from my HTC One M8 Running Paranoid Android. S-OFF.
Click to expand...
Click to collapse
What hboot and radios are you using?
There are often a few steps to go through when using GSM on the Rezound... and they vary based on using stock ROM or third-party ROM. On stock ROMs you have to use a third party messaging app (Hangouts, Textra, Handcent, etc) to get MMS to work since the embedded messaging app is hard coded to Verizon MMS servers. In third party ROMs you sometimes have to do that, but often have to flash a GSM enabler to get data to work properly. Remember that the Rezound isn't tuned very well to GSM, especially if it is used on US carriers, so often Edge, and occasionally basic 3G/HSPA, service is the best you can get with great signal.
Your APNs could be an issue as well, remember you can only have one active, but it is based on APN type field... if you need a seperate MMS APN than used for data/internet, your default selected APN must not contain the MMS APN Type, it would be in a stand-alone one, and the MMS APN must not contain the default or internet APN types, and your MMS APN should be the only one with the MMS APN type.
acejavelin said:
What hboot and radios are you using?
There are often a few steps to go through when using GSM on the Rezound... and they vary based on using stock ROM or third-party ROM. On stock ROMs you have to use a third party messaging app (Hangouts, Textra, Handcent, etc) to get MMS to work since the embedded messaging app is hard coded to Verizon MMS servers. In third party ROMs you sometimes have to do that, but often have to flash a GSM enabler to get data to work properly. Remember that the Rezound isn't tuned very well to GSM, especially if it is used on US carriers, so often Edge, and occasionally basic 3G/HSPA, service is the best you can get with great signal.
Your APNs could be an issue as well, remember you can only have one active, but it is based on APN type field... if you need a seperate MMS APN than used for data/internet, your default selected APN must not contain the MMS APN Type, it would be in a stand-alone one, and the MMS APN must not contain the default or internet APN types, and your MMS APN should be the only one with the MMS APN type.
Click to expand...
Click to collapse
How do I tell what radios and hboot I'm using?
I flashed a GSM patch I found on the LiquidSmooth ROM page but must have done it wrong because after I flashed it it lit up the backlight in the phone when it rebooted and just had a black screen for a long time. I Tried to just recover through TWRP but the phone continually got stuck on the 4G page on the reboot. So did I do the custom recovery wrong? I'm thinking I'm stuck flashing a custom ROM now and can't restore my phone. What is my best course of action? I love the custom ROMS but if I cannot even get service then that defeats the point of having the phone.
I do have to have 2 APN's, and the default (data) does not contain MMS APN in the Type field, it says default. And the MMS APN Type is "MMS".
Thank you!!!!
mdugger said:
How do I tell what radios and hboot I'm using?
I flashed a GSM patch I found on the LiquidSmooth ROM page but must have done it wrong because after I flashed it it lit up the backlight in the phone when it rebooted and just had a black screen for a long time. I Tried to just recover through TWRP but the phone continually got stuck on the 4G page on the reboot. So did I do the custom recovery wrong? I'm thinking I'm stuck flashing a custom ROM now and can't restore my phone. What is my best course of action? I love the custom ROMS but if I cannot even get service then that defeats the point of having the phone.
I do have to have 2 APN's, and the default (data) does not contain MMS APN in the Type field, it says default. And the MMS APN Type is "MMS".
Thank you!!!!
Click to expand...
Click to collapse
Remove battery and reinsert, power up holding VOL DN + POWER... that screen is the Hboot screen, at the top is listed Hboot version, radios, and other pertinent data.
I haven't messed with ROMs in some time on the Rezound, I don't even own one anymore... but the Rez is picky, some ROMs work well on some handsets, and others do not... I am surprised that the GSM patch would bootloop LS, there isn't really much you can do wrong if you are using the current TWRP, just flash and wipe cache and dalvik, reboot and wait. What recovery and version are you using (start it and it should show at the top of the screen). You could also try one of @sun_dream ROM's, his are pretty much exclusive to GSM users. What carrier and frequencies are we talking about here would be good info as well...
2 APNs are fine, although all APN types should be lower case, not sure if that would cause an issue or you just listed it that way in your message... Linux/Android is case sensitive for most things, Camera is different than camera.
I will say again that Rezound is a finicky GSM phone, things have to be just right... some people can get it to work with marginal success, but only a select few people can get it working "great", and with other devices being relatively cheap like the Doogee Voyager, Posh, and Sharkk with 5" screens, 1GB RAM, dual SIMs, and quad core processors being available for well under $100, and some devices, like the Blu Dash, for under $60 it makes little sense to push the Rezound too much even as a backup device. Are you located in the US? The Rezound can easily be sold for less than the cost of many of these devices to people with broken devices stuck in a contract with Verizon, I have seen ones in good condition sell for $100-$130, putting you in the realm of really pretty decent GSM phones like the BLU Studio 5.0 C HD for $130, it is a top rated budget phone.
Sorry I got off on a ramble there... I am not trying to sway you from trying to get it working, you might be able too, just don't set your expectations too high, the Rezound is a great device on Verizon... on GSM carriers not so much... I will continue to try to help you as much as I can .
acejavelin said:
Remove battery and reinsert, power up holding VOL DN + POWER... that screen is the Hboot screen, at the top is listed Hboot version, radios, and other pertinent data.
I haven't messed with ROMs in some time on the Rezound, I don't even own one anymore... but the Rez is picky, some ROMs work well on some handsets, and others do not... I am surprised that the GSM patch would bootloop LS, there isn't really much you can do wrong if you are using the current TWRP, just flash and wipe cache and dalvik, reboot and wait. What recovery and version are you using (start it and it should show at the top of the screen). You could also try one of @sun_dream ROM's, his are pretty much exclusive to GSM users. What carrier and frequencies are we talking about here would be good info as well...
2 APNs are fine, although all APN types should be lower case, not sure if that would cause an issue or you just listed it that way in your message... Linux/Android is case sensitive for most things, Camera is different than camera.
I will say again that Rezound is a finicky GSM phone, things have to be just right... some people can get it to work with marginal success, but only a select few people can get it working "great", and with other devices being relatively cheap like the Doogee Voyager, Posh, and Sharkk with 5" screens, 1GB RAM, dual SIMs, and quad core processors being available for well under $100, and some devices, like the Blu Dash, for under $60 it makes little sense to push the Rezound too much even as a backup device. Are you located in the US? The Rezound can easily be sold for less than the cost of many of these devices to people with broken devices stuck in a contract with Verizon, I have seen ones in good condition sell for $100-$130, putting you in the realm of really pretty decent GSM phones like the BLU Studio 5.0 C HD for $130, it is a top rated budget phone.
Sorry I got off on a ramble there... I am not trying to sway you from trying to get it working, you might be able too, just don't set your expectations too high, the Rezound is a great device on Verizon... on GSM carriers not so much... I will continue to try to help you as much as I can .
Click to expand...
Click to collapse
No problem on the ramble I have had a budget phone but the camera on the Rezound is much much better, and that's the main reason I have a smartphone to begin with. Here's the specs you requested in your earlier post:
VIGOR PVT SHIP S-ON RL
HBOOT-2.27.0000
RADIO-2.22.10.0801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012, 19:24:37
Team Win Recovery Project v2.8.1.0
GCI Communications in Alaska, prepaid SIM I believe is 3G
I do have data access on LS, but the service is worse than I had with the stock ROM, and I still cannot send SMS or MMS. I had to leave the house to get it. I will try flashing the GSM fix again, and there is a build.prop fix that I apparently overlooked in the LS postings. If that doesn't work then looks like I'm on to a different ROM. Does it sound like my recovery is just shot, since it won't go past the "4G" boot screen?
Thanks again! You are the Rezound dictionary I've been needing!!!
mdugger said:
GCI Communications in Alaska, prepaid SIM I believe is 3G
Click to expand...
Click to collapse
I'll look at the other stuff in a bit, at work, I'll reply in the morning, we probably need to try to upgrade radios but I gotta do some research that I can't ATM...
But is this a AT&T or Tmo MVNO, or an independent?
acejavelin said:
I'll look at the other stuff in a bit, at work, I'll reply in the morning, we probably need to try to upgrade radios but I gotta do some research that I can't ATM...
But is this a AT&T or Tmo MVNO, or an independent?
Click to expand...
Click to collapse
As far as I know, an independent, as AT&T has it's own towers up here in AK.
mdugger said:
As far as I know, an independent, as AT&T has it's own towers up here in AK.
Click to expand...
Click to collapse
I may be wrong, but it looks like GCI operates it's HSPA and LTE networks in the AWS spectrum... 1700/2100 MHz Band 4, similar to T-mobile, the Rezound does not support that frequency band in hardware, meaning you may only get 2G/Edge.
It is really tough to find any specifics though, I will have to look at their FCC filings, what market area are you in?
acejavelin said:
I may be wrong, but it looks like GCI operates it's HSPA and LTE networks in the AWS spectrum... 1700/2100 MHz Band 4, similar to T-mobile, the Rezound does not support that frequency band in hardware, meaning you may only get 2G/Edge.
It is really tough to find any specifics though, I will have to look at their FCC filings, what market area are you in?
Click to expand...
Click to collapse
So I would only be able to get 2G/Edge no matter what ROM or RUU I could flash? How does this affect the fact that I can't receive SMS or MMS on LS but I can on ICS stock? Or does it? I'm in the Matanuska-Susitna Valley area: Palmer, Wasilla, Houston, Big Lake area.
mdugger said:
So I would only be able to get 2G/Edge no matter what ROM or RUU I could flash? How does this affect the fact that I can't receive SMS or MMS on LS but I can on ICS stock? Or does it? I'm in the Matanuska-Susitna Valley area: Palmer, Wasilla, Houston, Big Lake area.
Click to expand...
Click to collapse
It appears that way, I will have to look at the FCC filings for GCI in that area and see if they support any other frequency ranges. I don't know about their prepaid plans, but the postpaid seems to have some kind of roaming agreement with AT&T. It's pretty uncommon for prepaid to have roaming capabilities though. I'll look into it more in the morning.
---------- Post added at 09:07 PM ---------- Previous post was at 08:45 PM ----------
Looked into it a little more this morning, doesn't look good for the Rezound on GCI
It appears they have:
1900Mhz for Voice/Text (GSM/GPRS) and 2G/Edge data - supported by Rezound
1900Mhz for UMTS (3G/WCDMA) data - Technically supported by the Rezound, but it is known not to work in the US
1700/2100Mhz AWS for HSPA/HSPA+ - NOT supported by Rezound
1700/2100Mhz AWS Band 4 for LTE - NOT supported by Rezound
The Rezound is known to support:
CDMA: 800/1900 Mhz (Verizon Voice/3G EVDO network)
GSM/GPRS: 850/900/1800/1900 MHz
WCDMA(UMTS): 900/1800 MHz (850/1900Mhz have been "detuned" from chipset)
HSPA: 900/2100 MHz
LTE: 700 MHz (Band 13 only)
To be honest, information on GCI's wireless network is tough to come by, and their FCC filings are very broad ranging for a wide variety of technologies, not very specific at all. Their website mentions BYOD (Bring Your Own Device) in a few places but gives no specifics, FAQ, or other information on what frequencies are supported. Frankly I am a little stumped on finding out more information.
It appears that anything over basic GSM or UMTS speeds requires a device that supports the AWS spectrum, which the Rezound does not, and even that information is sketchy as although UMTS seems to be supported by GCI at 1900Mhz, which the Rezound "technically" supports, the 1900Mhz band for UMTS/WCDMA and HSPA is known to be "detuned" in the Rezound... to a point where you basically have to be sitting on the tower to get minimal service. Whether this was an oversight by HTC and Verizon, or a deliberate plan to prevent the device from being switched to another US carrier since 1900Mhz data is only used in the US, has been a hotly debated issue.
So what this all boils down to it that you should be able to get voice, text, and minimal data services including MMS, working on the Rezound with GCI, but your service will be extremely slow... 2G/Edge in GSM networks usually run from 120Kbps to 384Kbps, and that is probably the best you will get with the Rezound on GCI.
Sorry I don't have better news for you.
Don't apologize!!!!!!!!!!!!!!!!!!!!!!! I'm grateful for the research and the time you put into helping me!!!!!! If you were in my shoes and stuck with the rezound then would you go back to stock via http://forum.xda-developers.com/showthread.php?t=2509770 (since SMS/voice/data at least worked with ICS), try different 3rd party ROMS until I find one that works with SMS/MMS/voice and data (in hopes of finding a better OS) or try to find a fix for my TWRP recovery-gone-wrong?
acejavelin said:
Looked into it a little more this morning, doesn't look good for the Rezound on GCI
It appears they have:
1900Mhz for Voice/Text (GSM/GPRS) and 2G/Edge data - supported by Rezound
1900Mhz for UMTS (3G/WCDMA) data - Technically supported by the Rezound, but it is known not to work in the US
1700/2100Mhz AWS for HSPA/HSPA+ - NOT supported by Rezound
1700/2100Mhz AWS Band 4 for LTE - NOT supported by Rezound
The Rezound is known to support:
CDMA: 800/1900 Mhz (Verizon Voice/3G EVDO network)
GSM/GPRS: 850/900/1800/1900 MHz
WCDMA(UMTS): 900/1800 MHz (850/1900Mhz have been "detuned" from chipset)
HSPA: 900/2100 MHz
LTE: 700 MHz (Band 13 only)
To be honest, information on GCI's wireless network is tough to come by, and their FCC filings are very broad ranging for a wide variety of technologies, not very specific at all. Their website mentions BYOD (Bring Your Own Device) in a few places but gives no specifics, FAQ, or other information on what frequencies are supported. Frankly I am a little stumped on finding out more information.
It appears that anything over basic GSM or UMTS speeds requires a device that supports the AWS spectrum, which the Rezound does not, and even that information is sketchy as although UMTS seems to be supported by GCI at 1900Mhz, which the Rezound "technically" supports, the 1900Mhz band for UMTS/WCDMA and HSPA is known to be "detuned" in the Rezound... to a point where you basically have to be sitting on the tower to get minimal service. Whether this was an oversight by HTC and Verizon, or a deliberate plan to prevent the device from being switched to another US carrier since 1900Mhz data is only used in the US, has been a hotly debated issue.
So what this all boils down to it that you should be able to get voice, text, and minimal data services including MMS, working on the Rezound with GCI, but your service will be extremely slow... 2G/Edge in GSM networks usually run from 120Kbps to 384Kbps, and that is probably the best you will get with the Rezound on GCI.
Sorry I don't have better news for you.
Click to expand...
Click to collapse
mdugger said:
Don't apologize!!!!!!!!!!!!!!!!!!!!!!! I'm grateful for the research and the time you put into helping me!!!!!! If you were in my shoes and stuck with the rezound then would you go back to stock via http://forum.xda-developers.com/showthread.php?t=2509770 (since SMS/voice/data at least worked with ICS), try different 3rd party ROMS until I find one that works with SMS/MMS/voice and data (in hopes of finding a better OS) or try to find a fix for my TWRP recovery-gone-wrong?
Click to expand...
Click to collapse
I would flash a custom ROM, then go s-off, then go through that procedure. You have to be s-off before you can do that. Honestly, if it was me and I needed to use GCI I would restore to stock and sell it, to be honest the Rezound camera on anything but stock is just marginal by today's standards. On sense roms the camera is much better
I've got a rooted unlocked s-off AT&T M8. I took the 4.4.4 update, then promptly moved to ARHD 34.0. Didn't realize it at first, but I am no longer able to receive calls while on LTE. (works fine for data, and outgoing calls)
If I force it down to 3g, I'm fine. I also noticed that outgoing calls automatically kick it down to 3g- then learned that LTE calls are not an option yet for AT&T. What I'm trying to figure out is, how was I able to have my stock rom on AT&T in LTE mode and still receive a call?
I've checked all the APN settings and it all is set to recommended parameters on AT&T's website. Is this an Android Revolution HD issue? SIM issue? AT&T issue?
I'm going to have to back out of ARHD if there is no solution here, and that would suck.
thanks.
ARHD 34.0 is Android 5.0 based (software 4.16); not 4.4.4 (software 3.x). You might be experiencing this issue due to firmware mismatch. My advice would be to flash the US Dev Edition RUU or firmware zip to get on the 4.x based firmware, and see if that helps. You can try the Euro 4.16.401 firmware, but my experience the US Dev Edition (4.16.1540) plays better on AT&T (as its designed to work on AT&T's network).
Even with the proper firmware, some folks have also had some random network issues running an "international" based ROM on AT&T's network. Most notably losing Google services while on LTE (possibly due to build.prop differences). So its possible your LTE issue may be related. Not to knock the ROM developers, but devs from Europe and other regions often aren't that familiar with the nuances of AT&T's network.
So if being on the proper firmware still does not resolve the issue, it might be the ROM itself doesn't play well with AT&T in your location.
Thanks Redpoint-
I hadn't considered that and am also shy to using the Dev RUU due to brick risk but will reassess that. (I have to convert my device to GPE to put that on don't I?) I recall some warnings about bricking if I change the ID of my phone and apply the wrong RUU or something- but I'll have to refresh myself on those caveats. Would have been so much simpler if AT&T had just released Lollipop but who knows how long I'd be waiting for that.
Thanks again.
jeremyenos said:
Didn't realize it at first, but I am no longer able to receive calls while on LTE. (works fine for data, and outgoing calls)
If I force it down to 3g, I'm fine. I also noticed that outgoing calls automatically kick it down to 3g- then learned that LTE calls are not an option yet for AT&T. .
Click to expand...
Click to collapse
Voice over LTE (VoLTE) not being available yet should not be the cause. VoLTE is not currently available on most carrier worldwide. Its a very new technology, and deployment is still ongoing in most regions. Only a few Asian countries currently have VoLTE.
That being the case, voice calls should be kicking down to 3G. The lack of VoLTE should not prevent you from receiving calls. As mentioned, I believe the issue is either a firmware mismatch, or ROM not playing well on AT&T's network.
---------- Post added at 10:50 AM ---------- Previous post was at 10:46 AM ----------
jeremyenos said:
Thanks Redpoint-
I hadn't considered that and am also shy to using the Dev RUU due to brick risk but will reassess that. (I have to convert my device to GPE to put that on don't I?) I recall some warnings about bricking if I change the ID of my phone and apply the wrong RUU or something- but I'll have to refresh myself on those caveats. Would have been so much simpler if AT&T had just released Lollipop but who knows how long I'd be waiting for that.
Click to expand...
Click to collapse
No, you don't need to convert to GPE to run Dev Edition RUU. Dev Ed not the same as GPE. Dev Ed is Sense, just without the AT&T branding. The US Dev Edition Lollipop ROM is actually pretty sweet (what I am currently on via RUU).
You won't likely brick the device with RUU unless you run an RUU for the wrong device.
Changing CID is safe as long as you type the command properly.
There is always some tiny risk of a brick if you mess with things s-off, and flashing hboot and radio. But I wouldn't say the risk is any more than installing the OTA (which also replaces hboot and radio) as long as you follow instructions carefully, and do the proper research, and take the proper care while performing the steps.
So thanks redpoint for the advice-
Dev edition RUU installed just fine, and updated my radio and hboot as I had hoped. I go to restore ARHD, and it fails though... even fresh install of ARHD fails with some symlink error. I think after reading up on it that this is due to partition resizing that Dev edition does. So now I can't seem to find a way to get ARHD back on the device. I have no idea what to do to the partitions to restore them to something ARHD can use again if that's the problem, and I can't find anything about it on XDA or elsewhere.
Kind of surprised by this if I'm on the only one hitting the issue... all of the issues. To my knowledge, without a radio update, no AT&T m8 in America with ARHD 34 is going to be receiving incoming calls with LTE enabled. The only way to get a radio update is to use an RUU- of which dev edition is the only one. AT&T/HTC only releasing the 4.4.4 RUU for right now it seems, without the radio and hboot update.
Maybe I've got this all wrong somehow... I can't be the only ARHD m8 AT&T LTE USA user that wants to have incoming calls right? How has anyone else accomplished this?
Stuck with Cyanogenmod for now... slower, less stable than ARHD.
jeremyenos said:
Dev edition RUU installed just fine, and updated my radio and hboot as I had hoped. I go to restore ARHD, and it fails though... even fresh install of ARHD fails with some symlink error. I think after reading up on it that this is due to partition resizing that Dev edition does. So now I can't seem to find a way to get ARHD back on the device. I have no idea what to do to the partitions to restore them to something ARHD can use again if that's the problem, and I can't find anything about it on XDA or elsewhere.
Click to expand...
Click to collapse
You're still misunderstanding about Dev Edition (DE) versus GPE. Only GPE has different partitioning from Sense. DE is still Sense, and has the same partitioning scheme as the stock AT&T (and other carrier) Sense setup.
Don't know why you are having the issues restoring ARHD nandroid and even flashing ARHD. Wipe cache and try to re-install TWRP or try a different version. Then try a "clean install" (factory reset in TWRP) of ARHD.
Or you might have a case where the DE firmware does not play well with ARHD. You can try the 401 firmware, for which ARHD is based. But this might cause as many issues as it solves, as the US DE firmware usually plays better with AT&T's network than the international firmware. But it might be worth a try.
---------- Post added at 11:31 AM ---------- Previous post was at 11:27 AM ----------
jeremyenos said:
The only way to get a radio update is to use an RUU- of which dev edition is the only one. AT&T/HTC only releasing the 4.4.4 RUU for right now it seems, without the radio and hboot update.
Click to expand...
Click to collapse
Since you are s-off, you can flash any carrier's M8 firmware, or flash the radio independently. Although a side note that you should stay away from flashing anything for CDMA (Sprint & VErizon) M8's or dual SIM M8.
If you mean there is no updated LP radio intended for AT&T, aside from the DE RUU that you are currently on; than yes that is correct.
Has this been solved? Im experiencing the same thing. I updated my m8 to the latest at&t lollipop ota. And installed xenon rom. Now i just noticed im not getting any calls. Wife is pissed lol
redpoint had my problem pegged. Just had the wrong rom w/o the radio update I think. I needed to get the developer edition from here. After applying it, I could put ARHD back on and all was good. It's been awhile, but that's how I roughly remember it.
simpl3lang said:
Has this been solved? Im experiencing the same thing. I updated my m8 to the latest at&t lollipop ota. And installed xenon rom. Now i just noticed im not getting any calls. Wife is pissed lol
Click to expand...
Click to collapse
There is no true fix for this, that I know of. Only workaround: turn off LTE in phone settings, or contact AT&T to have HD Voice (what AT&T is calling Voice Over LTE) turned off for your account. The latter is probably the best workaround if you want to continue using non-ATT ROMs; since it allows you to still utilize LTE speeds for data, and HD Voice only works if both parties have devices that support the feature (and many folks don't at this time).
redpoint73 said:
There is no true fix for this, that I know of. Only workaround: turn off LTE in phone settings, or contact AT&T to have HD Voice (what AT&T is calling Voice Over LTE) turned off for your account. The latter is probably the best workaround if you want to continue using non-ATT ROMs; since it allows you to still utilize LTE speeds for data, and HD Voice only works if both parties have devices that support the feature (and many folks don't at this time).
Click to expand...
Click to collapse
thank you for the quick reply. i will call at&t right now. and i will throw in an update.
redpoint73 said:
There is no true fix for this, that I know of. Only workaround: turn off LTE in phone settings, or contact AT&T to have HD Voice (what AT&T is calling Voice Over LTE) turned off for your account. The latter is probably the best workaround if you want to continue using non-ATT ROMs; since it allows you to still utilize LTE speeds for data, and HD Voice only works if both parties have devices that support the feature (and many folks don't at this time).
Click to expand...
Click to collapse
Update: i called, and the nice customer service lady couldnt turn off the feature. She said its part of billing something something. Damn what to do now besides turning off lte.
Should i input some apn or something? Revert radio image to an older one? Go back to kitkat?
simpl3lang said:
Update: i called, and the nice customer service lady couldnt turn off the feature. She said its part of billing something something. Damn what to do now besides turning off lte.
Click to expand...
Click to collapse
Just call again, the CS rep probably just didn't know what they were talking about. I think another user mentioned you need to talk to tech support, not the front line CS reps. Turning off HD Voice with AT&T was confirmed by at least 2 other XDA members to work.
simpl3lang said:
Should i input some apn or something? Revert radio image to an older one? Go back to kitkat?
Click to expand...
Click to collapse
Swapping radios or APNs probably won't help. Not sure about reverting to Kitkat.
redpoint73 said:
Just call again, the CS rep probably just didn't know what they were talking about. I think another user mentioned you need to talk to tech support, not the front line CS reps. Turning off HD Voice with AT&T was confirmed by at least 2 other XDA members to work.
.
Click to expand...
Click to collapse
+1000000000000000000
i guess third time calling is the charm. the first 2 calls i made, they said they couldnt turn it off, saying it was restricted. but the third person i spoke to made me turn my phone off and when it restarted it worked. i can receive calls now.. he said he turned the hd lte off in his side by putting me back to the settings i had before hd voice was added.
thanks again.
edit:
i was actually looking at this prior to making my third call to at&t. maybe it could help others. worth a try? do it at your own risk...
If for some reason the HD Voice Calling option is disabled or inaccessible on your phone after updating to Android 5.1, then you can try the following steps to fix the issue.
Navigate to Settings > More > Cellular Networks and enable the toggle switch for Enhanced 4G LTE Mode. However, if the toggle is missing then follow the steps provided below:
1.Launch the Dialer app on your phone, and dial *#*#4636#*#*.
2.Choose Phone information.
3.Enable or select VoLTE Provisioned Flag.
4.Restart the phone.
5.Go to Settings " More " Cellular networks and toggle the switch for Enhanced 4G LTE Mode, and the HD Voice calling feature should now be activated on your device running Android 5.1.
i got as far as rebooting my phone but the toggle was still missing.
Was working on Insert Coin 4.4.4, flash to OTA 4.16 5.0.2 works fine then I flashed to latest Insert Coin 7.1.9 5.0.2 I tried the following step suggested on post #13 don't see option #3 after click Choose Phone Info.
By calling AT&T turn off HD Voice you'll sacrifice anything?
First call attempt, att technical rep had me turn off phone, 1min later turn it back on and it's working now! Yay!!!
Sent from my HTC One_M8 using Tapatalk
@simpl3lang @redpoint73 Soo glad I found this thread, this was driving me nuts on my m9 running ARHD. When I called ATT they were able to take care of it and turn it off. I cannot find the setting under the *#4636#*, nor under phone settings in ARHD, Is this a setting that developers forget to include in their ROMS?
tc3sean said:
@simpl3lang @redpoint73 Soo glad I found this thread, this was driving me nuts on my m9 running ARHD. When I called ATT they were able to take care of it and turn it off. I cannot find the setting under the *#4636#*, nor under phone settings in ARHD, Is this a setting that developers forget to include in their ROMS?
Click to expand...
Click to collapse
The reason you won't find it in settings, is that "HD Voice" (or I forget what the actual toggle is called) is not a feature on non-ATT ROMs. Its an ATT-specific branding of what is more broadly being calling "Voice over LTE" or VoLTE. Further, most (or at least many) carriers worldwide have not started deploying VoLTE yet (or just starting to do so), so that is another reason why you won't see such a toggle in settings on most ROMs.
Even if such a toggle was present, I'm skeptical whether it would resolve the problem being discussed. It seems there is something unique in the way that ATT is deploying VoLTE, that is screwing with "international" based ROMs. So my hunch is that unless the ATT-specific tweaks are applied, you would still have the voice/SMS issue on LTE.
redpoint73 said:
The reason you won't find it in settings, is that "HD Voice" (or I forget what the actual toggle is called) is not a feature on non-ATT ROMs. Its an ATT-specific branding of what is more broadly being calling "Voice over LTE" or VoLTE. Further, most (or at least many) carriers worldwide have not started deploying VoLTE yet (or just starting to do so), so that is another reason why you won't see such a toggle in settings on most ROMs.
Even if such a toggle was present, I'm skeptical whether it would resolve the problem being discussed. It seems there is something unique in the way that ATT is deploying VoLTE, that is screwing with "international" based ROMs. So my hunch is that unless the ATT-specific tweaks are applied, you would still have the voice/SMS issue on LTE.
Click to expand...
Click to collapse
I can confirm that getting AT&T to turn off HD Voice fixed the issue with me. I installed SkyDragon v10. I had to call twice and go through a lot of crap to get them to do it. The last guy told me he was going to put the "opt-out" code on my number, but that wasn't technically supposed to do it. He said he was putting in that I had "requested" to opt-out (I was taking the line that it just stopped working, as I didn't want to have to deal with any fallout about having rooted and flashed my phone, perhaps that wasn't necessary, idk). So, I think you might take the short cut by saying that you want to opt out of HD voice, and that your "Brother-in-law" just did it, so you know it works. If you stick to your guns, and ask for a technical person and don't let them say no to that, you can definitely get it done.
Thanks to all of the participants on this thread I am out of a tight spot and would like to offer up a few more observations that may be helpful to the next person.
I had an LG G3 running CM13 20160504 that became unstable and I had to replace with my wife's old HTC One m8 also running CM13 20160504 (also tried 20160510 and 20160511) which, like the other phones discussed in this thread, did not get incoming calls, in fact calls did not even roll over to my Google Voice number.
Thanks to this thread I tried forcing the phone to 3g, found that I got calls and then got AT&T to turn of VoLTE (aka HD Voice) and now I can get calls while running with LTE data.
Rather than a fire-hose of details I'll just say that it seems that the G3 would get incoming calls on LTE, and I would not get the first ring then it would ring on what the caller perceived as the second ring. Whenever I was on a call I would note that I was running in 3G, after the call it went back to LTE. I assumed that it was a bandwidth issue but now I think in that lag between the callers first ring and my first ring the phone was negotiating down to a 3G connection like an old school high speed modem negotiating a call with a slower modem (anyone remember those days?). It looks like my HTC does not have the ability to negotiate down or that it was been somehow hardwired not to as there is a flag in the test menu (*#*#4636#*#*) marked "TURN OFF VOLTE PROVISIONED FLAG" which has no effect, i.e. I can press it and the is a visible deflection indicating that the phone knows that the button was pressed but the button text does not change to indicate that a toggle has been effected, calls continue to not ring and even rebooting after pressing does not make any difference.
In summary, having AT&T turn off HD Voice has me working fine with the HTC On m8 on CM13 and I am grateful to all of you for the conversation that got me out of that corner.
I'm creating this thread cuz no other helped me and are close to my problem. Before the beginning of all the issues, mobile was working fine with cloudyG3 2.5 and after messing up something in 3845*990#, got booting error and I had to flash ls990zv8 using flash tool and rooted it installed a custom recovery and installed cloudyG3 2.5 again, but this time whatever I do, the mobile data wont turn on. Changed APN, tried switching from global to LTE/CDMA to Global again but no luck. Tried all the GSM roms out there but the issue is still there. Also tried installing ZV4 bandbase. But, nothing happened. Guys, please help me with this issue. Tried replying to the respective rom threads, but got no reply.
Not even a single reply. Thought XDA members help each other. This was the only forum I constantly choose to comeback for its content. If you guys choose to ignore that's fine and goodbye.
kiran2309 said:
Not even a single reply. Thought XDA members help each other. This was the only forum I constantly choose to comeback for its content. If you guys choose to ignore that's fine and goodbye.
Click to expand...
Click to collapse
Take a look around this section. It's fairly dead. Of the few that remain, maybe no one has had an answer for your problem. I have this device and I rarely look at anything in the section since Sprint abandoned the G3. I go to the Fulmics thread in the bigger G3 section and that's about it. I can tell you that while XDA is helpful, a pissy attitude will get you very little, if any, assistance.
Now.....on to your issue.
You say you flashed back to ZV8 using a flash tool. Was that a tot file flash with the LG program? If so, did you have working data on the stock LG ROM once that was done? If no, you have a device issue.
If yes, and data is gone once you're on a custom ROM, it's a software problem. Try flashing MVNO Slayer (just search, it's in a Moto E section I believe). That will let you choose Sprint as the carrier and will properly set the APNs.
If that doesn't get you going, I'm out of ideas.
It's not about the pissy attitude and this is not the only post I made and got no reply for days. And I'm talking about no data with non-sprint sim cards on GSM roms. I said before all this it was on CloudyG3 2.5 which is a GSM rom and data was working on E/3G/H+. Now I can see that the network does stay on HSDPA in network info and the mobile connection state is disconneted all the time. I want to use this device as GSM.
BTW thanks for replying.
kiran2309 said:
It's not about the pissy attitude and this is not the only post I made and got no reply for days. And I'm talking about no data with non-sprint sim cards on GSM roms. I said before all this it was on CloudyG3 2.5 which is a GSM rom and data was working on E/3G/H+. Now I can see that the network does stay on HSDPA in network info and the mobile connection state is disconneted all the time. I want to use this device as GSM.
Click to expand...
Click to collapse
I can't say for certain, but it sounds like you need to do a sim unlock.
http://forum.xda-developers.com/sprint-lg-g3/general/unlock-sim-gsm-how-to-t2853594
Did that too on stock zv8 and had no luck. I can use the sim for calls, texts and from network info, I can see that the network does stay on HSDPA but the mobile network state is disconnected all the time. Before all this, I was able to use upto H+ speeds on any network. Now, it won't turn on.