Database Users

Can't hear audio in calls on 4.2.2

Hello all. I'm trying to solve this problem for more then 3 hours and I'm really starting to have a headache from all of it.
When I call someone or someone calls me I can't hear the person on the other side, but they can hear me with no problem. How to fix this?
I already did a Factory Reset and that didn't help, I tried connecting and disconnecting my headphones and the problem was still there. I don't care about LTE compatibility.
Phone specs are:
Android version: 4.2.2
Baseband version: .48
Bootloader:MAKOZ10o
Build number: JDQ39
I didn't update anything on my phone, it came with that software installed. I just rooted it and nothing else.
EDIT: I think this is important too so I will add it. At one time the earpiece speaker did work, the in stopped so I did a Factory Reset and it didn't help. When I plugged in and out my headphones, it was fixed. Later, it got broken again, but now I can't fix it with plugging my headphones in and out.
EDIT 2: So I read on the Internet that I can downgrade to a older Android version and that then the problem will be fixed. My question is, to what version and what functionality will I lose?
EDIT 3: Updating to radio .54 fixed the issue. Thank you for helping.

This may sound stupid but...... did you check the volumes?

zephiK said:
This may sound stupid but...... did you check the volumes?
Click to expand...
Click to collapse
Yes, it's all the way up.

Well your baseband is fine assuming you didn't try any LTE hacks (which you're on .33+ so you probably didn't). Stock rom, stock kernel?
What else did you do?

zephiK said:
Well your baseband is fine assuming you didn't try any LTE hacks (which you're on .33+ so you probably didn't). Stock rom, stock kernel?
What else did you do?
Click to expand...
Click to collapse
I only rooted my phone and installed a couple apps and games. I didn't fiddle with the settings too much as I didn't want to break my phone.

Help me ,please
Hello,I have the same problem ,i'm from argentina
And i bought in USA, from google play without contract.
Please can you tell me, where can i to obtain the baseband version .54 for update my baseband?
My phone is android version: 4.2.2
Baseband version: .48
Bootloader:MAKOZ10o
Build number: JDQ39
Any thread ? Thanks

SM-N9005 Demo live unit cannot play HD songs, restart problem

Hi,
Customer came to me with SM-n9005 live demo unit with 4.3 version, I just update it to 4.4.2 , its working fine but whenever I played HD songs on it, its restarts
I performed hard reset in recovery, change file but not solved,
I also install MXplayer from play store but it also could not solve it
Hope seniors and developers solve my problem
waiting for your suggestion,
br

i
nsnobel2 said:
Hi,
Customer came to me with SM-n9005 live demo unit with 4.3 version, I just update it to 4.4.2 , its working fine but whenever I played HD songs on it, its restarts
I performed hard reset in recovery, change file but not solved,
I also install MXplayer from play store but it also could not solve it
Hope seniors and developers solve my problem
waiting for your suggestion,
br
Click to expand...
Click to collapse
flash stock rom of another region is final choice to check if ur device has software problem or hardware
:good:

x102x96x said:
flash stock rom of another region is final choice to check if ur device has software problem or hardware
:good:
Click to expand...
Click to collapse
I already try Germany , Italy and U.K roms, At version 4.3 no such problem was facing by customer, Its only happened after update to 4.4.2
So we can say its not hardware problem,

up up up, Where all seniors,?

What do you mean by "HD song"?
Re-flash stock ROM via Odin. Make sure you get the region and model right. You can find the ROMs at http://samsung-updates.com or http://sammobile.com

Someguyfromhell said:
What do you mean by "HD song"?
Re-flash stock ROM via Odin. Make sure you get the region and model right. You can find the ROMs at http://samsung-updates.com or http://sammobile.com
Click to expand...
Click to collapse
HD songs means 1020P songs
Already flash stock rom of region O2 UK from sammobile , I think problem in live demo unit which some hardware not supported by stock firmware,

It could be the case, that demo/live units are not same models, that are sold and lack some minor features to keep costs down.

i
Someguyfromhell said:
It could be the case, that demo/live units are not same models, that are sold and lack some minor features to keep costs down.
Click to expand...
Click to collapse
no it s not good idea
there s same hardware in demo and retail units But maybe different software
>> so IF u flash another rom (official releases) it can solve problems
+++
@nsnobel2
send link of a hd song that i wanna test on my devices:good:

x102x96x said:
no it s not good idea
there s same hardware in demo and retail units But maybe different software
>> so IF u flash another rom (official releases) it can solve problems
+++
@nsnobel2
send link of a hd song that i wanna test on my devices:good:
Click to expand...
Click to collapse
you can download any hd song in youtube by searching "HD Songs"

[Q] Has anyone had problems with Android Wear after upgrading to a 5.0 rom?

This has been mentioned somewhere else before but I haven't found a reliable solution .... after upgrading to stock 5.0 (SM-N9005, tried both saudi arabia and poland rom), my LG G Watch R keeps getting disconnected. More accurately, it disconnects when out of range and refuses to reconnect when back in range. Only rebooting the phone lets it connect again. This is extremely frustrating and it's a problem that seems to be localized to the Note 3. I'm considering downgrading back to kitkat (but I'm not even sure how to go about doing that). Anyone know of a solution?

HyperShad0w said:
This has been mentioned somewhere else before but I haven't found a reliable solution .... after upgrading to stock 5.0 (SM-N9005, tried both saudi arabia and poland rom), my LG G Watch R keeps getting disconnected. More accurately, it disconnects when out of range and refuses to reconnect when back in range. Only rebooting the phone lets it connect again. This is extremely frustrating and it's a problem that seems to be localized to the Note 3. I'm considering downgrading back to kitkat (but I'm not even sure how to go about doing that). Anyone know of a solution?
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-note-3/help/tw-lollipop-n9005-problem-bluetooth-t2990348
So solution yet, but workaround.

Thanks for replying. Sorry I didnt notice that thread before posting. The only workarounds seem to be using a BT autoconnect app which drains battery or else flashing a 16GB Hong Kong rom with pit file. I had tried doing that recently and ran into all sorts of problems and almost bricked my phone. I was lucky to recover from it. I may have perhaps used the wrong pit file or something, but in any case there's no way I'm trying that again. Can anyone point me towards a quick guide to downgrading back to kitkat? Is it a simple matter of flashing a stock kitkat rom, or will that cause problems?

had this issue on CM11
HyperShad0w said:
This has been mentioned somewhere else before but I haven't found a reliable solution .... after upgrading to stock 5.0 (SM-N9005, tried both saudi arabia and poland rom), my LG G Watch R keeps getting disconnected. More accurately, it disconnects when out of range and refuses to reconnect when back in range. Only rebooting the phone lets it connect again. This is extremely frustrating and it's a problem that seems to be localized to the Note 3. I'm considering downgrading back to kitkat (but I'm not even sure how to go about doing that). Anyone know of a solution?
Click to expand...
Click to collapse
I had this issue on CM11 kitkat and Moto 360.
After installing the Poland ROM it was great. I had no issue.

Problems after last official update (signal and soft keys)

A friend has an S4 (i9505) from Vodafone Spain (ATL), unlocked and using another operator microSIM (Jazztel). Last week, via OTA, she received the latest update available: http://www.sammobile.com/firmwares/download/59777/I9505XXUHOJ4_I9505VFRHOF3_ATL/
After installing that OTA update, the signal level is very low, even none inside buildings, etc. This was not happening before.
In addition, the 2 soft keys (on both sides of the Home button) are not responding anymore, not even lighting up.
The Home button works, so... I think that it's not a hardware problem. Too much coincidence that the update and that hypothetical hardware problem happened at the same time...
First I did was a total hard reset, to factory settings, etc. No success, both problems (signal and soft keys) were still there.
Second, I flashed ROM manually via Odin. I flashed latest PHE one, so no Vodafone bloatware anymore: http://www.sammobile.com/firmwares/download/59311/I9505XXUHOJ2_I9505YXXHOJ1_PHE/
No success, still the same. I then did again a hard reset to factory setting, with Wipes first... and nothing.
Next thing I will do (when i have the phone in my hands again) is flashing with Odin the previous PHE one, and crossing fingers: http://www.sammobile.com/firmwares/download/48153/I9505XXUHOE3_I9505PHEHOE1_PHE/
Anyone with the same problem? Any solution/suggestion?

Flashed next-to-last Stock ROM for PHE http://www.sammobile.com/firmwares/download/48153/I9505XXUHOE3_I9505PHEHOE1_PHE/ and no success
Then I flashed Base HOH2 (4files+PIT) with Odin and... nothing either.
No idea what to try next. Suggestions?

