Until yesterday I used several different ROMs, without having any sound problem.
The problem started when I flashed Syiah kernel 1.2.6 (which might be a coincidence), while being on OMEGA-ROM. Thereafter I couldn't hear anything in phone calls any more (but others can hear me) on any ROOTED firmware or ROMs.
Reverting back to Syiah 1.1 (or switching to any other kernel) didn't help, neither did flashing any other rom.
Full wipe (including all storage space) solved the problem temporarlily. But after reboot no sound in phone calls again. Also changing the modem first helped, but the problem re-appeared after the first reboot.
Finally I flashed stock rom (LF2) via ODIN. Now the problem was solved - I believed. I could hear people in phone calls even after several reboots. But as soon as I rooted the phone with CF-Root AND changed some files on /system/media/ui the call sound was gone again after the following re-boot.
I reflashed again to stoch firmware via ODIN and now I have to live with an unrooted phone, which is not the worst thing in the world. But I really would like to be able to use custom ROMs again...
Anyone with similar experiences or with any idea about possible causes and/or solutions???
*** via Tapatalk ***
citronbitare said:
Until yesterday I used several different ROMs, without having any sound problem.
The problem started when I flashed Syiah kernel 1.2.6 (which might be a coincidence), while being on OMEGA-ROM. Thereafter I couldn't hear anything in phone calls any more (but others can hear me) on any ROOTED firmware or ROMs.
Reverting back to Syiah 1.1 (or switching to any other kernel) didn't help, neither did flashing any other rom.
Full wipe (including all storage space) solved the problem temporarlily. But after reboot no sound in phone calls again. Also changing the modem first helped, but the problem re-appeared after the first reboot.
Finally I flashed stock rom (LF2) via ODIN. Now the problem was solved - I believed. I could hear people in phone calls even after several reboots. But as soon as I rooted the phone with CF-Root AND changed some files on /system/media/ui the call sound was gone again after the following re-boot.
I reflashed again to stoch firmware via ODIN and now I have to live with an unrooted phone, which is not the worst thing in the world. But I really would like to be able to use custom ROMs again...
Anyone with similar experiences or with any idea about possible causes and/or solutions???
*** via Tapatalk ***
Click to expand...
Click to collapse
Really nobody who could help???
Can you record sound with other apps?
That should see if its a problem with just the phone apk or a more native problem.
Sent from my GT-I9300 using xda premium
Well, others can hear me but I can't hear them in phone calls. There is no problem with the phone speaker, because I can use viber without problems.
*** via Tapatalk ***
BUMP! I'm having the same problem!
I'm hoping it's not a hardware problem.
I wonder if any dev can chime in.
Well, it shouldn't be hardware related, because there is no problem on unmodified stock firmware.
*** via Tapatalk ***
Zabalba said:
BUMP! I'm having the same problem!
I'm hoping it's not a hardware problem.
I wonder if any dev can chime in.
Click to expand...
Click to collapse
You have the same problem, but after flashing syiah?
If yes it is not coincidence i think.
Kernel has sound modifications for last version 1.26
Sent from my GT-I9300 using xda premium
I noticed I had the problem intermittently when I first started using Foxhound on Saturday. Foxhound comes bundled with Syiah.
I thought it was something else all together. I asked in the Foxhound thread and only one other person +1'd my post. Today I switched to Omega hoping it the problem would go away and it was actually worse.
I was testing just now and every time I called my phone I could hear nothing on my handset or through headphones. Just in case I did't accidentally flubbed anything else up I unfroze all the TB apps I had frozen to see if it was working. Interestingly after defrosting and rebooting I can hear again. Attached are the apps I had frozen.
But this has not been the first time it was working correctly and then go back to not hearing calls.
JJEgan said:
Kernel has sound modifications for last version 1.26
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I strive for that. What I would do:
Flash stock rom
Factory reset via stock recovery
flash stock
cfroot
and then check if it is still a problem.
That is why the topic OMEGA asked that the next versions were the stock kernel.
That is why in order to avoid such problems.
marcinrek21 said:
You have the same problem, but after flashing syiah?
If yes it is not coincidence i think.
Click to expand...
Click to collapse
Yes, it all started after flashing syiah 1.2.6. So maybe it's not a coincidence after all.
*** via Tapatalk ***
Zabalba said:
I noticed I had the problem intermittently when I first started using Foxhound on Saturday. Foxhound comes bundled with Syiah.
I thought it was something else all together. I asked in the Foxhound thread and only one other person +1'd my post. Today I switched to Omega hoping it the problem would go away and it was actually worse.
I was testing just now and every time I called my phone I could hear nothing on my handset or through headphones. Just in case I did't accidentally flubbed anything else up I unfroze all the TB apps I had frozen to see if it was working. Interestingly after defrosting and rebooting I can hear again. Attached are the apps I had frozen.
But this has not been the first time it was working correctly and then go back to not hearing calls.
Click to expand...
Click to collapse
For me it has also been an intermittent problem. Kernel changes, modem changes, wipes, etc often temporarily helped - but only for one boot cycle. A reboot always brought the problem back. Only on stock firmware I can always hear.
*** via Tapatalk ***
marcinrek21 said:
I strive for that. What I would do:
Flash stock rom
Factory reset via stock recovery
flash stock
cfroot
and then check if it is still a problem.
That is why the topic OMEGA asked that the next versions were the stock kernel.
That is why in order to avoid such problems.
Click to expand...
Click to collapse
I have done exactly that - and the problem is gone as long as you only do these steps. But modifying the system partition in any way (changing, deleting or adding files or flashing custom rom) brings you back to square one.
*** via Tapatalk ***
citronbitare said:
I have done exactly that - and the problem is gone as long as you only do these steps. But modifying the system partition in any way (changing, deleting or adding files or flashing custom rom) brings you back to square one.
*** via Tapatalk ***
Click to expand...
Click to collapse
And may you have an earlier backup? Stock with cfroot or similar?
marcinrek21 said:
And may you have an earlier backup? Stock with cfroot or similar?
Click to expand...
Click to collapse
The sound problem is there even when I restore earlier backups. Now I am on stock firmware and everything is okay.
But I would like to use custom ROMs again with working phone call function, which is not possible for now.
*** via Tapatalk ***
This is the weirdest problem that I have seen here.
Just a status update. I have done some more testing and obviously what makes call sounds not to work is certain changes to the system partition (as compared to stock firmware).
In my case call sound works as long as I am on stock firmware (no matter what stock firmware; I have tested three or four different ones). If I root stock firmware with CF-root I still have call sound. I also can change kernels and it is possible to modify host files with ad-free.
However, as soon as I manually change or modify anything on the system-partition with root explorer or when I install custom ROMs the call sound disappears after the next reboot - no matter what radio I use. I also have tested the radio from the newest malaysian firmware which has surfaced today.
citronbitare said:
Just a status update. I have done some more testing and obviously what makes call sounds not to work is certain changes to the system partition (as compared to stock firmware).
In my case call sound works as long as I am on stock firmware (no matter what stock firmware; I have tested three or four different ones). If I root stock firmware with CF-root I still have call sound. I also can change kernels and it is possible to modify host files with ad-free.
However, as soon as I manually change or modify anything on the system-partition with root explorer or when I install custom ROMs the call sound disappears after the next reboot - no matter what radio I use. I also have tested the radio from the newest malaysian firmware which has surfaced today.
Click to expand...
Click to collapse
Thanks for your testing!
Like I mentioned in my earlier post I unfroze all of the apps and I have not run into the issue. My phone is running Omega 5.2 with Siyah 1.2.6. I'm totally expecting the problem to return but it has not so far. I wish it was consistent and reproducible.
Zabalba said:
Thanks for your testing!
Like I mentioned in my earlier post I unfroze all of the apps and I have not run into the issue. My phone is running Omega 5.2 with Siyah 1.2.6. I'm totally expecting the problem to return but it has not so far. I wish it was consistent and reproducible.
Click to expand...
Click to collapse
I'll keep my fingers crossed and hope that you have finally gotten rid of this problem. And thanks btw for asking Chainfire and Indie too look at this thread!
*** via Tapatalk ***
I got that problem myself, the only thing that really helped for me is to
flash my Stock Rom that where on the Phone out of the Box... since 2 Days
the Bug is gone. But havent tried any other Stock Rom.
I want to try Omega 6.0 Rom...(now)
I was thinking about flashing CF-Root and do those steps before custom:
1. Wipe Data/Factory Reset
2. Wipe Cache Partition
3. In Advanced ---> Format System/Cache/Data (someone tried this before?)
4. Flash the Rom.
My Question is for those guys like me where the only solution is to stay on
non rooted stock rom, have you tried flashing a custom rom with step 3. from above and still encounter the call issue?
I read somewhere that with step 3. the Phone is really FULL WIPE.
Sorry for my bad english :silly:
Related
Sup,
So, I flashed mutliple custom ROM's when I got this device like any other crack-flasher would but I then realised I much prefer it to be running stock with root access until an AOSP ROM comes along.
So I came from Omega 4.0 to stock LE8 in the UK, ever since I've flashed this stock ROM (Which is odexed) I keep getting the message "Sorry, messaging has unfortunately stopped" every time I open the app. I've tried wiping data/cache/dalvik and flashing in Odin again, same issues. I then went back to another custom ROM (HyperGalaxy) then went back to stock to test, still the same.
I have also tested an inverted AOSP 4.0.4 Mms app which worked on Omega, but didn't work on stock (Got the same message)
Data of the Messaging app has been wiped, i've disabled the app, rebooted, enabled again, still the same issues.
I've searched and I found 2 other threads with the same thing, but noone has been helpful enough yet.
It seems like the phone still thinks its running a Deodexed ROM but I need to get it back to full working order since I need to text something.
Any help is appreciated.
Try a factory reset...
Mopral said:
Try a factory reset...
Click to expand...
Click to collapse
Probably didn't make it clear enough, I did that already. 3 times to be exact.
i have the same issue. Need help.
i get this message with multiple apps.
all of them are standard run of the mill things like browser, messages, video player. My phone is only a week old and completely stock
some real bugs in this phone still that need sorting asap. poor effort by samsung really
Same issue here, has anyone found a fix for it yet?
I only encounter this in hyper x rom. So far so good in omega
Ok,I had this issue when I tried to install different firmware and modems using Mobile Odin. It fully resolved when I flashed back the official UK firmware and modem (le8) using normal desktop Odin. No force closes whatsoever since. Incidently, I'm now using LE9 firmware with UK CSC, rooted, with no issues at all. I used chainfires recovery, then flashed superuser to root.
Hope this helps.
nbhadusia said:
Ok,I had this issue when I tried to install different firmware and modems using Mobile Odin. It fully resolved when I flashed back the official UK firmware and modem (le8) using normal desktop Odin. No force closes whatsoever since. Incidently, I'm now using LE9 firmware with UK CSC, rooted, with no issues at all. I used chainfires recovery, then flashed superuser to root.
Hope this helps.
Click to expand...
Click to collapse
i got this everytime i clear cache and or wipe data from recovery before flashing new fw's.
so never wipe anything before flashing. if u already wiped, then flash it all over again and it will be all ok
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
cappiez said:
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I had the same issue today between 2 and 3, but it wasn't letting me send texts even though I could receive them. Maybe a network hiccup?
I am on stock radios, didn't know new ones came out. It is working for me now.
in the same boat
looks like we're in the same situation. I looked through the threads and this is another case of call errors. I found this thread and one other, not sure if it was droid dna related.
cappiez said:
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
sjhanson Today, 12:20 AM #1035
Junior Member
Thanks Meter 1
Posts: 11
Join Date: Jan 2011
I am running 3.0.3 now. I was running Viper until the big man published 3.0.3, then i switched back. But even on Viper I was getting the same COM.PHONE.ANDROID has stopped error.
Cheers!
http://forum.xda-developers.com/showthread.php?t=2126386&page=2
borkborkbork! said:
looks like we're in the same situation. I looked through the threads and this is another case of call errors. I found this thread and one other, not sure if it was droid dna related.
Click to expand...
Click to collapse
Link to any of the other threads?
http://forum.xda-developers.com/showthread.php?t=2157855
xDexter said:
Link to any of the other threads?
Click to expand...
Click to collapse
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
TheJ0hnman said:
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
Click to expand...
Click to collapse
You went back to S-ON or just a different kernel?
TheJ0hnman said:
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
Click to expand...
Click to collapse
I also tried going back to stock ruu , nothing worked for me
borkborkbork! said:
I also tried going back to stock ruu , nothing worked for me
Click to expand...
Click to collapse
I am having 0 issues anymore with S-OFF and .torrented's rom and suggested R/W kernel: http://forum.xda-developers.com/showthread.php?t=2150262
xDexter said:
I am having 0 issues anymore with S-OFF and .torrented's rom and suggested R/W kernel: http://forum.xda-developers.com/showthread.php?t=2150262
Click to expand...
Click to collapse
com.android.phone .. but I still get my txt messages, go figure. I think my partitions may be in rare shape from rom's, kernals, and all the other numerous changes. Never been the same after I got error 7 on schatka 3.0.2, I switched back and forth from viper/hatka and twrp/cwmr
I took my phone into Verizon yesterday, explained the situation. Told them it started after ota, and I had done a factory reset already. They tried a new SIM card to no avail, overnighting a new phone.
Sent from my HTC6435LVW using xda premium
xDexter said:
You went back to S-ON or just a different kernel?
Click to expand...
Click to collapse
Forgot about this post, sorry. Did not go back to s-on, just flashed stock kernel from here: http://d-h.st/Ma1, boot.img via fastboot and then the modules zip contained within in recovery, and everything was good.
This didnt work for me . Any other suggestions?
cappiez said:
I took my phone into Verizon yesterday, explained the situation. Told them it started after ota, and I had done a factory reset already. They tried a new SIM card to no avail, overnighting a new phone.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
Basically I hd the same situation happen to myself, no calls or data but wifi was good. Mine started to fail slowly , firs \t it was showing a 1X connection but dl were about 3G speeds. Next I lost signals in areas I never had signal issues with. Then total loss. New sim card and spent hours on the support line and a replacement unit.
Got a PM request for assistance, and thought I don't have a lot of tips to offer other than what I provided before, I'm going to post a more detailed overview (as I remember it, it's been awhile...) in case it's helpful for any other who may come across it later. The bottom line for me was that once things broke, it didn't work again until I flashed stock kernel via fastboot +modules in recovery and did a clean install of Hatka 3.03 w/ Sense launcher. That said, because of my flashing compulsion and failure to fully test things once installed, I can't pinpoint the exact step at which things broke.
Initially, I: Bought phone and factory reset, did not take Verizon OTA. Fiddled around, hated Sense, unlocked, flashed recovery, flashed Viper 1.1.0 (?, whatever the base was), booted and setup, fiddled around, hated Sense, wiped data, flashed 3 subsequent Viper updates (1.1.1,2,3 maybe?), booted and setup, fiddled around, hated Sense. Wiped and reinstalled de-Sensed Viper a few times in an attempt to get rid of Sense as much as possible.
Then things get murky. I did s-off, and at some point flashed (recovery) a kernel, Cubed I think. Wifi or something was borked (as I understand is the case with Cubed/Viper), and I flashed stock kernel back via recovery (no modules, I didn't catch that part at the time) and restored my backup for good measure, leaving me on fully functional Viper 1.1.3. Everything worked for a few days, but I continued to hate Sense, and began searching for something more sensible. At some point I flashed Hatka 3.03 w/ de-Sensed options, went to 320 DPI, and thought everything was fine for about 18 hours until I realized my phone was warm, and figured out it was rebooting every time I received (or placed) an incoming call (boss was pissed and kept trying to call me, already gives me a hard time about being an Android fanboy so I'm never going to hear the end of that). After a few hours of fiddling and various recovery attempts including restores and full wipe/clean installs of Viper, I finally managed to get things up and running with A. flashing stock kernel via fastboot + modules in recovery and a full wipe/clean install of Hatka 3.03 w/ Sense + Xperia launchers and eventually a 380 DPI.
One of or some combination of the s-off/custom kernel/failure to reinstall stock kernel modules/de-Sensed/low DPI/pin lock/Widget Locker/Viper combo I had going fouled something up, which I know is not entirely helpful. If I found myself in this situation again, I would flash stock boot.img via fastboot + modules in recovery, and probably flash a stock ROM to rule out anything else, then wipe and flash things from there until I got where I wanted or it broke.
For the record, I'm now back on my Galaxy Nexus until stable-ish CM 10.1 is within sight or I get tired of waiting and sell the thing, I just can't tolerate Sense.
same issue
I've been reading wherever I see this topic and haven't found the answer that I'm looking for. Have tried everything said but nothing has fixed my problem can't make or receive calls. This problem happened after I turned s-off have relocked boot loader, flashed RUU, reset factory, re-unlocked bootloader, re-flashed different roms, and flashed radios still not working. No doubt it is a software issue. Does anyone know how to format internal storage on this phone. My thinking is if that can be done problem should go away and then can re-flash to stock. Any help would be most appreciated.
jimmydee62 said:
I've been reading wherever I see this topic and haven't found the answer that I'm looking for. Have tried everything said but nothing has fixed my problem can't make or receive calls. This problem happened after I turned s-off have relocked boot loader, flashed RUU, reset factory, re-unlocked bootloader, re-flashed different roms, and flashed radios still not working. No doubt it is a software issue. Does anyone know how to format internal storage on this phone. My thinking is if that can be done problem should go away and then can re-flash to stock. Any help would be most appreciated.
Click to expand...
Click to collapse
Have you tried fixing permissions? In some other post I read phone process force closing was just a matter of wrong permissions.
In other hand I think if you format system, data and cache the phone storage would just keep hboot and recovery; at that point you could only run RUU to stock or adb sideload from recovery if your CWM version has the feature.
Sent from my HTC6435LVW using xda app-developers app
still problem
Yes have fixed permissions. Also have formatted everything I could in CWM still have problem. Is there a way to format with ADB commands?
Hi. I've got a challenge for the experts
I have a galaxy s4 (i9505) and currently on cyanogenmod 11-20140414-nightly so its running on 4.4.2
The minute i got my phone, i put foxhound rom and was on4.2.2 that time and everything was fine. It was about june last year. A couple of weeks ago, i decided to have a go at other roms or update to 4.4.2 so i tried foxhound rom that ran on4.4.2. This is when the problems started. The first problem was the signal was greatly affected that i could not get any signal indoors. So i tried several other roms like omega rom, cyanogenmod, wanamlite, wicked, virgin rom and several others but none of them perfectly worked. I always cleared cache and restore factory settings but still there were problems. On some roms the camera wont work as if there is another app using it. On others, i cant get any signal even though im in an area where i used to get strong signals. Another big problem is that i cant make a call! The screen goes black and can't do anything until the call gets disconnected. I can't use voice services like skype, ym, everything that uses the mic as if there is an app or service using it. When i put the jack to use the headset, i dont get the notification that im on headset unlike before.
So i decided to use stock rom on 4.3. Now i have even bigger problems. In addition to the previous problems stated, the wifi won't turn on but i can get a signal outside. Even though i have already removed the microsd card and wiped cache and restore to factory settings, the phone still says that the device was modified so i can't really return it even though it is still under warranty.
So now i decided to root it again and temporarily use cyanogenmod since the wifi works, texts and the internet works.
Btw, youtube doesnt work also. It doesnt play.
Sorry for the vrry long post but i just want to give much info as possible..
Thanks so much
Noypi14 said:
Hi. I've got a challenge for the experts
I have a galaxy s4 (i9505) and currently on cyanogenmod 11-20140414-nightly so its running on 4.4.2
The minute i got my phone, i put foxhound rom and was on4.2.2 that time and everything was fine. It was about june last year. A couple of weeks ago, i decided to have a go at other roms or update to 4.4.2 so i tried foxhound rom that ran on4.4.2. This is when the problems started. The first problem was the signal was greatly affected that i could not get any signal indoors. So i tried several other roms like omega rom, cyanogenmod, wanamlite, wicked, virgin rom and several others but none of them perfectly worked. I always cleared cache and restore factory settings but still there were problems. On some roms the camera wont work as if there is another app using it. On others, i cant get any signal even though im in an area where i used to get strong signals. Another big problem is that i cant make a call! The screen goes black and can't do anything until the call gets disconnected. I can't use voice services like skype, ym, everything that uses the mic as if there is an app or service using it. When i put the jack to use the headset, i dont get the notification that im on headset unlike before.
So i decided to use stock rom on 4.3. Now i have even bigger problems. In addition to the previous problems stated, the wifi won't turn on but i can get a signal outside. Even though i have already removed the microsd card and wiped cache and restore to factory settings, the phone still says that the device was modified so i can't really return it even though it is still under warranty.
So now i decided to root it again and temporarily use cyanogenmod since the wifi works, texts and the internet works.
Btw, youtube doesnt work also. It doesnt play.
Sorry for the vrry long post but i just want to give much info as possible..
Thanks so much
Click to expand...
Click to collapse
So, which type of rom do you want to be on, assuming most of the things work properly? I don't want to try to address all those issues because there are different ones for the different setups and would take forever. Most likely signal issues are from not using a matched modem with the firmware / rom you are running. Do you know the original carrier / region the phone is from so we can make sure you get the right stuff installed?
Please provide details on the the currently installed baseband version. Also, what is the last official version of Samsung's software that you installed via Odin or OTA (not via custom rom)?
es0tericcha0s said:
So, which type of rom do you want to be on, assuming most of the things work properly? I don't want to try to address all those issues because there are different ones for the different setups and would take forever. Most likely signal issues are from not using a matched modem with the firmware / rom you are running. Do you know the original carrier / region the phone is from so we can make sure you get the right stuff installed?
Please provide details on the the currently installed baseband version. Also, what is the last official version of Samsung's software that you installed via Odin or OTA (not via custom rom)?
Click to expand...
Click to collapse
Thanks for your reply.
The current cyanogenmod is fine although i prefer the virgin rom. but i can go back to virgin once the problems have been rectified.
I agree that the signal issue has something to do with the modem so i tried different modems using odin but the XXUBMEA wouldnt change despite trying several modems and several times.
The phone is on three network (uk) with its current baseband 19505XXUBMEA.
The official rom i tried was on 4.3 and kies said it was the latest
Thanks again
Alright, I'm with ya so far. I'll look into the rom situation when I get back in front of the PC, but the trick with updating the modem is you gotta flash it twice in a row before you reboot unless you flash official firmware.
es0tericcha0s said:
Alright, I'm with ya so far. I'll look into the rom situation when I get back in front of the PC, but the trick with updating the modem is you gotta flash it twice in a row before you reboot unless you flash official firmware.
Click to expand...
Click to collapse
Thanks again for replying.
What i havent actually tried (which i'm reading at the moment) is the formatting of data under the advanced options on twrp. I dunno if it will make a difference say i try a new rom. I don't mind trying and starting from scratch. Like format data then install a new rom. Do u think this will make a difference? (will this be similar to formatting a dard drive on a pc before installing windows?)
What i suspect is there is nothing wrong with the roms i've tried but something in the installation got messed up and remains there even after wiping the data.
I think i have tried doing it twice only to find out that it didnt change the modem despite odin saying pass.
Should i format data then install a fresh rom?
Hard
but challeng refused
Ok, so there is something odd here. If you had flashed the official 4.3 via Odin, your modem would have changed to a newer one. The one you have is still a 4.2.2 one. Or were you referring to the last stock rom that you loaded with a custom recovery? Also, which recovery are you using?
Try this modem via Odin:
http://d-h.st/Kwv
Install Guide:
Use Odin v3.04
Untick Autoreboot
Flash modem
Reboot once again into Download Mode using (Vol Down plus Home button combi)
Flash Modem once more
Once done,unplug then reboot device manually.
If this doesn't work, try repeating the flash process again while rebooting manually and with auto-reboot option turned off.
Reference thread: http://forum.xda-developers.com/showthread.php?t=2192025
Let's see if that doesn't help anything and go from there.
If you have issues with wifi, there is a wifi fix to be had in the reference thread. Remember to flash that through the Phone slot if needed.
thanks again.
i can't exactly remember what modem i had when i flashed it with the official 4.3 using odin. but my guess would be the XXUBMEA. most of the custom roms i've tried had this modem anyway. some had no problems with 3g signal.
i am using twrp.
i don't want to play around with the modem yet as the 3g and wifi signals are working fine on cyanogenmod. its the call and video that's not working that i want to sort out.
do u think if i reflash by formatting data would clear out the problems i specified earlier? i don't mind trying this if u think it will make a difference.. tthanks.
es0tericcha0s said:
Ok, so there is something odd here. If you had flashed the official 4.3 via Odin, your modem would have changed to a newer one. The one you have is still a 4.2.2 one. Or were you referring to the last stock rom that you loaded with a custom recovery? Also, which recovery are you using?
Try this modem via Odin:
http://d-h.st/Kwv
Install Guide:
Use Odin v3.04
Untick Autoreboot
Flash modem
Reboot once again into Download Mode using (Vol Down plus Home button combi)
Flash Modem once more
Once done,unplug then reboot device manually.
If this doesn't work, try repeating the flash process again while rebooting manually and with auto-reboot option turned off.
Reference thread: http://forum.xda-developers.com/showthread.php?t=2192025
Let's see if that doesn't help anything and go from there.
If you have issues with wifi, there is a wifi fix to be had in the reference thread. Remember to flash that through the Phone slot if needed.
Click to expand...
Click to collapse
Noypi14 said:
thanks again.
i can't exactly remember what modem i had when i flashed it with the official 4.3 using odin. but my guess would be the XXUBMEA. most of the custom roms i've tried had this modem anyway. some had no problems with 3g signal.
i am using twrp.
i don't want to play around with the modem yet as the 3g and wifi signals are working fine on cyanogenmod. its the call and video that's not working that i want to sort out.
do u think if i reflash by formatting data would clear out the problems i specified earlier? i don't mind trying this if u think it will make a difference.. tthanks.
Click to expand...
Click to collapse
The custom roms you've been using don't install a modem with them, so that would be why you've been on the same one for a bit. Often times the stock rom is a little more picky about which modem it likes best, though this varies by phone and update. What call issues are you having? There were so many issues listed for various things on the first post that I had trouble sorting which problem for which rom (not criticizing, just making sure we're on the same page). And as far as videos go, is it just YouTube that isn't working right or any type of video playback? If it is just YouTube - is it force closing, not loading searches or videos, or some other problem?
es0tericcha0s said:
The custom roms you've been using don't install a modem with them, so that would be why you've been on the same one for a bit. Often times the stock rom is a little more picky about which modem it likes best, though this varies by phone and update. What call issues are you having? There were so many issues listed for various things on the first post that I had trouble sorting which problem for which rom (not criticizing, just making sure we're on the same page). And as far as videos go, is it just YouTube that isn't working right or any type of video playback? If it is just YouTube - is it force closing, not loading searches or videos, or some other problem?
Click to expand...
Click to collapse
thanks again for your interest.
the issue about the modem is somehow clear. thanks for clearing that up.
i think it is better to tackle the problems i have in my current setup rather than the previous problems. so, as previously mentioned, i am on cyanogenmod 11 (on 4.4.2). here are some of the problems i am aware of or rather, those that i have experienced:
1. calls - whenever i dial a number, the screen goes black as if the phone is next to my ear (could there be something wrong with the proximity sensor? i haven't done anything to rectify this yet though. when this happens, i can't do anything as the seems to hang although i could see the call timer working. during that call however, i can't hear a sound nor the person i just rang. same thing happens when someone calls me. my phone vibrates (because there is another problem with the sound which i will discuss next) and when i answer it, i hear no sound and the screen goes black and i couldn't do anything with the phone. i have to wait till the caller disconnects before the phone becomes useable again.
i tried calling using viber and the same thing happens.
2. sound - phone is muted even though all the volume controls are midway or almost 100%. i tried changing the ringing tone but i don't hear any sound at all. normally, when i switch to a different ringtone, it should give me a preview of what the chosen sound is like.
3. videos - it doesn't work. when i go to youtube, it opens up the site, opens the selected youtube clip, tries to play it but pauses then tries to play again then pauses until i get a message saying "there was a problem while playing. touch to retry."
so far these are the problems i have faced.
sorry for the long post again.
Hmm. Seems weird that you are having so many issues that most others aren't having, at least not since some of the earlier builds. During the install of CM, did you wipe /system? If not, I definitely would just start fresh. Install the most up to date modem. Wipe everything (system, data, cache, dalvik). Use the most up to date CWM (I like TWRP most of the time, but since CM says you should try CWM before reporting issues, it's one of those things...) Some Samsung proximity sensors aren't that accurate and really don't work well with CM. Other users reported that issue i the main CM thread for your phone, but was definitely not prevalent. I had a Samsung phone that I couldn't use a tempered glass screen protector with as they had an app to install to test to see how sensitive it was and mine didn't pass the test, though it worked for everything else.
As far as the video bug. It affected some earlier builds and other roms based off of CM but I hadn't seen anyone commenting about it for a bit so can't imagine it still being a common issue as that's a deal breaker for most. It might just be easier at this stage to either go back to stable CM 10.2 or try another rom altogether, such as Slim.
es0tericcha0s said:
Hmm. Seems weird that you are having so many issues that most others aren't having, at least not since some of the earlier builds. During the install of CM, did you wipe /system? If not, I definitely would just start fresh. Install the most up to date modem. Wipe everything (system, data, cache, dalvik). Use the most up to date CWM (I like TWRP most of the time, but since CM says you should try CWM before reporting issues, it's one of those things...) Some Samsung proximity sensors aren't that accurate and really don't work well with CM. Other users reported that issue i the main CM thread for your phone, but was definitely not prevalent. I had a Samsung phone that I couldn't use a tempered glass screen protector with as they had an app to install to test to see how sensitive it was and mine didn't pass the test, though it worked for everything else.
As far as the video bug. It affected some earlier builds and other roms based off of CM but I hadn't seen anyone commenting about it for a bit so can't imagine it still being a common issue as that's a deal breaker for most. It might just be easier at this stage to either go back to stable CM 10.2 or try another rom altogether, such as Slim.
Click to expand...
Click to collapse
i know. i don't really want to blame these issues i've mentioned to the rom i am using or have tried. perhaps there was something i did not do or overdid that messed it all up. the cynagenmod 10 (the stable version for my s4 model) had similar issues as the cm11. so i suspect the problem i've created still lingers within my phone that messes up a lot of things.
during installation, i did wipe the system, data, cache and dalvik which i found in the advanced menu.
the thing is, everything else worked fine when i was on 4.2.2 (like the proximity sensors, videos, sounds, etc) so as i said earlier, i don't want to blame it on the roms.
i might have another go on the slim rom tonight but use CWM instead of TWRP.
thanks again for your interest and help
Noypi14 said:
i know. i don't really want to blame these issues i've mentioned to the rom i am using or have tried. perhaps there was something i did not do or overdid that messed it all up. the cynagenmod 10 (the stable version for my s4 model) had similar issues as the cm11. so i suspect the problem i've created still lingers within my phone that messes up a lot of things.
during installation, i did wipe the system, data, cache and dalvik which i found in the advanced menu.
the thing is, everything else worked fine when i was on 4.2.2 (like the proximity sensors, videos, sounds, etc) so as i said earlier, i don't want to blame it on the roms.
i might have another go on the slim rom tonight but use CWM instead of TWRP.
thanks again for your interest and help
Click to expand...
Click to collapse
Do you have a screen protector or anything like that? Sometimes if it isn't laying on the screen right or dirt gets around it, it can cause issues. There's also a way to pop out the actual proximity sensor and clean between the part and the little piece of clear glass on the back of the front piece of glass that can help too if it ends up being hardware related.
es0tericcha0s said:
Do you have a screen protector or anything like that? Sometimes if it isn't laying on the screen right or dirt gets around it, it can cause issues. There's also a way to pop out the actual proximity sensor and clean between the part and the little piece of clear glass on the back of the front piece of glass that can help too if it ends up being hardware related.
Click to expand...
Click to collapse
I put the screen protector when i got the phone and i don't see any visible dirt so i wouldn't want to blame it either. Although i did read about the screen protectors causing problems. But the thing is, even youtube or any videos do not play. Even any sound.
I've tried the slimkat rom by following the developers' instructions and still no youtube, no sound, can't make a call as i can't hear the person i'm calling nor can that person hear me.
Any other suggestions on what to do? I don't mind going back to stock as long as i get all the features back. I went to official 4.3 before but had more severe issues. Or perhaps i did it wrong?
Thanks..
Videos are another issue, but I still think the call problems and such are modem related. What I would do would be to wipe everything, then use Odin to install official Kit Kat, then test this stuff out and see if it works. If so, then you can do a nandroid and redo recovery and try the roms again, then if they still have that issue then your phone just doesn't cooperate with CM roms or something weird like that. If it doesn't work even after official 4.4.2, then there's probably something else going on, possibly hardware related.
es0tericcha0s said:
Videos are another issue, but I still think the call problems and such are modem related. What I would do would be to wipe everything, then use Odin to install official Kit Kat, then test this stuff out and see if it works. If so, then you can do a nandroid and redo recovery and try the roms again, then if they still have that issue then your phone just doesn't cooperate with CM roms or something weird like that. If it doesn't work even after official 4.4.2, then there's probably something else going on, possibly hardware related.
Click to expand...
Click to collapse
Thanks.
Got hold of the official 4.4.2 and flashed it via odin. Failed. But tried again and now working fine. Sound is back, video is back as well as calls. Just the annoying google search failing all the time.
The baseband it has is I9505XXUFNC9. i didn't install any modem in odin though. Just flashed in the pda section the tar file
Now i don't know whether to root this again and try custom roms or leave it as it is. I saw knox by the way but haven't installed it. Or is it pre installed? I have little knowledge about knox
So the other day my S3 gave up the ghost, and developed the hard-brick "QHSUSB_DLOAD" error. I have insurance so I was overnighted a new phone, and am sending the old one away. I believe this was related to a long-term power button issue I was having, perhaps a virus, or something. I had not changed anything to the ROM I was using since about October, and the issue just happened now in May.
At any rate, the new S3 I received is an MJB version, Android 4.3, Knox and all that other good stuff. After several failed attempts, I found a method to root this phone and disable Knox. The Warranty Bit is already tripped, so clearly I'm not sending this phone back until it hard bricks as well. I am trying to install the StockMOD ROM that is very popular, however I am being plagued by problem after problem.
I was able to flash a version of CWM Recovery onto my phone, but it was too old and couldn't mount any of the folders. Using ROM Manager, I was able to flash an update to my Recovery, and now it mounts and views all folders properly. However, when I go to install the StockMOD ROM, I continuously get a Status 7 error, something about "expects 5 args, got 3." I wiped the data, cache, and Dalvik, but kept getting this error. So, I had to recover my backup of stock, which didn't go well either. Once my backup was installed, all of my apps kept crashing. Gapps, ROM Manager, everything kept giving me constant FC errors. I had to wipe my data, cache, and Dalvik again and go back to factory default, and reinitialize the phone. Luckily I haven't installed anything of importance on here yet.
A quick search through here states that I need to use TWRP as my Recovery. I've flashed TWRP several times, first using the 2.6... version and then the most recent 2.7.0.0 version, and neither of these will mount any of my folders. It just gives me a litany of errors trying to mount the various locations. I've done Fix Permissions and everything else, TWRP will just NOT mount anything. Other folks say I need the latest PhilZ Recovery. I've downloaded the latest PhilZ Touch 6 and flashed it via Odin. It is giving me the same errors as regular CWM, Status 7, "expecting 5 args, got 3."
I don't know what else to do. My S3 that ran Android 4.0 was so much easier. I had that thing rooted and running a TW based ROM with Nova launcher in about 30 minutes. This phone has been a disaster since I turned it on. I'm just trying to get a 4.3 TW based ROM. I like the Samsung Camera, Calendar, Clock, Messaging, and Contacts apps far better than AOSP versions. But I also want much more customization to my notification drawer toggles. Stock TW doesn't have the toggles I use frequently like the data toggle as well as the torch toggle.
I don't know what I'm doing wrong, because unlike a lot of folks out there, once I find a ROM I like, I stick with it. I'm not constantly updating, changing, or searching for the newest version of Android. There's nothing wrong with that, it just isn't my cup of tea. So does anyone know what I need to do? At this point, I'm about to just give up and use Nova over top of rooted stock TW and call it a day.
Thanks!
Have you tried to go back stock rom using Odin ? I think it might resolve your recovery problem
nosphor said:
Have you tried to go back stock rom using Odin ? I think it might resolve your recovery problem
Click to expand...
Click to collapse
Everything is stock except the recovery. I'm using CWM 6.0.4.7 with PhilZ Touch 6. I'm still using the stock TW 4.3 ROM that shipped with the phone. The only exception is that I'm rooted now.
I suggest you to go back to a 4.1 official stock rom with odin to be sure to have no more issue.
This can help you : http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
Also, don't forget to backup your apps with titanium backup and all your sms :good:
nosphor said:
I suggest you to go back to a 4.1 official stock rom with odin to be sure to have no more issue.
This can help you : http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
Also, don't forget to backup your apps with titanium backup and all your sms :good:
Click to expand...
Click to collapse
Unfortunately, I've heard that it is not possible to revert to anything prior to 4.3 once a phone comes factory installed with 4.3, due to all of the security enhancements and etc. My kernel, modem, and baseband are all factory stock 4.3 MJB. Everyone else on the boards, under various other topics, warn of immediate and sudden death to the phone if you attempt to install a baseband prior to 4.3 MJB.
I'm very surprised to hear that, because recently i've flash stock 4.3 rom and then go back to 4.1.2 to flash a 4.4 rom without any issue and i've got nothing for issues.
Maybe it depends on which country you are ( i'm from France ) ? For what i know , there is a VERY little chance that this downgrade cause dammage to your phone
nosphor said:
I'm very surprised to hear that, because recently i've flash stock 4.3 rom and then go back to 4.1.2 to flash a 4.4 rom without any issue and i've got nothing for issues.
Maybe it depends on which country you are ( i'm from France ) ? For what i know , there is a VERY little chance that this downgrade cause dammage to your phone
Click to expand...
Click to collapse
I'm in the USA. The security features on the I747 US version are far different. I don't know how everyone else is succeeding. I am completely lost.
You are in the wrong forum, anything you try from here will hard brick your phone.
Sent from my GT-I9300 using Tapatalk
Sorry to tell you that, but what you say is not completely true.
Yes, there is a lot of people that rush to give an answer to the question, but there is also people that really like to help people that are in trouble :good:
Please, don't take most of the case for a generality
http://forum.xda-developers.com/showthread.php?t=1756338
Sent from my GT-I9300 using Tapatalk
Yes, i've read this, i know that, that's why i talk about the difference between country, different phone model
My apologies. Thought this was the 747 board. Go ahead and lock this, I'll repost in the correct forum.
Tried TWRP?
This seems to be a weird issue that I'm having, and I hope I'm not missing a step...
Anytime I install a custom rom past 4.1.2; I get no phone audio. I can load up web pages fine, SMS/MMS works to my knowledge, but there is no phone audio. I'll call my house phone, and it will ring the house phone, but I cannot hear myself through the other line. I've tried flashing radios/modems, different combination of ROMs and kernels, and the only way I'm able to keep an active phone, that is able to make phone calls, is to stick with a stock ROM.
My first thought is maybe it thinks it's an unlocked phone? And that's causing it to act up, but I've never had an issue like this before. Any help would be appreciated.
tricky_tee said:
This seems to be a weird issue that I'm having, and I hope I'm not missing a step...
Anytime I install a custom rom past 4.1.2; I get no phone audio. I can load up web pages fine, SMS/MMS works to my knowledge, but there is no phone audio. I'll call my house phone, and it will ring the house phone, but I cannot hear myself through the other line. I've tried flashing radios/modems, different combination of ROMs and kernels, and the only way I'm able to keep an active phone, that is able to make phone calls, is to stick with a stock ROM.
My first thought is maybe it thinks it's an unlocked phone? And that's causing it to act up, but I've never had an issue like this before. Any help would be appreciated.
Click to expand...
Click to collapse
I don't believe the kernal is problem
What is your specific device model?
What have you tried to flash exactly?
Who is your carrier?
Are you flashing clean with all wipes?
Are you letting rom settle?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
tricky_tee said:
This seems to be a weird issue that I'm having, and I hope I'm not missing a step...
Anytime I install a custom rom past 4.1.2; I get no phone audio. I can load up web pages fine, SMS/MMS works to my knowledge, but there is no phone audio. I'll call my house phone, and it will ring the house phone, but I cannot hear myself through the other line. I've tried flashing radios/modems, different combination of ROMs and kernels, and the only way I'm able to keep an active phone, that is able to make phone calls, is to stick with a stock ROM.
My first thought is maybe it thinks it's an unlocked phone? And that's causing it to act up, but I've never had an issue like this before. Any help would be appreciated.
Click to expand...
Click to collapse
After u answer captemos questions… let me ask u this. You say stock 4.1.2, do u mean you have actually odin'd the stock release from sammy?
Gil81 said:
After u answer captemos questions… let me ask u this. You say stock 4.1.2, do u mean you have actually odin'd the stock release from sammy?
Click to expand...
Click to collapse
Apologize for the delay - been busy at work. I guess I could've been clearer.
I am using the SGH-i717 on AT&T. By stock, I meant a Touchwiz-based rom (i.e., Padawan JB). I have no problems with making or receiving phone calls. Whenever I flash a ASOP-based rom, (i.e., LiquidSmooth, BeanStalk, etc.) I have intermittent phone issues. The phone issues I'm having is not having audio when making or receiving phone calls. I know that it is actually placing the call, but I cannot hear the person on the other end, nor can they hear me. Now if I go into network operators, and select an operator that I know isn't going to work (i.e, Verizon, or T-Mobile), and then use "Choose Automatically", sometimes that works for a little bit. However, that has been working less and less now.
My process of flashing includes flashing the rom of choice after a full wipe and reset (right now, it's LiquidSmooth 4.4), wiping the cache and dalvik a couple of times, installing Polluti0n's rom patch, wiping cache and dalvik a couple of times, then installing PA Stock 4.4 Gapp, and finishing the whole process by wiping cache and dalvik a few times more. This is all done through gimmeitorilltell's TWRP Recovery 2.8.0.0
As stated before; I have no issues with Touchwiz-Based roms. I can make and receive phone calls with no problems. Also, before I rooted the phone, i updated it through Kies; so I assume that would update it to the latest radio available. That would be my first suspect, but I'm having difficulty finding a flashable radio for the device.
There also might be a step I'm missing, since all my experience previously with rooting and flashing came on CDMA devices, so there was no issues with radios.
tricky_tee said:
Apologize for the delay - been busy at work. I guess I could've been clearer.
I am using the SGH-i717 on AT&T. By stock, I meant a Touchwiz-based rom (i.e., Padawan JB). I have no problems with making or receiving phone calls. Whenever I flash a ASOP-based rom, (i.e., LiquidSmooth, BeanStalk, etc.) I have intermittent phone issues. The phone issues I'm having is not having audio when making or receiving phone calls. I know that it is actually placing the call, but I cannot hear the person on the other end, nor can they hear me. Now if I go into network operators, and select an operator that I know isn't going to work (i.e, Verizon, or T-Mobile), and then use "Choose Automatically", sometimes that works for a little bit. However, that has been working less and less now.
My process of flashing includes flashing the rom of choice after a full wipe and reset (right now, it's LiquidSmooth 4.4), wiping the cache and dalvik a couple of times, installing Polluti0n's rom patch, wiping cache and dalvik a couple of times, then installing PA Stock 4.4 Gapp, and finishing the whole process by wiping cache and dalvik a few times more. This is all done through gimmeitorilltell's TWRP Recovery 2.8.0.0
As stated before; I have no issues with Touchwiz-Based roms. I can make and receive phone calls with no problems. Also, before I rooted the phone, i updated it through Kies; so I assume that would update it to the latest radio available. That would be my first suspect, but I'm having difficulty finding a flashable radio for the device.
There also might be a step I'm missing, since all my experience previously with rooting and flashing came on CDMA devices, so there was no issues with radios.
Click to expand...
Click to collapse
first off i would flash the rom like so.
1. Factory Data reset
2. Wipe Cache/Dalvik
3. Format System/Data
4. Install rom from Sdcard
5. Wipe Cache/Dalvik
6.Reboot device
7.boot back into recovery
8.Wipe Cache/Dalvik
9. Flash gapps
10.Wipe Cache/Dalvik
Check to see if all is well once the rom is flashed and only the rom. Seems like over kill but can help narrowing down the issue, but i do agree with you as kies being the culprit I never did use it let alone trust it to update the device. Odin would be a better choice and no need to update the device for the latest radio as we have flashable zips. Blazes ics modem is what I'm currently using and has been great, one last thing I'd recommend is to go here http://www.sammobile.com/firmwares/ and grab the JB update and flash it via odin if all else fails.
I experiencing a similar symptom. Intermittently, not one can her me no I can hear anyone. I'm currently on Slimkat 4.4.4 and I have to reboot in order to make the call. Never had this problem when on stock JB 4.1.2.
Can some one point me to how to downgrade to Stock 4.1.2. Thinking about going back, I need a reliable phone.
Upgrade Radio
You must get the best radio for your location:
http://forum.xda-developers.com/showthread.php?t=1693545
tricky_tee said:
Apologize for the delay - been busy at work. I guess I could've been clearer.
I am using the SGH-i717 on AT&T. By stock, I meant a Touchwiz-based rom (i.e., Padawan JB). I have no problems with making or receiving phone calls. Whenever I flash a ASOP-based rom, (i.e., LiquidSmooth, BeanStalk, etc.) I have intermittent phone issues. The phone issues I'm having is not having audio when making or receiving phone calls. I know that it is actually placing the call, but I cannot hear the person on the other end, nor can they hear me. Now if I go into network operators, and select an operator that I know isn't going to work (i.e, Verizon, or T-Mobile), and then use "Choose Automatically", sometimes that works for a little bit. However, that has been working less and less now.
My process of flashing includes flashing the rom of choice after a full wipe and reset (right now, it's LiquidSmooth 4.4), wiping the cache and dalvik a couple of times, installing Polluti0n's rom patch, wiping cache and dalvik a couple of times, then installing PA Stock 4.4 Gapp, and finishing the whole process by wiping cache and dalvik a few times more. This is all done through gimmeitorilltell's TWRP Recovery 2.8.0.0
As stated before; I have no issues with Touchwiz-Based roms. I can make and receive phone calls with no problems. Also, before I rooted the phone, i updated it through Kies; so I assume that would update it to the latest radio available. That would be my first suspect, but I'm having difficulty finding a flashable radio for the device.
There also might be a step I'm missing, since all my experience previously with rooting and flashing came on CDMA devices, so there was no issues with radios.
Click to expand...
Click to collapse
follow dzee advice for flashing...rock solid method..but i still would like to know if you were ever on stock unrooted jb 4.1.2
what version of android were you on when you rooted the device the first time.
---------- Post added at 06:19 PM ---------- Previous post was at 06:11 PM ----------
dodgy1 said:
I experiencing a similar symptom. Intermittently, not one can her me no I can hear anyone. I'm currently on Slimkat 4.4.4 and I have to reboot in order to make the call. Never had this problem when on stock JB 4.1.2.
Can some one point me to how to downgrade to Stock 4.1.2. Thinking about going back, I need a reliable phone.
Click to expand...
Click to collapse
follow the li.k above ur original post. dzee gives a li.k to sammobile. download the correct tar file and fladh via odin