heres my dilemma
http://forum.xda-developers.com/showpost.php?p=67719294&postcount=29[/url]
Originally Posted by macallik
Having mediocre reception since upgrading to stock MM in USA and I think this could resolve my issues.
The thing is I've never rooted the phone, so I am guessing I have to revert to 5.0.1 and then root the phone and then upgrade to MM and then flash the modem?
Quote:
Originally Posted by famewolf
Well..technically you don't have to be rooted to flash twrp and that's the only requirement to flash the modem zip...the problem you will have is I've heard mobile q is flashing marshmallow for the 6045i now.....so you'd have to flash the panasonic eluga switch software to get back to 5.0.2...flash twrp....then upgrade to mm using one of the rom's in android development so they won't wipe out your twrp. I saw at least one person say the factory rom won't wipe out your twrp either but I wouldn't risk it.
i was in the same boat as macallik, mobileq brought me back to mm so i went the eluga route. after unlocking boot loader and rooting i decided to take a stab at a custom rom. i failed miserably at the installation. so decided to start all over. so i mobileq to mm, then eluga back to 5.0.2, unlock boot loader, root(some steps were redundant). somewhere along the line i lost lte. back mm, no lte. back to 5.0.2, no lte. custom rom(spb2,1), no lte. flasf the 6045i 5.0.2 radio zip, no lte.
is my lte now fubar or is there still hope?
thanks
Click to expand...
Click to collapse
and currently:
famewolf said:
Mobile Q does a full reset of everything...the only reason you would not have lte at that point would be lte not being available in your area or your account not being setup to use it in carrier settings. For example you have to be using the t-mobile lte apn.
Click to expand...
Click to collapse
restored mm through mobileq and still had no lte. used eluga to again go to 5.0.2, flashed a couple different roms both your 6045i radios and nothing. im at a friends house and from sensorly saw that theres a bit of a dead zone through his house. he does have a tmo signal booster and does get lte on his iphone.
any way the radio could be pushed through adb?
any and all suggestions are welcomed. worst case scenario id be forced to upgrade.....
Thanks
rotor nuts said:
heres my dilemma
[/url]
and currently:
restored mm through mobileq and still had no lte. used eluga to again go to 5.0.2, flashed a couple different roms both your 6045i radios and nothing. im at a friends house and from sensorly saw that theres a bit of a dead zone through his house. he does have a tmo signal booster and does get lte on his iphone.
any way the radio could be pushed through adb?
any and all suggestions are welcomed. worst case scenario id be forced to upgrade.....
Thanks
Click to expand...
Click to collapse
Did you do clean installs or are you trying to restore data from old builds? Mobile Q resets ALL the partitions. The flashable radio's overwrite the modem partition. At that point the only factor is whether or not you are using the right config. Are you using the fast.t-mobile.com apn? Did you run the lte discover app to see what towers your phone is actually seeing? Are you comparing the results each time you change the radio? What towers/bands is your friends phone seeing?
If you ran mobile q and you STILL don't have lte then you have other issues..possibly hardware. The eluga software WILL break lte...it's going to install whatever radio the eluga uses and it's not meant for the usa. In another thread I posted how to identify what version radio you are running...that getprop command should work on most models unless you've installed cyanogenmod which wipes out alot of the info from stock.
Example:
1|[email protected]:/ $ getprop | grep non.ver
[ro.tct.non.ver]: [K7SRA0A0BG00]
famewolf said:
Did you run the lte discover app to see what towers your phone is actually seeing? Are you comparing the results each time you change the radio?
Example:
1|[email protected]:/ $ getprop | grep non.ver
[ro.tct.non.ver]: [K7SRA0A0BG00]
Click to expand...
Click to collapse
hadnt ran lte discovery or compared results. ill redo mobileq and see what that yields and try to get the radio version.
ive used both fast.tmobile apns. most have been clean installs. as soon as i get a hold of my friend ill look into his lte bands. installed cm around noon just to give it a try. everything else has been done with mobileq, eluga and mm roms.
lte discovery came up empty. i think my freinds iphone connects to band 4.
thanks
rotor nuts said:
hadnt ran lte discovery or compared results. ill redo mobileq and see what that yields and try to get the radio version.
ive used both fast.tmobile apns. most have been clean installs. as soon as i get a hold of my friend ill look into his lte bands. installed cm around noon just to give it a try. everything else has been done with mobileq, eluga and mm roms.
lte discovery came up empty. i think my freinds iphone connects to band 4.
thanks
Click to expand...
Click to collapse
You should also ensure your phone "mode" in cellular settings is LTE enabled and not set to only wcdma/gsm.
4 is a rather common band used by both AT&T and T-mobile which should work on just about ALL the radio's.
The mode in settings>more>cellular nerwork is set to LTE/wcdma/gsm. I enter a service menu yesterday and where it let you choose radio/service, the only option was wcdma/gsm. Tried tmo sim from iPhone and it only detected 3g/2g but wouldn't connect. So far LTE discovery just sees hspa.
When I get back home I'll try to upgrade with mobileq.
Thanks
I got the same problem like rotor nuts. Restored through mobile q. I did everything that rotor nuts did. Cannot get LTE back. I'm on straight talk att. APN setting are the same one that I always use to get lte. Only getting H network. Before this I was getting around 25 Mbps and now I'll be Lucky to even gets 2 Mbps.
buksua said:
I got the same problem like rotor nuts. Restored through mobile q. I did everything that rotor nuts did. Cannot get LTE back. I'm on straight talk att. APN setting are the same one that I always use to get lte. Only getting H network. Before this I was getting around 25 Mbps and now I'll be Lucky to even gets 2 Mbps.
Click to expand...
Click to collapse
First go into "adb shell" and run the following command..see if you are running the same radio...the N0N0 is the latest radio before the 6.0 version came out.
[email protected]:/ $ getprop | grep non.ver
[ro.tct.non.ver]: [K7SRN0N0BG00]
K7SR = 5.0.2
K7VA = 6.0
then under Settings, More, Cellular Networks, check to make sure your "Preferred Network Mode" is LTE/WCDMA/GSM.
famewolf said:
First go into "adb shell" and run the following command..see if you are running the same radio...the N0N0 is the latest radio before the 6.0 version came out.
[email protected]:/ $ getprop | grep non.ver
[ro.tct.non.ver]: [K7SRN0N0BG00]
K7SR = 5.0.2
K7VA = 6.0
then under Settings, More, Cellular Networks, check to make sure your "Preferred Network Mode" is LTE/WCDMA/GSM.
Click to expand...
Click to collapse
all the setting is correct. my radio version after using mobile q is K7VAUEB0BG00. do you think this might be because of eluga? before i flash eluga my lte was ok but because i wanted to downgrade to get root.
buksua said:
all the setting is correct. my radio version after using mobile q is K7VAUEB0BG00. do you think this might be because of eluga? before i flash eluga my lte was ok but because i wanted to downgrade to get root.
Click to expand...
Click to collapse
As the message you quoted indicates K7VA shows it's the 6045i Marshmallow (6.0) radio which is what mobile Q would install. If that's not your model or you are not on marshmallow then you should find the appropriate radio and flash it. Additionally if you need/want LTE Band 12 then you HAVE to use the 5.0.2 radio as it's been removed from the 6.0 one.
I'm working on a possible hybrid radio but I wouldn't expect it anytime soon. I'm not even in a band 12 area so I'd have to rely on a tester which will slow things down ALOT.
famewolf said:
First go into "adb shell" and run the following command..see if you are running the same radio...the N0N0 is the latest radio before the 6.0 version came out.
[email protected]:/ $ getprop | grep non.ver
[ro.tct.non.ver]: [K7SRN0N0BG00]
K7SR = 5.0.2
K7VA = 6.0
then under Settings, More, Cellular Networks, check to make sure your "Preferred Network Mode" is LTE/WCDMA/GSM.
Click to expand...
Click to collapse
sorry finally got around to adb.(lets just say that im not as smart as i once thought i was)
[ro.tct.non.ver]: [K7VAUEB0BG00]
everything is set to LTE and LTE discovery app only shows hspa
rotor nuts said:
sorry finally got around to adb.(lets just say that im not as smart as i once thought i was)
[ro.tct.non.ver]: [K7VAUEB0BG00]
everything is set to LTE and LTE discovery app only shows hspa
Click to expand...
Click to collapse
Please see the post right above yours. http://forum.xda-developers.com/showpost.php?p=67751447&postcount=9
If you are in a band 12 lte area that would explain things.
Related
Just joined from the iphone world to the android world after about 3 years. Wow. =]
Anyway, just bought the phone yesterday, activated it an within 15 minutes had it rooted phiz recovery and and installed AllianceRom 3.1 on it.
I've had a bit of an issue, It will not go LTE. It only stay on 4g or go to E,, H+, my friend who has an iphone, same provider and same service, his phone shows LTE in our same location at his desk but mine will not go above 4G.
Did I do something wrong with the root process? Anyone ever seen this issue? I'd say its an issue with the service but when you have a friend with the same provider and his phone is showing LTE, it begs to ask questions
Thanks all,
Alan
do a speed test and u will know, i think on yr ROM 4G = LTE, H+ = 4G, also check yr APN too.
Got it Hope this helps new rooters
koolboyztn said:
do a speed test and u will know, i think on yr ROM 4G = LTE, H+ = 4G, also check yr APN too.
Click to expand...
Click to collapse
I checked it out, I found that it was a combination of a couple of things,
When I bought the phone I rooted it immediately, didn't officially update it or anything. I was working on the older radio with the newer Alliance rom which required the latest radio.
The only way I was able to fix it was use Kies, update it, which put it back to stock recovery and stock rom. Reroot using Odin and install Omega's rom. It would of probably worked fine with Alliance rom but I saw a couple things I liked with Omega.
When I updated stock I saw LTE. Which told me that it was a radio issue, I tried updating the radio manually but it failed so I just let Kies do it.
All settled and done, it's purring like a kitten now Thanks Koolboyztn for your suggestion
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.
CM13 is available: http://www.cmxlog.com/13/klteduos/#
Seems to be quite stable for its early state.
Known issue is that most apps can only read from external SD, but not write because of changes in storage management of Marshmallow.
There are also voices saying LTE & 3G are not working.
Please test and report
Not working LTE and 3G , clean install....
Yeah same here, no LTE 3G. Clean install
Bad news 1st: LTE not working seems to be a known bug, too: http://forum.xda-developers.com/nexus-4/help/cm13-switching-to-wdcma-t3280353
Good news after: It seems to be already merged since yesterday : http://review.cyanogenmod.org/#/c/125897/
I have already flashed today's nightly and maybe, later on, I can sort out if it has been already fixed...
I hava had no problem with LTE/3G since day1.
I only get either G, E, H or H+ connection, but not yet 3G or LTE...
I had no data with 31st december nightly, came back to cm12.1.
I look forward this cm13 is stable !
LTE in Germany works (T-Mobile).
Really? I am German, too, but only G, E, H or H+. Provider is Vodafone.
Really! Perhaps another band?
No problems here. But using external SD is a problem. Any solutions?
No, not yet. Marshmallow has completely new memory management...
Mi Band no works on Bluetooth.
My xiaomi Mi Band no longer works with the cm-13.0-20160112-NIGHTLY-klteduos. Just can not be detected by ROM. Someone with the same problem?
nickaaai said:
Yeah same here, no LTE 3G. Clean install
Click to expand...
Click to collapse
You have to switch to other sim and turn that sim to 2G ( u may not turned to LTE before but it automatically turned into LTE) then switch back to data sim the ntry to change it to LTE or 3G..
shakthivsb said:
You have to switch to other sim and turn that sim to 2G ( u may not turned to LTE before but it automatically turned into LTE) then switch back to data sim the ntry to change it to LTE or 3G..
Click to expand...
Click to collapse
Thank you very much!!!
thiaguinhox said:
My xiaomi Mi Band no longer works with the cm-13.0-20160112-NIGHTLY-klteduos. Just can not be detected by ROM. Someone with the same problem?
Click to expand...
Click to collapse
Possible the same Problem in my reason. The mifit APP detect the miband but can Connect with it because the miband think its still connected with an other phone.
Next update i unpair first.
Gruß
Hello everyone,
I just flashed cm13 and found 2 bugs so far.
1: no setting for disabling either sim cards.
2: no setting for not pressing ok after inserting pin to unlock phone.
Anysolutions yet??
No. CM 13 has not been officially launched yet. It is still under development and proceeds step by step.
I have updated to stock 6.0.1 and updated Bootloader and Modem accordingly.
But from then on, I can't install CM13!
it gets in boot loop.
Has anybody been able to install CM13 after updating bootloader to 6.0.1?
@pc boy: it's not working atm, see https://forum.cyanogenmod.org/topic/125006-cm-13-wont-work-after-official-mm-upgrade/
Just got new LinageOS 14 and found there is no luck to use LTE(T-Mobile).
I tried several methods previous one but still no luck .....
Anyone has better idea to get LTE??????? :fingers-crossed:
Same problem here
I installed Lineage 14 on my N4 with base band **1701.07, I have read many posts but I don't know if it posible to enable LTE with this ROM.
Thanks in advance.
fernando.las said:
I installed Lineage 14 on my N4 with base band **1701.07, I have read many posts but I don't know if it posible to enable LTE with this ROM.
Thanks in advance.
Click to expand...
Click to collapse
You can get unstable LTE on nexus 4 I never got it to work properly you have to flash a hybrid modem/radio zip in a custom recovery to get LTE and make sure build prop is set up for LTE and make sure APN is set up for LTE and make sure ROM supports LTE
I've used at&t and T-Mobile neither seem to work properly with nexus 4 LTE
Idk how else to help have fun trying to get it to work
[email protected] said:
You can get unstable LTE on nexus 4 I never got it to work properly you have to flash a hybrid modem/radio zip in a custom recovery to get LTE and make sure build prop is set up for LTE and make sure APN is set up for LTE and make sure ROM supports LTE
I've used at&t and T-Mobile neither seem to work properly with nexus 4 LTE
Idk how else to help have fun trying to get it to work
Click to expand...
Click to collapse
Does Lineage support LTE?
I have a hybrid radio and I edited the build.prop to enable it and then I set the phone to LTE in the "Phone Info" settings and the APN is set to fast.t-mobile.com, but it just connects to HSDPA anyway.
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!