Help with MotoX Pure on Verizon. Only has cellular data, no voice/sms. - X Style (Pure) Q&A, Help & Troubleshooting

I purchased a used Moto X Pure Edition on Swappa. The phone was rooted, but the seller flashed it back to stock (as far as he told me). I was hoping that I could eventually get the OTA for nougat when it came out, so he assured me that the phone was in "stock" condition.
When I received it, I went to a verizon corp store and got a new sim and they activated the phone on my account. I see 4G LTE and data works great, but when attempting voice calls it says "no cellular network available". SMS messages don't send. I called verizon tech support and we changed some settings around, but it never worked. Guys at the corp store had no clue. The sim works fine in my old verizon galaxy SIII.
Someone on a reddit thread suggested that I check the firmware. It currently reports as: 24.12.18.clark_retus.retus.en.US.retus Does anyone know if this is correct? Is there anything I can do to get this working, or once it's rooted is it really impossible to get it back to stock, or has the seller somehow screwed it up during flashing?
Thanks!
UPDATE: It seems to be fixed after re-flashing the factory image from motorola. I used MPH24.49-18_18 from this page: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images#

I'm on VZN - was rooted running CM13 then Slim Rom then went back to stock (PITA) So it can be done ( my firmware : 24.221.4clark_retus.retus.en.US retus) but why would you want to go stock? I only did thinking we were getting Android N soon but that doesn't seem to be happening. Root the phone and throw a custom Rom on it. You will be happier. Have you checked the network type? and the APN?

MedzHovig said:
I'm on VZN - was rooted running CM13 then Slim Rom then went back to stock (PITA) So it can be done ( my firmware : 24.221.4clark_retus.retus.en.US retus) but why would you want to go stock? I only did thinking we were getting Android N soon but that doesn't seem to be happening. Root the phone and throw a custom Rom on it. You will be happier. Have you checked the network type? and the APN?
Click to expand...
Click to collapse
I've switched the network type (global and then LTE/CDMA). The APN that is default selected is Verizon Internet. But, I've tried all the other APNs as well.
I'm worried at this point that I'll never get it to work with voice, whether it is rooted and rom'd or not.

Try Flashing to CM 13 or Slim6 both worked for me.. Please dont hate me for asking.. you sure you have the sim in the right way? I know this try is tricky

MedzHovig said:
Try Flashing to CM 13 or Slim6 both worked for me.. Please dont hate me for asking.. you sure you have the sim in the right way? I know this try is tricky
Click to expand...
Click to collapse
Not hating. I'll take any help I can get. Yes, I'm certain I put the sim in correctly. Cellular data works, and the phone shows as being on the Verizon network, just not voice enabled.
I'd rather not root and flash at this point, as I'm likely going to return it as non-working. Unless someone has any other ideas?

Well, I guess I fixed it. I reflashed the factory image from this page: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images# and the sim is reporting voice and data, and calls and sms are working. I'm not sure what image the guy that sold it to me flashed, but it was obviously wrong or he didn't do it right. Thanks for the help!

Related

[Q] Note 3 N900W8 Not letting me choose network

