Database Users

[Q] G900F Network registration problem after flashing

Hi I have international version of S5 G900F. I flashed the phone with UK BTU stock rom. Now the problem is I cannot connect to the Network.
I tried going to Settings->More Networks -> Network Operators -> Select automatically . It took 5-10 mins to search but cannot connect.
Sim is not locked as it was working before I flashed the stock rom. also I read somewhere in internet that once the phone is region unlocked, it is permanently unlocked to use any other country sim. I don't know the original region of my phone but I bought it in Uk from 3rd party dealer not from any carrier.
I can think of two thing at the moment. It should be either regional locked again, but it does not prompt any thing to activate or enter pin or anything like that. or it should be wrong modem.
Is there a way to find if the phone is region locked ?
and is there a way to find correct region of the phone ?
the label on the box was removed so I cannot find from the box as well.
Thanks in advance.

I still haven't fixed this problem. Could someone suggest how to fix?

I've attached some screenshots with my phone info.
first image shows NETWORK:UNBLOCKED and IMEI Certi: PASS
-> I think this means, the phone is not blocked by network, and IMEI certificate has passed so it's not stolen or lost claimed phone.
another screenshot is the Firmware and CSC code/country information,
-> this means, this phone is build to sell in UK, so UK sim should unlock the regional lock.
Also the phone was working fine before I installed stock rom which I dowloaded from sammobile.
in the sceenshot, one of the network is connected but it says emergency call only because it cannot register to the network.
It is not sim lock also, because when I put T-mobile sim it does not ask for pin to unlock also.
what is wrong here. any idea guys? xda supposed to be the biggest android forum and samsung s5 is one of the most popular phone at the moment, isn't there anyone who have similar problem and solved? or atleast give some reason this cannot be fixed at all.

does the TMobile sim work? does it register with the network? If yes, then call the provider (of the other sim) and ask what's going on. Maybe you have a broken sim?

blesio said:
does the TMobile sim work? does it register with the network? If yes, then call the provider (of the other sim) and ask what's going on. Maybe you have a broken sim?
Click to expand...
Click to collapse
I've tried with Orange sim, and it still cannot register to the network. When I put the orange sim, it pop up a dialogbox asking to choose a network provider, there was two options, T-mobile and orange. So it is detecting the sim, but it cannot register.
And also, I tried my sim in another phone, and my sim works in another phone without any problem.

Did you try to flash the firmware again, and then after that restore factory defaults?

blesio said:
Did you try to flash the firmware again, and then after that restore factory defaults?
Click to expand...
Click to collapse
Yes I did, still it didn't work. I emailed samsung customer service with the problem, and they asked me to restore factory defaults.
I did that again but didn't work.
I tried one custom ROM as well. same problem in that rom.

You're rooted? If yes then there might be problem with the modem part of the ROM, can you install the official one part ROM and try with that?

blesio said:
You're rooted? If yes then there might be problem with the modem part of the ROM, can you install the official one part ROM and try with that?
Click to expand...
Click to collapse
I've installed stock rom several times, and several different versions( from here: http://www.sammobile.com/firmwares/1/?model=SM-G900F&pcode=0 ). Rooted several times, installed modem.bin files several times from many custom rom/ stock rom. None of them worked. I tried installing modem.bin when not rooted as well. And all the attempt failed.
I did everything I could possibly think of , Then I posted the question in the forum.

You have the IMEI ??!? Or it is lost?? Then only per efs-backup…
Or sim is broken…
Gesendet von meinem SM-G900F

lwiss said:
You have the IMEI ??!? Or it is lost?? Then only per efs-backup…
Or sim is broken…
Gesendet von meinem SM-G900F
Click to expand...
Click to collapse
I have imei , and sim is working fine, as I tested my sim in another phone.

uktel3315 said:
I have imei , and sim is working fine, as I tested my sim in another phone.
Click to expand...
Click to collapse
I'm having the same problem, but with G900H. I have stock firmware, rooted and everything's working fine until suddenly, I have no network. I restart the phone and get network again but only for a couple of minutes.
Sent from my SM-G900H using XDA Free mobile app

Any update?

XanoZuke said:
Any update?
Click to expand...
Click to collapse
Sry XanoZuke, I could not do anything to fix this, so I returned the phone and got another handset. I now have Exynos Octa-core version. Found snapdragon version is more power efficient. My phone gets heated very quickly.

uktel3315 said:
Sry XanoZuke, I could not do anything to fix this, so I returned the phone and got another handset. I now have Exynos Octa-core version. Found snapdragon version is more power efficient. My phone gets heated very quickly.
Click to expand...
Click to collapse
Don't worry, I found out that the motherboard was water damaged (the irony of life....), so a bought an LG G3.
Regarding the Exynos chip, I'm never buying anything exynos ever again. The performance is not as solid as Snapdragon and it gets heated really fast. Still, thanks for your reply! ?
Sent from my LG-D855 using XDA Free mobile app

uktel3315
Click to expand...
Click to collapse
So sad case remain unsolved, Got almost the same issue, Flashed 1st and last official firmware and custom rom without success NO NETWORK SIGNAL. No IMEI - Null regitered 15 zeros no efs backup etc.
Model : SM-G900S
ROM: XtrStoLite

