Database Users

Samsung Galaxy Express I8730 - No sound at all

I have a problem with my Samsung Galaxy Express (GT-I8730), international version.
I updated my firmware using Odin to a newer build. The firmware was downloaded from SamFirmware.com.
After the update finished and my phone restarted I've got no sound at all. I tried doing a factory reset but no luck. I thought the firmware was corrupted and after downloading and installing a new one, the exact same thing happened.
In the video posted below I am doing a factory reset from recovery, just to show you that I'm doing everything from the beginning.
The phone vibrates but there is no sound.
Before the update I had build version : I8730XWAMB8. After the update I tried with : I8730XWAMD7 and I8730XWAMC4. All these builds have the version number 4.1.2.
If I reinstall the I8730XWAMB8, I have sound but this build is branded and I'm very mad that I can't install other versions. This thing won't happen on my Note 2. I can install what firmware I want from SamFirmware.com.
I also saw that with all these builds my phone will randomly power-off at different times. It can be 5 minutes after I turn it on or it can be 18 hours. After the power-off I need to take out the battery.
What is wrong with the phone? Before these updates everything worked perfectly (before trying these updates, with the initial build I had sound and there were no random power-offs).
Any suggestion would be appreciated.

I also wanted to de-brand my i8730 and had similar issues as you. I tried 4 different firmwares, and the only firmware that really works OK is the original, branded one. With other firmwares (same version, same country but different branding) got me the occasional shutdowns like you described and wifi constantly disconnecting and connecting again.
Now I went back to the XWAMB8, rooted the phone and with Titanium Backup removed all the branded apps.
If you don't want to root your device you can always hide the apps, from the app list click on the Menu button and choose the option Hide applications.

Isn't that weird? I had a lot of Samsung smartphones and flashed a lot of firmwares (both stock and custom) and never experienced something like this. Can you tell me where you bought the phone from (what carrier and country)? Thanks.

ssweays composed
It is indeed very weird. My phone is branded to Portuguese Vodafone, I tried flashing other portuguese firmwares and also from other countries, the only stable one is the original one.

I think the phone is designed to be like that.
Sent from my GT-I8730 using xda-developers app

It is happened to me too, this power of thing in XWAMC4 firmware. (it is happened after less then 5 minuts after i turned out the screen)
finally i went back to the XWAMB8 and it's all work great.

No sound at all - not a problem in Australia
I updated and Optus branded i8730 with the plain vanilla variety and have had no problem.
Is your phone network locked?
99% sure mine is not and that may be what is causing it.
Bazzan

Well, it was a Vodafone Romania firmware but not really branded. I mean, it only had some apps installed by Vodafone. However, I'm getting my hands on an unbranded grey Galaxy Express today. Let's see what's going to happen with this one..

Something similar happened to me. I rooted it via motochoper from my linux desktop. Played a bit with root stuff, and later then I had no sim detection and no more speaker sound. I reflashed /system and got sim detected but still no speaker sound. Now I'm affraid of rooting the new one (I got lucky with my carrier). Something is weird about that phone...
Edit: In fact it seems to be TB that messed up the device... Everything fine now...

viges666 said:
Something similar happened to me. I rooted it via motochoper from my linux desktop. Played a bit with root stuff, and later then I had no sim detection and no more speaker sound. I reflashed /system and got sim detected but still no speaker sound. Now I'm affraid of rooting the new one (I got lucky with my carrier). Something is weird about that phone...
Edit: In fact it seems to be TB that messed up the device... Everything fine now...
Click to expand...
Click to collapse
I've got the same problem, no sound, when i call someone i can't hear the voice of my friend.
Base band version : I8730XWAMB7
Kernel version: 3.4.0-100842
[email protected]#1
Version number: JZO54K.I8730XWAMB8
Do you have any soluce to fixe this probleme ?
Thanks a lot

Wipe and full reflash with odin or heimdall...

Try full wipe and full reflash of original firmware with odin or heimdall...

Does somebody was able to flash a ROM released for a different carrier and still have sound working on this phone?
I either have no sound at all (after burning a new ROM for different carrier) or have strange sound (like "ET call home" - not my problem description, just found it on this forum too) after mixing new ROM with my original MODEM file.
Of course, everything is fine after burning back my original ROM.