Same here, after OTA no menu/back buttons (neither backlight or functionality)
Current status:
- seems to affect quite a lot of people, there are more threads like this on various sites
*e.g. here, here, here
- happenning after both OTA or ODIN based update to latest 5.0.1 ROM (for me it was i9505XXUHOJ2)
My findings so far:
- NO rom change seems to fix this
- it seems that touch keys' FW is updated (physically on the chip) along with the update (to version 0x12)
- Touch key FW update in menu *#2663# not applicable as it says that it won't update - versions are the same (you can check the version of driver used by ROM and the actual FW in chip on this page)
NOTE. my girlfriend has the buttons working after successful update and has both in version 0x12
Conclusion:
- It seems that the FW flashing process of the touch keys controllers somehow failed => phone says that it's also ver. 0x12 (same as android driver) but it is probably corrupted
- Re-flashing of the chip could solve the problems, however there are problems with this:
NOTES.
Menu *#2663# won't let us do the flash because of the version check - Can we use ADB to force the update on a rooted phone? Does anybody know how?
There is a slight chance, that it'll be fixed if Samsung will release some newer update which updates also the keys' FW
Samsung could release a fix, that will flash this manually as a lot of people have problem with this
!EDIT:
I've found very similar problem + solution on the Vietnamese forum bellow (don't use the files as it's for different phone!):
- to sum it up - force downgrading the FW, the update again... (any ROM cook that could help?)
see here
regards,
J.

I completely agree with you. I also tried the *#2663# path, the phone also has 0x12 touch keys FW, and it doesn't let me reflash it, either. Don't know what FW was there before the OTA update.
I have been told about the first German 5.0.1 stock ROM: http://www.sammobile.com/firmwares/download/44821/I9505XXUHOB7_I9505OXAHOB7_DBT/ and also about the last 4.4.2 one: http://www.sammobile.com/firmwares/download/40046/I9505XXUGNK4_I9505OXAGNK4_DBT/
Maybe one of those... makes something again on the Touch Keys FW?
I couldn't try anymore bcs I gave the phone back to my friend (with accesibility touch keys on-screen)

HI, have you found a solution? My Italian S4 suffered the same bug after the same upgrade. I tried to contact samsung and they said I need to replace the screen because upgrading the firmware put the electronic under stress and they got broken. I don't believe them because too many people have the same problem + my screen is two days old! Please help me!

Same problem for my S4! how we can flash/reflash/downgrade soft touch fw?

Has anyone tried the first first German 5.0.1 stock ROM: http://www.sammobile.com/firmwares/d...05OXAHOB7_DBT/ or the last 4.4.2 one: http://www.sammobile.com/firmwares/d...05OXAGNK4_DBT/ ?
A friend of mine (another one) told me that he fixed it with German HOA7 one, and then updated again to latest with no problem: https://mega.nz/#!VwcgXSQC!uGAhPxEuRrl-luS3sw8JmoPnjP4ybxrlsY4XcfFaWKE
I can't try it myself bcs I gave back the S4 to the owner. If anyone tries, please leave here the results!