edreab86 said:
So sad case remain unsolved, Got almost the same issue, Flashed 1st and last official firmware and custom rom without success NO NETWORK SIGNAL. No IMEI - Null regitered 15 zeros no efs backup etc.
Model : SM-G900S
ROM: XtrStoLite
Click to expand...
Click to collapse
have you found a solution yet? i have the exact same problem and have tried the same solutions as you listed...

have you found a solution yet? i have the exact same problem and have tried the same solutions as you listed...
Sorry i end up selling the phone as is..

Same deal
My g900f has no mobile services sims fine

I have the same problem.
Cannot connect to network after flashing new ROM. Since then I tried about 10 different original roms and couple custom roms. Number of different MODEMs and BOOTLOADERs but with no joy. SIM card works fine in different phone.
Also I tried to load different CERT files and QCN with Z3X Box but that didn't help either.
I've tried *#0011# command here are results:
with LTE/WCDMA/GSM auto-connect:
imgur.com/i69HCBM
with WCDMA only:
imgur.com/QPbvKHG
and GSM only:
imgur.com/8InhQWQ
It seems that GSM is not working at all.
At this stage I run out of ideas and probably gonna get rid of the phone as it is or use it as pimped-out ipod touch
(sorry for messed up links but I can't post to outside sites yet)

[PSA] **WARNING** DO NOT TRY TO DOWNGRADE YOUR G4 BOOTSTACK (in USA at least)

This was not written anywhere specifically on the LG G4 forums that I could find. But every flash-addict needs to be warned. It is something you want to know before you continue tinkering.
Several users (myself included) have made the unfortunate mistake of attempting to downgrade their bootstack (for various reasons) to a former version.
DO NOT DO THIS (at least for the USA T-Mobile H811 version, and possibly other USA versions, per @autoprime)! It will result in a hard brick! Specifically, this results in the "Qualcomm QDLoader HS-USB port ( 9008 )" error. Connecting your phone to a PC will pop up with this active connection, but nothing else. There is no download mode. There is no publicly available fix as of yet.
This WILL happen both through KDZ restore as well as flashing bootstack .zips.
Yes, an official KDZ image can BRICK your USA phone, if you try to rollback.
This is in stark contrast to other manufacturers (i.e. Samsung), where the attempt to flash an older bootloader/modem/radio will simply fail, but your phone is not bricked.
I have conferred with @autoprime, who confirmed that with each OTA firmware release (on T-Mobile it was 10H, and now 10N), the version # increments. Flashing a lower version # will result in brick.
I have searched far and wide for a DIY fix. Without the proper firmwares in the right format, as well as the right flashing software, your phone is done and must be sent in for LG repair.
To check what antiroll-back version you are on, input this sequence in the dialer (T-Mobile and ATT) and scroll down:
*#*#244773825625#*#*
Flashing a bootstack version less than this # (through KDZ or zip) will brick the phone. You are free to flash anything equal or higher than the version listed.
EDIT:
The 20i MM update for the H811 is v2 antirollback. The 10n bootstack is also v2. So flashing between the 2 (returning from MM to Lollipop) should not hard brick the phone.
EDIT 2:
The 20o MM update is v3 antirollback. Once you go 20o, you cannot go back.
For your flashing needs, I suggest you use LGUP and NOT LGFLASH, as LGFLASH will ignore the rollback flag and brick your phone without remorse!

Twitter announcement re: above from @autoprime
https://twitter.com/utoprime/status/641747333470912512

waylo said:
Twitter announcement re: above from @autoprime
https://twitter.com/utoprime/status/641747333470912512
Click to expand...
Click to collapse
This is probable because of the huge security flaw in older versions...they probably dont want anyone returning to a vulnerable state...stagefright was a nasty flaw and i think moving forward we will be able to roll back to what we have now

so bad... but if my firmware version and the KDZ are the same? ex. H81510c with H81510c.kdz...... this still works???

Sj12345 said:
so bad... but if my firmware version and the KDZ are the same? ex. H81510c with H81510c.kdz...... this still works???
Click to expand...
Click to collapse
Correct, shouldn't be a problem if they are the same revision.

thanks for the thread @waylo
I have checked the most recent international builds and all are still on "v0". Tho that could always change in the future... but as of today... "v0"
The original out of box Tmo h811 version was "v0"... after the first forced OTA it became "v1"... as of 10N it is now "v2".
I do not have access to the latest AT&T, Sprint, US Cellular or Verizon bootstacks (seems there are no new KDZ's for them and no one has dumped the files) so I cannot confirm if AT&T, Sprint, US Cellular or Verizon's latest OTAs also move it up to "v2" or if still on "v1".
Actually.. I'm not even sure if Sprint, US Cellular or Verizon got a 2nd OTA yet.. but I know AT&T has "10i". If any 10i users who are rooted could dump the bootstack for me and send it over I can confirm.
Latest I know of for Sprint is ZV5.. thats "v1". US Cellular.. not sure.. but 10C was "v1". Verizon... again.. not sure what latest is.. but 11A is "v1".
*edit*
just checked US991 10D... still "v1".

autoprime said:
thanks for the thread @waylo
I have checked the most recent international builds and all are still on "v0". Tho that could always change in the future... but as of today... "v0"
The original out of box Tmo h811 version was "v0"... after the first forced OTA it became "v1"... as of 10N it is now "v2".
I do not have access to the latest AT&T, Sprint, US Cellular or Verizon bootstacks (seems there are no new KDZ's for them and no one has dumped the files) so I cannot confirm if AT&T, Sprint, US Cellular or Verizon's latest OTAs also move it up to "v2" or if still on "v1".
Actually.. I'm not even sure if Sprint, US Cellular or Verizon got a 2nd OTA yet.. but I know AT&T has "10i". If any 10i users who are rooted could dump the bootstack for me and send it over I can confirm.
Latest I know of for Sprint is ZV5.. thats "v1". US Cellular.. not sure.. but 10C was "v1". Verizon... again.. not sure what latest is.. but 11A is "v1".
Click to expand...
Click to collapse
can you share the method to know if the bootstacks change with each ota?
I am pretty sure ATT has anti rollback on!
or give me the code for dump the bootstack

jamesd1085 said:
This is probable because of the huge security flaw in older versions...they probably dont want anyone returning to a vulnerable state...stagefright was a nasty flaw and i think moving forward we will be able to roll back to what we have now
Click to expand...
Click to collapse
That's a nice thought, but it will not be borne out until the next OTA comes out and we check the version. I wouldn't recommend you act on this supposition unless you have the time for a repair and a backup phone.

waylo said:
That's a nice thought, but it will not be borne out until the next OTA comes out and we check the version. I wouldn't recommend you act on this supposition unless you have the time for a repair and a backup phone.
Click to expand...
Click to collapse
It was just a shot in the dark...but i always read and am very careful what i flash...but on the other hand my best friend has a good bit of experience with Android repair and a very pricey computer and a rather nice jtag device...I'm just hoping lg isn't turning the way of Samsung and trying to block out development as it will be the reason if i ever leave lg devices...locking out development is a boner killer and i wont think twice but to move to more open oems...lol

I have a Sprint variant and we have only had one OTA as of right now.
Sent from my LGLS991 using Tapatalk

autoprime said:
thanks for the thread @waylo
I have checked the most recent international builds and all are still on "v0". Tho that could always change in the future... but as of today... "v0"
The original out of box Tmo h811 version was "v0"... after the first forced OTA it became "v1"... as of 10N it is now "v2".
I do not have access to the latest AT&T, Sprint, US Cellular or Verizon bootstacks (seems there are no new KDZ's for them and no one has dumped the files) so I cannot confirm if AT&T, Sprint, US Cellular or Verizon's latest OTAs also move it up to "v2" or if still on "v1".
Actually.. I'm not even sure if Sprint, US Cellular or Verizon got a 2nd OTA yet.. but I know AT&T has "10i". If any 10i users who are rooted could dump the bootstack for me and send it over I can confirm.
Latest I know of for Sprint is ZV5.. thats "v1". US Cellular.. not sure.. but 10C was "v1". Verizon... again.. not sure what latest is.. but 11A is "v1".
*edit*
just checked US991 10D... still "v1".
Click to expand...
Click to collapse
Does this also apply to TOT files? Say we upgrade to ZV6 when it comes out. Can we use a TOT file to flash to ZV5?

tabp0le said:
Does this also apply to TOT files? Say we upgrade to ZV6 when it comes out. Can we use a TOT file to flash to ZV5?
Click to expand...
Click to collapse
Anything that will attempt to rewrite the bootstack will cause this. So if the TOT file includes recovery + bootstack + system (I'm guessing it does if it behaves like a KDZ), it will have the same implications.

Well, for the G2 & G3, we had a fairly easy way to still fix the 9008 mode, i had even fixed my G2 that had those gazillion partitions show up in Linux (after shorting the chip pins). Maybe something like this can be done for the G4, especially if we output all of the G4's partitions from a working variant and then DD them back to the proper partitions.
For example this was for the G3
http://forum.xda-developers.com/lg-g3/general/unbrick-lg-g3-qhsusbbulk-qualcomm-9008-t3072091

Agimax said:
Well, for the G2 & G3, we had a fairly easy way to still fix the 9008 mode, i had even fixed my G2 that had those gazillion partitions show up in Linux (after shorting the chip pins). Maybe something like this can be done for the G4, especially if we output all of the G4's partitions from a working variant and then DD them back to the proper partitions.
For example this was for the G3
http://forum.xda-developers.com/lg-g3/general/unbrick-lg-g3-qhsusbbulk-qualcomm-9008-t3072091
Click to expand...
Click to collapse
I looked through all of that earlier, and those fixes sure made the G2 + G3 near-bulletproof recoverable phones. I'm sure a fix for the G4 would be similar as it's the same USB connection that's kept alive despite bricking.
Specifically for the G3 example, right now we're missing ALL required parts:
1. No TOT files available (actually just looking, Sprint is the only one). Can't convert KDZ to TOT as far as I could find.
2. Equally if not more important, no G4 chip setting available in the existing Board diag utility.

Well, as OP knows, I did this to mine. Its current status is Received at LG support. So now I nervously wait to find out if it is repairable (has to be). Their form letter doesn't make you feel comfortable, either
[FONT=&quot]Warranty Repair Notice:[/FONT][FONT=&quot] [/FONT]
[FONT=&quot]The device warranty does not cover physical, liquid, or cosmetic damage. If the device is damaged and deemed repairable charges may apply.[/FONT]
[FONT=&quot]If the device is deemed as un-repairable, the device will be returned to you as is.[/FONT]
[FONT=&quot]Charges may apply for units that are out of warranty by manufacturer‘s date code.[/FONT]
But when I needed the sim slot in my G3 replaced, I also received this email and a few days later, had my phone back in my hands all nicely repaired.

@waylo, @autoprime .... when you say antirollback, do you mean this???
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Sj12345 said:
@waylo, @autoprime .... when you say antirollback, do you mean this???
Click to expand...
Click to collapse
ooh fancy! im not sure if g4 has that displayed in the settings > about screen.. but maybe? it's not on mine tho (H815 10C)
But yes.. that would be what's being referred to in this thread. As your screen shows "1"... so any bootloader's at "v0" would brick phone... while any "v1" or higher" would work. and if you were to flash a "v2" bootloader.. the versioning would be updated and you could no longer flash anything under "v2".. etc etc.
I'd love to hear from other G4 users if they have this menu value on their phones... would make it easier on me to know which updates are at which version.

autoprime said:
ooh fancy! im not sure if g4 has that displayed in the settings > about screen.. but maybe? it's not on mine tho (H815 10C)
But yes.. that would be what's being referred to in this thread. As your screen shows "1"... so any bootloader's at "v0" would brick phone... while any "v1" or higher" would work. and if you were to flash a "v2" bootloader.. the versioning would be updated and you could no longer flash anything under "v2".. etc etc.
I'd love to hear from other G4 users if they have this menu value on their phones... would make it easier on me to know which updates are at which version.
Click to expand...
Click to collapse
It is not "settings > about", I used a secret code and scroll down
Code:
*#*#244773825625#*#*
Found in ATT G4 Forum XD
http://forum.xda-developers.com/att-g4/general/info-amazing-secret-cough-codes-t3201817

Sj12345 said:
It is not "settings > about", I used a secret code and scroll down
Code:
*#*#244773825625#*#*
Found in ATT G4 Forum XD
http://forum.xda-developers.com/att-g4/general/info-amazing-secret-cough-codes-t3201817
Click to expand...
Click to collapse
Wow, very useful.
On H811, on 10N, yes, anti-rollback listed as "2"
I will add this to the OP when I can.
Now we need an easy way to determine what anti-rollback # a flashable file is.

waylo said:
Wow, very useful.
On H811, on 10N, yes, anti-rollback listed as "2"
I will add this to the OP when I can.
Now we need an easy way to determine what anti-rollback # a flashable file is.
Click to expand...
Click to collapse
Yup, but I would like to know how to check this in a KDZ file...

A2017G Japan to A2017G European/other A2017G ROMs

Hi!
I am sorry if this has been asked here before. I'm fairly new to this kind of stuff.
So I'm a foreigner living in Japan. Due to the allure of local warranty, I decided to get the Axon 7 (A2017G JPV).
It has been months since the last Nougat update came to other A2017Gs but hasn't arrived on the A2017G JPV. So I thought, may be ZTE Japan was just taking a longer time, etc. So recently, I decided to contact customer support. And their answer was unclear at best. They were apparently still deciding if they would release a Nougat update for Axon 7.
So here's my question. Considering that my Axon 7 is also A2017G, is there a way for me to install the latest A2017G European ROM or any other A2017G Stock ROMs for that matter, without unlocking my bootloader and rooting? And get OTA updates from A2017G European? If so, can someone please kindly point me in the right direction, I'm getting a bit lost.
If that isn't possible, is there a way, to install the stock A2017G ROMs (aside from JPV) and then relock the bootloader afterwards?
Please help me. Thank you.

jjquinto said:
Hi!
I am sorry if this has been asked here before. I'm fairly new to this kind of stuff.
So I'm a foreigner living in Japan. Due to the allure of local warranty, I decided to get the Axon 7 (A2017G JPV).
It has been months since the last Nougat update came to other A2017Gs but hasn't arrived on the A2017G JPV. So I thought, may be ZTE Japan was just taking a longer time, etc. So recently, I decided to contact customer support. And their answer was unclear at best. They were apparently still deciding if they would release a Nougat update for Axon 7.
So here's my question. Considering that my Axon 7 is also A2017G, is there a way for me to install the latest A2017G European ROM or any other A2017G Stock ROMs for that matter, without unlocking my bootloader and rooting? And get OTA updates from A2017G European? If so, can someone please kindly point me in the right direction, I'm getting a bit lost.
If that isn't possible, is there a way, to install the stock A2017G ROMs (aside from JPV) and then relock the bootloader afterwards?
Please help me. Thank you.
Click to expand...
Click to collapse
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
Absolutely no need to root.
Enjoy.

Hamburgle4 said:
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
Absolutely no need to root.
Enjoy.
Click to expand...
Click to collapse
Hi
Thank you for replying so quickly.
Please bear with me as I am still a bit confused.
The link you gave mo contains Factory Images for the A2017G, right? Therefore, I should just put the factory images (zip file), into the root directory of my SD Card, and update via settings (no need to unlock bootloader or root, right?)?
My A2017G (JPV) is now on A2017G JPV1.0.0B03.
Which factory image should I use?
Thank you very much.

*Deleted for apparent "madness"

Are you mad?!!! This won't work as the signature's don't match.
At best you end up with a failed update, at worst a brick...

ultramag69 said:
Are you mad?!!! This won't work as the signature's don't match.
At best you end up with a failed update, at worst a brick...
Click to expand...
Click to collapse
Now I'm scared. Haha
Do you have any advice on how I should proceed with this? Thank you very much.

Hamburgle4 said:
*Deleted for safety reasons.
Click to expand...
Click to collapse
Considering @ultramag69 said, do you think I should still proceed with this?

I don't think you have to the same radio firmware with all the G version out there.... If you dare to try it probably you will end up bricking your phone.... So don try. Unless you are sure can warranty claim it if it is briked

Unfortunately this region locking thing came in, sometimes it's different hardware for different regions but mostly it's to stop the grey import trade...
Due to this it is a requirement to unlock your bootloader if you want to flash other region/carrier roms, which again is a trial in itself...
If you do wish to try it, make sure you have a flashable version of your FULL stock rom, not an OTA - the difference is an OTA is a patch, usually of a few hundred Mb or so to update parts of your ROM, the full ROM is a stand-alone installation that will completely replace the current ROM.
Generally this will get you out of hot water but be aware this is also not 100% guarantee...
It will probably also delete all your data, back up first....

ultramag69 said:
Unfortunately this region locking thing came in, sometimes it's different hardware for different regions but mostly it's to stop the grey import trade...
Due to this it is a requirement to unlock your bootloader if you want to flash other region/carrier roms, which again is a trial in itself...
Click to expand...
Click to collapse
What I'm confused about is he's not asking to flash A2017A/U firmware (where region locking comes into play) on his device, only another country's A2017G fw so why would he need to unlock bootloader? It's still fw for the global model if I understand correctly.

Hamburgle4 said:
What I'm confused about is he's not asking to flash A2017A/U firmware (where region locking comes into play) on his device, only another country's A2017G fw so why would he need to unlock bootloader? It's still fw for the global model if I understand correctly.
Click to expand...
Click to collapse
I'm on your side - the modem file might be different, but since the hardware is the same, it should work. Maybe the modem file has improved signal stuff for Japan, but it's extremely improbable considering ZTE's craptastic devs...
Also, what could be the worst thing that could happen? Here are the possibilities:
- Works: enjoy
- Installation failed: Should fail before even changing files anyways
- Soft brick: get to recovery, download full update zip, install, wait for Nougat
- Hard brick: "I woke up this morning and it was off, doesn't boot anymore, I want a replacement"
And if the modem is too crappy you can always go back to Japan's firmware

I believe that the Japanese version is different from the other G versions, at least on the modem level. Japan uses some bands that are not used by any other country in the world, so unless ZTE Japan decided to release the G model knowing that it would have some connectivity issues on all Japanese carriers, the Japanese G model must have at least a different modem.
Bold = band is present in the global G model
KDDI: CDMA BC0 / BC6, LTE 1/11/18/41
NTT Docomo: UMTS 1/9/19, LTE 1/9/19/21/28
Softbank: UMTS 1/8/11, LTE 1/8/9/41

I kinda get what you're getting at after looking further into the models. Basing off the spec sheets, Amazon JP has the exact same A2017G TD-LTE with matching bands sold by ZTE. Whereas on the ZTE JP page, it instead matches the bands of something named Axon 7 TD-LTE JP (couldn't find model number, but sounds like OP's A2017G). This has over half the exact bands available on A2017G, additional UMTS bands 6 & 19 and one CA band.
I think someone in another thread previously mentioned about potential signal issues with the Axon 7 being sold in Spain after flashing DE fw. Looking at their spec sheet, it appears to have a few bands missing, may have additional bands, but it's hard to tell since only the frequencies are stated. Could just be anecdotal as you'd think with the greater range of frequencies, it shouldn't face those issues. Anyways this is a separate matter, and potentially an apples to oranges comparison.

Thank you all for your advice and insights.
I figured, damn all worries, and just used the recovery mode to flash the update.zip.
Lo and behold, it was updated with seemingly no issue. Even tried if my mobile data would work properly. And it did.
Thanks everyone!

jjquinto said:
Thank you all for your advice and insights.
I figured, damn all worries, and just used the recovery mode to flash the update.zip.
Lo and behold, it was updated with seemingly no issue. Even tried if my mobile data would work properly. And it did.
Thanks everyone!
Click to expand...
Click to collapse
Great to hear. Also vindicates my apparent "madness" lol.

Hamburgle4 said:
Great to hear. Also vindicates my apparent "madness" lol.
Click to expand...
Click to collapse
Yeah it was nonsense, they are both a2017Gs anyways
We're all a bit mad though, flashing stuff on a 400 dolar thingy...

ive got the A2017 Chinese, bought from aliexpress. Ive rooted and installed the twrp flashable B15 from @djkuz, but the nougat firmware is awful for my DoCoMo phone reception (in far regional Nagasaki). So i need a method to either flash the modem for A2017G (not sure which B# release), or wait for the next chinese firmware release and hope for the best. Any suggestions or experiences to improve my reception? Is it the modem?
Thanks for all the contributions to this thread, as it has got me in the right direction.

jjquinto said:
Thank you all for your advice and insights.
I figured, damn all worries, and just used the recovery mode to flash the update.zip.
Lo and behold, it was updated with seemingly no issue. Even tried if my mobile data would work properly. And it did.
Thanks everyone!
Click to expand...
Click to collapse
Hey I know this is an old thread but I thought I would poke in and add my feedback. I also live in Japan and have the A2017G. I bought it because it was the only phone on the market at the time that [supposedly] supported Google Daydream. Later I realized that only the US version actually worked with Daydream. Later on support was added to European ROMS (when upgraded to 7.1.1). But for some reason the Japanese ROM, despite being 7.1.1 would say 'Incompatible Phone', even when installed manually. I contacted ZTE's customer service, which was terrible; all they said was "we don't know when it will be supported". This was about a year ago, so this week I just got sick of waiting, found the German firmware (A2017G-N-B10), installed it and everything works fine. The radios have no issues, and I was able to download Daydream right from the marketplace.
Thanks for everyone who contributed to this thread!

Was I scammed or is this a "real" phone?

Context: Bought a an s8 for cheap, model number comes up as g950fd, went about installing stuff then went to get a sim card the next day.
Aaaannddd I can't connect to my network, and upon checking i have no imei number, and my baseband is uknown. Only thing I have is a serial # that comes up "clean" upon checking on sndeep.info
I casually browse/lurk this forum so I'm not gonna ask for IMEI advice. Rather I'd like to know if I should be going after this dude (who has about 2 days head start I guess), or I can take this somewhere to have it "fixed"?
p.s. I'm in the philipines so IMEI services aren't illegal (I think?)
Thanks!

Best thing to do is to reinstall firmware with smart switch software. If after that it still says no imei and no baseband then whoever you bought the phone off, they messed up the efs possibly.

panicMode said:
Context: Bought a an s8 for cheap, model number comes up as g950fd, went about installing stuff then went to get a sim card the next day.
Aaaannddd I can't connect to my network, and upon checking i have no imei number, and my baseband is uknown. Only thing I have is a serial # that comes up "clean" upon checking on sndeep.info
I casually browse/lurk this forum so I'm not gonna ask for IMEI advice. Rather I'd like to know if I should be going after this dude (who has about 2 days head start I guess), or I can take this somewhere to have it "fixed"?
p.s. I'm in the philipines so IMEI services aren't illegal (I think?)
Thanks!
Click to expand...
Click to collapse
=======================================================================================
The only thing i would say about that, is this phone was locked to a network, and someone used a software to unlock it. But the issue with unlocked phone from their network, is that you might lose the IMEI, and i you lose that, you might not be able to use the phone properly. My only suggestion is to go to sammobile.com and download one of the ROMs from there, yet you need to know which network it was in before the happen to it. I think you need to speak with the buyer and ask about the name of the network.

You're basically scammed.
because the previous owner did rootings and stuffs i guess, (check if warranty is 0x0 instead of 0x1.)
If you've rooted and played around system files, wipes etc. You will probably lose your imei @ 10% chance possibility?
Unless you have a EFS Partition backed up before hand from this phone from TWRP. You're basically screwed?
https://forum.xda-developers.com/galaxy-s8/help/lost-imei-efs-folder-messed-t3614320
And yeah try reflashing firmware from your country etc.

panicMode said:
Context: Bought a an s8 for cheap, model number comes up as g950fd, went about installing stuff then went to get a sim card the next day.
Aaaannddd I can't connect to my network, and upon checking i have no imei number, and my baseband is uknown. Only thing I have is a serial # that comes up "clean" upon checking on sndeep.info
I casually browse/lurk this forum so I'm not gonna ask for IMEI advice. Rather I'd like to know if I should be going after this dude (who has about 2 days head start I guess), or I can take this somewhere to have it "fixed"?
p.s. I'm in the philipines so IMEI services aren't illegal (I think?)
Thanks!
Click to expand...
Click to collapse
sofir786 said:
Best thing to do is to reinstall firmware with smart switch software. If after that it still says no imei and no baseband then whoever you bought the phone off, they messed up the efs possibly.
Click to expand...
Click to collapse
I would follow this advice.This is about the same options i would do my self.Sometimes IEMIs can get messed up with basebands and such so no harm in trying stock restores but most def contact seller and return it if possible

Thanks for all the feedback guys. I'll try and get my money back but if this was done with prior knowledge that the phone was wonky my bet is he's gone.
As for the technical advice, will definitely look into it as I'm a complete novice. Will update when something comes up.
Thanks all.

panicMode said:
Thanks for all the feedback guys. I'll try and get my money back but if this was done with prior knowledge that the phone was wonky my bet is he's gone.
As for the technical advice, will definitely look into it as I'm a complete novice. Will update when something comes up.
Thanks all.
Click to expand...
Click to collapse
The reflashing of the firmware is quite easy,I hate it for ya buddy if he is gone....It's sad to see people scam others hard earned money....

Not a scam!
panicMode said:
Context: Bought a an s8 for cheap, model number comes up as g950fd, went about installing stuff then went to get a sim card the next day.
Aaaannddd I can't connect to my network, and upon checking i have no imei number, and my baseband is uknown. Only thing I have is a serial # that comes up "clean" upon checking on sndeep.info
I casually browse/lurk this forum so I'm not gonna ask for IMEI advice. Rather I'd like to know if I should be going after this dude (who has about 2 days head start I guess), or I can take this somewhere to have it "fixed"?
p.s. I'm in the philipines so IMEI services aren't illegal (I think?)
Thanks!
Click to expand...
Click to collapse
Don't panic just yet! I'm actually super new back into the android game, ditched iphone a few weeks ago and got myself an s8. I started looking into rooting my phone since the last time I rooted an android phone was back when T-mobile had their G1's. So, I thought I had to really re-educate myself upon what android now has to offer. Well, going through different sites, and the different models, versions, variants, etc about the s8, I did come across the G950FD. It's a legit phone. I believe (and feel free to correct me if i'm wrong) they were only sold in India, unlocked, and dual sim! The sim tray in the phone can either hold 2 sim cards, (1 nano sim, 1 micro sim) or if you preferred to extend the capacity instead, the slot for the micro sim, can hold a micro SD card instead, since they're the same size, give or take. The reason it doesn't have an IMEI nor baseband is because the dual-sim capability, thus why the serial number comes back clean. You weren't scammed, you're actually quite lucky since those versions of the s8 were sold in India, and you managed to come into possession of one, for cheap, yet alone a phone everyone here thought was a scam as well. I wish I could have one! But unfortunately, here in the states, I have a CDMA carrier and dual-sim phones don't support it. But heres a link to the source of your awesome new phone! Now you can relax! You not only got an s8, you have a rare one! Enjoy it!
EDIT: I tried to link you to the source, but being a new member I couldn't. However, if you search for Samsung g950fd, it should link you to the Samsung website, where your phone is it. Hope this has helped you feel more at ease with your phone!

G950fd is an international version. I believe the FD has an unlockable bootloader, which makes it sought after. Somebody probably wiped efs In Recovery by accident.

BBREEDMEE said:
Don't panic just yet! I'm actually super new back into the android game, ditched iphone a few weeks ago and got myself an s8. I started looking into rooting my phone since the last time I rooted an android phone was back when T-mobile had their G1's. So, I thought I had to really re-educate myself upon what android now has to offer. Well, going through different sites, and the different models, versions, variants, etc about the s8, I did come across the G950FD. It's a legit phone. I believe (and feel free to correct me if i'm wrong) they were only sold in India, unlocked, and dual sim! The sim tray in the phone can either hold 2 sim cards, (1 nano sim, 1 micro sim) or if you preferred to extend the capacity instead, the slot for the micro sim, can hold a micro SD card instead, since they're the same size, give or take. The reason it doesn't have an IMEI nor baseband is because the dual-sim capability, thus why the serial number comes back clean. You weren't scammed, you're actually quite lucky since those versions of the s8 were sold in India, and you managed to come into possession of one, for cheap, yet alone a phone everyone here thought was a scam as well. I wish I could have one! But unfortunately, here in the states, I have a CDMA carrier and dual-sim phones don't support it. But heres a link to the source of your awesome new phone! Now you can relax! You not only got an s8, you have a rare one! Enjoy it!
EDIT: I tried to link you to the source, but being a new member I couldn't. However, if you search for Samsung g950fd, it should link you to the Samsung website, where your phone is it. Hope this has helped you feel more at ease with your phone!
Click to expand...
Click to collapse
Dude I have the FD version and I have 2 IMEI's. Also, it's not just in India as it's also popular in UAE. Please do your research before replying.
Sent from my SM-G950F using Tapatalk
---------- Post added at 09:00 AM ---------- Previous post was at 08:53 AM ----------
bushako said:
Dude I have the FD version and I have 2 IMEI's. Also, it's not just in India as it's also popular in UAE. Please do your research before replying.
Sent from my SM-G950F using Tapatalk
Click to expand...
Click to collapse
Pic
Sent from my SM-G950F using Tapatalk

Vinnvin said:
You're basically scammed.
because the previous owner did rootings and stuffs i guess, (check if warranty is 0x0 instead of 0x1.)
If you've rooted and played around system files, wipes etc. You will probably lose your imei @ 10% chance possibility?
Unless you have a EFS Partition backed up before hand from this phone from TWRP. You're basically screwed?
https://forum.xda-developers.com/galaxy-s8/help/lost-imei-efs-folder-messed-t3614320
And yeah try reflashing firmware from your country etc.
Click to expand...
Click to collapse
Can we tone the FUD down a bit? "Rootings and stuffs" does not equate a 10% chance of losing your imei. There is a 0% chance of that happening. There is a 100% chance of that happening if you mess up and explicitly do it yourself, but even that is pretty hard to accomplish.
There are more than enough legitimate cautionary tales and lessons to be learned from this to spread around. Let's not ad not only unnecessary (and incorrect) information needlessly

So spent the last couple of days on a wild goose chase. Long story short, guy's gone.
So, novive me is gonna follow the guides on here. I've skimmed a through a few and would like some clarification before i end up messing this phone up even more.
What "stock rom" should i be looking for?
And for what model in the sense that the phone's model number is G950fd, but the Google play store tags it as g950f. Is that one letter difference important? Did this guy change the model name? Is there a way to double check?
Sorry if I'm coming off as paranoid. I've never done a flash before, nor have i ever been in this kind of situation.
Thanks!

Well, there's still hope. The seller had to possibly tampered with the firmware before giving it away towards you. Advice given before hand about re-flashing the firmware is strongly recommended to double check if everything is correct. You can either use sammobile.com or updato.com whichever you would prefer. since you have the SM-G950FD version, put that model number in the search bar and get the most up-to-date fw you can get. Use ODIN to re-flash the firmware back onto your phone and wait a couple of minutes to see if everything is back to normal. If the baseband and IMEI is still unknown, then we'll have to see another method to get it back to normal. But for now, re-flash the stock firmware.
Edit: Tell me what carrier you're using and i'll supply you with a link to the firmware you need, for now, download ODIN from here if you don't have it yet: https://samsungodin.com/

DaNamesFrank said:
Well, there's still hope. The seller had to possibly tampered with the firmware before giving it away towards you. Advice given before hand about re-flashing the firmware is strongly recommended to double check if everything is correct. You can either use sammobile.com or updato.com whichever you would prefer. since you have the SM-G950FD version, put that model number in the search bar and get the most up-to-date fw you can get. Use ODIN to re-flash the firmware back onto your phone and wait a couple of minutes to see if everything is back to normal. If the baseband and IMEI is still unknown, then we'll have to see another method to get it back to normal. But for now, re-flash the stock firmware.
Edit: Tell me what carrier you're using and i'll supply you with a link to the firmware you need, for now, download ODIN from here if you don't have it yet: https://samsungodin.com/
Click to expand...
Click to collapse
Ok so I'm going through the available firmwares in the Philippines and they have ones available for the g950fd. They do not have any available for the g950f.
Now, I'm scared bec the Google play store says my phone is NOT a g950fd, and is in fact a g950f. I also don't have a sim2 label on my sim card tray.
Is there a way to double check what model i actually have?

panicMode said:
Ok so I'm going through the available firmwares in the Philippines and they have ones available for the g950fd. They do not have any available for the g950f.
Now, I'm scared bec the Google play store says my phone is NOT a g950fd, and is in fact a g950f. I also don't have a sim2 label on my sim card tray.
Is there a way to double check what model i actually have?
Click to expand...
Click to collapse
Settings, about phone, model number should be under device name

panicMode said:
So spent the last couple of days on a wild goose chase. Long story short, guy's gone.
So, novive me is gonna follow the guides on here. I've skimmed a through a few and would like some clarification before i end up messing this phone up even more.
What "stock rom" should i be looking for?
And for what model in the sense that the phone's model number is G950fd, but the Google play store tags it as g950f. Is that one letter difference important? Did this guy change the model name? Is there a way to double check?
Sorry if I'm coming off as paranoid. I've never done a flash before, nor have i ever been in this kind of situation.
Thanks!
Click to expand...
Click to collapse
The only way to find out for sure what phone model you have is to put your phone in download mode. There you'll see your phone number. That's the only accurate way. Anything else it's useless. What Google play store show, what phone number is shown on settings it's irrelevant. The phone model listed by Google play store or on your phone settings can be changed very easy but editing a simple line on build.prop.
Now about your phone. From what you described it's obvious that you have your EFS partition corrupted. Without a backup of your EFS partition you're screwed. You can download and flash whatever firmware you want. It's just a waste of time. Flashing another firmware will not going to fix it. You have a backup of EFS partition? If yes, then it's great. Search for a guide for restoring EFS partition. If not, stop wasting your time. The result can be only one: a very expensive paperweight.

Ah thanks, so according to download mode I indeed have a g950f and not aG950fd - efs professional also shows the same thing
How screwed am I now that:
a. i'm apparently running on firmware that tags the unit as G950fd
b. sammobile doesn't show any G950f firmware for the philippines
c. i have no idea where this phone has been prior to my purchasing it
thanks

panicMode said:
Ah thanks, so according to download mode I indeed have a g950f and not aG950fd - efs professional also shows the same thing
How screwed am I now that:
a. i'm apparently running on firmware that tags the unit as G950fd
b. sammobile doesn't show any G950f firmware for the philippines
c. i have no idea where this phone has been prior to my purchasing it
thanks
Click to expand...
Click to collapse
Doing some research, there isn't any philippine fw for the g950f, hence the firmware being g950fd. I'll try to edit more with more info to find.

I am disappointed by all the FUD and paranoid advice in this thread so far.
@panicMode
Install the following app from playstore - Samsung Phone Info
And then post screenshot of each tab. MAKE SURE to hide IMEI and Serial number if visible in any screenshot.
If you are not sure how to do that, then you can PM me the screenshots or your telegram handle to take this conversation private.
There is no need to panic when there are ways to ascertain.

madnav said:
I am disappointed by all the FUD and paranoid advice in this thread so far.
@panicMode
Install the following app from playstore - Samsung Phone Info
And then post screenshot of each tab. MAKE SURE to hide IMEI and Serial number if visible in any screenshot.
If you are not sure how to do that, then you can PM me the screenshots or your telegram handle to take this conversation private.
There is no need to panic when there are ways to ascertain.
Click to expand...
Click to collapse
When I buy a device I expect it to have A IEMI also I dont expect to have to fix it myself....
Please next time take this into consideration with your disappointment As Most of the advice in this thread is legitimately correct AS no one should have to Fix it contacting the orig seller and then reflash correct firmware is proper steps.Just because you do not feel it is Does not make it "disappointing"

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!