Database Users

[Q] i9505 - Difference between GSM and LTE modem?

I've seen people saying they have a baseband for GSM and another for LTE. Where can I see this? All I see in "About phone" is "Baseband". It doesnt say specific for GSM or LTE.
And How can I get different basebands for each radio? In baseband collection thread all of them are just 1 zip file, so it updates both, right?

respider said:
I've seen people saying they have a baseband for GSM and another for LTE. Where can I see this? All I see in "About phone" is "Baseband". It doesnt say specific for GSM or LTE.
And How can I get different basebands for each radio? In baseband collection thread all of them are just 1 zip file, so it updates both, right?
Click to expand...
Click to collapse
anyone?
I see .zip packages that are supposed to upgrade GSM modem to one specific version and LTE to other version at the same time. Where can I check that?

Here (every modem you could ever want in that thread as well).

MistahBungle said:
Here (every modem you could ever want in that thread as well).
Click to expand...
Click to collapse
Thank you!
I was thinking that as well, but in Omega ROM's thread there is a zip file that flashes a modem for GSM and another for LTE
**If you are having the old bootloader XXUB flash GSM_Modem_XXUEMJ5_and_LTE_Modem_XXUBMH1.tar file with odin by selecting phone.
**If you are having the new bootloader XXUD flash GSM_Modem_XXUEMJ5_and_LTE_Modem_XXUEMJ5.tar file with odin by selecting phone.
That's why I'm asking.
Any idea?

You shouldn't need to touch/flash another LTE modem unless you have problems, the one already on the device should work just fine. I don't know specifically what might be in Omega rom to require those instructions as I've never used it, but I'm running XXUEMJ5 GSM modem with the 'old' bootloader on Foxhound 3.1, and everything is working as it it should. I've never touched the LTE modem/the one that was on the device when I bought it is still on it & LTE works fine in areas where my carrier has LTE coverage.
If you're about to flash Omega rom, I'd say follow the instructions (or ask in the thread), if you're not, I (your mileage might vary though, obviously) wouldn't touch the LTE modem at all unless you have problems with LTE connectivity, WiFi or sound.
Edit - Going back through some posts/threads I have bookmarked from months ago, people who messed around with non-HLOS.bin files seemed to have a funny habit of borking their WiFi & other stuff. As I said above, I wouldn't be flashing one separately unless you had a good reason to (I.E something like the Omega thing where it's a specific instruction as part of flashing the rom), or flashing a rom/something else borks your WiFi/LTE/sound or whatever as I said above, the one already on your phone should do the job.

MistahBungle said:
You shouldn't need to touch/flash another LTE modem unless you have problems, the one already on the device should work just fine. I don't know specifically what might be in Omega rom to require those instructions as I've never used it, but I'm running XXUEMJ5 GSM modem with the 'old' bootloader on Foxhound 3.1, and everything is working as it it should. I've never touched the LTE modem/the one that was on the device when I bought it is still on it & LTE works fine in areas where my carrier has LTE coverage.
If you're about to flash Omega rom, I'd say follow the instructions (or ask in the thread), if you're not, I (your mileage might vary though, obviously) wouldn't touch the LTE modem at all unless you have problems with LTE connectivity, WiFi or sound.
Edit - Going back through some posts/threads I have bookmarked from months ago, people who messed around with non-HLOS.bin files seemed to have a funny habit of borking their WiFi & other stuff. As I said above, I wouldn't be flashing one separately unless you had a good reason to (I.E something like the Omega thing where it's a specific instruction as part of flashing the rom), or flashing a rom/something else borks your WiFi/LTE/sound or whatever as I said above, the one already on your phone should do the job.
Click to expand...
Click to collapse
thank you vey much, but....
too late hahaha I've read your post right after flashing that zip. Everything seems fine but can't test LTE yet because my plan doesnt support it. I'll try to upgrade to LTE this week and I'll search for a method to revert LTE baseband if I need it in the future.
Thanks again sir.

[Q] GSM Rom suggestion ???

Hi all,
I just sim unlock my sprint s4 both international and domestic. It come with the NAE modem. while unlcok it, I odin to MDC modem.
I have signal and text on AT&T network on this phone now. ( Phone is not rooted yet, I did edit the build.prop to add ril.sales_code=LOL
ro.csc.sales_code=LOL. I am not sure if not-rooted matters).
Right now I am looking into flashing a rom to use on AT&T network. Lots people suggests Fenny's T-mobile rom. and some suggest SACS CUSTOM ROM
I am not sure which is better if I am using a GSM network.
And If T-mobile roms are better for GSM rom, how could I flash them? Do I need to flash NAE modem back?
Thank you for all of you idea/suggestion.

