Database Users

[FIXED] [S4 I9505] I have to update modem to fix CM11 issue, but there's no update.

Issue fixed. Updated to XXUGNG8.
Issue: network disconnects when I lock my screen, which results a phone being useless a brick on sleep.
Issue link: https://jira.cyanogenmod.org/browse/CYAN-5379
Solution: update firmware/modem/bootloader.
Solution issue: there's no available firmware update for my device.
Hey everybody,
You guys probably have heard that newer version of Cyanogenmod have issues with network. It seems like there's only way to fix it is updating modem and bootloader.
I have international i9505 with baseband of XXUAME2. I looked it up on Samsung firmware database and it turned out that it is for Russia and last update was in May 2013 and for Android 4.2.2.... the catch is that it's made for i9500. I don't know if it's a mistake or not, database said so.
I bought it last year from some sketchy shop for low, low price in Russia and phone was in french language and was made for french carrier. It doesn't matter because phone works perfectly fine and I wiped it clean by flashing it to Cyanogenmod.
Now recently I just moved to USA, using T-Mobile prepaid plan with my international I9505. There wasn't any issues using Russian baseband until Cyanogenmod updated.
I tried looking for USA T-Mobile baseband firmware for my device but there's nothing to be found. I tried looking for Russia's update for my device. Nothing found, just XXUAME2 that was last updated in May 2013.
How can I fix this new Cyanogenmod issue? People keep saying that updating their firmware fixed the issue, but I can't update my device. What should I do? Should I update to T-Mobile baseband if it's available?
Thanks a lot.

Issue fixed. Updated to XXUGNG8.

[T Mobile] Signal is cutting out, someone suggested updating bootloader / radio? How?

I have an S5 from T-Mobile, it is several months old. It is currently using Cyanogenmod 12.1 Nightly from July 4.
I updated to the October 21 Nightly a few days ago, and started seeing an issue, where the mobile signal cuts out after a while (usually after I wake up the phone after a long time of inactivity, such as sleeping). I will see a mobile signal, but there is an exclamation point next to it. LTE data won't work. MMS won't work. I don't know if SMS or Phone Calls will work, but I suspect not.
I asked on Reddit, and someone suggested that my phone might need a Bootloader / Radio update? Someone made the following suggestion:
"Many Samsung devices require a bootloader/radio update to run the latest CyanogenMod versions. You need to make sure it is both the bootloader and radio, becasue many update packages will do one or the other. You can find the flashable zips on the xda forums. "​
In the mean time, I have downgraded back to an old July 4 Nightly, but it looks like the problem is now persisting. So, finding a solution is now more urgent.
Does anyone know how to update the Bootloader / Radio for my T-Mobile S5? Directions / Links would be helpful... :-s Kinda newb at this.
Or, if you could recommend a ROM that you prefer over CM, that would be welcome info as well. I do like CM, but you know what they say, the grass is always greener. Plus, I think everyone here likes to tinker.
Device Model: SM-G900T
CM Version: 12.1-20150704-NIGHTLY-klte
Android Version: 5.1.1
Baseband Versioin: G900TUVU1DOB1

Galaxy S5 Plus (SM-G901F) losing mobile signal and gps after Marshmallow update

After updating to Android 6.0.1, the phone is randomly losing mobile and gps signal. It happens about 30-40 times a day, especially when moving around, like driving . Almost every time I look at my phone, I see "No service, network not found" or "gps lost" messages. After about 10 seconds, the signal comes back and everything is ok again. Very annoying and impossible to use navigation apps, like Waze and Google Maps. I have made a soft reset, a hard reset, wiped all data and cleared the phone cache, checked and cleaned the Sim card. Nothing helps. Before update the phone worked brilliantly. Also noticed, that the signal won't drop when using wifi, the problem occurs only when data connection is on. And I'm not the only one, I have 2 friends with the same phone and the same problem. Looks like a software issue. Can somebody help?
PS. I'm from Estonia, and the software version is G901FXXU1CPE1/G901FBAL1CPE1
Thank you in advance...