ionutzm05 said:
I have a problem with my Samsung Galaxy Express (GT-I8730), international version.
I updated my firmware using Odin to a newer build. The firmware was downloaded from SamFirmware.com.
After the update finished and my phone restarted I've got no sound at all. I tried doing a factory reset but no luck. I thought the firmware was corrupted and after downloading and installing a new one, the exact same thing happened.
In the video posted below I am doing a factory reset from recovery, just to show you that I'm doing everything from the beginning.
The phone vibrates but there is no sound.
Before the update I had build version : I8730XWAMB8. After the update I tried with : I8730XWAMD7 and I8730XWAMC4. All these builds have the version number 4.1.2.
If I reinstall the I8730XWAMB8, I have sound but this build is branded and I'm very mad that I can't install other versions. This thing won't happen on my Note 2. I can install what firmware I want from SamFirmware.com.
I also saw that with all these builds my phone will randomly power-off at different times. It can be 5 minutes after I turn it on or it can be 18 hours. After the power-off I need to take out the battery.
What is wrong with the phone? Before these updates everything worked perfectly (before trying these updates, with the initial build I had sound and there were no random power-offs).
Any suggestion would be appreciated.
Click to expand...
Click to collapse
I have this exact same problem!! Ughh.
Any fix?

Flash I8730XWAMK1, will work and you will not have the brand logo. I use this one and is perfectly ! Good Luck ! :good::good:

hi All
have the same problem
original firmware is AP I8730XWAMB8 / CP I8730XWAMB7 / CSC I8730BOGAMB1
phone freeze , restart , no sound ..........
Solved with I8730XWANE1_OXXANF1 , all is OK , sound OK

After I flashed LineageOS 14.1 for GT-I8730T (mine is GT-I8730) the sound doesn't work, video player and music players too, they open and I can fast forward it, but it doesn't play. I changed it back to I8730UBAMD2 and CM 13.1 but nothing. Please help me!

Wifi issue on Galaxy S4 I9505

Hi all,
Ever since updating to the latest MGA via OTA firmware nearly 2 weeks ago the Wifi has been causing me a lot of issues. The following evening after updating the firmware, the wifi just randomly turned itself off and would refuse to turn on again. When I attempted to turn it back on via the widget, it would go grey as it's attempting to turn on but then it would just stay at that and it will not turn on at all. After a few minutes it will either go back to being completely turned off or the phone would just reboot itself.
Now, I have tried several things to rectify the problem i.e. applying the MGA wifi fix, factory restoring the phone via the settings and also in Kies, downgrading back down to the MEA firmware, re-flashing the stock MGA firmware via Odin and re-flashing both the MEA & MGA modems seperately - all to no sucess!
At the same time while all this is going on, the phone itself will sometimes randomly reboot itself when attempting to turn on the wifi or even in the rare case when the wifi does turn on and it will work for 5 or so minutes - the phone will reboot itself again while trying to simultaneously update various apps through the play store.
Lastly, the phone has already been sent back to Samsung a few days ago regarding this issue and the phone was returned back to me yesterday with Samsung apparently stating that they had diagnosed and found an issue with the phone (even though they could not tell me what??) and that they had sucessfully repaired it. Upon turning the phone back on going through setting up the phone again, I come to the wifi connection and guess what... it doesn't turn on. Yep that's right, I'm still stuck with the same problem!
I got straight onto Samsung on the phone and complained about this as I'm not happy at all, and they have agreed to have the phone back in for another repair and apparently something will be done properly this time.
It's not good enough though, to me all it looks like that Samsung have done their end on the original repair is re-flash it with the MGA firmware once again, shove it back in the box back to me and hope for the best. Even the Samsung agent on the phone yesterday could not tell me exactly how they apparently repaired the phone as there was not anything on the repair report what so ever, unbelievable!
Anyway, do any of you guys have any ideas with what else I can do my end to try and rectify the problem? To me though, this sounds like a physical hardware fault that only Samsung themselves can sort out...
Thanks - Liam