oiluj said:
Has anyone tried the first first German 5.0.1 stock ROM: http://www.sammobile.com/firmwares/d...05OXAHOB7_DBT/ or the last 4.4.2 one: http://www.sammobile.com/firmwares/d...05OXAGNK4_DBT/ ?
A friend of mine (another one) told me that he fixed it with German HOA7 one, and then updated again to latest with no problem: https://mega.nz/#!VwcgXSQC!uGAhPxEuRrl-luS3sw8JmoPnjP4ybxrlsY4XcfFaWKE
I can't try it myself bcs I gave back the S4 to the owner. If anyone tries, please leave here the results!
Click to expand...
Click to collapse
I've tried a lot of ROMs - 4.4.2, also older 5.0.1 with no result...
I haven't tried UHOA7 I've tried UHOB7 instead, so I'll probably give it the shot, but I can't imagine how it could fix this issue (maybe if it for some reason has the touch-cypress FW update forced...)
- I've seen that on some German forums reverting back helped, but it wasn't my case (+it didn't fix the problem for many others...)
As I've wrote before, they've created modified kernel (with forced touch key FW reflash - bypassed version check) for a little bit different phone on the Vietnamese forum (see the link in my previous post) and it seems that it would be quite easy for somebody who has some knowledge with kernel compilation... (it would just need small modification in the "if" condition of 1 kernel source file) I've tried to do some research, but it takes some time to understand the process of building the kernel and to figure out how to properly pack it again... Also the sources are a little bit different for i9505.

kosmodisk said:
I've tried a lot of ROMs - 4.4.2, also older 5.0.1 with no result...
I haven't tried UHOA7 I've tried UHOB7 instead, so I'll probably give it the shot, but I can't imagine how it could fix this issue (maybe if it for some reason has the touch-cypress FW update forced...)
- I've seen that on some German forums reverting back helped, but it wasn't my case (+it didn't fix the problem for many others...)
As I've wrote before, they've created modified kernel (with forced touch key FW reflash - bypassed version check) for a little bit different phone on the Vietnamese forum (see the link in my previous post) and it seems that it would be quite easy for somebody who has some knowledge with kernel compilation... (it would just need small modification in the "if" condition of 1 kernel source file) I've tried to do some research, but it takes some time to understand the process of building the kernel and to figure out how to properly pack it again... Also the sources are a little bit different for i9505.
Click to expand...
Click to collapse
No idea, another friend of mine (different than the one who gave me her "broken" i9505 for fixing), who had the same problem with his own i9505 told me that with the I9505XXUHOA7_OXAHOA7 he fixed it. And sent me the Mega link, as it's not on SamMobile (or I didn't find it): https://mega.nz/#!VwcgXSQC!uGAhPxEuRrl-luS3sw8JmoPnjP4ybxrlsY4XcfFaWKE
I couldn't try it by myself, because I gave back the "broken" i9505 I was trying to fix to her owner before I was told about HOA7.
U know a lot more about this than me. Maybe you can give a try to that HOA7 Mega link, and see if it really works, or if my friend was extremely extremely lucky, and still doesn't know it (and ofc, doesn't know what the hell fixed his phone, and how).
Anyway, if u decide to give a try to the I9505XXUHOA7_OXAHOA7 one, don't forget to come back to tell us if it worked or... nothing. I keep fingers crossed!!!
Oh, and ofc: THANK YOU!!!

oiluj said:
No idea, another friend of mine (different than the one who gave me her "broken" i9505 for fixing), who had the same problem with his own i9505 told me that with the I9505XXUHOA7_OXAHOA7 he fixed it. And sent me the Mega link, as it's not on SamMobile (or I didn't find it): https://mega.nz/#!VwcgXSQC!uGAhPxEuRrl-luS3sw8JmoPnjP4ybxrlsY4XcfFaWKE
I couldn't try it by myself, because I gave back the "broken" i9505 I was trying to fix to her owner before I was told about HOA7.
U know a lot more about this than me. Maybe you can give a try to that HOA7 Mega link, and see if it really works, or if my friend was extremely extremely lucky, and still doesn't know it (and ofc, doesn't know what the hell fixed his phone, and how).
Anyway, if u decide to give a try to the I9505XXUHOA7_OXAHOA7 one, don't forget to come back to tell us if it worked or... nothing. I keep fingers crossed!!!
Oh, and ofc: THANK YOU!!!
Click to expand...
Click to collapse
I got the problem but only the back button was not working. Did factory reset and it did not help.
Then i flashed I9505XXUHOA7_OXAHOA7 from your link with Odin 3.10 and YES!!! i can confirm it is working again So happy now.
It is my Moms Phone now and she loves it!!. I was unly helping her doing the OTA so she realy hated me and SAM for F****** up her phone.
This tread realy saved my ass

Can confirm this is happening to me as well. All firmwares starting from HOF2 seem to have this problem so if you encounter this, downgrading to a HOE/HOD firmware should correct this bug. The downside is that without a proper fix, you won't be able to update.

BUBA0071 said:
I got the problem but only the back button was not working. Did factory reset and it did not help.
Then i flashed I9505XXUHOA7_OXAHOA7 from your link with Odin 3.10 and YES!!! i can confirm it is working again So happy now.
It is my Moms Phone now and she loves it!!. I was unly helping her doing the OTA so she realy hated me and SAM for F****** up her phone.
This tread realy saved my ass
Click to expand...
Click to collapse
@kosmodisk, did u read that? have u tried I9505XXUHOA7_OXAHOA7 by urself? Ur conclusions?
@BUBA0071:
- Did u look before (and after) flashing HOA7 which FW had (and have now) the touch keys? Remember: *#2663#
- After flashing HOA7, did u update again to latest one? Did the update work well this time, and now u have latest version with touch leys working?
MoLoCEL said:
Can confirm this is happening to me as well. All firmwares starting from HOF2 seem to have this problem so if you encounter this, downgrading to a HOE/HOD firmware should correct this bug. The downside is that without a proper fix, you won't be able to update.
Click to expand...
Click to collapse
I tried with a HOE1 one and... didn't work. Couldn't try one even older, but HOE1 seems to keep the same problem.