I just asked pretty much the same question in the following post...
http://forum.xda-developers.com/showthread.php?t=2764201
I think we have to build the roms for the device ourselves, but I was reading about calling issues on unlocked phones so I'm trying to find out what to do as well. Flashing recovery is easy enough, then the rom of course, but getting this right rom zip seems to be a little tricky in our scenario. Not hijacking or anything, but check my thread too in case someone answers on mine first.
BTW, this is the post I was referring to about phone issues with non-stock roms on an unlocked sprint s4...
http://forum.xda-developers.com/showthread.php?t=2539794
Well, it looks like the 100% sure way to get this working is to do the outlined steps in the post linked above to the nightly builds of CM11, which I will link below (notice the spr/att designation at the end of the link)...
http://download.cyanogenmod.org/?device=jfltespr
http://download.cyanogenmod.org/?device=jflteatt
Other way looks to grab a jflteatt labeled rom from the Sprint Android dev subforum, but it looks more hit or miss. I might be way off and overthinking this, but I'm gonna try the mix/match way.

Well, I ended up working this out myself. I grabbed the nightly CM11 spr and att jflte builds, then followed the directions from the post I linked before that showed how to mix the 2 so the Sprint boot.img was in the AT&T build, including changing the updater-script so that the assert line read "jfltespr" in the 3 locations it had "jflteatt", then flashed the jfltespr CWM recovery from Heimdall, used recovery to wipe data/cache/darvik, installed the mixed rom from recovery, then installed the Chronic kernel (blackscreen without this), and the gapps apk for CM11. Once I was done everything worked perfectly, I only had to change the APN to the ATT Phone one for HSPA+. From what I can tell the CDMA portion of the phone is pretty much gone, and it shows the phone model as the AT&T version instead of the Sprint version (ie shows l337 instead of l720). The correct phone number from the SIM is now properly displayed as well. Also, with the Chronic kernel (slight OC) and CM11 the phone is lightning fast and responds instantly. Overall I'm very happy with this. Hope this helps anyone else in the same scenario. BTW, still using MDC modem from Odin flash during the domestic unlock.

i9505 i337m canada mobile network connectivity

Hello All,
I have a samsung galaxy s4 i337m in canada using the rogers netowork. Ive been using customs roms shortly after i got this phone. Ive used samsung rom, original, GPE but eventually settled on Cyanogenmod. I use TWRP for the i9505 which allows me to use any rom (since CM12 doesnt have a build for the i337m, and other builds wont flash in a i337m TWRP).
Anyway ive been using CM 12.1 with a i9505 build for some time, and it works great. I had to update my modem to the NI2 build to get it to work, but its been working flawless ever since.
Now to my problem, buddy has an S4, same model, same carrier. He claims he needs a new phone and i beg to differ. I rooted, installed twrp (i9505)and cm12.1 (i9505). works great, however no network connectivity. I remember i need a new modem, try the same one that works with mine....nothing... try a different one.... nothing. calls and SMS, but not data of any speed.
Reverting to kitkat roms results in it working perfectly (multiple modems). both from his original Nandroid and CM 11. All lollipop roms seems to have the same issue, no mobile data. Wifi works fine. No issues with SIM card, switched them between the two phones and confirmed its HIS phone with the issue.
Im a little puzzled, can someone recommend a modem to load? should I try to use TWRP an CM12 for the ATT variant/ different variant? I want to help him but this is making me look amateur (even if its true).
Thanks ahead of time.

Canadian i337m compatible marshmallow roms?

Ok I'm just a little confused.
Canadian i337m compatible marshmallow roms?
Are they jflteatt jfltexx i9505 or something else or all of the above.
(I'm running wamanlite 4.4.2 9505 rom now on my jfltecan I don't think there are any good links for it left, and when I flash a new one there will be no going back)
I know there are others confused out there as well..
If you are using marshmallow and you have flashed the rom to your Canadian s4 and all is working great.
Please post a link to that rom here
If you needed some other kernel or file to flash in to make it work
Please post that info with links also.
Thanks for any info you can provide.
(And bite me Samsung att and others for locking so many U.S. carrier boot loaders which has reduced development)

The s4 should work with the 9505, jflteatt, and jfltexx ROMs; however, editing the updater script may be required to get the ROM to install.