AndroidLEK said:
Hi all,
Ever since updating to the latest MGA via OTA firmware nearly 2 weeks ago the Wifi has been causing me a lot of issues. The following evening after updating the firmware, the wifi just randomly turned itself off and would refuse to turn on again. When I attempted to turn it back on via the widget, it would go grey as it's attempting to turn on but then it would just stay at that and it will not turn on at all. After a few minutes it will either go back to being completely turned off or the phone would just reboot itself.
Now, I have tried several things to rectify the problem i.e. applying the MGA wifi fix, factory restoring the phone via the settings and also in Kies, downgrading back down to the MEA firmware, re-flashing the stock MGA firmware via Odin and re-flashing both the MEA & MGA modems seperately - all to no sucess!
At the same time while all this is going on, the phone itself will sometimes randomly reboot itself when attempting to turn on the wifi or even in the rare case when the wifi does turn on and it will work for 5 or so minutes - the phone will reboot itself again while trying to simultaneously update various apps through the play store.
Lastly, the phone has already been sent back to Samsung a few days ago regarding this issue and the phone was returned back to me yesterday with Samsung apparently stating that they had diagnosed and found an issue with the phone (even though they could not tell me what??) and that they had sucessfully repaired it. Upon turning the phone back on going through setting up the phone again, I come to the wifi connection and guess what... it doesn't turn on. Yep that's right, I'm still stuck with the same problem!
I got straight onto Samsung on the phone and complained about this as I'm not happy at all, and they have agreed to have the phone back in for another repair and apparently something will be done properly this time.
It's not good enough though, to me all it looks like that Samsung have done their end on the original repair is re-flash it with the MGA firmware once again, shove it back in the box back to me and hope for the best. Even the Samsung agent on the phone yesterday could not tell me exactly how they apparently repaired the phone as there was not anything on the repair report what so ever, unbelievable!
Anyway, do any of you guys have any ideas with what else I can do my end to try and rectify the problem? To me though, this sounds like a physical hardware fault that only Samsung themselves can sort out...
Thanks - Liam
Click to expand...
Click to collapse
Well I have only had this problem with rooting phones etc... to me this happened with so many ROMs I tried. Even certain stock roms. I am not sure fully how I fixed it, but I know now I am running the OMEGA rom and this seemed to have worked for me so possible to try that? Just an option

PSPNikos said:
Well I have only had this problem with rooting phones etc... to me this happened with so many ROMs I tried. Even certain stock roms. I am not sure fully how I fixed it, but I know now I am running the OMEGA rom and this seemed to have worked for me so possible to try that? Just an option
Click to expand...
Click to collapse
When I first downgraded back down to the MEA firmware that I was linked to from another forum, I discovered straight after flashing that it was a pre-rooted ROM and the wifi still would not turn on then.
The phone has been sent back to Samsung again today for another repair but last night as a last ditched attempt, I downloaded & flashed the stock XXUAMDM firmware from April and the wifi still refused to turn on.
I'm still convinced that the problem itself is hardware related rather than software based going by that the problem is still present regardless of what ROM I'm on, it's just a case of trying to get Samsung to see that. I can understand now why that Samsung the first time round probably only did a fresh re-flash of the MGA firmware instead of going ahead and taking the phone apart/replacing parts as I imagine it's very labour intensive/standard procedure and not only that - the S4's mainboard (from what I've seen the wifi module is part of the mainboard) retails at over £200 which is a hefty repair cost on their part.
Liam