Hi mate,
I Have the same device although mine uses a custom ROM but the problem I experienced was exactly like yours
Samsung released a new issue of the 6.0.1 for our phone, PDA G901FXXU1CPF6 CSC G901FPHN1CPF2 you can login to the sammobile site and download it
As I said above I have a custom ROM so I only flashed the modem firmware from that release and worked fine after that!
Hope that will help you!

Thanks for your response! But I'm using a totally stock phone and I see, that this firmware is for Netherlands. Does it work on my phone or I have to wait until the Baltic version is released?

MirandoKersman said:
Thanks for your response! But I'm using a totally stock phone and I see, that this firmware is for Netherlands. Does it work on my phone or I have to wait until the Baltic version is released?
Click to expand...
Click to collapse
Hello,
I don't see any reason why it wouldn't work but just in case make a note of your Access point name settings in the mobile networks tab just to make sure that everything is the same after you flash the new release .
If you follow the steps as described in the sammobile site you won't have any problems.
What I have noticed however is that after I flashed the new modem firmware the mobile hotspot does not work anymore but this has to do with my custom ROM.
It worth trying though the performance of the phone after that is exceptional and the signal strength is higher than before and most importantly, doesn't crash anymore..
Let me know if you need help and keep me posted about your results!

i had that ROM for a while, didnt help in my case, still same issue. I'm currently on XXU1CPG3 with which the issue still persists, gonna try flashing the new TPD CSC ROM (currently the newest) ROM Version CPH9. My baseband is still CPE1, which do you guys have?

Randi said:
i had that ROM for a while, didnt help in my case, still same issue. I'm currently on XXU1CPG3 with which the issue still persists, gonna try flashing the new TPD CSC ROM (currently the newest) ROM Version CPH9. My baseband is still CPE1, which do you guys have?
Click to expand...
Click to collapse
Baseband:
G901FXXU1CPE1, I have a totally stock phone with the latest official firmware.

Latest official firmware from where? ("latest" is region dependent)
Ok, the cph firmware updated the baseband to cph, on my side it's only been a while 14 hrs since flashing but it seems the signal problem is finally fixed

Randi said:
i had that ROM for a while, didnt help in my case, still same issue. I'm currently on XXU1CPG3 with which the issue still persists, gonna try flashing the new TPD CSC ROM (currently the newest) ROM Version CPH9. My baseband is still CPE1, which do you guys have?
Click to expand...
Click to collapse
From what I understand it doesn't matter which ROM you are using the baseband is the one that causing this problem..
As I said I have a custom ROM and when I had the CPE1 baseband then I had all these problems.
If you flashed the ROM and your baseband is still CPE1 then something did not go per plan I think..
After flashing ONLY the modem firmware from the CPF6 release to my SMG901F is reported that the baseband version is CPG2 however..
This version works for sure..
I might try the CPH9 release now to see if the issues i have with the mobile hotspot will be solved

George A. said:
From what I understand it doesn't matter which ROM you are using the baseband is the one that causing this problem..
As I said I have a custom ROM and when I had the CPE1 baseband then I had all these problems.
If you flashed the ROM and your baseband is still CPE1 then something did not go per plan I think..
After flashing ONLY the modem firmware from the CPF6 release to my SMG901F is reported that the baseband version is CPG2 however..
This version works for sure..
I might try the CPH9 release now to see if the issues i have with the mobile hotspot will be solved
Click to expand...
Click to collapse
I'll try to install that CPH9 release too. Let's see what happens, because I have tried everything else.
To me it seems, that this CPE1 version is having problems with switching between network modes. I checked, that in Settings- Mobile networks- Network mode is set to LTE/3G/2G (automatic connect), but I haven't seen H+, H or Edge symbols on top of the screen. Only 4G/4G+ or no reception at all. Like it's locked in 4G network or something. And sometimes when there is no 4G network coverage, there is also no signal. But that is just my logic...

Ok, I flashed the latest CPH9 firmware and my baseband changed to CPH3. CSC Country turned to Netherlands instead of Baltic. And it seems that the issue is fixed!
I made a little test, I went to the cellar to get bad 4G reception and instead of showing No Service, 4G turned to H without losing the cell signal. Let's wait and see...
Thank you guys a lot for your help! :good:

Hi
1) I have the latest PHN version for SM-G901f stock& rooted. I see the TPD version, will it have dutch language if i flash it ( without wipe anything) in ODIN?
2) What does TPD stand for anyway?
I want to do this because i see TPD has latest security_patch sept 1
With rooted Phone there is no way (as far as i know (3) ) to get security updates without getting the message it as screenshot given under here....

I can confirm that the issue has been fixed for me as well! ****ing finally! :cyclops:
Btw it will not switch to Dutch

MirandoKersman said:
After updating to Android 6.0.1, the phone is randomly losing mobile and gps signal. It happens about 30-40 times a day, especially when moving around, like driving . Almost every time I look at my phone, I see "No service, network not found" or "gps lost" messages. After about 10 seconds, the signal comes back and everything is ok again. I have made a soft reset, a hard reset, wiped all data and cleared the phone cache, checked and cleaned the Sim card....
PS. I'm from Estonia, and the software version is G901FXXU1CPE1/G901FBAL1CPE1
Thank you in advance...
Click to expand...
Click to collapse
I'm from Indonesia and buy used g901f from singapure,
I have same problem with marsmallow latest update too
My software version is G901FXXU1CPH3/G901FOLB1CPH1/G901FXXU1CPH1
How to fix it? Step by step..
Thank you before..
*) sorry for my bad english
---------- Post added at 01:43 AM ---------- Previous post was at 01:36 AM ----------
Randi said:
I can confirm that the issue has been fixed for me as well! ****ing finally! :cyclops:
Btw it will not switch to Dutch
Click to expand...
Click to collapse
Pliss help me with step to fix it

Hello! It seems all the firmwares ending with CPE1/CPH1 are problematic. You can try some other firmware from http://www.sammobile.com/firmwares/database/SM-G901F/
Select the firmware what seems best for you, don't select the operator-based ones, like vodafone etc. If you click on the firmware and scroll the page down, you will see step-by-step instructions how to install it. Good luck!

Ok but i can't found latest country band FW have same with indonesia network (except FW country singapure now i using it)
So i'll try to download FW update 2016-09-03
Country Unknown
Build date Tue, 13 Sep 2016
Security Patch Level 2016-09-01
Product code ORL
PDA G901FXXS1CPI4
CSC G901FORL1CPF1

How do I go from 7.0 with "U" software to 8.0?

I'm trying to wrap my head around all this, but my head is spinning. In December I was looking to get my S7 flat to 7.0 rooted. I discovered that root can only be achieved with eng kernel and that has its drawbacks. I decided I don't need/want root at that cost of stability, performance and battery life. Somehow I settled on installing a "U" variant that seemed to work well with less Verizon bloat. I couldn't get the S Health app and monitors on the back of the phone working, but I figured I could live with that. Recently I tried casting my phone to a Amazon Fire Stick and discovered the "Smart View" button is missing and I couldn't figure out how to get it back, so I might've lost that too. I also discovered in the past nine months Oreo is out with additional features and I figure if I'm going to go through the hassle of reinstalling, I might as well upgrade.
So, I hear root with Oreo is better than it's been, but not perfect, so I'l like to upgrade to unrooted oreo, either stock or debloated (if such a version exists without tradeoffs). Is there a certain version I'm supposed to go to so there's some flexibility in reinstalling the OS? Like I know sometimes versions of software are released that upgrade little, but patch exploits.
Also, if I do get whatever version of Oreo installed, do I then ignore OTA updates going forward? Is there any advantage to that?
And I can use the mobile hotspot feature. I don't think I have any special plan to accommodate that, nor do I have an unlimited plan (with Verizon). Is that intended, or is that from the "U" variant. Would I lose that?
My phone's info is below, if anyone can decipher what I did:
Model #: SM-G930U
Android Version: 7.0
Baseband Version: G930UUEU4BQE2
Kernel Version: 3.18.31
Build #: NRD90M.G930UUEU4BQE2
I apologize, I know my nomenclature isn't up to snuff. I realize that this stuff isn't for the casual user, at least on this phone. It's very hard to figure out what's current if you're not in the loop.
Thank you for any help you can offer.