Hahaha - you will likely get yelled at to use the search bar and to read the stickies with these sorts of questions, but I was a noob once too, so here's an olive branch. (that being said, please do use these in the future!)
Your i337m will be cross-compatible with ALL GS4 devices (at least to my knowledge). I've had one now for a little over 4 months and have explored most of the options available to the Canadian variant. I have run everything from 4.2.2 to 5.1.1 on my device successfully, but you will have the most luck where the developer indicates that the build is for jflte devices in general, not one in particular.
Furthermore, the GS4 or ANY device sporting a Qualcomm chipset can use a modified modem file to access WCDMA/HSPA bands (ie. WIND, or T-Mobile).
Again, the search bar is your friend here! Also try Google, or Duckduckgo (google will tailor your results, sometimes in a way which will actually hinder your search).
If all else fails, send me a PM and I will assist you wherever possible.
Best of luck!

Graysonh said:
Hahaha - you will likely get yelled at to use the search bar and to read the stickies with these sorts of questions, but I was a noob once too, so here's an olive branch. (that being said, please do use these in the future!)
Your i337m will be cross-compatible with ALL GS4 devices (at least to my knowledge). I've had one now for a little over 4 months and have explored most of the options available to the Canadian variant. I have run everything from 4.2.2 to 5.1.1 on my device successfully, but you will have the most luck where the developer indicates that the build is for jflte devices in general, not one in particular.
Furthermore, the GS4 or ANY device sporting a Qualcomm chipset can use a modified modem file to access WCDMA/HSPA bands (ie. WIND, or T-Mobile).
Again, the search bar is your friend here! Also try Google, or Duckduckgo (google will tailor your results, sometimes in a way which will actually hinder your search).
If all else fails, send me a PM and I will assist you wherever possible.
Best of luck!
Click to expand...
Click to collapse
Just wondering what modem to use. Do I use the latest modem for I337M or can I use modem for I9505. I live in Canada and have always used the modems for the I337M model. The latest modem is PA1, I think for the I9505.

Hey tvsite,
Modems for this phone in Canada puzzled me for quite some time, however, this is what I did to make things work.
--> Downgraded from 5.1.1 CM 12.1 Optimized via odin using "I337MVLUAMDJ_I337MOYAAMDJ_VMC.zip" (http://www.sammobile.com/firmwares/download/14412/I337MVLUAMDJ_I337MOYAAMDJ_VMC/)to net me 4.2.2 (note: your wifi or calling WILL NOT WORK).
You may have even better luck using the SaskTel firmware at this point, although I have not tried it yet. (http://www.sammobile.com/firmwares/download/14418/I337MVLUAMDJ_I337MOYAAMDJ_BWA/)
--> Do the AWS mod, unlocking etc.
--> Upgraded to 4.4.1 using "I337MVLUFNC1_880525_REV06_user_low_ship_MULTI.tar"
https://mega.co.nz/#!h8pTnCZS!t2-PiSb5W9ZyNp7fct7WD_Pg_dnc-eZqtMvpsuKv_9Q
--> I forget what modem I was on at this point, however, after letting OTA do its thing, I wound up at 5.0.1, OH1 modem, and AWS still enabled.
Good luck!

Graysonh said:
Hey tvsite,
Modems for this phone in Canada puzzled me for quite some time, however, this is what I did to make things work.
--> Downgraded from 5.1.1 CM 12.1 Optimized via odin using "I337MVLUAMDJ_I337MOYAAMDJ_VMC.zip" (http://www.sammobile.com/firmwares/download/14412/I337MVLUAMDJ_I337MOYAAMDJ_VMC/)to net me 4.2.2 (note: your wifi or calling WILL NOT WORK).
You may have even better luck using the SaskTel firmware at this point, although I have not tried it yet. (http://www.sammobile.com/firmwares/download/14418/I337MVLUAMDJ_I337MOYAAMDJ_BWA/)
--> Do the AWS mod, unlocking etc.
--> Upgraded to 4.4.1 using "I337MVLUFNC1_880525_REV06_user_low_ship_MULTI.tar"
https://mega.co.nz/#!h8pTnCZS!t2-PiSb5W9ZyNp7fct7WD_Pg_dnc-eZqtMvpsuKv_9Q
--> I forget what modem I was on at this point, however, after letting OTA do its thing, I wound up at 5.0.1, OH1 modem, and AWS still enabled.
Good luck!
Click to expand...
Click to collapse
I flashed the OK1 modem which is posted, here, which is for the I337M model. I believe this is country code Mexico. This modem is working fine. Have you tried flashing a I9505 modem using Odin. I tried and it said "failed", so I may have answered my own question---that you cannot flash modems over different model numbers even though its the same phone, ie. S4

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!