It is some sort of permissions issue.
If you do chmod 777 on /dev/*, /system/etc/wifi/* it should be working.
The only thing I haven't figured out is why
And it has to be done again after rebooting the phone, wich makes me sad.....

How I fixed my WiFi and sound problems after updating to latest firmware over
Hi there. (Sorry for any mistake about my English). By the way, I'm newbie on Android.
After freaking out about my WiFi problem, i didn't even care about the others problems like the sound, and I don't know if there were or if there is still some, but WiFi and sound got fixed.
After a lot of research on Google and XDA I came to the conclusion that if I could just re-install the firmware, I had
1- I Download the same firmware you are on (i guess it safer this way) I got the same (I9505VJUEMKE) that had caused the problem when was update trough Kies.
GT-I9505_PDA_I9505VJUEMKE_4.3
Changelist: 2210919
Build date: Wed, 27 Nov 2013
CSC: I9505ZTOEMKE_ZTO_Brazil
MODEM: I9505VJUEMKE
Gdrive: (créditos ao +Alexandre Affonso - Vlw)
Two links for download this firmware. (really fast download since its on gdrive)
goo.gl / UrZWAE .
goo.gl / omJC9e  "
2- Unpack the Zip File
3- Putt the phone in "Download Mode"
4- Open Odin 3.07 and Connected the cable. (check if Odin linked a port to your phone, i didnt get any color change, just the COM Port number and the "added" mentioned on Odin)
5- Load the firmware on "PDA", wait a few seconds till Odin load it.
6- Click Start and wait the whole process. Don't disconnect the cable until Odin says that it was Successfully.
Finished!
After all I did the root with Odin + CF Auto Root + Supersu and So far everything is fine and better than before.
Hope I can help few of you guys.
Thanks.

Galaxy I9505 bootloop/overheat since OTA 4.3

Hi all...did OTA 4.3 update on i9505 last week and the update failed.....the phone overheated during the installation and started bootlooping after that.
Connected the phone to Kies to see if it would detect the phone and sort the issue but it didn't even see it.
I was determined to keep the phone stock for warranty purposes so I downloaded the android SDK to get the ADB tools to see if I could connect that way. After a ton of tinkering I finally managed to get a connection. I then proceeded to try to locate the right ROM for the EE network in the UK so that I could either install by ODIN or via recovery seeing as I could now transfer files via ADB....
Now that Hotfile is down.....I can't locate the file successfully.
I crumpled and decided to try a custom ROM. I grabbed a 4.4 google edition and installed that....It booted up fine and I was able to insert all my details....then it crashed....I tried to restart but it got to the splash screen and restarted over and over......it was pretty hot so decided to turn it off for a while and remove the battery..
I let it cool down overnight and turned it back on.....it loaded up fine....I kept it in power saving mode and only turned the screen on to check that it was still alive.....it lasted about 5 hours into the day then had a major crash and started bootlooping again....
I have now tried going back to a BTU (non network specific) 4.2.2 ROM via ODIN but that is just boot loopiong. I have also used a i9505 PIT file to reset the partition table and then reinstall a standard ROM but no go.
I have tried Cyanogenmod too.....it got me to the sign in details then crashed and bootlooped......it basically bootloops until the battery runs out or it overheats...whichever comes first!
I am at the end of my current level of talent and looking for ideas on where to go next... The battery serial starts with "BD" so is apparently not one of the ones that are affected by previous issues.....the phone is only 1 month old
Anyone have any ideas....I thought soft bricks were generally fixable?

Update - I have now installed a stock ROM but it is for MK1 (India??) rather than EVR (EE - UK)
I was able to get it started up fine and it sat quite happily overnight on charge with no issues (WIFI and mobile data were on...sim card and SD card were installed)...made a phone call this morning and it was fine...that was a couple of hours ago.
I just downloaded a small app update via mobile data and the phone crashed and started bootlooping...
Took out battery and left for 5 mins and it has now booted up again without issue..
I am mucho confused!!
Are there any apps to track faults similar to Event Viewer in windows....I am pretty sure that I have a hardware issue but it may be caused by software...
Any help would be much appreciated.
cheers

fuzzynavel said:
Update - I have now installed a stock ROM but it is for MK1 (India??) rather than EVR (EE - UK)
I was able to get it started up fine and it sat quite happily overnight on charge with no issues (WIFI and mobile data were on...sim card and SD card were installed)...made a phone call this morning and it was fine...that was a couple of hours ago.
I just downloaded a small app update via mobile data and the phone crashed and started bootlooping...
Took out battery and left for 5 mins and it has now booted up again without issue..
I am mucho confused!!
Are there any apps to track faults similar to Event Viewer in windows....I am pretty sure that I have a hardware issue but it may be caused by software...
Any help would be much appreciated.
cheers
Click to expand...
Click to collapse
here you go sir try to find your stock room /provider from here and flash it via odin.http://www.sammobile.com/firmwares/2/
Edit: Remember flashing a new 4.3 stock may lead you to a newbootloader , Please read it here :http://forum.xda-developers.com/showthread.php?t=2447832 or either you can either flash the 4.2.2 stock pre-rooted rom from here (xxBMGA)http://forum.xda-developers.com/showthread.php?t=2250824 then reroot/recovery then use any Custom rom to flash via recovery in order to keep your old bootloader. i hope this make sense. thank you

Thanks Repulsa,
Already been through sammobile and many other sites looking for the correct ROM but as Hotfile is down there are no real sources...
I have come across many sources in China etc but they are downloading at 5kbps and would need a week to download 1.4 - 1.7GB
I have just checked my voicemail and made another call and the phone is fine....
I am thinking that I have an issue with the chip that handles mobile data....I am only on HSPA not LTE at the moment as I am outside of an LTE area....(LTE at home but HSPA/3G at work)
Will do more testing with downloading data over the mobile and also on WIFI and see if I can track down why it is crashing!

Thanks Repulsa,
Already been through sammobile and many other sites looking for the correct ROM but as Hotfile is down there are no real sources...
I have come across many sources in China etc but they are downloading at 5kbps and would need a week to download 1.4 - 1.7GB
I have just checked my voicemail and made another call and the phone is fine....
I am thinking that I have an issue with the chip that handles mobile data....I am only on HSPA not LTE at the moment as I am outside of an LTE area....(LTE at home but HSPA/3G at work)
Will do more testing with downloading data over the mobile and also on WIFI and see if I can track down why it is crashing!

fuzzynavel said:
Thanks Repulsa,
Already been through sammobile and many other sites looking for the correct ROM but as Hotfile is down there are no real sources...
I have come across many sources in China etc but they are downloading at 5kbps and would need a week to download 1.4 - 1.7GB
I have just checked my voicemail and made another call and the phone is fine....
I am thinking that I have an issue with the chip that handles mobile data....I am only on HSPA not LTE at the moment as I am outside of an LTE area....(LTE at home but HSPA/3G at work)
Will do more testing with downloading data over the mobile and also on WIFI and see if I can track down why it is crashing!
Click to expand...
Click to collapse
I let u latest STOCK ROM for UK EE EVR (everywhere) if u are interested -> Enjoy it

Put on the stock MK9 ROM last night.....watch you tube videos and played games to get it to overheat and die but, although it got hot, it stayed working....
In other news.....I tried to look at my calendar this morning and it crashed and started bootlooping.....I need to find some way to track what is going on at the time it crashes.

fuzzynavel said:
Put on the stock MK9 ROM last night.....watch you tube videos and played games to get it to overheat and die but, although it got hot, it stayed working....
In other news.....I tried to look at my calendar this morning and it crashed and started bootlooping.....I need to find some way to track what is going on at the time it crashes.
Click to expand...
Click to collapse
Go to Apps - Settings - More - About device and make us a beaty screenshot about :fingers-crossed:

[Q] I seem to have killed my WiFi - any suggestions would be appreciated

Hi there. Very sorry to post about this - I've tried my best to solve the issue on my own and doing various searches, here and elsewhere, but to no avail. Long and short of it is that WiFi and Bluetooth both seem to have died on me.
I have a Canadian Bell Samsung Galaxy S4 (SGH-I337M). I have been installing Danvdh's Google Edition ROM for some time now, and so far, it's been great. After installing 4.4.4 (clean, after a full wipe), it seemed to work, but my phone froze up - completely unresponsive, including the power switch. Pulled the battery but then afterwards could not turn on WiFi or BT - just says "Turning Wifi On" but nothing ever happens - the message just stays there perpetually. Bluetooth same thing, except the message goes away after a few seconds.
I've tried all of the following to try to restore WiFi, none of which has worked:
- Odin reflash of modem.bin and NON-HLOS.bin, multiple times (from the most recent stock ROM for my device - I337MVLUFNE1, 4.4.2)
- Complete reversion to stock (I337MVLUFNE1, 4.4.2) using Odin - neither WiFi nor BT worked under stock either
- Factory reset while in stock
- After rooting stock, using an SQL editor to check the value of wifi_display_on - it was 0 but just to make sure I set it to 0 again
- After rooting stock, deleting wpa_supplicant.conf in both /data/misc/wifi/ and /etc/wifi/
- Reinstalling Danvdh 4.4.4 (clean), but this time with the Googy kernel rather than the KT kernel (in both cases it was the customized version, not the pure Nexus one)
- Also tried, just for the heck of it, switching to ART to see if that might make a difference - it didn't
- Ringing a bell, opening a book and lighting a candle
In other words, I am at my wits' end. If anyone might have any suggestions - even just a link to some other possible solution I would be most grateful. I have tried searching, both in XDA and elsewhere, for a possible solution and have tried everything I've found, but so far, nothing has worked. Any suggestions would be most appreciated.
Please note - I originally posted this in the thread for Danvdh's ROM. I didn't get any feedback there, so suspect I perhaps might be posting the question in the wrong place, so am trying here, in addition to the thread for Canadian S4s. I trust such cross-posting is OK (but if not please let me know).

not_su said:
Hi there. .....
- Ringing a bell, opening a book and lighting a candle
In other words, I am at my wits' end. If anyone might have any suggestions - even just a link to some other possible solution I would be most grateful. I have tried searching, both in XDA and elsewhere, for a possible solution and have tried everything I've found, but so far, nothing has worked. Any suggestions would be most appreciated.
Click to expand...
Click to collapse
To be honest, I have no idea if that could be related... on one of my I9300, directly after OTA, I lost the WiFi and BT. Problem was WiFi or/and BT, when I pressed to switch it on, was turning on, for maybe 0.5 sec, and then was turning itself off.
now the funny story: because I unrooted it and cleaned prior to OTA, it was immaculate, so I took it to Sammys hiTech local specialists.
They two times were returning phone to me, stating that they are unable to repeat the problem. So, I asked them to not send it back, and that I'll pick it from Service Centre. I used that opportunity, and asked another local master to show me how to use the WiFi on my 100% working phone. He itself packed it into same envelope and disappeard for half a time, after that itme I was informed that my phone will be sent to me after motherboard replacement.
now, the correlation: no (in theory) action which could affect hardware, obviously CAUSED damage. If I'd be you, I'd try to restore the clean condition, and I'd go to service centre.

spamtrash said:
now, the correlation: no (in theory) action which could affect hardware, obviously CAUSED damage. If I'd be you, I'd try to restore the clean condition, and I'd go to service centre.
Click to expand...
Click to collapse
Thanks very much - appreciate the suggestion, but the warranty on my phone ended last month, so I'd get hit for a bill for the repair.
You raise a good point - it may well be a simple hardware failure that happened, coincidentally, when I updated. Alas, I wouldn't know where to begin to try to figure out whether or not it is a hardware failure...

I have the same problem with WiFi (bluetooth works though) after upgrading to 4.4.2 today.
The only modification I had done before were CF-AutoRoot and TWR.
I unrooted from SuperSU's menu prior to upgrading to stock 4.4.2 with KIES, everything seemed to work, except now I can't turn on wifi.
Where can I get the modem.bin for a Canadian Bell Samsung Galaxy S4 (SGH-I337M)?
Thanks for any help!
Here's the about screen: (Shouldn't the Baseband version be the same as the build? What gives?)

Tsuushin said:
Where can I get the modem.bin for a Canadian Bell Samsung Galaxy S4 (SGH-I337M)?
Thanks for any help!
Click to expand...
Click to collapse
here....

Tsuushin said:
I have the same problem with WiFi (bluetooth works though) after upgrading to 4.4.2 today.
The only modification I had done before were CF-AutoRoot and TWR.
I unrooted from SuperSU's menu prior to upgrading to stock 4.4.2 with KIES, everything seemed to work, except now I can't turn on wifi.
Where can I get the modem.bin for a Canadian Bell Samsung Galaxy S4 (SGH-I337M)?
Thanks for any help!
Here's the about screen: (Shouldn't the Baseband version be the same as the build? What gives?)
Click to expand...
Click to collapse
I don't remember where I got mine but it was extracted from the latest stock rom. Googling the build led me to this page, which seems to have links to download the most recent stock for the S4.
Not sure about your other question. I know when I update a new custom rom, the baseband version doesn't change - that only changes when I update the modem or flash an updated stock rom using Odin. You might also want to try flashing the NON-HLOS.bin file - I read elsewhere that that has helped others. Of course, feel free to also try all the other options I've noted above.

In case it helps other people with the same problem, here's what I did that fixed the WiFi issue:
I flashed the latest modem.bin (twice) and NON-HLOS.bin, but it didn't fix the WiFi.
I flashed the latest stock ROM, and now WiFi works.
Cheers.

S4 i337M - No sound on calls (in/out) after flashing Stock 5.01 Loliipop ROM

Flashed stock 5.01 ROM and phone call function stopped working.
When calling, there is a connection but no sound can be heard on either end of call.
It WAS working briefly and briefly managed to 'fix' it. Everything else functions correctly. Wifi calling works perfect. SMS works perfect.
I have searched forums and Googled this (about 9 hours worth so today) so quite at a loss how to proceed.
Tried forums suggestions to:
- disable Google Now/OK Google voice functions
- disable S Voice functions
- removing and replacing SIM/SD card
- wiping cache
- air dusting earphone port
- clear Google Play services cache and data
- clear Drive cache
- boot into Safe Mode, still not working
Additionally tried re-wipe cache/DALVIK/data/entire device and re-installed different stock ROM, same problem
I flashed both BELL and Rogers stock Lollipop ROM from XDA post (http://forum.xda-developers.com/galaxy-s4-att/general/sgh-i337m-canadian-stock-official-t3082758) via Odin
Any suggestions???
The only thing that worked briefly was:
In App Info for the Phone App, I did 'clear data' and 'clear cache' for all THREE Phone Apps (yes, there are three, I don't know if this is normal or not as this is first time with Lollipop). This allowed the phone to work BRIEFLY, then problem returned.

Try flashing the latest stock from sammobile.com.

Hi,
Attempting this but both Bell and Rogers Lollipop firmware .ZIP are corrupt from Sammobile.com I've contacted their admin to advise of this as I have tried downloading multiple times with the same corrupt file result.
Are there any other reputable download site?
audit13 said:
Try flashing the latest stock from sammobile.com.
Click to expand...
Click to collapse

I did a nandroid / efs backup with TWRP. Would there be any problems in restoring to 4.4.2 Kitkat using that???
audit13 said:
Try flashing the latest stock from sammobile.com.
Click to expand...
Click to collapse

Anything to be concerned about reverting via TWRP to Kitkat
Tried Emergency Firmware recovery via KIES, no luck, re-wiped cache, did factory reset in stock recovery, still no good.
Tried swapping Sim card tray and Earphone port (had a parts phone kicking around that is stuck on boot logo ((TWRP/ODIN Flashing does not recover this phone sadly)))
Will try to revert to Kitkat via TWRP next.
Note: I AM able to make normal calls as long the device is connected via Bluetooth to my car or to my bluetooth headset. Discovered this after more googling/forum searching.
rogue_element said:
I did a nandroid / efs backup with TWRP. Would there be any problems in restoring to 4.4.2 Kitkat using that???
Click to expand...
Click to collapse

What are you using to download from sammobile? I always use a win 7 machine.
What are program is being used to unzip the rom? You're only unzipping once?

Hi,
I'm using Win7 x64 Home Premium. WinRAR to unzip.
Since posting last I have restored Nandroid backup - phone function still didn't work and Google Play Services glitched out.
So, next downloaded 4.4.2 Kitkat from Sammobile, extracted no problem, flashed via Odin (no errors)- still no phone function
Wiped phone yet again, re-installed Kitkat one more time with Odia (no errors) - still no phone function
Used Kies to do Firmware Update and Initialization, (no errors) - still no phone function
Re-wiped again and used Kies once more, this time not doing App Restore function in case there is App causing issues and not signing into Google or Samsung Account to avoid anything restoring - still not working but interestingly there was a OTA update to 5.01 that installed fine - end result... phone function still not working.
If anybody can offer me another suggestion to try, I'll be happy to attempt but at this point I'm prepared to say f**k it and buy another phone.
I've been at this since last Saturday.
audit13 said:
What are you using to download from sammobile? I always use a win 7 machine.
What are program is being used to unzip the rom? You're only unzipping once?
Click to expand...
Click to collapse

After flashing with Odin, are you able to confirm that the bootloader and baseband match each other and the rom that was flashed? The imei is correctly displayed?
Since you are able to make calls via Bluetooth, are you able to hear the other party and the other party can hear you? What about calls via speakerphone?

Yes, I've attached a screenshot. Bootloader and baseband do match. This last round of install was done via OTA update that popped up after installing Kitkat. I just rolled with it as I figured if it's coming from Samsung directly, why not.
When making calls via Bluetooth, there are no issues. It functions as normal. It is just through the Phone App itself.
Interestingly, I discovered I can make outbound call no problem via Google Hangouts dialer as well. This is incredibly frustrating.
audit13 said:
After flashing with Odin, are you able to confirm that the bootloader and baseband match each other and the rom that was flashed? The imei is correctly displayed?
Since you are able to make calls via Bluetooth, are you able to hear the other party and the other party can hear you? What about calls via speakerphone?
Click to expand...
Click to collapse

Did you try reflashing the OH1 ROM? Sounds redundant but I'm not sure what else to suggest short of putting the motherboard into another phone and trying it out.

Hi audit13,
Haven't tried installing mobo in another phone, will give that a whirl for sh*ts''grinz.
Been an incredibly frustrating process. Another interesting thing that has been happening is that I notice the boot up sequence takes a lot longer than I recall.
Have been trying to avoid using the phone.
Re-flashed OH1 using ODIN and earlier tonight, Kies. Still not working.
I'm wondering if doing something like reverting to very old ROM may do the trick instead.
Do you happen to know how old I can go? Jellybean? I will check sammobile and see what the oldest they have there.
Phone functions perfectly fine via Bluetooth still, IP calls via WhatsApp and Hangouts Dialer also work per normal. Just trying to place normal calls does not work.
Have also had bootloops lately too I notice.

You can go as far back as 4.4.2 from my experience.
You'r performing a factory wipe right after flashing in Odin?
Initial boot up after flashing and wiping usually takes a long time but it should become quicker as the cache builds up with each reboot.

@rogue_element have you found a solution?
My wife's phone is having the exact same problem.
It started happening like a couple months ago. Haven't flashed anything to it. It just suddenly happened.

Hi ImpheOtus,
No, I'm still searching for a solution. I tried reflashing and then factory reset per audit13 suggestions but still no luck. I even tried swapping the ear piece module from a parts phone and no go. Extremely frustrating. Shopping for a new phone at this point but I'm still trying for a resolution as I'm stubborn and don't like giving up.

Hi audit13,
I'm actually suspecting the something else at this point (virus/malware, etc.) in the bootloader or deeper. There has been other random odd behavior, and while I don't rule out something like a hardware problem either, the behavior has been very strange.
Perversely, my wife's phone briefly experienced the same issue as mine but it cleared up after a reboot.
I will go hunting for a tut on flashing bootloader and kernel only next to see if that helps. If you have any suggestions of where to look for tutorial and/or files please feel free.
I tried flashing 4.4.2 but no luck there either btw

Okay, try flashing with a pit file and the latest stock rom from sammobile.

audit13 said:
Okay, try flashing with a pit file and the latest stock rom from sammobile.
Click to expand...
Click to collapse
Any particular suggestions regarding locating/selecting a pit file?

Is your phone a 16 GB sgh-i337m from Rogers, Telus, or Bell?

audit13 said:
Is your phone a 16 GB sgh-i337m from Rogers, Telus, or Bell?
Click to expand...
Click to collapse
Its a Bell SGH-I337M 16gb phone

I attached a 16 GB pit file from my i337m.