the file is corrupted when i try to extract it ? any other files that i can try ? im having the same problem right now with my s4.. have been looking for quiet some times now, and this is my only hope, hope this way will works smoothly...

wild081 said:
the file is corrupted when i try to extract it ? any other files that i can try ? im having the same problem right now with my s4.. have been looking for quiet some times now, and this is my only hope, hope this way will works smoothly...
Click to expand...
Click to collapse
download it again

@oiluj
HOE3 works for me. Problems start from HOF onwards.
I have also tried flashing HOA7 DBT and upgrading. Problem persists. My touchkey firmware is 0x1a and won't update no matter what Firmware package I tried. Up to now i have tried: GNG2, GNI2, GNK4, HOA7, HOB7, HOD7.
I'm pretty sure a rom (custom or early kitkat/lollipop leaks) caused this, altough I never flashed the initial chinese leak.

MoLoCEL said:
[MENTION=3170873]I'm pretty sure a rom (custom or early kitkat/lollipop leaks) caused this, altough I never flashed the initial chinese leak.
Click to expand...
Click to collapse
The phone that that girl gave to me, for fixing... was completely in official status. Always official ROMs, and official OTA updates, from first minute. And the problem was caused by latest official OTA update available: http://www.sammobile.com/firmwares/download/59777/I9505XXUHOJ4_I9505VFRHOF3_ATL/
So the problem was not caused by any custom ROM or a not official one.

oiluj said:
@kosmodisk, did u read that? have u tried I9505XXUHOA7_OXAHOA7 by urself? Ur conclusions?
@BUBA0071:
- Did u look before (and after) flashing HOA7 which FW had (and have now) the touch keys? Remember: *#2663#
- After flashing HOA7, did u update again to latest one? Did the update work well this time, and now u have latest version with touch leys working?
I tried with a HOE1 one and... didn't work. Couldn't try one even older, but HOE1 seems to keep the same problem.
Click to expand...
Click to collapse
Hardware key firmware 0X12 parth 0X1a (when it was not working, dont know if it have changed after german firmware flash). I have not updated again, think my CSC is blocking. It stayed on NEE after update to German firmware.
It was NEE I9505XXUPOJ2 firmware that F***** up my Phone

BUBA0071 said:
Hardware key firmware 0X12 parth 0X1a (when it was not working, dont know if it have changed after german firmware flash). I have not updated again, think my CSC is blocking. It stayed on NEE after update to German firmware.
It was NEE I9505XXUPOJ2 firmware that F***** up my Phone
Click to expand...
Click to collapse
unfortunately I've tried I9505XXUHOA7_OXAHOA7 with no luck (even with repartition when flashing) - the buttons still don't respond
BUBA0071, I'd like to ask which custom ROM have you tried? It seems that your keys have FW of version 0x1a which should be newer than 0x12, so this could lead to some sollution. Was it some cyanogen mod or MIUI?
thx

kosmodisk said:
unfortunately I've tried I9505XXUHOA7_OXAHOA7 with no luck (even with repartition when flashing) - the buttons still don't respond
BUBA0071, I'd like to ask which custom ROM have you tried? It seems that your keys have FW of version 0x1a which should be newer than 0x12, so this could lead to some sollution. Was it some cyanogen mod or MIUI?
thx
Click to expand...
Click to collapse
Wups it have been some time since it was custum, but in any cace it must have been some of the first lollipop roms. I gave to my mom 13 feb 2015 and i did a lot of flashing before that, i think one of the roms i tryed was Project Chaos. but also i tryed all the google editition roms for i9505 and cyanogen.
but when it whent back to stock it i used PDA I9505XXUHOD7 CSC I9505NEEHOD2 NEE firmware

I've got a question. When you flash the HOA7 file from the Mega link, do you use only the AP file, or you use AP,BL,CP, CSC and PIT files?
I'm gonna try to fix my S4 but i'm not sure about the right process I should follow.
Thank you!

Galaxy S5 Play Store problems

