I just recently flashed HispAsian_BlackOut_v0.2 and also odin NH7 modem. Now when I try to make phone calls, nothing happens. As in, I try to dial a number and it just stays on the dialer and it says "Process com.android.phone isn't responding"(I can still send/recieve text and use data). I tried reflashing the rom, the modem, updating the NH7 Firmware and I still have the same problem (I always do a full wipe). Any ideas how to fix this?
Even though i updated the firmware, it didnt work the first time.
Related
so I flashed Lifeless rom v14 a, the ZVB Radio Update M9615A-CEFWMAZM-2.0.1690: and Joker kernel. I was coming from lifeless v11 and old radio. ever since flashing i cant send short text messages they fail to send 75% of the time if I send a complete sentence it goes through no problem. I tried restoring with a nandroid i had from twrp with efs backed up it didnt fix it and now my wifi wont connect to home network even though it recognizes it as saved. I reflashed lifeless v14 and new radio, wifi works again but text has same issue. I downloaded Go sms pro and set send settings to send through smsc with sprints # , still wont fix it. I had sprint send a refresh signal didnt work. I have an older nandroid through cwm recovery that i want to flash but I get a md5 mismatch . I tried to fix md5 through adb but my computer wont pick up usb debugging in charge only mode only when media sync is enabled. I deleted and re-installed the drivers, different cables and ports still wont work. Any ideas for either issue guys?[/B]
Ever get it fixed? i can't send any texts and it was working fine with several roms till yesterday. Even called sprint and got one text to send and then it stopped again.
I first seen this problem when i flashed synergy rom. My phone failed to activate so as a result it wouldnt make/recieve phone calls but i could text and use data normally. So i tried skipping the setup, using global apn, went to stock then came back, re-flashed many times and the result was either no service or i couldnt make/recieve calls. So i tried to Odin back to stock and unroot, then tried a different rom but still it wouldnt work. I then restored a backup i had of CS ROM but still not working. Any help would be appreciated.
Update: Okay so incase anyone runs into this problem I found a fix that works for me. What i did was bring my phone completely to stock and unroot it. Then i got a notification telling me about a software update, when i opened it a popup came telling me Im now registered. Then I rooted and flashed synergy rom, skipped the setup but then text or phone calls didnt work, so i put airplane mode on then off, and voila it working again.
osman212 said:
I first seen this problem when i flashed synergy rom. My phone failed to activate so as a result it wouldnt make/recieve phone calls but i could text and use data normally. So i tried skipping the setup, using global apn, went to stock then came back, re-flashed many times and the result was either no service or i couldnt make/recieve calls. So i tried to Odin back to stock and unroot, then tried a different rom but still it wouldnt work. I then restored a backup i had of CS ROM but still not working. Any help would be appreciated.
Click to expand...
Click to collapse
Did you check your IMEI? If it's unknown or 0, there's a stickied thread on how to restore it.
Also, make sure you have the right modem for you carrier (modem thread if you're not sure). As well as having the right APNs.
BWolf56 said:
Did you check your IMEI? If it's unknown or 0, there's a stickied thread on how to restore it.
Also, make sure you have the right modem for you carrier (modem thread if you're not sure). As well as having the right APNs.
Click to expand...
Click to collapse
IMEI seems to be fine. I dont know why i didnt think of flashing a different modem, ill try that. Thanks
osman212 said:
IMEI seems to be fine. I dont know why i didnt think of flashing a different modem, ill try that. Thanks
Click to expand...
Click to collapse
In case you hadn't found the link yet.
http://forum.xda-developers.com/showthread.php?t=1831898
My phone modem randomly shuts itself, I think.
My phone was broken about a month ago, no efs backup, generic imei, 00000 serial number. It was fixed by a local shop who has those "boxes".
It was formatted to the early iterations of JB 4.1.2. DMA1 I think. I then updated it through OTA to the latest version DMC3.
Then it happened. My messages would suddenly be lost. I dialed *102# in the dialer then it hangs, The signal icon would then be the circle icon like those in no parking signs after 10 sec. This method actually forces the modem to restart. Then all would be okay again like nothing happened. All messages are intact.
I flashed the stock rom thinking it would repair the problem but I mistakenly flashed Dr Ketans pre rooted rom marked XME which is for Malaysia. Flashed the proper firmware from Sammobile, XTE for the Philippines. No Signal. Restored using the efs I backed up after my phone got repaired. Emergency Calls Only. Installed Ariza Patch. Got my signal back, Imei normal, Serial Number Normal, but my Baseband Version shows Ariza_NII_[V.01].
I thought I fixed my problem but its still there. It still randomly hangs while Im texting.
Could it be a Kernel Problem? What Kernel could you suggest?
Could it be a bug in the messaging and phone app? Even for Google Play apps, it hangs, looses my messages.
Has anyone encountered such?
I would post a video if it happened again.
Please HELP!
I was using CarbonROM based on JB 4.3.1 but was getting fed up with not being able to connect with families oversea through VOIP such as skype, viber, etc... because the mic doesn't work with voip apps in AOSP Roms. So I decided to go back to stock and full flash samsung's 4.3 stock rom via Odin 3.9; the rom was 2.24GB extracted so I'm almost certain and well aware that it's the bloated tmo samsung tw version.
About device show android version 4.3, baseband M919UVUEMK2, and I can get LTE signal fine but cannot toggle wifi on. And when I go to place a phone call the entire UI freeze and won't respond, then come the "Process com.android.phone isn't responding" dialog box. Except for wifi and phone call everything else seems to work, but I haven't tested extensively yet nor are they important to me.
From here I went about installing latest CWM recovery and SU, and I was able to install OmniROM and CM11 nightlies. But the phone UI freezing problem still persist even with those custom roms.
At this point I have an inkling it has something to do with the new MK2 modem. I noticed that when installing the stock fw it had modem.bin and NON-HLOS.bin entries in Odin. I read through other threads and some mention about not installing NON-HLOS.bin file, but it was included in the stock fw so I don't know why it would misbehave (if it's the culprit)
At this point I am out of options. Someone with knowledge and experience with this please give helps or suggestions. Thank you!
If you flashed via Odin, you had no choice with the non _hlos.bin. That's only for peoples sticking with mdl bootloader but flash 4.3 ROM.
Have you tried a factory reset after updating to 4.3
☞ Sent from here☜
I did a factory reset in TW and it still freeze. I can open the dialer app, punch in a number or choose from contact list, but as soon as I hit Dial the whole phone freeze. The connection is made because I test dialed my home phone # and it rang, just that I could not get the phone to talk. No dial sound from the phone, screen it black; I can see status bar but it won't respond to my touch. When I pick up the home phone and tried to make a conversation there's no sound coming out of the S4, and even if I yell real loud into the mic no voice is carried over to the home phone.
I tried installing latest Omni rom 4.4.2 kitkat nightly, did a factory reset after letting phone sit still at home screen for 5 mins after installation, still can't get the phone app to do its job at all.
Edit: forgot to mention that the phone is unlocked and I'm using Straight Talk AT&T LTE sim. LTE works fine, just no calling due to this update problem here.
nvm I fixed it by reflashing a file Modem_UVUAMDL.tar.md5 until it turns back to MDL baseband, then flashed modem.bin only and it everything works again.
kawaiichi said:
nvm I fixed it by reflashing a file Modem_UVUAMDL.tar.md5 until it turns back to MDL baseband, then flashed modem.bin only and it everything works again.
Click to expand...
Click to collapse
i'm having the same issue, I was to download the modem_UVUAMDL.tar.md5 but it did not include the modem.bin. is it safe to use any version of the modem.bin file I find here?
So about 6 months ago, I decided to finally try out some custom roms on my t999 after running stock for over a year. I tried a couple of roms and stuck with cm11. Every thing was great until about 3 weeks ago. Out of nowhere, my phone randomly decides to drop connection to tmo towers. Sometimes i have bars and 4g symbol and sometimes i don't have anything. When I pull the battery and restart, I am able to connect to data, make calls, and send messages for a few minutes, but then i lose everything. Randomly throughout the day, I will get signal back for a few minutes but thats it. I flashed a touchwiz rom for now so I can use wifi calling, So that still works.
So I tried to flash a different baseband modem from DocHoliday77 and none of them worked. I also tried going back to stock following DocHoliday77s guide once again, but for some reason that does not work. I launch odin3.07, put my stock firmware in the pda section, make sure only auto reboot and F reset time are checked. I connect my phone in download mode, it is detected and i start the process. The phone restarts but gets stuck at the samsung logo screen. I have tried flashing different roms and none work.
I dont think its an imei problem because I got the phone direct form tmo with a contract.
Does anyone know what I might be doing wrong? ANY help would be greatly appreciated.
Did you factory reset after you flashed the firmware in Odin? That's the only way it will boot coming from cm.. You may just need a new sim if flashing to stock won't fix it.. And BTW T-Mobile doesn't do contracts