HTC 8X/8S
HUAWEI W1
Confirmed brick after 8.1 developer update with CDMA network.
Lumia 822 Verizon
Confirmed no problem if you use GSM/WCDMA.
If you have already bricked your phone, try this:
1.Power down phone by pressing Power button.
2.Press Power button and Volume +/- button at the same time, phone will go to flash mode.
3.Press Camera button for 5 seconds to power off your phone.
4.insert a GSM/WCDMA SIM card in your phone and turn on phone.
It seems that 8.1 not compatible with CDMA SIM card.
reker said:
HTC 8X/8S
HUAWEI W1
Confirmed brick after 8.1 developer update with CDMA network.
Lumia 822 Verizon
Confirmed no problem if you use GSM/WCDMA.
If you have already bricked your phone, try this:
1.Power down phone by pressing Power button.
2.Press Power button and Volume +/- button at the same time, phone will go to flash mode.
3.Press Camera button for 5 seconds to power off your phone.
4.insert a GSM/WCDMA SIM card in your phone and turn on phone.
It seems that 8.1 not compatible with CDMA SIM card.
Click to expand...
Click to collapse
I have it on my htc 8xt and its working fine. Well I am having lockscreen issues but the network is working fine for me on sprint.
starsoccer9 said:
I have it on my htc 8xt and its working fine. Well I am having lockscreen issues but the network is working fine for me on sprint.
Click to expand...
Click to collapse
the problem with me no wifi
no mobile data
That is so far from something you could call a "brick" it's not funny. "Brick" means un-recoverable. If you can "un-brick" something without diassembling it or at least using hardware a normal user couldn't have access to, it's not a brick!
Also, has anybody else actually had this problem? A few people seem to indicate that they have *not*...
No problems what-so-ever updating and running on my Odyssey...other than taking forever to download and install.
Working fine in my Lumia Icon from Verizon.
No cellular data after hard reset
I by no means have a brick, but I do now have an issue. Here’s what happened.
I have a Sprint ATIV S Neo, GDR3, Interop-unlock, the whole deal.
Installed the 8.1 update yesterday, and everything was working. I have been playing with all kinds of “stuff” in the registry and such, so I decided that since I had just installed 8.1 I would start fresh and do a hard reset. I don’t really care about keeping interop-unlock at this point. Even with it, so much is still locked down. I’m sure in the future someone will get this cracked and we can really have fun, but until then, just being developer unlocked is good enough.
So, when I got home I reset the phone (power+volume down, exclamation point, then the remaining sequence).
Phone boots back up, and I connect to my WiFi and set everything back up. I think life is wonderful at this point. Then decide to test my 4G download speed so I turn off wifi.
Oops, no cellular data, phone calls and text are fine (didn’t try mms, but probably doesn’t work, blank url in the provisioning). Tried all the usual tricks (##72786# and such). I have my msl, so I go into the provisioning, and things look messed up. My MDN and MSID are 000003872. That makes no sense, so I set them back to the correct values and still no go.
Called Sprint. They ran me through all the usual things that I had already done (hour on the phone with them).
Long story short: The activation program seems to be missing from my phone. Hands free activation never tries to start, in fact, after hard resetting again and watching closely, during setup it says “Activate your device can’t be opened”. And the network settings are missing from the settings menu.
So after work I’m going to take it to Sprint and hopefully they have a factory image they can flash (hopefully an older version so I can update things myself).
My thinking is that the 8.1 update is basically the new rom, but during install doesn't delete the existing carrier programs. When I hard reset, all that got re-installed was the strictly Microsoft stuff, not the carrier specific items i.e. hands free activation.
PS Sorry about the novel...
GoodDayToDie said:
That is so far from something you could call a "brick" it's not funny. "Brick" means un-recoverable. If you can "un-brick" something without diassembling it or at least using hardware a normal user couldn't have access to, it's not a brick!
Also, has anybody else actually had this problem? A few people seem to indicate that they have *not*...
Click to expand...
Click to collapse
HTC confirmed this yesterday, they awared the problem and contacting with MS. Announcement by HTC China
The problem covered both HTC 8s(A620D) and 8x(C620d)
8X/8S have similar but more serious problem with gdr1 - gdr2 upgrade last year, even can't boot into SPL.
By the way, to normal users, if their phone turn into black screen and can't boot, it's a brick. No one will care about if it's a real brick, what they know is: I can't use my phone, it's not working, just like a brick.
fgr said:
I by no means have a brick, but I do now have an issue. Here’s what happened.
I have a Sprint ATIV S Neo, GDR3, Interop-unlock, the whole deal.
Installed the 8.1 update yesterday, and everything was working. I have been playing with all kinds of “stuff” in the registry and such, so I decided that since I had just installed 8.1 I would start fresh and do a hard reset. I don’t really care about keeping interop-unlock at this point. Even with it, so much is still locked down. I’m sure in the future someone will get this cracked and we can really have fun, but until then, just being developer unlocked is good enough.
So, when I got home I reset the phone (power+volume down, exclamation point, then the remaining sequence).
Phone boots back up, and I connect to my WiFi and set everything back up. I think life is wonderful at this point. Then decide to test my 4G download speed so I turn off wifi.
Oops, no cellular data, phone calls and text are fine (didn’t try mms, but probably doesn’t work, blank url in the provisioning). Tried all the usual tricks (##72786# and such). I have my msl, so I go into the provisioning, and things look messed up. My MDN and MSID are 000003872. That makes no sense, so I set them back to the correct values and still no go.
Called Sprint. They ran me through all the usual things that I had already done (hour on the phone with them).
Long story short: The activation program seems to be missing from my phone. Hands free activation never tries to start, in fact, after hard resetting again and watching closely, during setup it says “Activate your device can’t be opened”. And the network settings are missing from the settings menu.
So after work I’m going to take it to Sprint and hopefully they have a factory image they can flash (hopefully an older version so I can update things myself).
My thinking is that the 8.1 update is basically the new rom, but during install doesn't delete the existing carrier programs. When I hard reset, all that got re-installed was the strictly Microsoft stuff, not the carrier specific items i.e. hands free activation.
PS Sorry about the novel...
Click to expand...
Click to collapse
i got the same issue with my ativ s.
everything works except mobile data.
is there some settings i can try since i didnt do a hard reset but the normal reset from the phones "about" menu.
my network is WIND greece.
fgr said:
I by no means have a brick, but I do now have an issue. Here’s what happened.
I have a Sprint ATIV S Neo, GDR3, Interop-unlock, the whole deal.
Installed the 8.1 update yesterday, and everything was working. I have been playing with all kinds of “stuff” in the registry and such, so I decided that since I had just installed 8.1 I would start fresh and do a hard reset. I don’t really care about keeping interop-unlock at this point. Even with it, so much is still locked down. I’m sure in the future someone will get this cracked and we can really have fun, but until then, just being developer unlocked is good enough.
So, when I got home I reset the phone (power+volume down, exclamation point, then the remaining sequence).
Phone boots back up, and I connect to my WiFi and set everything back up. I think life is wonderful at this point. Then decide to test my 4G download speed so I turn off wifi.
Oops, no cellular data, phone calls and text are fine (didn’t try mms, but probably doesn’t work, blank url in the provisioning). Tried all the usual tricks (##72786# and such). I have my msl, so I go into the provisioning, and things look messed up. My MDN and MSID are 000003872. That makes no sense, so I set them back to the correct values and still no go.
Called Sprint. They ran me through all the usual things that I had already done (hour on the phone with them).
Long story short: The activation program seems to be missing from my phone. Hands free activation never tries to start, in fact, after hard resetting again and watching closely, during setup it says “Activate your device can’t be opened”. And the network settings are missing from the settings menu.
So after work I’m going to take it to Sprint and hopefully they have a factory image they can flash (hopefully an older version so I can update things myself).
My thinking is that the 8.1 update is basically the new rom, but during install doesn't delete the existing carrier programs. When I hard reset, all that got re-installed was the strictly Microsoft stuff, not the carrier specific items i.e. hands free activation.
PS Sorry about the novel...
Click to expand...
Click to collapse
No need to apologize for the novel! I did the SAME exact thing as you (except I hard resetted via settings > about > more info > reset your phone). Luckily I know my MSL, and have my MSID handy. I wiped my settings by doing ##72786# and selecting ok twice. I rebooted my phone manually and then went to the 'activate my device' app in settings. It did what looked like a profile update and it said my phone was successfully activated with my phone number listed.
I can browse the web on Sprint's network, make/receive calls and send/receive texts. The only thing I can't figure out to fix is MMS. I can't get or send picture mail, group texts or any kind of MMS at all.
I've managed to get my coworkers settings from his ATIV S Neo but I can't figure out how to edit them on my phone. Going into ##3282# doesn't let me edit things that deeply.
From what I've heard on other forums is that we're basically SOL unless Sprint releases their firmware updates and their release of 8.1 soon (which they have confirmed they will do this summer).
I figured from the get go when this started yesterday that this 8.1 release doesn't seem to properly support CDMA and judging by how many people have this issue, I was correct. Microsoft really needs to work better on the CDMA side of things.
fgr said:
I by no means have a brick, but I do now have an issue. Here’s what happened.
I have a Sprint ATIV S Neo, GDR3, Interop-unlock, the whole deal.
Installed the 8.1 update yesterday, and everything was working. I have been playing with all kinds of “stuff” in the registry and such, so I decided that since I had just installed 8.1 I would start fresh and do a hard reset. I don’t really care about keeping interop-unlock at this point. Even with it, so much is still locked down. I’m sure in the future someone will get this cracked and we can really have fun, but until then, just being developer unlocked is good enough.
So, when I got home I reset the phone (power+volume down, exclamation point, then the remaining sequence).
Phone boots back up, and I connect to my WiFi and set everything back up. I think life is wonderful at this point. Then decide to test my 4G download speed so I turn off wifi.
Oops, no cellular data, phone calls and text are fine (didn’t try mms, but probably doesn’t work, blank url in the provisioning). Tried all the usual tricks (##72786# and such). I have my msl, so I go into the provisioning, and things look messed up. My MDN and MSID are 000003872. That makes no sense, so I set them back to the correct values and still no go.
Called Sprint. They ran me through all the usual things that I had already done (hour on the phone with them).
Long story short: The activation program seems to be missing from my phone. Hands free activation never tries to start, in fact, after hard resetting again and watching closely, during setup it says “Activate your device can’t be opened”. And the network settings are missing from the settings menu.
So after work I’m going to take it to Sprint and hopefully they have a factory image they can flash (hopefully an older version so I can update things myself).
My thinking is that the 8.1 update is basically the new rom, but during install doesn't delete the existing carrier programs. When I hard reset, all that got re-installed was the strictly Microsoft stuff, not the carrier specific items i.e. hands free activation.
PS Sorry about the novel...
Click to expand...
Click to collapse
I saw your reply to my thread for the same issue. I did some research on WP Central and found another thread where someone was having the same issue with an Ativ S and the solution was to manually enter the APN information. I don't know what the APN info is for Sprint, but when I checked it on my phone it was blank. It seems like a safe bet that updating that info would fix the issue.
---------- Post added at 04:01 PM ---------- Previous post was at 03:40 PM ----------
iknowsingh said:
No need to apologize for the novel! I did the SAME exact thing as you (except I hard resetted via settings > about > more info > reset your phone). Luckily I know my MSL, and have my MSID handy. I wiped my settings by doing ##72786# and selecting ok twice. I rebooted my phone manually and then went to the 'activate my device' app in settings. It did what looked like a profile update and it said my phone was successfully activated with my phone number listed.
I can browse the web on Sprint's network, make/receive calls and send/receive texts. The only thing I can't figure out to fix is MMS. I can't get or send picture mail, group texts or any kind of MMS at all.
I've managed to get my coworkers settings from his ATIV S Neo but I can't figure out how to edit them on my phone. Going into ##3282# doesn't let me edit things that deeply.
From what I've heard on other forums is that we're basically SOL unless Sprint releases their firmware updates and their release of 8.1 soon (which they have confirmed they will do this summer).
I figured from the get go when this started yesterday that this 8.1 release doesn't seem to properly support CDMA and judging by how many people have this issue, I was correct. Microsoft really needs to work better on the CDMA side of things.
Click to expand...
Click to collapse
Would you be willing to post the settings? I am guessing that the issue may be partially related to APN settings being missing under Settings, Cellular+SIM, SIM settings. I read a post by someone on another forum who had the same data issues but fixed them by entering the APN information for his carrier. I've tried a couple of different APN settings that I've found out on the web for Sprint, but I'm not sure they are accurate. All I know is that they were missing when I checked them on my phone.
i have fixed my issue with some internet research.
adding manually the APN of the provider in the APN settings solved the issue for me.
hope i helped.
Would you be willing to post the settings? I am guessing that the issue may be partially related to APN settings being missing under Settings, Cellular+SIM, SIM settings. I read a post by someone on another forum who had the same data issues but fixed them by entering the APN information for his carrier. I've tried a couple of different APN settings that I've found out on the web for Sprint, but I'm not sure they are accurate. All I know is that they were missing when I checked them on my phone.
Click to expand...
Click to collapse
I would not mind at all! I went into ##3282# on his phone, selected 'view' then 'others' then 'MMSC URL' . The two pictures are attached, the order of the settings begins with the picture that says '[email protected]'. The second pic is literally a continuation as it starts right where the first picture ends (I scrolled neatly!)
I've been trying to find the correct Sprint APN settings around the web, and a lot of sites have similar settings as options but either Windows Phone doesn't have enough fields for the settings, and the fact that in the APN settings on 8.1, it doesn't let me change the authentication type.
I noted on my coworker's ATIV S Neo that in his 'cellular+SIM' section, he doesn't have options to input APN like I do... the hard reset must've kicked the CDMA stuff in our phones to the curb.
fatdata said:
i have fixed my issue with some internet research.
adding manually the APN of the provider in the APN settings solved the issue for me.
hope i helped.
Click to expand...
Click to collapse
Would you mind posting the APN settings you used? That would be appreciated... I've tried going to various sites but wasn't sure what was the correct ones.
iknowsingh said:
Would you mind posting the APN settings you used? That would be appreciated... I've tried going to various sites but wasn't sure what was the correct ones.
Click to expand...
Click to collapse
they are for greek providrs though... I think you need to find the ones for your provider.
note: i just used the GPRS APN address for wind (my provider) and it worked the rest seemed to not make any diference
VODAFONE
GPRS APN: - internet.vodafone.gr ή webonly.vodafone.gr
Username: - {κενό}
Password: - {κενό}
MCC=202
MNC=05
APN type=default
DNS: - 213.249.17.10, 213.249.17.11
WIND
GPRS APN: - gnet.b-online.gr ή gint.b-online.gr
Username: - {κενό}
Password: - {κενό}
MCC=202
MNC=10
APN type=default
DNS: - 212.152.79.19, 212.152.79.20
fatdata said:
they are for greek providrs though... I think you need to find the ones for your provider.
note: i just used the GPRS APN address and it worked the rest seemed to not make any diference
Click to expand...
Click to collapse
Ahhhh, Vodafone... I assumed you were a Sprint brethren... I appreciate your post nonetheless! Thank you, sir. Now to continue the hunt for correct Sprint settings -_-
Just got back from two Sprint stores and a Best Buy with Samsung reps on hand. None of them had access to any means of reflashing to stock, and really had no useful information. I was surprised by how little they knew about any Windows phones.
I do have TEP though, and they ordered me a new phone. I should have it in a few days. Costing me nothing
Wish I had something useful to tell you folks...
fgr said:
Just got back from two Sprint stores and a Best Buy with Samsung reps on hand. None of them had access to any means of reflashing to stock, and really had no useful information. I was surprised by how little they knew about any Windows phones.
I do have TEP though, and they ordered me a new phone. I should have it in a few days. Costing me nothing
Wish I had something useful to tell you folks...
Click to expand...
Click to collapse
I actually work for a Sprint store (non service/repair location) and I don't have TEP. I actually DO have an upgrade available since I bought the ATIV S Neo off-contract. I wouldn't mind using my upgrade on another ATIV S Neo... and whatever Windows Phones Sprint gets in the future, I'll have to buy off contract (which is nothing new to me lol).
I could technically add TEP to my line and wait a few days then do an advanced exchange at a local repair center but I'll most likely get a refurb as most of them are. I'd rather a brand new device
So I'm currently debating using my upgrade...
fgr said:
Just got back from two Sprint stores and a Best Buy with Samsung reps on hand. None of them had access to any means of reflashing to stock, and really had no useful information. I was surprised by how little they knew about any Windows phones.
I do have TEP though, and they ordered me a new phone. I should have it in a few days. Costing me nothing
Wish I had something useful to tell you folks...
Click to expand...
Click to collapse
Did you mention the update to 8.1 or did you just play dumb? I am thinking I am going to have to do the same thing as you but I don't want to walk in there and tell them that I did the update and have them tell me I'm SOL.
ZogJones said:
Did you mention the update to 8.1 or did you just play dumb? I am thinking I am going to have to do the same thing as you but I don't want to walk in there and tell them that I did the update and have them tell me I'm SOL.
Click to expand...
Click to collapse
I was completely honest, gave them the whole story from start to finish. Even pointed out some of the cool features of 8.1 :laugh:
If this was the new Galaxy they might have given me a hard time, who knows.
Related
I already started this at the end of this thread:
http://forum.xda-developers.com/showthread.php?p=1881093#post1881093
but now I'm in real trouble so I'm starting a new thread hoping for help.
I was using 3.16 ROM on my mogul and all seemed fine until today I got an authentication error while voice roaming(edit: I said data roaming initially by accident). I called sprint to get an HLR reload becasue the above thread indicated this was helping people.
My phone quit making calls and quit data connections. Data ended with "cannot connect for unkoww reason". Calls simply disconnecte imediately. I could call *2 though.
Sprint had me rest my phone a few times and the checked the MSN/MSID info (which was fine) and evenutually sugestet I try the official rom (yes I was honest with them). I tried this, flashed 2.17 same deal.. after an hour with a tech he eventually told me the 2.17 is an "upgrade" rom and that it won't overwrite everything and that I should reload the original rom... so I just loaded 2.09.. checked MSN and MSID... in fact checked every setting in the EPST stuff against my touch. Everything is the same... except the security section (which doesn't exist on the touch) had the wrong username was my [email protected]nt... instead of sprint email) and some giberrish for a password.
I'm not sure what this should be, but actually I doubt it's the issue.
I'm stuck though. My phone is effectively bricked(it plays bubble breaker well at least) and I'm at a loss. Please advise if you can.
I just got off the phone with sprint. I have reverted to the 2.09 ROM. With the sprint reps help I did "master reset" which i didn't know existed. This is deeper than both a soft reset and a hard reset. It resets all the EPST data like MDN and MSID. We then set these back to what they should be. But no dice. She told me the phone radio must be broken and claimed that the *2 call uses a different radio. (really? does anyone believe that?) So her advice was to go to the repair center (which is 40 miles from here). OH.. and she put a diferent MSID which I find strange. It's no longer my phone number. I asked her if this was right and she said it probably changed when I asked for the HLR reload but that it was correct... weird. I'm in bad shape.
I called back becuase after forcing the phone to roaming I got an interesting message from verzion sayign they would transfer me to their operator where I could pay money to make a call... doesn't sound like a broken radio to me.
So I told the guy this but this time I got someone who knew what he was doing and before I could finish telling him about it he had it fixed. Aperently there was a setting in there system called HSA_Roaming_only that was set incorrectly and was forcing to try to connect to other networks. He checked it (I think.. or maybe unchecked it..) and voila... after several hours and three roms... it works.
The same thing happened to me when I did an HLR reload. I called sprint and told them my symptoms and they fixed it within 3 minutes. I didnt reinstall anything. You got totally whored by sprint, I feel for you.
dagurasu said:
I called back becuase after forcing the phone to roaming I got an interesting message from verzion sayign they would transfer me to their operator where I could pay money to make a call... doesn't sound like a broken radio to me.
So I told the guy this but this time I got someone who knew what he was doing and before I could finish telling him about it he had it fixed. Aperently there was a setting in there system called HSA_Roaming_only that was set incorrectly and was forcing to try to connect to other networks. He checked it (I think.. or maybe unchecked it..) and voila... after several hours and three roms... it works.
Click to expand...
Click to collapse
Did this allow you to EVDO roam? I cant data roam on EVDO and my girlfriends phone can. She is on the 2.17 official and i am on the 3.17 unofficial.
dagurasu said:
With the sprint reps help I did "master reset"
Click to expand...
Click to collapse
How do you do a master reset?
In the end I did get everything working again. I did get voice roaming working on 3.16 and I do have 1x roaming. I don't believe I have evdo roaming, but I probably won't know for sure until I go into work tomorrow.
I don't think the master reset was needed in the end.. but I could see that it might help someone someday. There is I think a ##something# code to get to the full epst settings, but I just go to \windows\EPST.lnk (edit: this is wrong.. see my next post)
Run it, select edit.. enter you MSL.. please don't ask how to find it.. search. Then under the menu tab... right soft key there is a reset option that I never noticed before. This will reset all the radio setup options to some default values and will do hard reset... erasing your data as usual. I have no idea where these defaults live on the phone... It seems like some roms end up changing at least the MSID and MDN, but some don't. I don't know what else they might change or how they affect what the defaults are that this resetting does.
In summary to my issue, there were two problems:
1) MSID was changed (during the hlr reload) in sprints system to something other than my phone number, (and now it likes to go back to phone number in my phone during upgrades thus not matching with what sprint has)
2) the HSA_ROAMING_ONLY flag in SPRINT's system (not my phone) was set wrong.
You got totally whored by sprint, I feel for you.
Click to expand...
Click to collapse
oh well.. not the first time.
dagurasu said:
In the end I did get everything working again. I did get voice roaming working on 3.16 and I do have 1x roaming. I don't believe I have evdo roaming, but I probably won't know for sure until I go into work tomorrow.
Click to expand...
Click to collapse
keep us updated on the evdo roaming. this is a big deal to me and i hope this isnt like this in the final version of the rom...
First.. I'm wrong about the reset.. it seems you must do the ##something# to get the epst that has the reset option in the menu tab. Opening through the windows link doesn't give that option. (edit: it's ##786#.. some googling found it.. doesn't seem terribly common information though plus google won't take "##".)
I am not getting evdo roaming and I'm pretty certain there should be verizon evdo coverage here... in fact I occassionally see the evdo symbol briefly when I switched to forced roaming, but it goes away immediately.. I suspect it doesn't authenticate.
Being that verizon seems to have much more evdo coverage than sprint, and that they make like $40 a month off their own customers for access to it(last I checked), it wouldn't be at all surprising if sprint can't pay/provide them enough (with all these sero plans) to get them to allow it. But I speculate.
Did anyone ever have this working? I never did.
well mine wont evdo roam on the new leaked rom. But my girlfriend has the same phone in the same house with the 2.17 rom and can evdo roam just fine... so it is baffling me
Something about the new rom is causing the problem, because having these two phones side by side and them acting differently is strange. mine also roamed fine on evdo before i installed the leaked rom btw
Everything else seems to function as normal, but the no evdo roaming is driving me mad. i really hope this isnt an issue in the official rom when it comes out.
we are also both on sero plans and roaming on alltel towers here.
Masater Reset Code
in order to do a master reset you need your MSL# then type ##MSL# and then you can do the master reset this will reset everything and i mean evereything to factory defaults. you will have to go through the sasme initial setup as when the phone was activated the first time. so make sure you have all your correct MSN/MISD numbers
tlhop911 said:
in order to do a master reset you need your MSL# then type ##MSL# and then you can do the master reset this will reset everything and i mean evereything to factory defaults. you will have to go through the sasme initial setup as when the phone was activated the first time. so make sure you have all your correct MSN/MISD numbers
Click to expand...
Click to collapse
Hmm .. when I go in there I still do not see where I can do a master reset. All I can do is change the MDN and MSID and then select OK.
Cool. I haven't been able to roam on Verizon's towers since I added the leaked ROM either. If I can manage to get through to tech support (the CSR in chat said she couldn't help me) I will have them reset the HSA flag to allow high speed digital roam.
well mine wont evdo roam on the new leaked rom. But my girlfriend has the same phone in the same house with the 2.17 rom and can evdo roam just fine... so it is baffling me
Click to expand...
Click to collapse
I'm on sero too, but again it's verizon roaming here.. so may be related to why it never worked for me in the first place. You could dare to just call sprint and ask why it's not working.
tlhop911 said:
in order to do a master reset you need your MSL# then type ##MSL# and then you can do the master reset
Click to expand...
Click to collapse
This is wrong.. this won't get you there, at least not on my phone.. and actually you DON'T need an MSL... BUT you better have it handy to fix things after you do the reset.
Just do ##786# as I stated above (sorry for the confusion the first time) and then look in the menu soft key.
EDIT: After you do the master reset... then you can do the ##MSL# and fix your MSID and MSN to what they should be.
To neodorian... please read what I wrote... this flag DID NOT do anything for my data roaming (and I am in verizon territority) This didn't even fix the usual voice roaming problem as far as I can tell (that's something else unknown which is fixed by the HLR reload, this only fixed my rather unusual problem where I could ONLY roam... and furthermore had to supply a credit card number to do so! This was something sprint broke for me just because they liked me better than you.
I had the authentication issue on my VZW XV6800 - I called in to tech support and after talking to the first person, and mentioning a HSL reset, she transferred me to level 2. The guy had me do basic troubleshooting, and examined some settings, then had me remove the battery for at least 1 minute. reload phone, try over the air programming, and test calls. all to no avail. he then had me go in and edit the settings using ##778 (VZW default password for editing is 000000) you don't need to use the hex code and program designed to give you the password, especialy since I tried this, and it didn't work.
Anyway, he generated a new A(uthentication) code on his end, had me manually input it, and he also had me change my Home SID/NID. Mine said 30/65535. He said it should be 30748/65535.
I then did another *228 #2 and was now able to make a test call. After hanging up I went back and looked, and the Home SID/NID #1 was 30/65535 again. Not sure if those extra numbers did anything, but the phone got rid of them.
I am able to call out and receive calls now, and the data seems to be zipping right along. When I tested gps last night it had me miles from where I was located.
UPDATE:
GPS seems to be working fine. I'm guessing the tower I was "connecting to" was miles away, since I live at the base of a butte, and have terrible reception. Most likely that WAS the closest tower to where my phone was.
Hello all! Its 'That Guy' Again
I recently bought a new HTC Vogue because my old one had *crud*crap*Stuff* on the screen. I called into Sprint customer service as always when swapping.
Everything seems to be fine. The phone is working. Texting is a-ok.. Data is a no-go.
This new Vogue ahs not been *modded*Tweaked*Flashed* (yet)
However when I launch an app to activate the provisioning feature, nothing happens. It dials the usual #777 and proceeds with the 'provisioning data services" msg. But after that it just disappears.
I dont not get a reply back or anything. If I try to refresh the browser to loop through it once more it just does the same thing over and over. Provisioning-----Then nothing
After 2 hours with customer service at Sprint we have gone through just about everything we could think of.. Still nothing.. The phone is practically brand new! Is there something im missing here? Maybe a bug in a certain version of the stock rom?
My old vogue provisioned fine previously and after I flashed to Froyo it was pure bliss.. However this phone will not take the data onnection O-o
If there is anything I can do/attempt to do id be forever greatful! And ill gladly donate my old Vogue to anyone who can use the parts.. It looks like super glue or something in a 3cm patch on the touch screen.. It still recognizes touch on ALL parts of the matrix, it just doesnt look pretty. The shell is kinda scuffed but over the phone works perfect =) This was one phone I didnt want to (ORD) to death.. Thanks in advance to anyone who gives insight on the issue!
Are you running on the most recent Vogue stock rom? which is 6.1
Yes =) Im running the Stock 6.1 Pro from from the HTC website
hexalot said:
Yes =) Im running the Stock 6.1 Pro from from the HTC website
Click to expand...
Click to collapse
I am not certain of what the Sprint rep asked you to do, but I have a feeling that your issue lies in the EPST programming. You are likely missing username and/or passwords under the Connections section in EPST. Give it a go and let me know what happens. If you need instructions, let me know as well...
I would be glad to take your old Vogue off your hands if you are serious about giving it away.
Sorry for the lateness! I did discover that she(the rep) had seriously messed up the epst settings in the phone, however after recovery still no data. Its almost as if the phone hates it lol. Eitherway in that case its not as useful as it could be. Ill really only bought the second one because it was new and i wanted the screen to be scratchless I dont mind sending you my old Vogue especially since youre already on the east coast lol ill log in again when i get back to the office and we can swap details.
Thanks again for you help!
hexalot said:
Sorry for the lateness! I did discover that she(the rep) had seriously messed up the epst settings in the phone, however after recovery still no data. Its almost as if the phone hates it lol. Eitherway in that case its not as useful as it could be. Ill really only bought the second one because it was new and i wanted the screen to be scratchless I dont mind sending you my old Vogue especially since youre already on the east coast lol ill log in again when i get back to the office and we can swap details.
Thanks again for you help!
Click to expand...
Click to collapse
There really are 3 or four things on EPST that you need to modify to get the device working properly (in most cases anyways): MIN, MDN, Username, Password, and maybe a couple of others to get better performance out of your connection (cycle, priority, etc). If you flash to stock, why don't you try to do *228 to do automatic provisioning?
Let me know when you want me to give you the shipping details for your Vogue. Thanks.
Only thing that pops in to my mind is that maybe you bought the phone off of eBay? Was it a "Sprint" branded phone, or like an Alltel or something that you activated on Sprint? I would imagine flashing the Sprint ROM from the HTC website would handle everything, but just as a shot in the dark, you could try to install the Carrier CAB (http://winbreak.com/winmo/voguegoodies) for Sprint.
NuAngel
@egzthunder1 Go 'head and pm the info m8! Sorry for the delay again im just hardly at this location anymore.
@NuAngel I actually bought the phone new from some rich guy on craigslist. It was flawless and my vogue had the previously mentioned "crap" on the screen.
It is branded Sprint and they activated the phone just fine as far text and phone. They are saying the data is active however no matter what rom/radio i use it wont access the data network. With WinMo it always says provisioning data but it never happens.. the browser goes idle. if i try to access any data apps it tries to provision but never seems to finish the job.. Android rom same deal just no provision of course. And as you know the Stock Sprint rom has also been flashed with no success of accessing data. Everything else works fine and i have the same service with my current vogue which works perfectly everytime.
If the data issue cant be resolved it will always make an awesome test device.. However, while I cant dig up anyone else having the issue, someone is bound to..
hexalot said:
@egzthunder1 Go 'head and pm the info m8! Sorry for the delay again im just hardly at this location anymore.
@NuAngel I actually bought the phone new from some rich guy on craigslist. It was flawless and my vogue had the previously mentioned "crap" on the screen.
It is branded Sprint and they activated the phone just fine as far text and phone. They are saying the data is active however no matter what rom/radio i use it wont access the data network. With WinMo it always says provisioning data but it never happens.. the browser goes idle. if i try to access any data apps it tries to provision but never seems to finish the job.. Android rom same deal just no provision of course. And as you know the Stock Sprint rom has also been flashed with no success of accessing data. Everything else works fine and i have the same service with my current vogue which works perfectly everytime.
If the data issue cant be resolved it will always make an awesome test device.. However, while I cant dig up anyone else having the issue, someone is bound to..
Click to expand...
Click to collapse
PM sent. Thanks a lot!
Whatever is causing this, after reading your explanation, now I am positive is in the EPST programming parameters. Android builds here have APNs for Sprint in there out of the box (no provisioning required). But to connect, it looks at the PST programming (just like WM does). I would try to speak with someone else at Sprint and see if they tell you something else. There aren't too many things that should be modified in there for the internet to work...
I have the Moto G4 Play (XT1607) (Harpia) and I have decided to flash LineageOS (lineage-14.1-20170131-nightly-harpia-signed.zip) on it using TWRP v3.0.2 r5. After getting it installed I noticed that it was not connecting to my 4g LTE Internet (I have Ting). So I figured I needed to make some changes to the APN settings. So I go to Settings>... More> Cellular Networks and the moment I click on "Cellular networks" I get an error message saying "com.android.phone has stopped". After reflashing and trying again a few times with the same result, I tried using a completely different ROM. AOKP. (aokp_harpia_nougat_nightly_2017-01-31.zip) and I ran into the same exact problem I was having with LineageOS.
I then tried to see if I could force my way into the APN configuration using an app called "Change APN". This worked, but now I see the message "Access Point Name settings are not available for this user". I decided to ignore this and click on the + to create a new APN. After filling the correct info out for Ting APN, I click on "Save"... and it doesn't save at all.
I decided to revert to the stock rom, and everything works perfectly fine with the stock rom. 4G LTE on Ting works fine. Whenever I try using a custom ROM of any kind, I run into the problem I described above. I don't know if I am forgetting to do something, or completely doing something wrong. I could use some help with this guys.
Isn't Ting a Sprint service? I didn't think CDMA-based networks had APN settings to configure. Verizon and US Cellular have always used *22XXX for programming, as far as I can remember.
mkollersms said:
Isn't Ting a Sprint service? I didn't think CDMA-based networks had APN settings to configure. Verizon and US Cellular have always used *22XXX for programming, as far as I can remember.
Click to expand...
Click to collapse
Yes. Ting is a Sprint service. Well either way LTE isn't working and the 3G keeps randomly turning on and off whenever I use a custom ROM. However, when I use Stock firmware, everything works perfectly fine. I am unsure what is causing the issue.
It seems nearly all custom ROMs at this point are having data connectivity issues. I'm trying to find a nandroid of the original xt1607 rom so I can just go back until its all sorted out.
mkollersms said:
Isn't Ting a Sprint service? I didn't think CDMA-based networks had APN settings to configure. Verizon and US Cellular have always used *22XXX for programming, as far as I can remember.
Click to expand...
Click to collapse
With Ting you can choose to use Sprint or T-Mobile. I am using the T-Mobile side of Ting and you do need to add Ting's APN settings for it to work. I am still on factory ROM but watching closely to see what others are experiencing with custom ROMs.
n76 said:
With Ting you can choose to use Sprint or T-Mobile. I am using the T-Mobile side of Ting and you do need to add Ting's APN settings for it to work. I am still on factory ROM but watching closely to see what others are experiencing with custom ROMs.
Click to expand...
Click to collapse
I haven't noticed any issue with my GSM ting service on lineage. I get LTE and the WiFi/LTE handoff seems to work. I don't install many apps and don't let them run in the background, so perhaps there's a conflict between them that's shutting down LTE service. This is just a guess.
Anyone have any information pertaining to this subject? I've searched hours on hours to no avail. I run U.S. Cellular and on the newest RR-5.8.1-OMS after I go to Settings>More>Cellular Networks>Crash. Every time. Resets my radio and picks right back up again. Everything works until I'm in my house, then I'm roaming and there's no way to manage in settings because of the crash.
I looked around in the file system and in /data/data/com.android.phone/ there is no files, no .db files or anything. I don't know of there's supposed to be either. But like OP stated, stock rom is flawless.
Would I be and to copy com.android.phone from stock and restore after flashing? I don't know what to do but this is with every single custom ROM out right now on every release. Data and everything works fine as far as I can tell but just no way to configure the settings. Any help would be greatly appreciated!!!
[email protected] said:
Anyone have any information pertaining to this subject? I've searched hours on hours to no avail. I run U.S. Cellular and on the newest RR-5.8.1-OMS after I go to Settings>More>Cellular Networks>Crash. Every time. Resets my radio and picks right back up again. Everything works until I'm in my house, then I'm roaming and there's no way to manage in settings because of the crash.
Click to expand...
Click to collapse
Just out of curiosity, have you tried the *22XXX thing yet?
EDIT: Just so we're clear, with you all who have CDMA phones, when you go into "IMEI Information," it does show both an IMEI and an ICCID, right? Because if not, I think I figured out why your LTE isn't working.
I tried, I tried dialing *22999 (guessing that the x stood for the 9 button in T9 language) and pressed the make a call button. Am I wrong about the "XXX" part? Because I did try that when I seen it previously in the thread earlier but had the same thoughts.
So to make that novel a shorter version, what exactly should I dial?
[email protected] said:
I tried, I tried dialing *22999 (guessing that the x stood for the 9 button in T9 language) and pressed the make a call button. Am I wrong about the "XXX" part? Because I did try that when I seen it previously in the thread earlier but had the same thoughts.
So to make that novel a shorter version, what exactly should I dial?
Click to expand...
Click to collapse
It depends on the carrier and the model of the phone. For most Tracfones, it's *22890. For US Cellular, I've seen it as *228 and *22894. You may have to call your carrier and ask what their phone programming code is.
Aaah ok I got you now. Yes I've tried that on nearly every ROM. Matter of fact I just noticed I posted a little off topic almost, but I'm here for the relevance of com.android.phone crashing EVERY SINGLE TIME I try to open Cellular Networks. The only ROM I will say it doesn't force close on is the Slim Nougat ROM, but I don't run that because instead of Cellular Networks settings making com.android.phone crash its when you place a call and then it force closes the UI part of the call but still carries the call through. I forgot to mention that by the way, whatever it is in Slim that is the making the different reason for force closing com.android.phone could probably be a pretty easy red flag for someone better equipped for this Lind of troubleshooting than myself!
Thank you for the suggestion though on the *22(8 in my case)
[email protected] said:
Aaah ok I got you now. Yes I've tried that on nearly every ROM. Matter of fact I just noticed I posted a little off topic almost, but I'm here for the relevance of com.android.phone crashing EVERY SINGLE TIME I try to open Cellular Networks. The only ROM I will say it doesn't force close on is the Slim Nougat ROM, but I don't run that because instead of Cellular Networks settings making com.android.phone crash its when you place a call and then it force closes the UI part of the call but still carries the call through. I forgot to mention that by the way, whatever it is in Slim that is the making the different reason for force closing com.android.phone could probably be a pretty easy red flag for someone better equipped for this Lind of troubleshooting than myself!
Thank you for the suggestion though on the *22(8 in my case)
Click to expand...
Click to collapse
After I posted that, I went back to try and see if Lineage was able to pick up my phone's MEID (even though I use a GSM SIM, the MEID is still tied to the phone hardware). For some reason, Lineage is not reading it, and I think all of your problems are being attributed to that fact.
The way CDMA phones work (and god, do I hate this), is your 2G/3G network is tied to the phone MEID, while the LTE SIM is data only. The OS needs to read both the 14-digit MEID (sometimes shows as a 15 digit IMEI where last digit is 0) as well as the 20 digit ICCID (SIM Number). A phone may also use the SIM number itself as an IMEI (BYOP SIMs do this) by dropping the first five digits of the 20 digit SIM number.
If you phone is showing only one 15 digit number in the system settings, then it's either the MEID OR the SIM, not both. So either you have calling and no LTE, or LTE and no calling. You can't program APN settings because the phone has no idea what ID number to tie APN settings to. This is actually a rather serious conundrum.
Ok ok, makes sense. I checked my Status info, every ROM has dual SIM capability by the way so I don't know if that would effect anything for xt-1607, but I looked at SIM slot 1 info and it reads my MEID correctly with 14 digits. I couldn't find anything about ICCID. My head pounding question here though, why in the hell (pardon the language) is everything flawless on stock, but on every ROM this problem occurs? Here's my next killer, everything works like it should for me, LTE, 3G, Calls, SMS/MMS, just can't change any of the settings due to a force close, AND I put my friends Straight Talk SIM in and it fired right up with no force close when going to change Network settings...?!
[email protected] said:
Ok ok, makes sense. I checked my Status info, every ROM has dual SIM capability by the way so I don't know if that would effect anything for xt-1607, but I looked at SIM slot 1 info and it reads my MEID correctly with 14 digits. I couldn't find anything about ICCID. My head pounding question here though, why in the hell (pardon the language) is everything flawless on stock, but on every ROM this problem occurs? Here's my next killer, everything works like it should for me, LTE, 3G, Calls, SMS/MMS, just can't change any of the settings due to a force close, AND I put my friends Straight Talk SIM in and it fired right up with no force close when going to change Network settings...?!
Click to expand...
Click to collapse
I think you just answered your own question. As stated in PCMag back in 2015, "Nobody makes a Dual-Sim phone compatible with Sprint or Verizon." It legitimately believes your MEID is a GSM-based IMEI, and is attempting to cross the streams, so to speak. And the only way your friend's StraightTalk SIM would work is if it was piggybacking off ATT or TMo's networks (the MEID would have been paired to the other phone causing a mismatch).
If you look at the stock ROM for this phone, you will see a BUNCH of system apps for programming Sprint and Verizon network information. They never made it into the custom ROMs we're using. FWIW, here's my thoughts on the matter. Someone needs to go back and make a single-SIM variant of these ROMs, as well as a flashable ZIP containing the necessary APKs for Android to detect the necessary information correctly. And if that doesn't happen, then everyone who bought an XT-1607 has to ditch their carrier and move to a GSM carrier.
That makes complete and total sense! Because I wasn't thinking this while time of it but I was in Oklahoma at the time where the main towers are AT&T, matter of fact Sprint and U.S. Cellular lose almost all signal right when you hit the county line where I was at. Verizon only gets signal because it's Verizon, lol. Reason I say that is because I was wondering why this whole time I has full signal with LTE coverage and completely list everything when I went hone, because where I live is complete opposite, there is hardly any GSM coverage, we don't even have an AT&T store, just Verizon, Sprint, USC.
So, with that being figured out, my laptop just recently kicked the bucket on me so I'm out for the most part, I do have a trick to swap files in and out of a compressed archive without extracting it in any way! But, it takes a while, not too much longer I guess but nowvi just remembered everything is pretty much .dat files so nevermind that.
Not that this thread isn't the most popular, but where would be the best place to take this request too to get the most attention from it? I mean if I had to go back to stock, so be it, but I'm a little spoiled to the custom life. Lol.
[email protected] said:
Not that this thread isn't the most popular, but where would be the best place to take this request too to get the most attention from it? I mean if I had to go back to stock, so be it, but I'm a little spoiled to the custom life. Lol.
Click to expand...
Click to collapse
IIRC, there is a Verizon thread with 80ish replies, but I think a developer like Squid might need to be made aware of this, so I might copy this into the Lineage thread.
A bit of good news. While reflashing all the time that were force closing when opening cellular networks, I looked in /data/data/com.android.phone/ and was looking, now remember to go back to that directory after I say all this, I found that directory was empty, on all of the Roms. Was curious so I flashed back to stock. Went to the same directory, BOOM! com.android.phone was not empty, in that folder I found 2 folders that were now populated with in:
1: (/files/ )I now had a file named carrierconfig-com.android.carrierconfig- (and after the dash was my ICCID number) so for this directory I need /data/data/com.android.phone/files/carrierconfig-com.android.carrierconfig**ICCID** (replace **ICCID** my ICCID number)
2: then there was this /data/data/com.android.phone/shared_prefs/_has_set_default_values.xml
and
phone/shared_prefs/com.android.phone_preferences.xml
These files are missing on all the Roms, I know this doesn't since everything, but I know for almost a fact it's a good chunk of something that needs to be available. Can I copy these files and move them into place, and set permissions how they were? I ran out of time tonight, and am busy all week so this is mainly for reference I guess. More research told me these files can be edited to change what is available to configure in cellular network settings like option to change from 2G, 3G, LTE, APN, and so on. Sorry for the mess, that's all I have for right now.
[email protected] said:
These files are missing on all the Roms, I know this doesn't since everything, but I know for almost a fact it's a good chunk of something that needs to be available. Can I copy these files and move them into place, and set permissions how they were? I ran out of time tonight, and am busy all week so this is mainly for reference I guess. More research told me these files can be edited to change what is available to configure in cellular network settings like option to change from 2G, 3G, LTE, APN, and so on. Sorry for the mess, that's all I have for right now.
Click to expand...
Click to collapse
That is definitely a major find! My only concern is even if you do that, there might be further missing components that would cause Dialer to crash on startup or some other wacky side effect. However, if you can make it work, then it's possible the proper APN settings will load by default and you'll no longer need to change them.
If you can, go into the System Apps on the stock ROM and look for any APKs branded by/with Sprint, VZW or USCellular, or anything CDMA related. They might be necessary for reading the SIM's ICCID.
That's what I was thinking too, and sadly for me I don't really know EVERYTHING to look for so it'll be mostly out of trial and error for me to figure it out. I wish they didn't compress Roms into .dat so I could use a root explorer to swap between tabs rather than copy, flash the rom, paste files and then if that didn't work start all over on restoring stock, so on and so forth. I miss my laptop. =(
Updates?
Has anyone looked into this further? I'm experiencing the same problem with the latest LineageOS nightly. US Cellular Prepaid with an XT1607.
I noticed that in my case i had to skip the Insert Sim thing on 1st boot. It never did whatever it wanted to there. (Maybe because I have no signal or weak roaming where I live?)
I'm seriously considering trying it from an area that I have good service in..
Before I updated via OTA to 8.1 the Essential was connecting to LTE without issue. Since 8,1 I have to connect to CDMA and 3g in order to user my Dialer, otherwise Server Error is generated. No calls in or out.
I wanted to downgrade Yes rebooted, factory reset, etc.
I searched google up and down with no real answers that work. How do I get Sideload working again? It has to be a simple configuration or driver problem I will assume.
Thanks
Im in the same situation you are in also im on 3g at 1.50mbs up & down i have searched every where....
Exxeviant said:
Im in the same situation you are in also im on 3g at 1.50mbs up & down i have searched every where....
Click to expand...
Click to collapse
Here you go
https://forum.xda-developers.com/showpost.php?p=74920423&postcount=506
wolfu11 said:
Here you go
https://forum.xda-developers.com/showpost.php?p=74920423&postcount=506
Click to expand...
Click to collapse
Thanks. Still stuck using 3G. I can connect to 4G/LTE but cannot make phone calls as I still get the Server Error, Try Again.
Bigdny said:
Thanks. Still stuck using 3G. I can connect to 4G/LTE but cannot make phone calls as I still get the Server Error, Try Again.
Click to expand...
Click to collapse
I wrote that post that he referred you to, and while it worked in Oreo 8.0 it does not seem to work in 8.1 for me either.
Try this:
dial *228 and get a PRL update
reboot
*#*#4636#*#* (it may take a few seconds for it to come up if you do it right after a reboot)
set it to LTE/WCDMA
reboot
(you may have to check in mobile network settings that your APN is set to VZWINTERNET)
Let me know how it works out for you. I know that Verizon doesnt support WCDMA, but it forces you over to the Verizon LTE bands which is more or less the goal of this. For some reason this functions differently than any of the other settings that include LTE in them (believe me, I've tried them).
wolfhelm said:
I wrote that post that he referred you to, and while it worked in Oreo 8.0 it does not seem to work in 8.1 for me either.
Try this:
dial *228 and get a PRL update
reboot
*#*#4636#*#* (it may take a few seconds for it to come up if you do it right after a reboot)
set it to LTE/WCDMA
reboot
(you may have to check in mobile network settings that your APN is set to VZWINTERNET)
Let me know how it works out for you. I know that Verizon doesnt support WCDMA, but it forces you over to the Verizon LTE bands which is more or less the goal of this. For some reason this functions differently than any of the other settings that include LTE in them (believe me, I've tried them).
Click to expand...
Click to collapse
Well I reset my PRL via *228 and sure enough selecting 4G/LTE does put us at LTE/wcdma but my phone functions perfectly. I do notice the menus are changed and I got a couple other options though now. See attached
wolfu11 said:
Well I reset my PRL via *228 and sure enough selecting 4G/LTE does put us at LTE/wcdma but my phone functions perfectly. I do notice the menus are changed and I got a couple other options though now. See attached
Click to expand...
Click to collapse
Yep those are how the menu should look for a device that's not locked to sprint. It seems to me there are some firmware files that prefer sprint in these beta builds, because even on other carriers (and more than one person has said this) you can see 'sprint' pop up in the bar or in the settings even when you arent on sprint.
Interesting that yours gives you the option of 'wifi calling provisioned', I cant get that to not be greyed out on mine.
wolfhelm said:
Yep those are how the menu should look for a device that's not locked to sprint. It seems to me there are some firmware files that prefer sprint in these beta builds, because even on other carriers (and more than one person has said this) you can see 'sprint' pop up in the bar or in the settings even when you arent on sprint.
Interesting that yours gives you the option of 'wifi calling provisioned', I cant get that to not be greyed out on mine.
Click to expand...
Click to collapse
Yeah I've screwed with this phone so much I don't know what I did LOL but now it shows wifi calling even in dialer. I'm not sure if it really works cuz I have a good signal so it never switches. My e911 address is set up from my Moto z and I do have a wear24 watch tied to this phone not sure if that's what triggered it. ? I did get a new SIM card on Monday as well because I was fighting with the vzw crap so I don't know exactly what triggered the WiFi calling.
wolfhelm said:
I wrote that post that he referred you to, and while it worked in Oreo 8.0 it does not seem to work in 8.1 for me either.
Try this:
dial *228 and get a PRL update
reboot
*#*#4636#*#* (it may take a few seconds for it to come up if you do it right after a reboot)
set it to LTE/WCDMA
reboot
(you may have to check in mobile network settings that your APN is set to VZWINTERNET)
Let me know how it works out for you. I know that Verizon doesnt support WCDMA, but it forces you over to the Verizon LTE bands which is more or less the goal of this. For some reason this functions differently than any of the other settings that include LTE in them (believe me, I've tried them).
Click to expand...
Click to collapse
Thank you for the steps but still cannot use 4G for phone calls, but it does work for internet, facebook, email,etc.
Have to go back to 3G for phone calls.
Very interesting why it happening and not widespread. No special configurations or setups on my phone.
Bigdny said:
Thank you for the steps but still cannot use 4G for phone calls, but it does work for internet, facebook, email,etc.
Have to go back to 3G for phone calls.
Very interesting why it happening and not widespread. No special configurations or setups on my phone.
Click to expand...
Click to collapse
Are you on 8.0 or 8.1?
wolfhelm said:
Are you on 8.0 or 8.1?
Click to expand...
Click to collapse
I upgraded to 8.1 via OTA. No root, no rom.
Bigdny said:
I upgraded to 8.1 via OTA. No root, no rom.
Click to expand...
Click to collapse
That's where I'm at too... the one thing that might be different about this is I tried my old steps first before figuring out how to get it to work with these new ones... seems like a lot of effort, but it might be what is needed (or some amount of it) to get it all working. So try going through the old ones before the new ones (you probably dont need to *228 again since you just did)
My old steps linked here (these worked in 8.0, if they work for you in 8.1, more power to you, but they dont work for me):
https://forum.xda-developers.com/showpost.php?p=74920423&postcount=506
I'm still routinely messing with it because I feel like the setting I have now prevents me from falling back to CDMA if LTE is unavailable for some reason. Fortunately that is a rarity for me... but I maintain that Essential has something in the ROM itself that is preferring sprint and I think it's screwing with us using Verizon.
wolfhelm said:
That's where I'm at too... the one thing that might be different about this is I tried my old steps first before figuring out how to get it to work with these new ones... seems like a lot of effort, but it might be what is needed (or some amount of it) to get it all working. So try going through the old ones before the new ones (you probably dont need to *228 again since you just did)
My old steps linked here (these worked in 8.0, if they work for you in 8.1, more power to you, but they dont work for me):
https://forum.xda-developers.com/showpost.php?p=74920423&postcount=506
I'm still routinely messing with it because I feel like the setting I have now prevents me from falling back to CDMA if LTE is unavailable for some reason. Fortunately that is a rarity for me... but I maintain that Essential has something in the ROM itself that is preferring sprint and I think it's screwing with us using Verizon.
Click to expand...
Click to collapse
There is something there.
I've done that procedure.
If I go into the menu and play around it will try to connect to sprint even with a Verizon SIM. Go figure?
tech_head said:
There is something there.
I've done that procedure.
If I go into the menu and play around it will try to connect to sprint even with a Verizon SIM. Go figure?
Click to expand...
Click to collapse
Exactly. If I leave it on certain settings it'll actually sit there and tell me I'm connected to Sprint.
wolfhelm said:
Exactly. If I leave it on certain settings it'll actually sit there and tell me I'm connected to Sprint.
Click to expand...
Click to collapse
I just reported this to Essential in their beta feedback.
Others should report their similar issues.
It seems to be associated with them making a unified release.
If you look at some releases they are specifically for Sprint or Not.
tech_head said:
I just reported this to Essential in their beta feedback.
Others should report their similar issues.
It seems to be associated with them making a unified release.
If you look at some releases they are specifically for Sprint or Not.
Click to expand...
Click to collapse
That's a good point, I have reported as well.
tech_head said:
I just reported this to Essential in their beta feedback.
Others should report their similar issues.
It seems to be associated with them making a unified release.
If you look at some releases they are specifically for Sprint or Not.
Click to expand...
Click to collapse
Doing the same right now. Just glad Im not the only one having the problem.
Bigdny said:
Thank you for the steps but still cannot use 4G for phone calls, but it does work for internet, facebook, email,etc.
Have to go back to 3G for phone calls.
Very interesting why it happening and not widespread. No special configurations or setups on my phone.
Click to expand...
Click to collapse
Try turning off Enchanted 4G LTE Mode. It's possible going to 8.1 just reset this setting to on. This should only be on if you have HD Voice enabled on your line on Verizon (you'll have to call Verizon to enable it, it's a free feature).
This should fix server error on 4G, randomly connecting to Sprint is a separate issue.
UPDATE Now working
Took the advice from someone on Reddit who had the same problem. Ran to VZW store and received a new SIM. Without any programming on my end or reboot, back to LTE without issue. FINALLY. As soon as the rep popped in the SIM the essential connected on its own.
Bigdny said:
Took the advice from someone on Reddit who had the same problem. Ran to VZW store and received a new SIM. Without any programming on my end or reboot, back to LTE without issue. FINALLY. As soon as the rep popped in the SIM the essential connected on its own.
Click to expand...
Click to collapse
Just wanted to second this post that a new sim card is the key to solving this issue. In my case, I was using Red Pocket CDMA (VZW network), and I ran into the same problem. Red Pocket rep explained to me that my sim got provisioned to 3g only and that I needed a new sim to connect to LTE. As soon as we switched to a new sim, I got LTE. I hope this helps others.
I have a new S10+ and the phone can no longer connect to my carriers cellular network. I bought the phone directly from Samsung but put in on the TELUS (Canadian) network. It worked fine until yesterday when I noticed I had no network connection. I rebooted the phone and still no network. I took it to TELUS and they replaced the SIM card and it connected for about 10 minutes and then dropped the connection again. I tried the SIM in my old Note and it seems to work fine. I factory reset my S10+ and this did not solve the issue. Tried to submit a warranty claim to Samsung only to have their web page refuse the request, keep getting and OOPS, something went wrong message!!??
So,,, Everyone listen to this. My brand new S10+ worked for a total of 2 weeks and then wouldn't connect to any carrier network. I called Samsung and they gave me a place to take it to see if it could be repaired. I was told the phone needs a new motherboard. I said no, I need a new phone. You are not selling me a repaired phone for $1800 when it was only two weeks old. They said there was nothing I could do about and on top of that, it would take two weeks before they could repair it. I called Samsung back to discuss and was told that's the way it works, you don't get a new phone just because it doesn't work. Nice customer service SAMSUNG!!!
Sword Fish said:
I have a new S10+ and the phone can no longer connect to my carriers cellular network. I bought the phone directly from Samsung but put in on the TELUS (Canadian) network. It worked fine until yesterday when I noticed I had no network connection. I rebooted the phone and still no network. I took it to TELUS and they replaced the SIM card and it connected for about 10 minutes and then dropped the connection again. I tried the SIM in my old Note and it seems to work fine. I factory reset my S10+ and this did not solve the issue. Tried to submit a warranty claim to Samsung only to have their web page refuse the request, keep getting and OOPS, something went wrong message!!??
Click to expand...
Click to collapse
Read this article, don't know if it also affects Canadian Tellus, but it might give you some clues:
https://www.androidpolice.com/2019/...nal-and-connectivity-issues-on-some-carriers/
Omg this is the same issue i had, i posted in the forst sticky thread under Noobs QnA page 2. Till now nothing can be done just wait for the software updates but if still not resolved will send in
fiqueudrue said:
Omg this is the same issue i had, i posted in the forst sticky thread under Noobs QnA page 2. Till now nothing can be done just wait for the software updates but if still not resolved will send in
Click to expand...
Click to collapse
same here in Australia
I am unable to get any codes using the dialer working.
Sent from my [device_name] using XDA-Developers Legacy app
Mine was more than 4G icon is available, with full service reception, yet cant be able to connect to the internet. Been dropping data connectivity once in like 15 20 mins for a good 40sec to 1 min
If you are on Sprint, this will fix it until a real fix comes:
You must disable Band 41 AND Band 25!. Enter Data Programming Mode: ##3282# Edit -> Enter MSL: 000000 -> OK -> LTE -> Band41 Enabled -> Deselect -> Band25 Enabled - Deselect then Reboot. So far seems to fix the issue. Again, you must disable both Band41 and Band25! Works like a charm Smiley Happy
mzsquared said:
Read this article, don't know if it also affects Canadian Tellus, but it might give you some clues:
https://www.androidpolice.com/2019/...nal-and-connectivity-issues-on-some-carriers/
Click to expand...
Click to collapse
Thanks for this. I sent this link to the shop that is supposed to repair my phone and they said this isn't the same issue as my phone is experiencing. I am not sure how they can say it because it sounds exactly like what my phone is doing. I did try the SIM from my work phone which is on a different carriers network and it wouldn't work either. It would connect at times, at least it would display it was connected but then you wouldn't be able to connect to anything. It even said it was connected once when we had removed the SIM???
dhonzik said:
If you are on Sprint, this will fix it until a real fix comes:
You must disable Band 41 AND Band 25!. Enter Data Programming Mode: ##3282# Edit -> Enter MSL: 000000 -> OK -> LTE -> Band41 Enabled -> Deselect -> Band25 Enabled - Deselect then Reboot. So far seems to fix the issue. Again, you must disable both Band41 and Band25! Works like a charm Smiley Happy
Click to expand...
Click to collapse
Any idea on how to do this for US Cellular?
So this experience turned into one of the worst I have ever had with any consumer product. I tried calling Samsung to see if I could get a new phone and felt like I was talking to some kid in his basement. He had no idea what I was talking about and just kept saying Sorry, I can't do anything about that. So, I let the recommended service center handle the repair of my phone. After having my phone for a week they called and said come get it. When I got there, the tech said, and I quote "Your phone is conditionally fixed". So what does that mean?? He said they put a new motherboard in it, but they put the wrong one in. The one they put in only had 128 gig and was for the non ceramic versions. He asked me if that was ok???? I told him to fix it properly!! So my phone stayed another week with these guys and I finally got it back this past weekend. First thing I noticed was I have all this bloatware from Rogers on my phone. Big problem because I use TELUS, not Rogers, so they loaded the wrong software on my phone and I can't seem to remove it, I can hide it but not remove it. Also, about twice per day, my phone randomly reboots. I start wondering why I am not getting any calls or texts and find my phone rebooted and wants me to type my pin in to enable apps.
So, I called Samsung today to complain again, and I swear I got the same immature brat on the phone again. He told me to take it back to the service guys again. I told him I was going to buy a new phone and it wouldn't be a Samsung. I will file a claim in small claims court to recoup my money I paid for this phone ($1851 CDN).