Hello everyone. I recently bought an Samsung Galaxy S5 (SM-G900F). After I made the "first run set-up" , I went to Google Play to download all the apps I needed.And then Google Play suddenly stopped and an error poped out : "Google Play stopped working"..ok I tried again,after aproximatively 3 minutes the error shows up again and again..I know that Samsung has some problems with Google Play,so I tried some fixes found on the internet. I tried deleting all data,cache,and updates.. It worked.Looks like my phone has some "problems" with the new update (6.0.5) for Google Play Store. With the old one (5.x - sorry I can't remember the version),I have no problems. But,the other problem is that after a few minutes,the app updates itself to the last version. I even tried to make a factory reset,but the error still shows up (I tried to reset the phone from the settings and from the recovery boot). I don't have a problem using the old version of PLay store,but I also can't use an outdated version for too long. Is there any way to fix it? I'm trying all kind of fixes found on the internet for hours and I'm getting angry. Is there any way to fix it,or I can send it to warrany? (I'm afraid to send it to warranty because I know that all they do there is to reset my phone and I lose a lot of time waiting to make a freaking reset that I can make even myself).
I would have posted an image with the error,but this forum doesn't allow me to put links into my threads for "security reasons".
So please,if you can help me It would be awesome. Thank you again and sorry for my bad english.
I forgot to mention,phone model is SM-G900F with Android 5.0 (I can`t make update to 5.1,I dont know why.)

Try reflashing 5.0 stock firmware using Odin
Note: G900F does not have 5.1.1 yet
Daniel Iuga said:
Hello everyone. I recently bought an Samsung Galaxy S5 (SM-G900F). After I made the "first run set-up" , I went to Google Play to download all the apps I needed.And then Google Play suddenly stopped and an error poped out : "Google Play stopped working"..ok I tried again,after aproximatively 3 minutes the error shows up again and again..I know that Samsung has some problems with Google Play,so I tried some fixes found on the internet. I tried deleting all data,cache,and updates.. It worked.Looks like my phone has some "problems" with the new update (6.0.5) for Google Play Store. With the old one (5.x - sorry I can't remember the version),I have no problems. But,the other problem is that after a few minutes,the app updates itself to the last version. I even tried to make a factory reset,but the error still shows up (I tried to reset the phone from the settings and from the recovery boot). I don't have a problem using the old version of PLay store,but I also can't use an outdated version for too long. Is there any way to fix it? I'm trying all kind of fixes found on the internet for hours and I'm getting angry. Is there any way to fix it,or I can send it to warrany? (I'm afraid to send it to warranty because I know that all they do there is to reset my phone and I lose a lot of time waiting to make a freaking reset that I can make even myself).
I would have posted an image with the error,but this forum doesn't allow me to put links into my threads for "security reasons".
So please,if you can help me It would be awesome. Thank you again and sorry for my bad english.
I forgot to mention,phone model is SM-G900F with Android 5.0 (I can`t make update to 5.1,I dont know why.)
Click to expand...
Click to collapse

Well,I'm very dissapointed because I got my phone to some GSM Services,and most of they told me that this is a common issue for Samsung devices and you must be pretty lucky to not get into such errors with an Samsung phone. So yes,I will "maybe" try to flash the original firmware with Odin,but I don't think it will help. So anyway thank you for helping me,I will try to use this phone with this bulls*it error and maybe,maybe (which is quite impossible) Samsung will release an update that would solve this problem.

Whats your firmware build number?
Daniel Iuga said:
Well,I'm very dissapointed because I got my phone to some GSM Services,and most of they told me that this is a common issue for Samsung devices and you must be pretty lucky to not get into such errors with an Samsung phone. So yes,I will "maybe" try to flash the original firmware with Odin,but I don't think it will help. So anyway thank you for helping me,I will try to use this phone with this bulls*it error and maybe,maybe (which is quite impossible) Samsung will release an update that would solve this problem.
Click to expand...
Click to collapse

Just to lighten you up, this problem is not "common" in Samsung devices. My family and relatives uses mostly Samsung phones and tablets and never did we have this problem, even on two Galaxy S5s (G900F and G900FD).
Flashing the stock firmware should help.
Sent from my SM-G900F using XDA Forums

Well,I reflashed the stock rom with Odin3.9 but this problem still occurs. If you are talking about Baseband version than this is it: G900FXXU1BOJ1
EDIT: After 2 months of trying to fix the problem,it still occurs.