I've been trying to fix since installing the new update at 2pm (PST) today. Finally decided to post a question here hoping someone more knowledgeable can help me fix it.
I bought the phone and it was locked to Bell so I bought a code and was using it on Fido. I flashed the Telcel 4.4.2 update and after I flashed all the files it worked (I tried not flashing modem). When it started I got a screen that said "Network Lock" with only a dismiss button (i.e. nowhere to put re-input my unlock code). If I click it 3 times it lets me into device. In the status bar it says "Invalid SIM card" "Network locked SIM card inserted". When I try to make a call I get "Not registered on network"
I've also tried flashing my old modem.bin via ODIN but that just cause the phone to boot and vibrate a bunch. I was able to get into settings but no option for Network Operator or APN.
The network doesn't work but WiFi and everything else does. So I rooted using the new N9005 root. Added APN settings, and of course, looked for network operators. Fido doesn't show up but all other carriers do (except Chatr).
I'm in the same situation as you are but which new N9005 root are you talking about? I'm on Rogers so if I can use that to get my signal back, that would be awesome.
zerojay said:
I'm in the same situation as you are but which new N9005 root are you talking about? I'm on Rogers so if I can use that to get my signal back, that would be awesome.
Click to expand...
Click to collapse
Here>> https://plus.google.com/+Chainfire/posts/QbVy3arpymx
Please post back if you find anything. I've been looking all day and I've given up for the night.
Don't forget to say thanks
JamesKroll said:
Here>> https://plus.google.com/+Chainfire/posts/QbVy3arpymx
Please post back if you find anything. I've been looking all day and I've given up for the night.
Don't forget to say thanks
Click to expand...
Click to collapse
I got the autoroot installed and working fine. It says invalid SIM.
Previously, I had installed the firmware without flashing the CSC and I don't remember having sim lock issues then (as the Telcel specific files are not flashed) however you have to deal with the Samsung keyboard repeatedly crashing, so you have to find a way around it.
So my suggestion is reflash without the CSC file and brainstorm a way to put another keyboard on it without needing to input anything first (so Google Play is a no-go), probably side load a keyboard apk through ADB or something. Going to give it a shot.
---
The keyboard idea worked fine. Unfortunately I did still get the region/sim lock stuff because everywhere outside of Canada seems to have it turned on and the ROM defaults to tmobile without the CSC apparently. I've decided to bite the bullet and just pay for an unlock as I was planning to do so anyways.
---
And that worked until I rebooted and it asked for a SIM unlock code... well... damn. I'm just going to try to flash a rom with region/sim locking removed. Ugh.
Looks like we can fix this by downgrading or creating our own Rogers files: http://forum.xda-developers.com/showthread.php?t=2608178&page=54
I have the CSC and modem.bin. Tested and working (remember, I flashed PIT as said here http://forum.xda-developers.com/showpost.php?p=49512809)
https://www.mediafire.com/?yjdgd4j8s72bo46
I rolled my own too. Working fine.
Sent from my SM-N900W8 using Tapatalk
hi i just found this thread, i have a rogers note 3, unlocked to virgin, i just flashed the mexican rom. it was working the first time but i messed something up so i had to reflash it, and on this second flash it now says region locked sim. and heres the bad news. the original unlock code IS NOT WORKING ANYMORE. wtf do i do now?
evil-doer said:
hi i just found this thread, i have a rogers note 3, unlocked to virgin, i just flashed the mexican rom. it was working the first time but i messed something up so i had to reflash it, and on this second flash it now says region locked sim. and heres the bad news. the original unlock code IS NOT WORKING ANYMORE. wtf do i do now?
Click to expand...
Click to collapse
Same thing was happening to me. Just follow the instructions in my previous post.

Help No Service

Hello everyone,
I'm getting no service on my Sprint Galaxy S4 SPH-L720.
I've tried Slimkat 4.4.2, 5.0.1 and Google Play 5.0.1. I get service at times but it keeps cutting out for no reason. I am on baseband L720VPUFNAE, and PRL version 55020. I'm using an app called Roam Control which keeps the phone on roaming mode but it won't stay connected either. Even when set to force roaming it trys to connect to Sprint service. Perviously it would stay connected to Verizon.
Also on Slimkat 5.0.1 when enabling Roam Control it says "please make sure device is rooted" I know it is, because roam control doesn't give me that error on Slimkat 4.4.2 or Google Play Edition 5.0.1
I started having these issues about a week ago, before that everything was working fine. I was on Google Play Edition for a week, and then I started having these issues and went back to slimkat which worked flawlessly.
So to summarize this, phone will not stay connected to roaming no matter what I do. It wants to go back to Sprint, I've tried calling the ##872283# number or whatever it is. That didn't work, it told me it was unavailable and to try again.
Also, one time my cat knocked my phone off the table and it said no sim card inserted so I rebooted my phone and have been having issues since that day.
Did you check to make sure the SIM card didn't get jarred loose when it fell. If that's not it do you have a backup of your stock Rom you could restore? I have had connection problems before and going back to stock TW Rom restored it.
Hi, thanks for replying
I removed the sim card and put it back in, but that isn't fixing it.
I'm on GPE 5.0.1 latest update. Sometimes Roam Control works, and my phone will stay on roaming network, and sometimes it won't. Whenever I go to switch between Home and Roaming it doesn't want to go back to roaming. I have no idea what's going on.
Hi again,
So this is what i've noticed so far.
Slimkat 4.4.4 = Confirmed working, phone goes in and out of roaming back to Sprint network just fine. All data/mms works perfectly.
Slimkat 4.4.2 = Confirmed working, phone goes in and out of roaming back to Sprint network just fine. All data/mms works perfectly.
GooglePlayEdition 5.0.1 = Phone has intermediate service
Sacs Custom Rom v4 = Phone has no wifi, but the Roam Control works.
Slimkat 5.0.1 (Beta/Alpha) = Phone tells me it isn't rooted.
So the good news is, i've got the phone to be atleast usable now. But I want to know why these other roms are giving me problems, is it the baseband/modem I am using? Which one's am I supposed to be using for these roms?
From what I've read here on xda you have to be on the latest firmware, NG2 to have any success getting lollipop working smoothly. So I would look up how to use Odin to upgrade that. All the rooms that I've flashed recently have mentioned in the op to be sure you're on the latest firmware so it may also help with the other KK rooms.
I'm on Baseband version L720VPUFNAE isn't that the latest one?
No NAE is more than a year old NG2 was released last summer.
Hi,
I went ahead and updated to NG2 baseband using this file http://www.androidfilehost.com/?fid=23622183712458249 and Odin. (I am stating this to help people who might be Googling). It updated my Modem from the NAE one to the NG2 baseband, I am still on Slimkat 4.4.4. I will try flashing Google Play Edition 5.0.1 and see what happens.
Thank you guys for the assistance!
Does everything work the way it should on SK 444? If so make a backup so you have a solid place to revert to if you need it in the future. Also be sure to get a good GPS lock before flashing to a 5.0 Rom.
Yes everything works in Slimkat 4.4.4. The phone goes in and out of roaming without any hiccups. Also what do you mean by make sure you get a good GPS lock?
Furthermore, I have went back to Google Play Edition 5.0.1 and I am still experiencing the issue where my phone does not want to go back to roaming after being on the Sprint network. I will be out of service and the phone will just say "searching for service" even though I have Roam Control set too "Roam Only Mode". In order to get my phone to get service back I have to go into Cellular network settings and select System select and put my phone on Home only and then go back to Automatic to make the phone connect to the roaming network.
This is becoming a real nightmare.
The GPS not working was a common problem with GPS 5.x and having a good lock on your position in a stick TW Rom before flashing to GPE is supposed to fix it. So my comment was merely a preventive one. I have no idea for you on the roaming problem in GPE.
---------- Post added at 02:58 PM ---------- Previous post was at 02:52 PM ----------
Have you tried updating the profile and prl while in SK 444? Then flash into GPE, that's one thing I would try if you haven't done so.
Wonk258 said:
The GPS not working was a common problem with GPS 5.x and having a good lock on your position in a stick TW Rom before flashing to GPE is supposed to fix it. So my comment was merely a preventive one. I have no idea for you on the roaming problem in GPE.
---------- Post added at 02:58 PM ---------- Previous post was at 02:52 PM ----------
Have you tried updating the profile and prl while in SK 444? Then flash into GPE, that's one thing I would try if you haven't done so.
Click to expand...
Click to collapse
How would I go about updating the profile and PRL while in SK 444? It's based off of Cyanogenmod kernal, as is GPE.
trenth said:
How would I go about updating the profile and PRL while in SK 444? It's based off of Cyanogenmod kernal, as is GPE.
Click to expand...
Click to collapse
You must be on a stock touchwiz rom in order to update your data profile or prl.
Sent from my GT-I9505G using Tapatalk
My bad, I meant have you tried updating the prl and profile while in a stock TW rom? My apology for the confusion.
Here's another thought, perhaps try one of the other non GPE 5.x Roms to see if your troubles are limited to the one GPE Rom or if it's a lollipop issue. That may be useful info for those smarter than I to help you work this out.
trenth said:
Hello everyone,
I'm getting no service on my Sprint Galaxy S4 SPH-L720.
I've tried Slimkat 4.4.2, 5.0.1 and Google Play 5.0.1. I get service at times but it keeps cutting out for no reason. I am on baseband L720VPUFNAE, and PRL version 55020. I'm using an app called Roam Control which keeps the phone on roaming mode but it won't stay connected either. Even when set to force roaming it trys to connect to Sprint service. Perviously it would stay connected to Verizon.
Also on Slimkat 5.0.1 when enabling Roam Control it says "please make sure device is rooted" I know it is, because roam control doesn't give me that error on Slimkat 4.4.2 or Google Play Edition 5.0.1
I started having these issues about a week ago, before that everything was working fine. I was on Google Play Edition for a week, and then I started having these issues and went back to slimkat which worked flawlessly.
So to summarize this, phone will not stay connected to roaming no matter what I do. It wants to go back to Sprint, I've tried calling the ##872283# number or whatever it is. That didn't work, it told me it was unavailable and to try again.
Also, one time my cat knocked my phone off the table and it said no sim card inserted so I rebooted my phone and have been having issues since that day.
Click to expand...
Click to collapse
I may be having a related issue. I didn't want to make a separate thread in case this is the case.
My data was just fine about a week ago. Then I decided I'd try out a new ROM because there's a couple things that annoy me with CM12 at the moment, so I tried the GPE ROM. It was all great except I wasn't getting service when I'm at work.
The problem is that this is now the case with EVERY ROM I flash. I also tried nandroid restoring what I had before flashing GPE. I even went back to stock, did the whole PRL and Profile thing, but I still have no service.
What's also a problem is that I have service (LTE) at home, so whenever I get home to try a new thing that will hopefully fix the issue, I can't find out til I go back to work or leave home or whatever. So far, every day has been unsuccessful.
Edit: A weird thing is that even where I have LTE, if I go to view my network status, it shows "Out of service" under Service State, and Mobile Network State as disconnected. Actually just noticed this, but my phone number is 0.
Alright, so further testing has commenced.
I went over to a Touchwiz rom, updated my PRL, activated the phone, and did all of that. Went back to SlimKat 4.4.4 and thought my phone was on "Roam Only". Well turns out I was wrong, the phone is set to Roam Only and I am still trying to connect to Sprint towers while at home (Where I have no Sprint service) so something definately up. Maybe I need to re-root my phone as I am having some weird issues when it comes to root. Can someone perhaps link me to a thread to get started on rooting the device? I don't remember how I did it last year when I bought the phone. But I am comfortable with using Odin and SamsungKey drivers.

[Q] No 4G/LTE in my LG G2 D802.

Hey guys,
As you can read in the tittle, my problem is that I don't have 4G/LTE I get 3G+/3G or HSPA+/HSPA.
Right I'm running Lollipop with the custom ROM, BlissPop with B14ckB1rd Kernel. I tried other ROMs (CM, RR, Paranoid) but I don't get 4G in neither of them.
I lost my 4G a quite ago, don't remember exactly how but I can imagine it was when I tried those early Lollipop builds, after that I went back to KitKat and the 4G was gone, even I tried going to full stock but neither that work.
I'm sure is a phone problem because I been with 2 different carriers and couldn't get 4G. The SIM card is brand new and today I spent around 2 hours talking with the Tech Support of my carrier checking everything is all right.
I also tried to change the Baseband/Modem/Radio (Right now I have Cloudyfa KK for the D802).
This might be also helpful for guess what could be the problem, when I dial *#*#4636#*#* go this phone information, down to prefer network type and select LTE only I lose service, by the way, in that configuration I have selected LTE/GSM/CDMA auto (PRL) and USA radio band.
I'm open for all kind of suggestions, If you need more information don't doubt in asking me.: fingers-crossed:
Asiier said:
Hey guys,
As you can read in the tittle, my problem is that I don't have 4G/LTE I get 3G+/3G or HSPA+/HSPA.
....:
Click to expand...
Click to collapse
I am having exactly the same issue. I have been going around in circles since days. Recking APN settings constantly etc. Going mad. Would be great to find a solution together!
damnation333 said:
I am having exactly the same issue. I have been going around in circles since days. Recking APN settings constantly etc. Going mad. Would be great to find a solution together!
Click to expand...
Click to collapse
Well is good to know I'm not the only one.
Could you share more information?, like when and how it happened, so we can figure out what is wrong.
Today I'm going to try to get some logs, and check the system folder.
It happened to me with stock lollipop v30d vodafone ITA with another carrier sim (TIM). Solved after flashing v30a open ITA kdz.
jnr88 said:
It happened to me with stock lollipop v30d vodafone ITA with another carrier sim (TIM). Solved after flashing v30a open ITA kdz.
Click to expand...
Click to collapse
I'm gonna try it, will send feedback as soon as possible.
Sent from my LG-D802 using xda Forum
No luck, I installed the V30a Italian version as you suggested but as you can in the screenshots no 4G at all, when I try to force LTE (This time with the command 3845#*802#) is lose service like in my last ROM, so I'm almost sure is hardware and not software.
Can some confirm me that, cause when you go back to stock by a kdz or how ever their is not residual imformation, every thing is fully clean right? Or some firmware just stay for ever?
If you guys have more suggestions that could try before I send it to somewhere for get it repair.

Delayed Texts and Unknown Carrier with Custom ROMs (7.1.2 / 8.1) on Verizon S5-G900V

So I have posted before without any replies and am still seeking help...
I know there are others out there in the same situation as me:
On an Unlocked VZW bootloader
On Verizon Wireless 4G LTE in the US
Trying to run a Custom ROM on their phone
But for some reason, I seem to be the only one who has a random delayed texts (both SMS and MMS) issue (by 1-15 minutes) on these forums. Sometimes on Custom ROMs the texts come in normally but other times there is a long delay and it makes having a conversation with people very difficult and irritating. There is NO text delay on rooted (Magisk) QL1, the latest Samsung stock TW S5 6.0.1 ROM, and I have gone back to it since I have no more ideas left to try.
What I have tried:
AEX 5.8 (Oreo 8.1), Havoc OS (8.1), Lineage 15.1 (Latest 8.1), crDroid 3.8.5 (7.1.2), MoKee (7.1.2), AOKP (7.1.2)
Changing APN settings to include the MMSC http://mms.vtext.com/servlets/mms and leave blank which is the default on Custom/Stock ROMs
Changing APN settings to match the stock VZW settings exactly
Flashed new VZW APN files from an ltefix.zip file I found on XDA
Changing CDMA to be Home and not just Automatic
Changing from Global to CDMA/LTE+EVDO
Went to the Verizon store and got a new SIM card
Booted up without SIM and powered off; then inserted SIM and booted up again
Tried different Modem/Non-HLOS versions like QC2 and QL1
Went into the secret *#*#4636#*#* Phone menu to see what differences exist between stock and Custom ROM settings
Added some lines from the stock VZW Build Prop to Custom ROM Build Prop
Removing HD Voice/VoLTE from my Verizon account
Avoided installing any apps after flashing a Custom ROM to see if the problem remained
Nothing worked! Still get Delayed Texts trying everything I could think of, except when on the stock VZW ROM. Custom ROMs may boot up showing my carrier as Verizon Wireless, but then after some random amount of time will show the Carrier as either "Unknown" (7.1.2) or "Roaming Indicator Off" (8.1). It is usually at that time when the Delayed Texts issue arises once the phone loses its lock on Verizon.
This makes me think it is a Verizon Band issue where for some reason not enough Bands are available for my phone to use on these Non-Verizon Custom ROMs. Or it could have something to do with VoLTE being active on my account at one point (I turned it off on My Verizon to try to combat this problem). Or maybe something to do with how we all unlocked the bootloader in the same way.
But what I don't understand is why I am the only person with this issue since I am pretty sure there are a lot of people on Verizon with CID 15 on Custom ROMs who don't seem to be mentioning this problem!
Any thoughts on how to fix it? Could it be a matter of augmenting the Bands my phone has access to on the Custom ROMs?
Thank you very much!
Drew
drewcu said:
So I have posted before without any replies and am still seeking help...
I know there are others out there in the same situation as me:
On an Unlocked VZW bootloader
On Verizon Wireless 4G LTE in the US
Trying to run a Custom ROM on their phone
But for some reason, I seem to be the only one who has a random delayed texts (both SMS and MMS) issue (by 1-15 minutes) on these forums. Sometimes on Custom ROMs the texts come in normally but other times there is a long delay and it makes having a conversation with people very difficult and irritating. There is NO text delay on rooted (Magisk) QL1, the latest Samsung stock TW S5 6.0.1 ROM, and I have gone back to it since I have no more ideas left to try.
What I have tried:
AEX 5.8 (Oreo 8.1), Havoc OS (8.1), Lineage 15.1 (Latest 8.1), crDroid 3.8.5 (7.1.2), MoKee (7.1.2), AOKP (7.1.2)
Changing APN settings to include the MMSC http://mms.vtext.com/servlets/mms and leave blank which is the default on Custom/Stock ROMs
Changing APN settings to match the stock VZW settings exactly
Flashed new VZW APN files from an ltefix.zip file I found on XDA
Changing CDMA to be Home and not just Automatic
Changing from Global to CDMA/LTE+EVDO
Went to the Verizon store and got a new SIM card
Booted up without SIM and powered off; then inserted SIM and booted up again
Tried different Modem/Non-HLOS versions like QC2 and QL1
Went into the secret *#*#4636#*#* Phone menu to see what differences exist between stock and Custom ROM settings
Added some lines from the stock VZW Build Prop to Custom ROM Build Prop
Removing HD Voice/VoLTE from my Verizon account
Avoided installing any apps after flashing a Custom ROM to see if the problem remained
Nothing worked! Still get Delayed Texts trying everything I could think of, except when on the stock VZW ROM. Custom ROMs may boot up showing my carrier as Verizon Wireless, but then after some random amount of time will show the Carrier as either "Unknown" (7.1.2) or "Roaming Indicator Off" (8.1). It is usually at that time when the Delayed Texts issue arises once the phone loses its lock on Verizon.
This makes me think it is a Verizon Band issue where for some reason not enough Bands are available for my phone to use on these Non-Verizon Custom ROMs. Or it could have something to do with VoLTE being active on my account at one point (I turned it off on My Verizon to try to combat this problem). Or maybe something to do with how we all unlocked the bootloader in the same way.
But what I don't understand is why I am the only person with this issue since I am pretty sure there are a lot of people on Verizon with CID 15 on Custom ROMs who don't seem to be mentioning this problem!
Any thoughts on how to fix it? Could it be a matter of augmenting the Bands my phone has access to on the Custom ROMs?
Thank you very much!
Drew
Click to expand...
Click to collapse
When you are on stock you are seeing the verizon lte correct? It not showing unkown?
I have a CID 15 I can try and see if that one is having an issues. it has an older lineage rom on it but it should still work for a test.
Fear_The_Fluff said:
When you are on stock you are seeing the verizon lte correct? It not showing unkown?
I have a CID 15 I can try and see if that one is having an issues. it has an older lineage rom on it but it should still work for a test.
Click to expand...
Click to collapse
Yes, stock shows Verizon as the Network in Settings/About Phone/Status and Verizon Wireless as Carrier and LTE as Type in the secret phone settings page I get to through the app Advanced Signal Status.
Appreciate your assistance in testing Lineage on your CID 15. Since no one else seems to be complaining I have a feeling it will show as Verizon as you'd expect. Feels very lonely on my island lol, but at least rooted stock with Xposed is livable for now.
drewcu said:
Yes, stock shows Verizon as the Network in Settings/About Phone/Status and Verizon Wireless as Carrier and LTE as Type in the secret phone settings page I get to through the app Advanced Signal Status.
Appreciate your assistance in testing Lineage on your CID 15. Since no one else seems to be complaining I have a feeling it will show as Verizon as you'd expect. Feels very lonely on my island lol, but at least rooted stock with Xposed is livable for now.
Click to expand...
Click to collapse
No issues with my S5, but I later remembered this post:
https://forum.xda-developers.com/galaxy-s5/help/solved-unknown-baseband-fixed-t3680402
Try it, I know it was a huge problem awhile back, maybe this will help you.
Fear_The_Fluff said:
No issues with my S5, but I later remembered this post:
https://forum.xda-developers.com/galaxy-s5/help/solved-unknown-baseband-fixed-t3680402
Try it, I know it was a huge problem awhile back, maybe this will help you.
Click to expand...
Click to collapse
Thanks for trying! Assume you waited a while with the S5 in Lineage before responding because mine will start as Verizon but then after 1-30 minutes will switch over to Unknown.
Yeah I recently came across the same post in my research on this. Seems like most of the people who used that guide weren't able to do anything with their modem like call or had missing SIM card messages. I have always had the ability to call except when I debloated the stock ROM too much lol! I am hesitant to start deleting modem files and find myself in worse trouble than I am in now when stock works perfectly (aside from the lagginess).
Besides this issue with Lineage Oreo, I also found AOSP Extended Oreo to be a huge battery hog because my phone ran HOT (but maybe it's related to my main modem? issue). On stock, I almost never find the thing getting warm, it's just not as smooth as Oreo is. I am going to let S5 Oreo mature further and improve on the battery performance before going back to it I think and just stay on working stock for now. If I had concrete evidence that my daily driver could be fixed without any risk, I might consider following instructions.
Appreciate your assistance regardless since no one else has really made any suggestions!
Thank you!
Drew
drewcu said:
Thanks for trying! Assume you waited a while with the S5 in Lineage before responding because mine will start as Verizon but then after 1-30 minutes will switch over to Unknown.
Yeah I recently came across the same post in my research on this. Seems like most of the people who used that guide weren't able to do anything with their modem like call or had missing SIM card messages. I have always had the ability to call except when I debloated the stock ROM too much lol! I am hesitant to start deleting modem files and find myself in worse trouble than I am in now when stock works perfectly (aside from the lagginess).
Besides this issue with Lineage Oreo, I also found AOSP Extended Oreo to be a huge battery hog because my phone ran HOT (but maybe it's related to my main modem? issue). On stock, I almost never find the thing getting warm, it's just not as smooth as Oreo is. I am going to let S5 Oreo mature further and improve on the battery performance before going back to it I think and just stay on working stock for now. If I had concrete evidence that my daily driver could be fixed without any risk, I might consider following instructions.
Appreciate your assistance regardless since no one else has really made any suggestions!
Thank you!
Drew
Click to expand...
Click to collapse
I tried this one once when my old sprint S5 didn't have 4G. I ended up with no network at all, I had to do a forget network and reboot to get everything back. I never got that phone fixed I know there is another forum about that issue as well:
https://forum.xda-developers.com/galaxy-s5/help/galaxy-s5-galaxy-note-3-sprint-help-t3698708
Most people were able to get it fixed by replacing the SIM, but since you did that I didn't mention this post.
UPDATE:
Forgot to ask, have you tried a different messenger? I know it wont fix you unknown errors but I thought I'd ask. Also, when you did the modem update, was it this update: https://forum.xda-developers.com/verizon-galaxy-s5/development/modem-modems-t3154630
Fear_The_Fluff said:
I tried this one once when my old sprint S5 didn't have 4G. I ended up with no network at all, I had to do a forget network and reboot to get everything back. I never got that phone fixed I know there is another forum about that issue as well:
https://forum.xda-developers.com/galaxy-s5/help/galaxy-s5-galaxy-note-3-sprint-help-t3698708
Most people were able to get it fixed by replacing the SIM, but since you did that I didn't mention this post.
UPDATE:
Forgot to ask, have you tried a different messenger? I know it wont fix you unknown errors but I thought I'd ask. Also, when you did the modem update, was it this update: https://forum.xda-developers.com/verizon-galaxy-s5/development/modem-modems-t3154630
Click to expand...
Click to collapse
Thanks for the quick reply!
You tried the deleting the modems fix or the link in your prior post for your Spring S5? And what is a "forget network" fix -- just resetting all network settings in Android?
Yeah I was really hoping the replacement SIM would fix it but sadly it was a dead end.
I have tried several messengers like the stock Lineage one, Google Messenger, and landed on Textra because it has the most configuration options.
Yeah I tried Odining modems from both the link you referenced and extracting them myself from the firmware. Not sure if this is essentially the same thing as overwriting the modems in the corrupted TWRP modem guide. I am tempted to try this over the weekend after making an EFS backup. Hard for me to believe that deleting modemst1 partitions and not restoring them afterwards as is what seems to be the fix... Does the system automatically rebuild them or something?
Fear_The_Fluff said:
No issues with my S5, but I later remembered this post:
https://forum.xda-developers.com/galaxy-s5/help/solved-unknown-baseband-fixed-t3680402
Try it, I know it was a huge problem awhile back, maybe this will help you.
Click to expand...
Click to collapse
So I decided to bite the bullet and run the dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1 and 2 in TWRP terminal and got the "No space left on device" in the output (tried over ADB with the same result). Supposedly this isn't necessarily a bad thing as evidenced https://forum.xda-developers.com/showpost.php?p=68532486&postcount=115. Had no problems on stock after doing this (but had no problems on stock prior either).
Then I switched back to AOSP Extended 5.8 (Oreo) and sadly I got the Roaming Indicator Off right away. I tried zeroing out the modemst's again with the same No Space result and back in Oreo got the same delayed texts and Roaming Indicator Off after a few minutes. Dead end, but at least I tried I guess. I am back on stock and my only other thought is to unlock some LTE bands but that may be too technical for me to bother with. Stock works with the current bands so I wonder why I should have to do that on Lineaage.
drewcu said:
So I decided to bite the bullet and run the dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1 and 2 in TWRP terminal and got the "No space left on device" in the output (tried over ADB with the same result). Supposedly this isn't necessarily a bad thing as evidenced https://forum.xda-developers.com/showpost.php?p=68532486&postcount=115. Had no problems on stock after doing this (but had no problems on stock prior either).
Then I switched back to AOSP Extended 5.8 (Oreo) and sadly I got the Roaming Indicator Off right away. I tried zeroing out the modemst's again with the same No Space result and back in Oreo got the same delayed texts and Roaming Indicator Off after a few minutes. Dead end, but at least I tried I guess. I am back on stock and my only other thought is to unlock some LTE bands but that may be too technical for me to bother with. Stock works with the current bands so I wonder why I should have to do that on Lineaage.
Click to expand...
Click to collapse
This bug has been around for awhile and affects all S5s differently and at different times. There are still S5s that work great, who knows if they will ever gets this bug. You may want go to the Lineage post on XDA to see if they maybe able to help you. Maybe something has changed since I gave up on my S5. Good Luck!
Fear_The_Fluff said:
This bug has been around for awhile and affects all S5s differently and at different times. There are still S5s that work great, who knows if they will ever gets this bug. You may want go to the Lineage post on XDA to see if they maybe able to help you. Maybe something has changed since I gave up on my S5. Good Luck!
Click to expand...
Click to collapse
Can you do me one more favor and tell me if your CID is 1501004d414732474300bd6d97165100 (think we all have the same)? Not sure if my problem relates to the way my S5 was unlocked as I originally used one of the early unlock methods (wipe the SD) from https://forum.xda-developers.com/ve...t/rd-unlocking-galaxys-s5-bootloader-t3337909. Thanks!
drewcu said:
Can you do me one more favor and tell me if your CID is 1501004d414732474300bd6d97165100? Not sure if my problem relates to the way my S5 was unlocked as I originally used one of the early unlock methods (wipe the SD) from https://forum.xda-developers.com/ve...t/rd-unlocking-galaxys-s5-bootloader-t3337909. Thanks!
Click to expand...
Click to collapse
My Verizon S5 (this is the working phone) is a CID 15 (I don't have the phone with me right now to get the CID ID), I can look around for the setup I used. It was some months ago when I ran the bootloader unlock and root. BUT! the phone I had an issue with the LTE was a sprint S5 that was unlocked for years before they started locking the bootloaders. This bug affects all carriers, but mostly sprint and verizon.
drewcu said:
Can you do me one more favor and tell me if your CID is 1501004d414732474300bd6d97165100 (think we all have the same)? Not sure if my problem relates to the way my S5 was unlocked as I originally used one of the early unlock methods (wipe the SD) from https://forum.xda-developers.com/ve...t/rd-unlocking-galaxys-s5-bootloader-t3337909. Thanks!
Click to expand...
Click to collapse
Here is the root I used: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
Fear_The_Fluff said:
Here is the root I used: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
Click to expand...
Click to collapse
Thanks yeah that's the more recent method and I am just trying to figure out if that results in the same CID I have. If not, there may be some issue because I am using the same CID as others. But perhaps we all are using the same CID and then I can cross that theory off my long list haha. When you get a chance, can you please check the CID of the Verizon S5 you have?
Thanks!
drewcu said:
Thanks yeah that's the more recent method and I am just trying to figure out if that results in the same CID I have. If not, there may be some issue because I am using the same CID as others. But perhaps we all are using the same CID and then I can cross that theory off my long list haha. When you get a chance, can you please check the CID of the Verizon S5 you have?
Thanks!
Click to expand...
Click to collapse
The CID doesn't change, its just the Chip ID of the phone. You either have the CID 11, which you wouldn't be able to unlock the boot loader let alone put lineage on it. Then there's the CID 15 which does let you unlock the boot loader. I never used the CID checker I ended up finding out if I had a 15 by going to this forum: https://forum.xda-developers.com/verizon-galaxy-s5/help/to-id-cid-15-loading-app-t3756413
Now, with that being said, could there be some sort of correlation between a CID 15 with a specific version number and the bug? Its possible, I could have a different CID 15 version than you and that one may not be affected. Who knows
Fear_The_Fluff said:
The CID doesn't change, its just the Chip ID of the phone. You either have the CID 11, which you wouldn't be able to unlock the boot loader let alone put lineage on it. Then there's the CID 15 which does let you unlock the boot loader. I never used the CID checker I ended up finding out if I had a 15 by going to this forum: https://forum.xda-developers.com/verizon-galaxy-s5/help/to-id-cid-15-loading-app-t3756413
Now, with that being said, could there be some sort of correlation between a CID 15 with a specific version number and the bug? Its possible, I could have a different CID 15 version than you and that one may not be affected. Who knows
Click to expand...
Click to collapse
Pretty sure this whole unlocking the bootloader on CID 15 requires that you change your CID to match the Developer CID. I know that my current CID is referenced in the thread https://forum.xda-developers.com/ve...locking-galaxys-s5-bootloader-t3337909/page39 back when this was all just coming out (and when I first unlocked it using the old method 4 - https://forum.xda-developers.com/ve...t/rd-unlocking-galaxys-s5-bootloader-t3337909). I used to have a different CID that's saved somewhere else.
Any chance you can look your CID to see if it matches 1501004d414732474300bd6d97165100?
Thanks!

Flashing unlocked Samsung S10+ to T-Mobile Firmware

Hey guys, first time on this forum and I am trying to figure things out. I never flashed a firmware so im a noob to this, but I can definitely follow along. Here is my main concern:
Seems like you need a T-Mobile device to get access to features like advanced messaging, visual voicemail, wifi calling, etc. Things I use all the time, but I never knew it would be taken away if I purchased an unlocked S10 plus.
My main goal is to get these features back, which from what I understand requires flashing the firmware? If there is any other way I am more than open to listen to it!
I have Odin and downloaded the "userdata" linked into this post: https://forum.xda-developers.com/galaxy-s10/how-to/g975u-g975u1-firmware-links-t3905897 specifically USERDATA_TMB_G975USQU1ASAT_CL15296297_QB21819666_REV00_user_low_ship_MULTI_CERT.zip
I figure I unzip to get the tar file, select Odin use data and only flash this file? Kinda clueless about all this.
In addition, if I were to flash I hope that Samsung Pay, Knox, finance apps will still work; also the warranty is still good. I know that rooting the device will/may make these unusable, but I just want to confirm.
Any guidance is greatly appreciated, thanks!
mdiddyshow said:
Hey guys, first time on this forum and I am trying to figure things out. I never flashed a firmware so im a noob to this, but I can definitely follow along. Here is my main concern:
Seems like you need a T-Mobile device to get access to features like advanced messaging, visual voicemail, wifi calling, etc. Things I use all the time, but I never knew it would be taken away if I purchased an unlocked S10 plus.
My main goal is to get these features back, which from what I understand requires flashing the firmware? If there is any other way I am more than open to listen to it!
I have Odin and downloaded the "userdata" linked into this post: https://forum.xda-developers.com/galaxy-s10/how-to/g975u-g975u1-firmware-links-t3905897 specifically USERDATA_TMB_G975USQU1ASAT_CL15296297_QB21819666_REV00_user_low_ship_MULTI_CERT.zip
I figure I unzip to get the tar file, select Odin use data and only flash this file? Kinda clueless about all this.
In addition, if I were to flash I hope that Samsung Pay, Knox, finance apps will still work; also the warranty is still good. I know that rooting the device will/may make these unusable, but I just want to confirm.
Any guidance is greatly appreciated, thanks!
Click to expand...
Click to collapse
WiFi Calling, VoLTE are working just fine, but I get what you mean... I mostly flashed 4 firmware files: BL, AP, CL and CSC and couple of times did flash USERDATA too. As userdata file was not required to be flashed unless you want all bloatware from the carrier. Don't know if S10 needs this "userdata" file. You would want to flash I mentioned and specifically flash CSC file and not the HOME CSC(as it usually retains user data on your phone) and in your case you want odin to wipe the device. I want to flash too, but waiting for firmware to become available on sammobile website
Charkatak said:
WiFi Calling, VoLTE are working just fine, but I get what you mean... I mostly flashed 4 firmware files: BL, AP, CL and CSC and couple of times did flash USERDATA too. As userdata file was not required to be flashed unless you want all bloatware from the carrier. Don't know if S10 needs this "userdata" file. You would want to flash I mentioned and specifically flash CSC file and not the HOME CSC(as it usually retains user data on your phone) and in your case you want odin to wipe the device. I want to flash too, but waiting for firmware to become available on sammobile website
Click to expand...
Click to collapse
Basically I should wait for Sammobile to upload those 4 firmware files (BL,AP,CL,CSC) and then use Odin to flash the firmware. Seems the instructions for that are really easy.
As far as the Samsung pay / finance apps, would it mess those up like rooting the device?
mdiddyshow said:
Basically I should wait for Sammobile to upload those 4 firmware files (BL,AP,CL,CSC) and then use Odin to flash the firmware. Seems the instructions for that are really easy.
As far as the Samsung pay / finance apps, would it mess those up like rooting the device?
Click to expand...
Click to collapse
There should be no issue with Samsung Pay and other apps, as you would be flashing official Samsung firmware. Wait for firmware files to be available and then you would be able to see which files will be included and go from there. On my unlocked S8, I didn't flash userdata file and still had all T-Mobile features you were mentioning. If with S10 we will have the same, then skipping userdata is better as the device is pretty much clean without unneeded apps
I installed T-Mobile's Visual Voicemail app from Play Store, and it works just fine. (Unlocked S10)
I did the same. Figured if I was paying outright might as well get an unlocked device. But the Samsung's from tmobile have the multi line function and I'm trying to get rid of my iPhone. But I use that number alot as well. So that multi line function built in for DIGITS worked for me. If you flash it let me know if it has it built in
Sent from my SM-G973U1 using Tapatalk
bradbutter said:
I did the same. Figured if I was paying outright might as well get an unlocked device. But the Samsung's from tmobile have the multi line function and I'm trying to get rid of my iPhone. But I use that number alot as well. So that multi line function built in for DIGITS worked for me. If you flash it let me know if it has it built in
Sent from my SM-G973U1 using Tapatalk
Click to expand...
Click to collapse
Wait. How did you get the multi line functioning on the s10? I have been scouring the internet for a solution
Curious, are there any features/capabilities that the unlocked version has, but the TMobile version does not? I ordered an unlocked S10+ (haven't received it yet) and TMobile is my carrier.
From what I've read so far, built-in caller ID, and the ability to turn mobile data off, are not on the TMobile variant, but I can't confirm that.
mosi76 said:
Wait. How did you get the multi line functioning on the s10? I have been scouring the internet for a solution
Click to expand...
Click to collapse
I don't. I have the unlocked version. But I have tmobile. Didn't think about it until I received my device. So If flashing the tmobile software will give it to me i will flash it.
Sent from my SM-G973U1 using Tapatalk
Thanks for the info too! I am also quite curious about this as I have an unlocked S10+ still pre-ordered. Unfortunately, it's too late for me to cancel it and re-ordering it on T-Mobile before April comes around as I would like to use the phone on my travels by then (still hanging on to my S5 at the moment... lol).
From what I've read, the two major features lost on unlocked phones are EVS and RCS messaging. While RCS messaging is something I can live without, I would really like to keep the EVS (Enhanced Voice Service) feature usable on the phone when it arrives.
One other question, are you able to get the updates via T-Mobile on the flashed firmware or does it have to be flashed again for future updates?
KunoMochi said:
Thanks for the info too! I am also quite curious about this as I have an unlocked S10+ still pre-ordered. Unfortunately, it's too late for me to cancel it and re-ordering it on T-Mobile before April comes around as I would like to use the phone on my travels by then (still hanging on to my S5 at the moment... lol).
From what I've read, the two major features lost on unlocked phones are EVS and RCS messaging. While RCS messaging is something I can live without, I would really like to keep the EVS (Enhanced Voice Service) feature usable on the phone when it arrives.
One other question, are you able to get the updates via T-Mobile on the flashed firmware or does it have to be flashed again for future updates?
Click to expand...
Click to collapse
What is EVS? Is that just another term for VoLTE?
Sent from my ZTE A2017U using Tapatalk
Kjn246 said:
What is EVS? Is that just another term for VoLTE?
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
VoLTE and EVS are different. EVS is an evolution of the AMR-WB speech codec (aka HD Voice) whereas VoLTE uses said speech codecs to work. VoLTE is currently recommended to use at least AMR-WB for good voice quality. As EVS is the newer speech codec that uses similar concepts to that of AMR-WB, it is backwards compatible with technologies already using AMR-WB, which includes VoLTE.
That is what I can gather, feel free to correct me if I am wrong in any of the details.
Thanks to all for their insight. Just an update:
I flashed the T-Mo firmware on my unlocked S10+. It worked - RCS and video calling are back! However I noticed 3 things: 1st I used the CSC, but it did not delete all my apps. 2nd when the device rebooted after flashing it went into recovery mode (is this normal?), but i re-rebooted it and it went right into my phone.
3rd while RCS is working on the phone and between my Android 8.0 Note8 Tmo phone, the Note8 cannot send pictures/files to my S10+. The S10+ can send anything to me, but not the other way around. Read, Delivered, typing indicators work. I am not too concerned about this as I am getting an S10+ myself next week so this will not be an issue.
Any thoughts about that?
Other than the RCS thing, the S10+ device is working completely normally. I heard you have to change the CSC on the device but I did not do that (echo, adb, and all that jazz) - is that necessary as well?
Lots of random thoughts over here!
mdiddyshow said:
Thanks to all for their insight. Just an update:
I flashed the T-Mo firmware on my unlocked S10+. It worked - RCS and video calling are back! However I noticed 3 things: 1st I used the CSC, but it did not delete all my apps. 2nd when the device rebooted after flashing it went into recovery mode (is this normal?), but i re-rebooted it and it went right into my phone.
3rd while RCS is working on the phone and between my Android 8.0 Note8 Tmo phone, the Note8 cannot send pictures/files to my S10+. The S10+ can send anything to me, but not the other way around. Read, Delivered, typing indicators work. I am not too concerned about this as I am getting an S10+ myself next week so this will not be an issue.
Any thoughts about that?
Other than the RCS thing, the S10+ device is working completely normally. I heard you have to change the CSC on the device but I did not do that (echo, adb, and all that jazz) - is that necessary as well?
Lots of random thoughts over here!
Click to expand...
Click to collapse
Would you be able to help walk me through the process to do this. I used to root and flash custom roms to phones but the carrier specific and Samsung stuff is new to me. I'm interested in getting on the TMO firmware possibly for RCS but I don't know if it's worth the hassle for it yet
mdiddyshow said:
Thanks to all for their insight. Just an update:
I flashed the T-Mo firmware on my unlocked S10+. It worked - RCS and video calling are back! However I noticed 3 things: 1st I used the CSC, but it did not delete all my apps. 2nd when the device rebooted after flashing it went into recovery mode (is this normal?), but i re-rebooted it and it went right into my phone.
3rd while RCS is working on the phone and between my Android 8.0 Note8 Tmo phone, the Note8 cannot send pictures/files to my S10+. The S10+ can send anything to me, but not the other way around. Read, Delivered, typing indicators work. I am not too concerned about this as I am getting an S10+ myself next week so this will not be an issue.
Any thoughts about that?
Other than the RCS thing, the S10+ device is working completely normally. I heard you have to change the CSC on the device but I did not do that (echo, adb, and all that jazz) - is that necessary as well?
Lots of random thoughts over here!
Click to expand...
Click to collapse
Thanks for that update.
By any chance, could you let us know if the built in VVM is working? (accessed from the dialer by tapping the 3-dot menu button ((from within Dialer)). You should see Visual Voicemail as an option, not just Voicemail.
I flashed the TMo firmware as well, but used Home_CSC. That didn't seem to matter, since Userdata wipes the phone anyways, but I'm curious as to whether that is why I am not seeing Visual Voicemail.
As for the booting into recovery, did you have the reboot option checked in Odin when you started the flash? Mine has booted to recovery before, but it has always been because I forgot to check that box.
jordanyork said:
Thanks for that update.
By any chance, could you let us know if the built in VVM is working? (accessed from the dialer by tapping the 3-dot menu button ((from within Dialer)). You should see Visual Voicemail as an option, not just Voicemail.
I flashed the TMo firmware as well, but used Home_CSC. That didn't seem to matter, since Userdata wipes the phone anyways, but I'm curious as to whether that is why I am not seeing Visual Voicemail.
As for the booting into recovery, did you have the reboot option checked in Odin when you started the flash? Mine has booted to recovery before, but it has always been because I forgot to check that box.
Click to expand...
Click to collapse
So I have another update about this. When I included the userdata in Odin it reset my device. The visual voicemail is not working still, and i can't confirm (or i dont know how to confirm) if wifi calling or VoLTE is working as there isn't any real indication on the device. But all my RCS problems have been fixed!
...Except that all my MMS contains the "Subject: No Subject" header on every single MMS. Every. Single. One. I had to change my default messages app because this was just too damn annoying.
and yeah, i did check the box.
mdiddyshow said:
So I have another update about this. When I included the userdata in Odin it reset my device. The visual voicemail is not working still, and i can't confirm (or i dont know how to confirm) if wifi calling or VoLTE is working as there isn't any real indication on the device. But all my RCS problems have been fixed!
...Except that all my MMS contains the "Subject: No Subject" header on every single MMS. Every. Single. One. I had to change my default messages app because this was just too damn annoying.
and yeah, i did check the box.
Click to expand...
Click to collapse
Is there a voicemail icon in the dialer after flashing? Or it's still not there?
---------- Post added at 03:48 PM ---------- Previous post was at 03:47 PM ----------
WiFi calling option is within the phone app settings itself, and it would word even without flashing tmo
Anyone know if flashing tmobiles firmware onto the unlocked s10 will void warranty? if so id rather just get the locked tmobile version.
Low_Key_Slaps said:
Anyone know if flashing tmobiles firmware onto the unlocked s10 will void warranty? if so id rather just get the locked tmobile version.
Click to expand...
Click to collapse
No. This does not trip knox, nor will it void your warranty. Tampering such as flashing unofficial software will incr the Knox counter. This matters because technicians inspect the software state (among other things during checkups).
Assuming they actually verify it, the device will fail this step (not the case when using signed packages from Samsung for conversion!). .
Ace42 said:
No. This does not trip knox, nor will it void your warranty. Tampering such as flashing unofficial software will incr the Knox counter. This matters because technicians inspect the software state (among other things during checkups).
Assuming they actually verify it, the device will fail this step (not the case when using signed packages from Samsung for conversion!). .
Click to expand...
Click to collapse
I spoke with a Samsung care rep on their website, who told me it will void the warranty. But then again, most customer care reps dont actually know what their talking about beyond the basic questions...

Categories

Resources