If possible, I'd try just doing an Odin of the full Verzion equivalent to what you are on. That has the best chance of being compatible with the bootloader you are on. If not, you may have to downgrade to earlier U variant and then switch to equiv V variant. If I recall correctly the *BRA1 firmware intersected on all carrier releases. In my case in the past, I was on too new of an AT&T variant and it wouldn't let me switch because the model didn't match. I had to switch to the generic U variant and then go to Verizon variant after.
In your case I'd try either of these in full Odin form (and may need princecomsy Odin or other that will force it):
G930VVRS4BQC9 - Closest Verizon V variant firmware that is released same month as your current version (a couple weeks later)
G930VVRU4CRE5 - June 5th 2018 Verizon V variant firmware based on 8.0
Edit:
Alternatively I think you should be able to go to the latest U generic variant 8.0 firmware, whatever that would be. I think that's G930UUEU4CRG2 at the moment

djh816 said:
If possible, I'd try just doing an Odin of the full Verzion equivalent to what you are on. That has the best chance of being compatible with the bootloader you are on. If not, you may have to downgrade to earlier U variant and then switch to equiv V variant. If I recall correctly the *BRA1 firmware intersected on all carrier releases. In my case in the past, I was on too new of an AT&T variant and it wouldn't let me switch because the model didn't match. I had to switch to the generic U variant and then go to Verizon variant after.
In your case I'd try either of these in full Odin form (and may need princecomsy Odin or other that will force it):
G930VVRS4BQC9 - Closest Verizon V variant firmware that is released same month as your current version (a couple weeks later)
G930VVRU4CRE5 - June 5th 2018 Verizon V variant firmware based on 8.0
Edit:
Alternatively I think you should be able to go to the latest U generic variant 8.0 firmware, whatever that would be. I think that's G930UUEU4CRG2 at the moment
Click to expand...
Click to collapse
Thank you for the reply! I really wasn't expecting any replies, there's just too much going on in my post.
I backed up everything tonight so when I flash it I can wipe everything and do it right. This sammobile site lists all the firmware updates and that helped somewhat demystify things. Is it true that the fifth digit from the right of build is the bootloader? If that's the case, does that mean I can install any version from the last MM update through the september oreo update and upgrade and downgrade between them without issue since they all have a "4" for that digit? Is the bootloader the thing that sometimes gets updated, preventing downgrades or is the baseband and modem also something that I need to consider. If I just install the latest verizon oreo update, am I limited in downgrading?
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930V/

Umbra. said:
Thank you for the reply! I really wasn't expecting any replies, there's just too much going on in my post.
I backed up everything tonight so when I flash it I can wipe everything and do it right. This sammobile site lists all the firmware updates and that helped somewhat demystify things. Is it true that the fifth digit from the right of build is the bootloader? If that's the case, does that mean I can install any version from the last MM update through the september oreo update and upgrade and downgrade between them without issue since they all have a "4" for that digit? Is the bootloader the thing that sometimes gets updated, preventing downgrades or is the baseband and modem also something that I need to consider. If I just install the latest verizon oreo update, am I limited in downgrading?
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930V/
Click to expand...
Click to collapse
Purely anecdotal but in my case I think the newer version I had was the issue. I don't believe you are limited in downgrading if you have a full signed odin of your current model variant that you can downgrade too. I think the main issues come in when you are going from a different model and a newer/older firmware. If you are staying on latest G930V Verizon firmware for example, I believe you could downgrade as far back as needed with full Odin. Just not necessarily U variant firmware without finding the crossover point with that firmware (like AT&T and Verizon variants both on BRA1 firmware). I could be mistaken on the requirements but messing around with flashing an older rom with same 930 variant, then switching to a new variant from that may work. In my case I had to downgrade to BRA1 AT&T, then switch to BRA1 generic 930U, then switch to Verizon BRA1 930V. Also the stock version of Odin didn't like me switching variants but princecomsy version worked (not sure if that works well with new firmwares though). As you say though, there may be some limits in downgrading depending on what bootloader you are on. I don't think I've personally had a situation where I couldn't but with all those efuses out there who knows..But even then you should be able to pivot to another variant of similar release date

