As the title suggests, suddenly I started getting force closes with com.android.phone when I'd receive a call. I immediately tried to call out, same story. I've been troubleshooting for the past few hours, and had no luck finding anything relevant on XDA or any other site.
Firstly I switched kernels, since I'd updated to DSB's latest, though I'd had no issues with it until then. That failed, so I reverted to Viper's stock build.prop, undoing some changed I'd been running for a while (and hadn't modified at all today).
With no luck there, I backed up my sdcard and did a full factory reset and formatted the sdcard in twrp and then in cwm, followed by a reinstall of the latest Viper ROM. Even that didn't work, so I relocked and RUU'd back. Twice. Same exact issue. I can text anyone just fine, data over LTE goes on as normal, but anytime I try to make a call, be it with the stock dialer or through a diff one from the play store (for kicks, last resort). I reseated the SIM card a multitude of times, to no avail. I get full functionality with my SIM in my other phone, so I'm sure it must be the hardware itself on the phone. Every time com.android.phone stops, the SIM initialization happens like when you physically re-seat the SIM.
The troubling thing is that I haven't done anything, save for a simple kernel and recovery update, which would've been negated by two RUU runs to stock. I haven't touched the SIM card or anything, at least until that started happening. Furthermore confusing is how all other functionality can remain except for actually making phone calls.
Removing the SIM entirely and dialing a number does the exact same thing, just as an FYI.
Has anyone seen this? Any ideas?
As I've unlocked my phone, my last resort is to go into a VZW store and act like an idiot so they don't check to see if i unlocked it. Further complicating that is the fact that the DNA was actually purchased on my own account, which I closed, and brought to an unlimited data line that was preexisting. I'm half tempted to wait for the official OTA and see if that will remedy the issue, but my fear is this may be a physical issue beyond the remedy of a firmware update.
http://forum.xda-developers.com/showthread.php?t=2126386
Check this thread, me and another member faced the same problem. I can get 3g/2g data, sms and all other functions just right. Just no phonecalls, every time i make a call i get a crash of the app.
So, i am pretty sure this is a software bug. For god's sake, what a strange problem!Did your phone used to work right?
I bought my phone from ebay, did not check if phonecalls are working(i couldn't imagine such a bug) and went straight away to rooting/other kernels/roms etc. But can't find a solution too,tried everything as you, and the worst, i am overseas!!!
Is the update coming soon?
edit1: i have seen lots of threads about sim errors,a very common issue of DNA, i am believing that these two bugs have something in common. No hardware defect, just software bugs.
ergotelis said:
http://forum.xda-developers.com/showthread.php?t=2126386
Check this thread, me and another member faced the same problem. I can get 3g/2g data, sms and all other functions just right. Just no phonecalls, every time i make a call i get a crash of the app.
So, i am pretty sure this is a software bug. For god's sake, what a strange problem!Did your phone used to work right?
I bought my phone from ebay, did not check if phonecalls are working(i couldn't imagine such a bug) and went straight away to rooting/other kernels/roms etc. But can't find a solution too,tried everything as you, and the worst, i am overseas!!!
Is the update coming soon?
edit1: i have seen lots of threads about sim errors,a very common issue of DNA, i am believing that these two bugs have something in common. No hardware defect, just software bugs.
Click to expand...
Click to collapse
thanks for the thread, for the life of me i couldn't find anything exactly relating to what i described. that is spot on though, and def makes me feel a bit more at ease that maybe it can be resolved with an update to the firmware that's due soon.
yea, the funny thing is that it worked flawlessly, i never even got the SIM error message, i'd been texting my gf, a few friends, and my parents and then my pops called in the evening and it immediately closed out the call before it really even rang. i called him right back and that's when the force closes started happening, calls never working agian thereafter. however, i was able to still text everyone i was before and data was working flawlessly as always, just no calls, not even after all the crap i did to troubleshoot.
the update is hopefully going to be out soon. the support documents came out a few days ago. i def can't survive on this galaxy nexus after having used my DNA since launch!
I will wait for the update too, hopefully it will be uploaded today or tomorrow i think. But just because i can't get on the air update, i need to download from a server the update and install it on my own.
If anyone finds a solution or have an idea of what to look/do, please post here. I am pretty sure it is a software bug, something is stucking the application from working properly. The other solution is RMA, but it is a very difficult to send it back and get it back again.
ergotelis said:
I will wait for the update too, hopefully it will be uploaded today or tomorrow i think. But just because i can't get on the air update, i need to download from a server the update and install it on my own.
If anyone finds a solution or have an idea of what to look/do, please post here. I am pretty sure it is a software bug, something is stucking the application from working properly. The other solution is RMA, but it is a very difficult to send it back and get it back again.
Click to expand...
Click to collapse
The update is out now, can someone send it to me too? I am overseas, trying to find a way to download it.
OP, can you test this one to see if you get a fix?Thanks!!!
Ok, I had the same exact issue. I was stock then went to viper Dna then tried going to hatka and soft bricked my phone. I went back to stock using the RUU. That's when I got the com. Android. Phone crash message. So I had to re unlock reboot and then flash viper Dna again. Everything works as it should now.
After saying all that I just got the new update from Verizon. I assume I shouldn't flash this since I'm on a custom rom.
Sent from my Nexus 7 using xda premium
Thanks for the input, really interesting!Will try it right away! Hope you won't have any problems with the update now!
msturner79 said:
Ok, I had the same exact issue. I was stock then went to viper Dna then tried going to hatka and soft bricked my phone. I went back to stock using the RUU. That's when I got the com. Android. Phone crash message. So I had to re unlock reboot and then flash viper Dna again. Everything works as it should now.
Click to expand...
Click to collapse
THIS IS THE SOLUTION!Now working! A HUGE HUGE HUGE THANKS TO YOU!!!! :victory:
ergotelis said:
THIS IS THE SOLUTION!Now working! A HUGE HUGE HUGE THANKS TO YOU!!!! :victory:
Click to expand...
Click to collapse
Hi guys i got a similar problem. My DNA was perfect since yesterday but now i can use data connection for internet. All the other stuff is working fine....SMS,call, wifi, the only thing that is not working is the 3g data. All of this problem came when i flashed the viper DNA, so i flashed the supercharged hoping it was an issue of the rom. Olso with the supercharged the problem was always here.... So i decide to came back to stock and i re-lock my bootloader and flasched stock RUU. But data connection is still not working :crying:
can anyone please tell me what can i do?
Did you install patches 1.1.1& 1.1.2 from viper?They fix some gsm problems.
As I've unlocked my phone
ergotelis said:
Did you install patches 1.1.1& 1.1.2 from viper?They fix some gsm problems.
Click to expand...
Click to collapse
yes but notthing changed.... :'(
Now i'm compleatly stock and the problem is still here.
flash again the viper rom, do the whole procedure again, at least this is what i did and fixed the problem!(stock->viper->stock-> viper and then OK)
ergotelis said:
flash again the viper rom, do the whole procedure again, at least this is what i did and fixed the problem!(stock->viper->stock-> viper and then OK)
Click to expand...
Click to collapse
Which version of viper worked for you?
hard problem
Has any one figured out this problem? I have not been able to received any phone calls since I did s-off. I have tried everything that has been wrote so with no luck. I have relocked my phone and flashed stock RUU no change. Unlocked and tried several roms still no calls. formatted everything under CWM not change. Fixed permissions. Went back and re-locked and reflashed stock RUU. I know that some of the things above have fixed others phones and some still have problems. I also found a script someone wrote lock my phone which now it says locked and flashed stock rom after that still have problem. Does anyone here here a idea that I have not already mentione above? I like my droid dna but if I can't get it to make and take calls it is a paperweight.:crying:
jimmydee62 said:
Has any one figured out this problem? I have not been able to received any phone calls since I did s-off. I have tried everything that has been wrote so with no luck. I have relocked my phone and flashed stock RUU no change. Unlocked and tried several roms still no calls. formatted everything under CWM not change. Fixed permissions. Went back and re-locked and reflashed stock RUU. I know that some of the things above have fixed others phones and some still have problems. I also found a script someone wrote lock my phone which now it says locked and flashed stock rom after that still have problem. Does anyone here here a idea that I have not already mentione above? I like my droid dna but if I can't get it to make and take calls it is a paperweight.:crying:
Click to expand...
Click to collapse
Still broke?
Sent from my HTC6435LVW using xda app-developers app
kaliblazin707 said:
Still broke?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Yes it is still broke I just don't know what to do at this point paper weight right now.
Related
I'm having a problem with my touchscreen that started happening yesterday after I flashed a new ROM. I flashed Android Revolution HD 1.1.1, and on the lockscreen after the first boot is when it first started acting up. This youtube video shows exactly what my phone is doing: http://www.youtube.com/watch?v=iIrmLOTiUZk
I've nand back to other roms that I've used in the past, and still the same issue. Superwiped and flashed different roms, and it would solve the problem for several hours, but the issue comes back. When the problem happens, a restart will solve the issue for maybe 15 minutes. It seems as if it's a hardware issue, but I don't get why rebooting/wiping and reflashing would solve the issue for a period of time. If anyone has any advice or the same issue with a fix, it would be much appreciated. Thanks in advance.
*Idk if it matters, but I'm hboot 1.4, zagg invisishield screen protector on.
Also, the touchscreen issue only happens at the bottom center of the screen - where the lock ring is located.
Update: I nand backed to stock rom, no issues for about 24 hours, started happening again. Any thoughts anyone??
Might be a hardware issue. If it keeps occurring I'd suggest taking it in to be looked at. Or you could try reflashing your recovery and doing a full data wipe and flash a stock rooted rom and see if that helps. Hope it does. Good luck.
Locked & Loaded
""shooter on Deck""
Thanks, I'll try reflashing my recovery tonight. It seems to be hardware related, but the temporary fix (data wipe and flash Rom) is what confuses me. I just hope I don't have to send it in and get a refurb with hboot 1.5.
Also, when I do super wipe, should it automatically boot into recovery? It just hangs on the white HTC screen, and I have to.pull the battery to get into recovery. And after I install a Rom, why does it keep my some of my same settings, like the wallpaper and ring volume, and not go to the defaults? I am he if the super wipe is actually doing its thing or not.
Well if your doing a super wipe and it still keeps some of your old settings of a prior rom then I'd suggest trying a different wipe method or redownloading the the super wipe zip, you might have gotton a bad download. As far as if it's supposed to boot right into recovery that I don't know because I don't use any wipe method but the recovery. It hs always worked for me. Try reflashing your recovery and wiping with just the recovery options. Wipe data "complete factory" ,cache and davlik-cache. Then try flashing a stock rooted rom. Or if that doesn't work try the official ruu.
Locked & Loaded
""shooter on Deck""
b1gsby_02 said:
And after I install a Rom, why does it keep my some of my same settings, like the wallpaper and ring volume, and not go to the defaults? I am he if the super wipe is actually doing its thing or not.
Click to expand...
Click to collapse
Well it keeps your wallpaper because Google syncs it with your Google account. That's normal. But as for everything else, it sounds like a hardware issue.
I'm having the same problem on my HTC Flyer and flashing a new ROM or restoring an old backup won't fix it anymore.
Sent from my PG86100 using Tapatalk
I flashed twrp 1.1.1 over 1.0.3 and did a data wipe, cache and dalvik. Flashed a rom and so far so good. I'll see if I can go more than 24 hrs without an issue. If it's a hardware issue, I don't understand why flashing a new rom temporarily fixes the issue, and since the issue started right after I flashed a new rom. I'll continue to update on here and hopefully the reflashing of recovery helps - thanks laie.
Didn't know wallpaper was synced with google account - thanks gumby
Gumby63 said:
I'm having the same problem on my HTC Flyer and flashing a new ROM or restoring an old backup won't fix it anymore.
Click to expand...
Click to collapse
Did you do anything else to try fix the problem?
b1gsby_02 said:
Did you do anything else to try fix the problem?
Click to expand...
Click to collapse
I'm not sure what else to do. I suppose I'm stuck with contacting HTC about a repair. I've done a little bit of research and some people having similar problems have said that it could be a problem with the digitizer. But most explanations were very vague so I'm still not sure what I'm going to do.
Sent from my PG86100 using Tapatalk
Well you should be good to go. Post back in 24hrs with what's going on. Glad your running ok for now.
Locked & Loaded
""shooter on Deck""
Phone was fine all last night and this morning. Early afternoon it started acting up a little bit. Nothing like it used to, but I notice when I set it down or shake the phone a little, it will trigger the issue. So it's more than likely hardware related. Does anyone know Sprint's policy on fixing a phone that is rooted? I am jw if I should revert back to s-on before I go to a Sprint store to have them look at it. I don't know if they check that or not. Usually the first thing they always do is make sure everything is up to date too. Any insight is appreciated, thanks.
I'm in the same boat. Touch screen freaking out, rebooting fixes it for a short time, then it does it again. I'm going to take it in to sprint today and first ask them if they care if it is rooted.
Rob the plumber said:
I'm in the same boat. Touch screen freaking out, rebooting fixes it for a short time, then it does it again. I'm going to take it in to sprint today and first ask them if they care if it is rooted.
Click to expand...
Click to collapse
Please update us after you talk to Sprint. I am curious to what they say about you being rooted and what the problem may be. My phone has been running fine for awhile now. After I reflashed recovery, data wipe, flashed rom, it acted up for a short while about 12 hours later. It's been almost 24 hours since it last acted up and has been fine so far.
Rob, just wondering if you talked to Sprint yet?
Also, does anyone know if I should go back to 100% stock and S-on before bringing my phone into Sprint? They always seem to update everything, and if there is an update, they usually tell you that's the reason why your phone isn't working the way it should.
UPDATE:
I went back to 100% stock and S-ON following this guide: http://forum.xda-developers.com/showthread.php?t=1194053 Then I went into my Sprint store, told them about the issue, and the first thing they did was asked if I had reset the phone and they checked to see if there's any updates available. The phone started to act up again while they were looking it, luckily, because they have to replicate the issue before they can fix the problem. They said it was probably the screen and they were going to replace it. They had me come back an hour and half later, told me they tried replacing the screen and that wasn't it. They didn't know what was wrong, but concluded it was a bad phone. They replaced my phone with one that someone returned within their 30 days. It's not a refurb, but not a brand new one either. I had to pay $35 for the service charge for fixing my phone. I hope this helps anyone who's having the same issue.
Of course my replacement phone has hboot 1.5.
I have not been to sprint yet. I swapped batteries and it had not acted up since. Strange. I had already pulled the stock battery a bunch of times and it would be fine for a half hour or so, then flip out.
Maybe my battery was bad.
Rob the plumber said:
I have not been to sprint yet. I swapped batteries and it had not acted up since. Strange. I had already pulled the stock battery a bunch of times and it would be fine for a half hour or so, then flip out.
Maybe my battery was bad.
Click to expand...
Click to collapse
I have tried a few different batteries, and it didn't seem to matter. Maybe your situation is different. Hopefully that fixes your issue!
My issues have returned. Off to the sprint store!
Rob the plumber said:
My issues have returned. Off to the sprint store!
Click to expand...
Click to collapse
Good luck! Did you revert back to stock and s-on? Or are you going to tell them you're rooted?
I think I'm going to just put a stock ROM on it and ask them first before I hand over the phone.
So I was looking to leave my Sprint contract (long story) and decided to sell my Evo 4g LTE to help pay off the massive contract-breaking bill. I'd had my phone rooted and running CM10 nightlies for quite a while without any sort of trouble.
So right before I put the phone on the market, I took out the SD card, and wiped everything using TWRP recovery. This included Cache/Dalvik/System/Factory reset and the only thing I did different, which was to wipe Internal and External storage.
After that, I flashed the latest CM10 nightly at the time (which was cm-10-20121008 at the time) and called it a day as I didn't want to put any of my info on the phone before I sold it.
Flash forward a couple of days, I sell the phone and almost immediately get a call back saying it has no sound at all.
The guy I sold it to tells me he even tried unrooting and flashing the stock ROM to no avail. I bought the phone back from him, and am trying to figure out what exactly is wrong with it.
Since then, I've discovered that not only is there no sound, although occasionally I will hear the buttons click, so I know the speaker hardware itself is fine, There is also no video playback at all, which makes me think this is some sort of software or firmware problem, though I can't tell where the problem lies.
I've tried installing different ROM's and the best I could get out of video was the Youtube app showing still images every couple of seconds, without any sound at all. I tried loading videos to the SD cards only to get a message saying "This video cannot be played" without any further reason.
I'm currently downloading the latest OTA stock ROM to see if I can restore it to Factory settings, but I'm lost as to what could possibly cause this strange behaviour.
Anybody ever encounter something similar? Any ideas what I could try next?
Alternatively, does anyone want a (mostly) working phone at a steep discount?
Have you ran an RUU yet?
How much do you want for it as is?
jayjam99 said:
Have you ran an RUU yet?
How much do you want for it as is?
Click to expand...
Click to collapse
I tried running the RUU, still won't work.
If you want it, an even $100 will do.
i have the exact same problem ive ran ruu and relocked and locked bootloader i have unrooted ive done everything and the problem still is there please someone help me
So after flashing Cookies and Cream 4.1.2 and working fine for a few days, Calling and texting stopped working. I flashed an ICS Rom and it worked again, for 1 call. Midway the call dropped and everything stopped working again. Phone still gets signal, data works and everything else too. I clean flashed 3 different stock ICS roms with TWRP, nothing is working. Any ideas as to what could have happened?? Im thinking I can only fix it by flashing stock image with ODIN, but im curious as to what could have gone wrong. Im thinking maybe the IMEI got screwed up?? But the symptoms dont really seem like that would be the issue. Any help would be greatly appreciated!!
H0rn3t920 said:
So after flashing Cookies and Cream 4.1.2 and working fine for a few days, Calling and texting stopped working. I flashed an ICS Rom and it worked again, for 1 call. Midway the call dropped and everything stopped working again. Phone still gets signal, data works and everything else too. I clean flashed 3 different stock ICS roms with TWRP, nothing is working. Any ideas as to what could have happened?? Im thinking I can only fix it by flashing stock image with ODIN, but im curious as to what could have gone wrong. Im thinking maybe the IMEI got screwed up?? But the symptoms dont really seem like that would be the issue. Any help would be greatly appreciated!!
Click to expand...
Click to collapse
Try flashing a different modem?
H0rn3t920 said:
... Im thinking I can only fix it by flashing stock image with ODIN, but im curious as to what could have gone wrong? ...
Click to expand...
Click to collapse
That's what I would do...then take it back for warranty repair. Extremely unlikely any ROMS caused this problem.
crutzulee said:
Try flashing a different modem?
Click to expand...
Click to collapse
It sounds like you have a modem that isn't compatible. Many times it will still catch a strong signal, but your sound, if there is any, will be garbled. I would try flashing a couple of different ones and make a test call with each to find what you like and works.
Sent from...
I've got 2 I717 with that problem, good signal 'Not Registered On Network'. I think it's a hardware issue. I've seen more than a few posts about it now. I've tried everything to correct this, I have a good IMEI.
H0rn3t920 said:
So after flashing Cookies and Cream 4.1.2 and working fine for a few days, Calling and texting stopped working. I flashed an ICS Rom and it worked again, for 1 call. Midway the call dropped and everything stopped working again. Phone still gets signal, data works and everything else too. I clean flashed 3 different stock ICS roms with TWRP, nothing is working. Any ideas as to what could have happened?? Im thinking I can only fix it by flashing stock image with ODIN, but im curious as to what could have gone wrong. Im thinking maybe the IMEI got screwed up?? But the symptoms dont really seem like that would be the issue. Any help would be greatly appreciated!!
Click to expand...
Click to collapse
I am having similar problems and after weeks of flashing (ROMS and modems) to no avail, I am going to take my phone in and get a refurb.
I would reflash a stock ROM with Odin, then flash a custom ROM of your choice and the radio(s) that work for your carrier and check the APN setting. If none of that helps, it may more than likely be a hardware issue and would need to be fixed.
Depending on your carrier you can just warranty your phone as a hardware problem. If they refuse because you flash your phone I have yet to hear of Samsung refusing service or warranty because of it. My note stopped working and I have flashed tons of modems & roms, no questions asked it was fixed and back in my hands in 5 working days.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
AT&T's Device Support Center(s) can replace your phone on the spot so long as you're within warranty and they can duplicate the issue after a factory reset/OS flash.
wasnt this version released February 2012? Then shouldnt any i717 qualify under the Samsung 1 year warranty. I'm having the same problem with mine while trying to connect to Mobilicity in Canada. Doesnt help that it drops the Wifi connection every now and again for no reason.
Making me wonder why i just got rid of my S2X yesterday for
Warranties don't start the second the device comes off the assembly line.
The warranty goes into effect on the date purchased, so yes every single I717 falls under the oem warranty.
Shirokishi said:
wasnt this version released February 2012? Then shouldnt any i717 qualify under the Samsung 1 year warranty. I'm having the same problem with mine while trying to connect to Mobilicity in Canada. Doesnt help that it drops the Wifi connection every now and again for no reason.
Making me wonder why i just got rid of my S2X yesterday for
Click to expand...
Click to collapse
Good grief, I was speaking in general terms. AT&T's MDS terms apply to any phone you buy from them.
I've had issues where voice has been lost and nothing can fix it except a reflash. Happens on my sII and the gnote. Luckily I'm able to fix it but I'd rather it never happen.
I don't see mention of it very often so I have to assume it's just me, but I have a terrible time with the radio getting borked out of the blue when I run any of the CM10 based ROMs. It will work fine for a few days, but out of nowhere, one I day I will turn the phone on and the radio will be messed up again. For example, this morning I installed the latest CM10.2 stable release. All was working fine... data, phone, etc. I got the ROM setup with all my apps and decided to make a backup. After doing the backup in recovery and rebooting, the radio no longer worked. So obviously I did something in recovery to screw it up.
Does anyone have any clue as to what I could be doing to cause this to happen so often? I want to run a CM Rom, but having to reset the radio once or twice a week is getting tiresome.
Thanks. For now i'll just reset the radio again and go back to stock and hope someone has some suggestions.
flyinjoe13 said:
I don't see mention of it very often so I have to assume it's just me, but I have a terrible time with the radio getting borked out of the blue when I run any of the CM10 based ROMs. It will work fine for a few days, but out of nowhere, one I day I will turn the phone on and the radio will be messed up again. For example, this morning I installed the latest CM10.2 stable release. All was working fine... data, phone, etc. I got the ROM setup with all my apps and decided to make a backup. After doing the backup in recovery and rebooting, the radio no longer worked. So obviously I did something in recovery to screw it up.
Does anyone have any clue as to what I could be doing to cause this to happen so often? I want to run a CM Rom, but having to reset the radio once or twice a week is getting tiresome.
Thanks. For now i'll just reset the radio again and go back to stock and hope someone has some suggestions.
Click to expand...
Click to collapse
There are some versions that lose connectivity/data connection but it's not a borked radio. Most of the time you can restore a working system by just turning off data for a minute and then turning it back on.
I am in the process of downloading the "stable" release from 2013-12-11, but my current nightly of 2013-12-10 hasn't had any hiccups.
I wish it was that simple for me. I can typically get data to work again when it goes out by doing what you said, but the ability to make phone calls never comes back unless I do the whole restore radio procedure. When I look at my phone info, it has my phone number listed as all zeros. It's a pain.
Thanks for responding...
flyinjoe13 said:
I wish it was that simple for me. I can typically get data to work again when it goes out by doing what you said, but the ability to make phone calls never comes back unless I do the whole restore radio procedure. When I look at my phone info, it has my phone number listed as all zeros. It's a pain.
Thanks for responding...
Click to expand...
Click to collapse
Ahhh, the 000-000-0000 number. Seriously, pull the battery. Don't shutdown, just pull it out, reseat, and turn on.
BTW, I installed the stable version yesterday and haven't had any problems. Flawless install, all of my apps still work and I didn't lose any data.
If that is all I needed to do, then I feel like a complete dummy. I guess I will reload the stable version again tomorrow and see what happens. Thanks for the info.
EDIT: I've come to the conclusion that i'm just not going to be able to run a CM10 based ROM. I have tried everything I can think of and/or read about on these forums and no matter what, I lose my ability to make calls using any of the CM10 ROMs. I know it's me because everyone else seems to run them fine, but I can't. It's a real bummer because I hate the stock ROM. I just don't know what to try anymore. I tried setting all the network settings as described in the directions (although I can't find the options for RIUU\SIM and NV mode anywhere). I triple wiped everything before flashing, I tried all the different CM10 ROMs and nightlys, I tried flashing with and without the sim card installed, etc. and nothing works. I get the 4G network, but my MEID ad phone number keep coming up as all zeros. It's very frustrating because the only reason I bought the phone off Ebay was to be able to run a CM rom.
I only have one thing left to try and I don't even know if it's worth it. Verizon sent me 2 4G sim cards by mistake so I have a spare sim card. I'm thinking of activating it and swapping out the old one in the hopes that it's a sim card issue. Although the current sim card works fine with the stock ROM so I doubt that's the problem but I don't know what else to try. Boy switching around to different ROMs sure was a lot easier with my old Dinc and Dinc2.
Have you tried running the latest RUU then flashing recovery and restoring? That seemed to solve a random reboot issue I was having, although I've never had radio issues. I have dirtyracun s-off, so it was pretty quick and easy.
flyinjoe13 said:
If that is all I needed to do, then I feel like a complete dummy. I guess I will reload the stable version again tomorrow and see what happens. Thanks for the info.
EDIT: I've come to the conclusion that i'm just not going to be able to run a CM10 based ROM. I have tried everything I can think of and/or read about on these forums and no matter what, I lose my ability to make calls using any of the CM10 ROMs. I know it's me because everyone else seems to run them fine, but I can't. It's a real bummer because I hate the stock ROM. I just don't know what to try anymore. I tried setting all the network settings as described in the directions (although I can't find the options for RIUU\SIM and NV mode anywhere). I triple wiped everything before flashing, I tried all the different CM10 ROMs and nightlys, I tried flashing with and without the sim card installed, etc. and nothing works. I get the 4G network, but my MEID ad phone number keep coming up as all zeros. It's very frustrating because the only reason I bought the phone off Ebay was to be able to run a CM rom.
I only have one thing left to try and I don't even know if it's worth it. Verizon sent me 2 4G sim cards by mistake so I have a spare sim card. I'm thinking of activating it and swapping out the old one in the hopes that it's a sim card issue. Although the current sim card works fine with the stock ROM so I doubt that's the problem but I don't know what else to try. Boy switching around to different ROMs sure was a lot easier with my old Dinc and Dinc2.
Click to expand...
Click to collapse
Do you have system select as automatic or home only? I have that issue when automatic is selected.
Sent from my ADR6425LVW using Tapatalk
I tried both automatic and home with same results. At some point i'll give it another try, but for now i'm going to stick with the Venom ROM because i'm getting tired of having to reset the radio. Some cold winter weekend day when i'm stuck in the house, i'll give it another shot.
I work with a guy that owns an ATT m7. He isnt too knowledgeable on rooting however he does flash his own roms and has some idea about it all. he told me he bricked his phone and thinks that after flashing so many roms he fried something with the radio. The phone does not receive a signal.
I took the phone home for him to fix. Just to test I flashed CM11 and just as he said radio was not working. It showed bars but if i tried to make a call it didnt work. I figured this would happen anyways so i carried on with obtaining s-off. I then flashed a 4.1.2 RUU. I put my sim card in (straightalk) and at first it didnt work. after a few minutes I looked again and vuala I had service. I added in my APN and everything seemed to go smooth. I did notice that periodically I would look at the phone and see it said "emergency calls only" but it quickly fixed itself (my s4 does the same thing so it could just be my area)
I used the phone all day and it seemed to be fine. Texts and calls worked perfectly. Feeling confident I then rooted and installed twrp. I backed up the stock rom and flashed CM.
No service.....
Anyone have any clue whats going on? I am currently RUUing again to see if it will work again and I am sure it will.
Im having trouble understanding this issue as I feel that if there was a mismatched radio then RUU fixed it. How would CM make this not work? Only thing I havent tried is a different rom (this was a nightly so i dont know if it has an issue) I just really don't feel like going through all the trouble again just to find out its not the ROM.
Hopefully someone has some insite.
Something is wrong with the software hes using if working on regular sense build and not cm,best aaking in the rom developers thread.
paradoxed said:
I work with a guy that owns an ATT m7. He isnt too knowledgeable on rooting however he does flash his own roms and has some idea about it all. he told me he bricked his phone and thinks that after flashing so many roms he fried something with the radio. The phone does not receive a signal.
I took the phone home for him to fix. Just to test I flashed CM11 and just as he said radio was not working. It showed bars but if i tried to make a call it didnt work. I figured this would happen anyways so i carried on with obtaining s-off. I then flashed a 4.1.2 RUU. I put my sim card in (straightalk) and at first it didnt work. after a few minutes I looked again and vuala I had service. I added in my APN and everything seemed to go smooth. I did notice that periodically I would look at the phone and see it said "emergency calls only" but it quickly fixed itself (my s4 does the same thing so it could just be my area)
I used the phone all day and it seemed to be fine. Texts and calls worked perfectly. Feeling confident I then rooted and installed twrp. I backed up the stock rom and flashed CM.
No service.....
Anyone have any clue whats going on? I am currently RUUing again to see if it will work again and I am sure it will.
Im having trouble understanding this issue as I feel that if there was a mismatched radio then RUU fixed it. How would CM make this not work? Only thing I havent tried is a different rom (this was a nightly so i dont know if it has an issue) I just really don't feel like going through all the trouble again just to find out its not the ROM.
Hopefully someone has some insite.
Click to expand...
Click to collapse
Yes but after 4.1.2 RUU it still cuts data on and off. Is it possible it's a bad radio or should we try a differentRUU?U
first id say get to an area where the radio reception is better, get an att card and not straight talk and test.this could very well be a hardware issue as well, but it seems more of a simcard issue/software issue than a hardware issue