This thread is dedicated to those users with a Sprint compatible (Sprint, Boost, Virgin Mobile USA, TextNow) Moto G3 (xt1548) who wish to convert their device into a Virgin Mobile Data Done Right variant by means of a full partition flash. In other words, a complete partition dump from a Data Done Right Moto G3 can be flashed to a Sprint, Boost, TextNow, or Virgin Mobile USA variant for full conversion to a Data Done Right variant. This conversion, due to MEID and other device IDs, is limited in terms of its ability to be activated on the Virgin Mobile DDR network. In other words, a converted device will not register in Virgin Mobile's system as a DDR device. However, your converted device can nevertheless connect to the DDR network with a properly provisioned and paired UICC. (Note: this method does not alter, modify, edit, change or otherwise clone any device IDs such as MEID, IMEI, MAC Address, etc, and is otherwise fully compliant with XDA rules and state & federal law). This thread is also dedicated to general topics regarding the xt1548 Moto G3 Virgin Mobile Data Done Right variant, which is a separate variant from the Moto G3 Virgin Mobile USA device.
Also, as this thread grows, so will the abundance of information and available firmware files needed for this task. This thread is not geared toward instruction or guidance on the notorious Data Done Right loophole. Upon converting your device to a DDR variant, connecting to the DDR network, UICC provisioning, etc., is entirely up to the user. I will not provide information on subjects regarding the DDR loophole. However sparse, there are a few threads here on XDA which provide information on that particular subject.
Sent from my MotoG3 using XDA Forums
First, it is noteworthy in opening this thread to point out that the APN Settings for Internet and MMS for the Data Done Right network are not the same settings as the Virgin Mobile USA variant. Your Data Done Right (hereinafter "DDR") APN Settings for LTE/4G Data and MMS should be set as such:
Virgin Mobile LTE
APN: n.ij.ispsn
Username: Sprint
Password: *
MMSC: http://mms.sprintpcs.com
MMS Proxy: 68.28.31.7
MMS Port: 80
APN Type: mms,default,fota,supl,hipri,dun
APN Protocol: IPv4
APN Roaming Protocol: IPv4
Bearer: LTE
(Any fields not noted should be left blank or default).
A common misconception of Virgin Mobile USA and Virgin Mobile DDR is that the two are the same network and utilize the same APN & Network Settings. In fact, Virgin Mobile DDR is a completely separate network from Virgin Mobile USA and the two are not compatible or transferrable from one to the other. Although both are MVNO subsidiaries of Sprint, they are two separate and distinct entities in regards of networks. So, a Virgin Mobile USA account on a Moto G3 can not be transferred to to a Virgin Mobile DDR account and vice versa. Although the DDR line of devices were discontinued from retail sales from Walmart around a year or so ago, the network itself is still in full operation and its plans are still fully available. As such, Virgin Mobile retailed two variants of its Moto G3 xt1548: the Virgin Mobile USA variant and the Virgin Mobile DDR variant. Owners of the DDR variant can reach Customer Service at 1-844-326-1261.
MotoJunkie01 said:
APN Type: mms,default,fota,supl,hipri,fun
Click to expand...
Click to collapse
APN Type 'fun' ?!?! lol... I think you mean 'dun', I have never heard of a APN type of fun, although it was enough to give me a chuckle reading it.
https://tamingthedroid.com/apn-type
acejavelin said:
APN Type 'fun' ?!?! lol... I think you mean 'dun', I have never heard of a APN type of fun, although it was enough to give me a chuckle reading it.
https://tamingthedroid.com/apn-type
Click to expand...
Click to collapse
I'm sure it's a Typo.
By the way, is the topic interesting enough to you, where you'd like to help out and be a contributing force to it.
I've read a few of your undertakings and your GOOD :good:
would be a pleasure to see your expertize and talent here in helping out with the thread.
Me (I'm) a nobody here or anywhere, but I've PM'ed MotoJunkie01 much, and he's knowledgeable and helpful - just as you are, as I've read your Threads and helpful posts. So how about it, would that sound like something you'd be interested to do in helping develop this thread. I know MotoJunkie01 was looking for help to co-chair this topic along I think you're just that person he's looking for.
Thanks for considering it. . .
ResistanceIsFutile said:
I'm sure it's a Typo.
By the way, is the topic interesting enough to you, where you'd like to help out and be a contributing force to it.
I've read a few of your undertakings and your GOOD :good:
would be a pleasure to see your expertize and talent here in helping out with the thread.
Me (I'm) a nobody here or anywhere, but I've PM'ed MotoJunkie01 much, and he's knowledgeable and helpful - just as you are, as I've read your Threads and helpful posts. So how about it, would that sound like something you'd be interested to help develop this thread. I know MotoJunkie01 was looking for help to co-chair this topic along
Thanks for considering it. . .
Click to expand...
Click to collapse
Projects like this interest me... swapping ROMs, tweaking settings, etc... So that lead me to read the thread, and I would help where I could. My issues is I don't have a CDMA Moto G, in fact I don't even have Sprint service in my area without traveling 200 or so miles, so I don't know how much help I would be.
Under the hood princples
acejavelin said:
Projects like this interest me... swapping ROMs, tweaking settings, etc... So that lead me to read the thread, and I would help where I could. My issues is I don't have a CDMA Moto G, in fact I don't even have Sprint service in my area without traveling 200 or so miles, so I don't know how much help I would be.
Click to expand...
Click to collapse
I'm sure this is better discussed with @MotoJunkie01 through PM's, though you both share the love for Moto's, and any knowledge brought to light will help that part of Moto users on the CDMA side. Besides anything you guy's could learn/exchange between yourselves would help all Moto users - Yes?
acejavelin said:
Projects like this interest me / I would help where I could / I don't have a CDMA Moto G, so I don't know how much help I would be.
Click to expand...
Click to collapse
{Please forgive me for taking your words out of context}
In the areas of tweaks and of their under the hood principles related to all Moto's, in a threads structure and content to it's beneficial coverage for the reader, answering of questions where your knowledge is greater, I see many areas you could be very helpful. Then think about some friends or far off relatives that may have need to the knowledge that this thread will cover. In that of Data Done Right.
acejavelin said:
APN Type 'fun' ?!?! lol... I think you mean 'dun', I have never heard of a APN type of fun, although it was enough to give me a chuckle reading it.
https://tamingthedroid.com/apn-type
Click to expand...
Click to collapse
Good catch on my "fun" entry. Great eye for detail
acejavelin said:
APN Type 'fun' ?!?! lol... I think you mean 'dun', I have never heard of a APN type of fun, although it was enough to give me a chuckle reading it.
https://tamingthedroid.com/apn-type
Click to expand...
Click to collapse
Your contributions to this thread would be invaluable, and enlightening to many. Would love it if you were on board. Thanks for your consideration regardless of your decision.
Sent from my MotoG3 using XDA Forums
Moto G3 Virgin Mobile DDR Modem [Radio) Firmware Files
As always ....you flash these files at your own risk. ALWAYS make a full Nandroid backup before proceeding with firmware flashing or major configuration changes.
The following link is for the Modem [Radio] Firmware which comes stock on the Virgin Mobile DDR variant of the Moto G3 (xt1548). More specifically, this modem firmware is from the final Stock Android 5.1.1 Lollipop Build - the build next preceding the Android 6.0.1 Marshmallow OTA. (Android 5.1.1 LPI23.72-32-S.28_cid9) Included in this link are three raw partition .img files: /modem & /fsg (classified as modem [radio] firmware) and /persist, which encompasses vital network and telephony configurations specific to the Virgin Mobile DDR network, including unrestricted enabling of Mobile Hotspot, USB Tethering and Bluetooth Sharing of your high speed 4G/LTE Data. There are also telephony configurations in /persist which are unique to DDR. Again, it should be noted that these particular firmware partitions and network configurations are specific to the DDR variant, and are not the same as those partitions and configurations on the Virgin Mobile USA variant.
DOWNLOAD LINK:
https://drive.google.com/folderview?id=0B4PvIFOs0G3jVmF1dXloWFpLZzA
These partitions may be flashed via a number of different methods. Flashfire by @Chainfire, Partition Backup & Restore by @wanam, and Rashr are all capable of flashing these partitions. Preferably, and arguably the best method, is to install Minimal ADB & Fastboot on your PC (and also the most current version of Motorola Device Manager, to ensure the correct and most current USB drivers for your Moto G3 are installed on your laptop or PC). Put your device into AP Fastboot Mode by powering off your device, and then holding the Power button and Volume Down button of your device simultaneously until the fastboot menu appears. Connect your Moto G3 to your PC or laptop with an OEM or equivalent in quality micro USB to USB charge/sync cable. Place the three .img files you downloaded in your adb/fastboot directory and open a command window in that directory. Execute these commands:
First, type fastboot devices. Your device Serial Number will appear in the command window if you are properly connected with the requisite USB drivers installed. If you do not see the Serial Number or if you see a message "Waiting for Any Device" in the command window, try switching USB Ports, reinstall the Motorola Device Manager, and/or try a different sync cable. Execute these commands to install the DDR Modem Firmware on your device:
fastboot oem fb_mode_set
fastboot flash modem modem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.img
fastboot oem config fsg-id virgin
fastboot oem config carrier virgin
fastboot flash persist persist.img
fastboot oem fb_mode_clear
Your Moto G3 will now be running the DDR modem firmware and is configured to the carrier specific parameters of the DDR network. Again, these firmware dumps are from Stock Android 5.1.1 (LPI23.72-32-S.28_cid9). This firmware can be used while running any stock or custom ROM and, to the best of my knowledge and experience, on any version of Android. However, if any members want the more recent Android 6.0.1 modem firmware, just request it and I'll post a link.
This firmware can be used while running any stock or custom ROM and, to the best of my knowledge and experience, on any version of Android.
Click to expand...
Click to collapse
While still keeping in mind that of a Sprint compatible (Sprint, Boost, Virgin Mobile USA, TextNow)-Variants- of the Moto G3 (xt1548) is needed here.
ResistanceIsFutile said:
While still keeping in mind that of a Sprint compatible (Sprint, Boost, Virgin Mobile USA, TextNow)-Variants- of the Moto G3 (xt1548) is needed here.
Click to expand...
Click to collapse
Yes. This thread is focused on the Sprint compatible variant of the Moto G3, the xt1548 Variant -- Virgin Mobile USA, Virgin Mobile Data Done Right, Boost Mobile, Sprint, TextNow, FreedomPop, etc. For members that need it, I will be posting a download link in the next day or so of the stock Android 5.1.1 ROM shipped on the DDR variant.
ResistanceIsFutile said:
While still keeping in mind that of a Sprint compatible (Sprint, Boost, Virgin Mobile USA, TextNow)-Variants- of the Moto G3 (xt1548) is needed here.
Click to expand...
Click to collapse
By the way, glad you finally drummed in with some input. Haha. Good to hear from you as always.
MotoJunkie01 said:
Yes. This thread is focused on the Sprint compatible variant of the Moto G3, the xt1548 Variant -- Virgin Mobile USA, Virgin Mobile Data Done Right, Boost Mobile, Sprint, TextNow, FreedomPop, etc.
For members that need it, I will be posting a download link in the next day or so of the stock Android 5.1.1 ROM shipped on the DDR variant.
Click to expand...
Click to collapse
That's good - but maybe @acejavelin and yourself, and others might consider if it's possible to do this mod on any device variant, that would be of a VM USA, Boost, Sprint, TextNow, FreedomPop, with the Snapdragon 410, msm8916 Baseband used.
It's way over my head, but wouldn't any device (branded from any of the above) with the Snapdragon 410, msm8916 Baseband work for this? This ideal then ported to them? I know it's drifting away from your "Virgin Mobile Data Done Right Moto G3" - thread title, maybe you could add others too, in the title - if this application fits.
EDITED - Removed content not being directly related to the Threads Title.
MotoJunkie01 said:
By the way, glad you finally drummed in with some input. Haha. Good to hear from you as always.
Click to expand...
Click to collapse
But Friend, I had posts #4, and #6 before post #10- eerie of that addition factor to math. . . adds up to the post you've quoted
I highly doubt this would possible with any other device that doesn't have a DDR variant... The Moto G 2015 is kind of unique in that we have the radio firmware and other vendor specific files for the DDR variant and a way to flash them. Few other devices could fit that criteria.
acejavelin said:
I highly doubt this would possible with any other device that doesn't have a DDR variant... The Moto G 2015 is kind of unique in that we have the radio firmware and other vendor specific files for the DDR variant and a way to flash them. Few other devices could fit that criteria.
Click to expand...
Click to collapse
I agree. The msm8916 baseband seems to be significant to the data loophole yet it is not. I once thought this myself until I discovered the single thread that makes the loophole possible. It lies in the network itself -- and the DDR Moto G3 can connect to this loophole --- as @acejavelin noted --- due to the unique nature of the radio firmware. I have the radio firmware to other DDR devices as well -- the G3 just happens to be my favorite.
MotoJunkie01 said:
I agree. The msm8916 baseband seems to be significant to the data loophole yet it is not. I once thought this myself until I discovered the single thread that makes the loophole possible. It lies in the network itself -- and the DDR Moto G3 can connect to this loophole --- as @acejavelin noted --- due to the unique nature of the radio firmware. I have the radio firmware to other DDR devices as well -- the G3 just happens to be my favorite. But I must admit I once thought the exact same thing on the msm8916 Snapdragon 410 devices.
Click to expand...
Click to collapse
Your analysis is exactly what I once theorized -- that the "trick" was in the construction of the device -- That the msm8916 was necessary for the loophole to work. In fact, many DDR devices have the msm8916 under the hood. But there are also others with different basebands which also attain connectivity.
MotoJunkie01 said:
I agree. The msm8916 baseband seems to be significant to the data loophole yet it is not. I once thought this myself until I discovered the single thread that makes the loophole possible. It lies in the network itself -- and the DDR Moto G3 can connect to this loophole --- as @acejavelin noted --- due to the unique nature of the radio firmware. I have the radio firmware to other DDR devices as well -- the G3 just happens to be my favorite.
Click to expand...
Click to collapse
Slowly this is sinking into some logic for me, as I've never rode a twisting, turning, bucking bull - I guess I'll have to learn to stay on this too, as the wild ride that bull would of been.
Ok radio firmware then - is anyone on XDA up to understanding fully the principles here, and if any mod's are possible to that kind of a nature in porting any values out? Looking at it another way is there a possibly of a DDR firmware porting in (changing) the value in that firmware to be used on a different msm8916 baseband device variant? Someone with a good knowledge could compare different DDR radio firmware to other DDR or NON-DDR devices and see common points of interest in them? What's possible here?
MotoJunkie01 said:
But there are also others with different basebands which also attain connectivity. /-\ It lies in the network itself.
Click to expand...
Click to collapse
Others as in what kind of reference - non DDR devices? What are the other basebands that are useful to the network?
I know I can come up with the questions, but I have no knowledge to find the answers yet. Hopefully my line of questions spurs someone into thinking along these lines and then does have some knowledge to experiment.
Radio firmware is not open source, it's binaries... You can't really just open and compare it to another radio. Radio firmware is proprietary, it just talks to the RIL and kernel, it's part of Android we don't get get the source for.
acejavelin said:
Radio firmware is not open source, it's binaries... You can't really just open and compare it to another radio. Radio firmware is proprietary, it just talks to the RIL and kernel, it's part of Android we don't get get the source for.
Click to expand...
Click to collapse
That's interesting and a good point made Sir.
If it's talking to the RIL and kernel - can one trap this conversation?
If it's talking in binaries then is it possible to be converted to something understandable or at least viewed? Does it talk differently to both or say
more less the same thing to both (RIL and kernel) ?
Thanks
ResistanceIsFutile said:
That's interesting and a good point made Sir.
If it's talking to the RIL and kernel - can one trap this conversation?
If it's talking in binaries then is it possible to be converted to something understandable or at least viewed? Does it talk differently to both or say
more less the same thing to both (RIL and kernel) ?
Thanks
Click to expand...
Click to collapse
The communication by the firmware isn't relevant to the loophole. Trust me when I say the loophole lies in the network itself. The DDR devices can connect to this loophole due to known configurations in radio firmware.
Hi guys,
I (we) desperately need help. Myself and a number of other Moto X Style are crying out loud for help on getting our roaming issue fixed. Long story short:
I have a Motorola X Style (all original, no mods), after the upgrade to Nougat International roaming stopped working (it was working on 6.0). Or better, international roaming does not work with a SIM from a Polish operator named PLAY. Funny enough the same SIM in another phone roams internationally fine and a SIM from another operator in the Moto X roams fine too. It seems to be a sick combination of Moto X Android 7.0 and PLAY. I (we) have tried everything, theres a thread on the official Motorola forum if you dare to read ( I cannot post the link because I'm new, but a search for "Moto X Roaming not working Polish Play" will give you a link). And when I say everything I really mean it... Starting from Clear the Cache to Factory Reset, and the obvious/trivial things too like "enable data while roaming" etc... According to the PLAY provider all is OK on their side and Motorola is ignoring the issue... Its 8 months that their "engineers" are allegedly looking into it, and that it will be "hopefully resolved in future updates" .... yeahhh believe it... Solution from Motorola: "send the phone in for a downgrade to 6.0". Many of us, me included, are locked into a # of years contract with PLAY so it is not that easy to dump the operator and go with someone else. That's why someone with a real deep knowledge on how this stuff work is needed. The last thing to add is that PLAY operator is one of the few that uses national roaming too to fill in the gaps on their national coverage, needless to say that national roaming works fine.
Any help will be really appreciated ... best regards Fulvio.
There's not much we can do about it. Editing the stock modem is nearly impossible.
Best you can do right now is flash Nougat Custom ROMs that are based on Marshmallow modem (Official LineageOS), In this way you'll get the Nougat features on Marshmallow base.
or.. try flashing other variants nougat modem RETUS, RETLA (this is not recommended and has a high risk)
antariksh said:
There's not much we can do about it. Editing the stock modem is nearly impossible.
Best you can do right now is flash Nougat Custom ROMs that are based on Marshmallow modem (Official LineageOS), In this way you'll get the Nougat features on Marshmallow base.
or.. try flashing other variants nougat modem RETUS, RETLA (this is not recommended and has a high risk)
Click to expand...
Click to collapse
RetLA & RetUS will not work in Europe, RetAsia has the same baseband.
I think @fulvy70 has locked bootloader so he can't flash anythng.
dzidexx said:
RetLA & RetUS will not work in Europe, RetAsia has the same baseband.
I think @fulvy70 has locked bootloader so he can't flash anythng.
Click to expand...
Click to collapse
Yes of course he has to unlock first and if the device is out of warranty, I don't see any harm in doing it.
Me to.
Someone here uses MM when he's on travels and Nougat at home.
Because...
Delta app doesn't work good on Nougat.
Hi,
Thank you for your answers... I understand that you are all pinpointing the issue in the Modem/Radio Firmware, not the Android OS itself ... this is already a step forward... I understand the risks connected with flashing a different Modem/Radio FW but anyhow is something to know ... I believe it is also something to consider if eventually any custom ROM will be compatible with the new modems/radios ... at that point even changing the ROM to custom will not solve the issue I believe...
Regards Fulvio.
Flashing custom rom doesn't change the modem/radio/baseband.
I don't know where is problem - only Play(Poland) doesn't support LTE roaming.
You can flash any custom for N modem and check it. @fulvy70
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!