djh816 said:
Purely anecdotal but in my case I think the newer version I had was the issue. I don't believe you are limited in downgrading if you have a full signed odin of your current model variant that you can downgrade too. I think the main issues come in when you are going from a different model and a newer/older firmware. If you are staying on latest G930V Verizon firmware for example, I believe you could downgrade as far back as needed with full Odin. Just not necessarily U variant firmware without finding the crossover point with that firmware (like AT&T and Verizon variants both on BRA1 firmware). I could be mistaken on the requirements but messing around with flashing an older rom with same 930 variant, then switching to a new variant from that may work. In my case I had to downgrade to BRA1 AT&T, then switch to BRA1 generic 930U, then switch to Verizon BRA1 930V. Also the stock version of Odin didn't like me switching variants but princecomsy version worked (not sure if that works well with new firmwares though). As you say though, there may be some limits in downgrading depending on what bootloader you are on. I don't think I've personally had a situation where I couldn't but with all those efuses out there who knows..But even then you should be able to pivot to another variant of similar release date
Click to expand...
Click to collapse
I don't still know about downgrading and switching, but I can live with that. I took the plunge and opted to install the latest Verizon firmware last night. Surprisingly I was able to just install it over the U firmware with basic Odin. I Then went into recovery and did a factory reset. It's gonna take awhile to set everything up how I like, but S Health works, I've got the Smart view toggle (didn't get to test it yet), mobile hotspot works, but I get some cool new features to explore (I especially like being to able to have more control over what notifications show for each app, instead of a blanket on/off). Not crazy about the new AOD font, but I'll get used to it. Thanks for nudging me in the right direction

Umbra. said:
I don't still know about downgrading and switching, but I can live with that. I took the plunge and opted to install the latest Verizon firmware last night. Surprisingly I was able to just install it over the U firmware with basic Odin. I Then went into recovery and did a factory reset. It's gonna take awhile to set everything up how I like, but S Health works, I've got the Smart view toggle (didn't get to test it yet), mobile hotspot works, but I get some cool new features to explore (I especially like being to able to have more control over what notifications show for each app, instead of a blanket on/off). Not crazy about the new AOD font, but I'll get used to it. Thanks for nudging me in the right direction
Click to expand...
Click to collapse
Woo, welcome back to the walled garden lol.. BTW I found in the themes/lockscreen app (can't recall where) they had the old lockscreen font I preferred as a clock option

Galaxy S5 losing WiFi after 10 seconds since LOS16.0 22. Oct. 2019

Hello everyone,
first of all a big thank you to everyone who made this possible!
I have been reading the XDA Forums since a couple of years,
also using a successfully flashed S5 (SM-G900F with lineage_klte-userdebug 9 PQ3A. 190801.002 ac382b672 ) since then.
So the Issue is that since the last Update (LOS16.0 22. Oct. 2019) the WIFi
connection breaks after 5~10 seconds after being connected.
The indicator shows a connected good signal but no Data output...
Upon disconnect and reconnect, the same. Also this appears to happen
on all WiFi networks.
I read a few threads from 2014 where almost the same behavior was
described after an official Samsung update. But no working solution
for me. I wiped the cache partition with TWRP, but no result...
So, anyone have an Idea what i should do?
Best Regards & always Upcycle!

Upcycle said:
...So the Issue is that since the last Update (LOS16.0 22. Oct. 2019) the WIFi
connection breaks after 5~10 seconds after being connected...
Click to expand...
Click to collapse
Which LineageOS version & build date did you have before & how did you update?
Updating your modem may help.
See S5 Odin Flashable Modem & Bootloader.
***

curiousrom said:
Which LineageOS version & build date did you have before & how did you update?
Updating your modem may help.
See S5 Odin Flashable Modem & Bootloader.
***
Click to expand...
Click to collapse
Hey there Curiousrom,
I guess that i had the build date 1 Week earlyer as i do weekly Updates on Monday.
Thanks for the hint with the modem update, I'll check if this helps and report.
Best regards!