When rooting my phone by mistake I flashed my phone with a gingerbread firmware, so I flashed the phone again with the stock Argentina Claro firmware (because I live in Argentina and my carrier is claro), then I rooted it. But now the dialer can't make phone calls, and if I try to make a call sound breaks, so my phone ends up with no sound until I reboot it, and trying to change any sound setting crashes Android. How can I fix this?
Mastermagnus said:
When rooting my phone by mistake I flashed my phone with a gingerbread firmware, so I flashed the phone again with the stock Argentina Claro firmware (because I live in Argentina and my carrier is claro), then I rooted it. But now the dialer can't make phone calls, and if I try to make a call sound breaks, so my phone ends up with no sound until I reboot it, and trying to change any sound setting crashes Android. How can I fix this?
Click to expand...
Click to collapse
Wipe cache and dalvik cache from recovery.
If that do not help do factory reset.
Thanks! A factory reset fixed the issue.
Related
Hello
I just installed Darky's 5.2 ROM over my stock 2.1-update1 and everything works fine, but whenever I receive a call something (dialer?) gets a force close and the call is rejected together with a temp. loss of signal.
Then everything is back to normal...
Any steps I'd take? I'm pretty new to this.
have the exact same problem... can dial out no problem but only receiving calls. so thinking about whether I should flash another rom until this is fixed.....
I was wondering could I just do a factory reset and then flash the rom over again? Do I have to disable the voodo lagfix before? Not too sure how this works heh.
I don't have this problem. But whenever i am in the game "flick kick football," I get some random hangs, and is forced to close. I suspect that happens when I get incoming calls. Anyway to confirm this?
Jule1k said:
Hello
I just installed Darky's 5.2 ROM over my stock 2.1-update1 and everything works fine, but whenever I receive a call something (dialer?) gets a force close and the call is rejected together with a temp. loss of signal.
Then everything is back to normal...
Any steps I'd take? I'm pretty new to this.
Click to expand...
Click to collapse
I have the same problem. I recived a call, something force closed, the signal dropped and i lost the operator. I had similar problems with bluetooth and file manager before on this ROM, but I re-flashed it and everything worked again.
no problem here with Darky's 5.2 ROM and the Clean Guide Instruction, i just received a call without any problems
I used the easy guide and did not clean anything or do a factory reset, I just followed it like a dumbo. I came from 2.1-update1 stock JM5 kernel with a ton of apps installed, if that helps.
hey I think I found a solution to this. I went to recovery mode, wiped cache, wiped dalvik, did a factory reset and voila, receiving calls works without force closing.
phew.. was about to download another rom. anyhow, hope that works for you Jule!
still a few problems with the ROM that i encountered:
- my AT&T home button is not working.... not to sure whether there will ever be a fix for it
- media volume, even set to max, is not working when playing movies and youtube.
Hi all,
Last week I upgraded my Note to new LT4 rom.(s). Couple of days later, my Note was unable to make calls. When I try to make call or receive a call, there is no sound neither from earpiece nor from the speaker. If I reboot the phone I sometimes be able to make some calls with a great noise on the background then it stops.
I re-flashed the rom and flashed other roms even re-flashed LZS roms with all clean install even finally formatted the internal sd card . No change.
Since I can make one-two calls after each reboot I still think it may be a software issue rather than hardware.
All other functions including cell reception, 3G, internet, wireless all working very well but cannot use it to make phone calls.
If you have any suggestions I appriciate.
Best Regards
Update - I installed the stocked LZS Rom but the problem still continues.
tugrulbey said:
Hi all,
Last week I upgraded my Note to new LT4 rom.(s). Couple of days later, my Note was unable to make calls. When I try to make call or receive a call, there is no sound neither from earpiece nor from the speaker. If I reboot the phone I sometimes be able to make some calls with a great noise on the background then it stops.
I re-flashed the rom and flashed other roms even re-flashed LZS roms with all clean install even finally formatted the internal sd card . No change.
Since I can make one-two calls after each reboot I still think it may be a software issue rather than hardware.
All other functions including cell reception, 3G, internet, wireless all working very well but cannot use it to make phone calls.
If you have any suggestions I appriciate.
Best Regards
Update - I installed the stocked LZS Rom but the problem still continues.
Click to expand...
Click to collapse
have you checked that your IMEI is the correct one? maybe it got corrupted...If that is the issue, should be solved by restoring your EFS backup .
glevitan said:
have you checked that your IMEI is the correct one? maybe it got corrupted...If that is the issue, should be solved by restoring your EFS backup .
Click to expand...
Click to collapse
No, I haven't checked. But I don't know my previous IMEI . How am I supposed to know if changed or not? I haven't backed it up. How to restore to original status?
Thanks
tugrulbey said:
No, I haven't checked. But I don't know my previous IMEI . How am I supposed to know if changed or not? I haven't backed it up. How to restore to original status?
Thanks
Click to expand...
Click to collapse
Below the battery you have the original IMEI number...if it is changed, then that is the issue. If you don't have a backup of your EFS, I am not sure but you can try to flash the stock rom by selecting EFS in ODIN PC. That is stuff is quite delicate, so I would recommend you to ask Dr. Ketan that he is more familiar with it.
But again, make sure that your imei is fine first. If that is not, then might be a hardware issue..
Thank you for your kind suggestions. I checked and it looks O.K. there is no change on IMEI. Actually I can receive SMS and 3G is working very well, my phone rings if someone calls but cannot talk.
Problem continues
Hi There,
The problem still hasn't been solved. Somehow all is going fine and suddenly re-occures. Has anybody come up with same problem and found a solution? Please share.
ı am on xlt6 Rom with Philz kernel
Regards
Dear, all
first of all, sorry for my bad english...
I have my galaxy s3 mini for a few months (i bought it on august 2013), a week ago my HH had a notification that a new ugrade available. So i tap OK, and the phone downloaded the upgrade (195 MB, if i remember correctly). When the phone succesfully updated, i check the system. I noticed that the baseband version was upgraded from i8190DXAMA2 to i8190DXAMJ1. A few days later, my phone started acting wierd. All the system apps start to crash a lot. One day the messaging dan contact app not responding, and i had to force close and reboot the phone. The other day was clock app crashing, and i had to reboot the phone.
Does anyone have same problem like me? How can i fix this? I tried to clear app data, but that didn't work. Reboot is the only way to fix this problem. And i don't want to reboot the phone every day or two. If i want to downgrade my baseband version to original, how can i do that?
and oh, my phone is not rooted. Still using stock ROM.
thanks
I'm guessing you didn't do a factory data reset after update?
Reinstall firmware using kies, after it's done, turn on the phone, do a factory reset and then setup it as you would with new phone.
Optionaly you can make a backup with KIES before the upper ster, and after doing a factory reset, restore the backup. Or just copy/paste stuff you need (music, picture, etc)
zvorkapic.os said:
I'm guessing you didn't do a factory data reset after update?
Reinstall firmware using kies, after it's done, turn on the phone, do a factory reset and then setup it as you would with new phone.
Optionaly you can make a backup with KIES before the upper ster, and after doing a factory reset, restore the backup. Or just copy/paste stuff you need (music, picture, etc)
Click to expand...
Click to collapse
No, i didn't. The update was via OTA. Ok, i will try it and see if it works, thanks. :fingers-crossed:
So for some reason today, my phone restarted and now I can't call people or receive calls, if I do. My phone restarts. Also can't use Bluetooth or it also does the same and restarts what can cause this? My phone getting too hot and damaged the motherboard? When I installed a kernel it was corrupted? I really have no understanding what caused this. I had resurrection from on it. I updated it with a newer one and did a bootloop. So I put cyangemod on it and worked but noticed those huge issues. Thinking the ROM was corrupted I put rr back on it and had the exact same issues. Any help would mean everything to me
austtint said:
So for some reason today, my phone restarted and now I can't call people or receive calls, if I do. My phone restarts. Also can't use Bluetooth or it also does the same and restarts what can cause this? My phone getting too hot and damaged the motherboard? When I installed a kernel it was corrupted? I really have no understanding what caused this. I had resurrection from on it. I updated it with a newer one and did a bootloop. So I put cyangemod on it and worked but noticed those huge issues. Thinking the ROM was corrupted I put rr back on it and had the exact same issues. Any help would mean everything to me
Click to expand...
Click to collapse
How are you flashing your roms? Like, what sort of wipe, what flash order, etc.
Sent from my DROID Turbo using Tapatalk
for some reason after going back to stock which fixed everything, everytime I go back now to cm 13. I go to advance options under wiping and just check them all, and wipe. Then put the rom and gapps on then do the cache wipe. Then roboot. Afterwards, I still had the problem so I just went back to stock again.
Settings -> Apps -> gear icon -> Default Apps -> Phone app.
Make sure you set your Google Dialer to default, otherwise incoming and outgoing calls cause reboots.
Hello,
I have a motorola G6 that after bad root get stuck on bootloop.
I flash the phone with two roms but the phone after flash dont have sound during calls, the earpice dont work even in loudspeaker, but the phone rings when is receving calls.
anyone already have this problem?
tanks
This question is probably in the wrong section but anyway...I did. I never checked the phone prior to rooting so I'm not sure if a "bad root" was the cause or not. However, I experienced the exact same problem as you. I was originally on build OPS27.82-19-4 so I reflashed stock OPS27.82-19-4 as described here. But I still had the same problem. On a whim I randomly flashed build OPS27.82-19-4 following the same instructions. The phone has been working great ever since (I have it rooted, xposed. etc...). Not sure why there was a problem, or if reflashing the newer build "fixed" it or not...but as I said, all is good now. FWIW, when I check the sim status in settings>about phone, the network section is blank. It was blank when I had problems too.
Perhaps this will help you..
PS When I reflashed the firmware, the phone would boot into fastboot mode, then when I selected "Start" it would boot to the OS. If you run into that, here is how it was fixed. See posts 5, 6, 7, & 8.
Good luck!
I had a similar problem, I did the root, TWRP, I ended up giving up and flash again on the stock of the bike G6 Play (Brazil) available here in XDA, to my surprise, he made and received calls normally, the speaker for music and connections of other applications (Whatsapp, Messenger, Hangouts, etc.), but it did not work for the rom dialer.
I thought I had a problem, it was when a system update appeared, I installed it and it worked again.
I figured it was some rom bug I installed.
Tanks for the help.
I solved the problem flashing the phone with flashrom.bat instead of put the comand one by one.
Many tanks
Multiredes said:
Tanks for the help.
I solved the problem flashing the phone with flashrom.bat instead of put the comand one by one.
Many tanks
Click to expand...
Click to collapse
That's because a custom rom or GSI does not have all the necessary files. 99.9% of the time, flashing stock will fix a problem.