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.
Related
Hi,
Sometime today I lost my phone signal on my SG2. I'm not sure exactly at what moment as I first noticed that I had a couple of bars but no 3G when I tried to browse the web. So I restarted the phone but to no avail. Since then I've lost all bars and can't make any calls either.
The only thing I have done today "out of the ordinary" was to connect to the phone using Wifi File Explorer to transfer a file, which I tried to connect to without being on a wifi network by first trying the "Wifi Direct settings" in Settings, which didn't work, and then by tethering by Wifi which worked. Maybe some setting got stuck in the process, but I'm not sure since never checked if it worked right before and after.
If anyone has any idea what could be wrong please let me know, as I am literally without a phone!
I recommend downloading http://www.androidzoom.com/android_applications/communication/no-signal-alert-pro_fyyo.html this will definitely be of benefit to you if your suffering from signal problems, it has been of good use to me.
Check your IMEI is the correct one for your phone .If not restore your backed up EFS folder .
Or try backup data and factory reset as a first step.
jje
Thanks for the quick replies!
The IMEI does not correspond to the one I have written down, though I'm not 100% I what have on my note is the latest IMEI; but how could that change though by itself, if my note is correct??
Also, I just saw something very strange: I turned on my phone and had full bars (no 3G though), and right in front of my eyes all bars dropped, one by one, during the course of 5-6 seconds. Something is VERY off...
Regarding factory reset: my phone is rooted (thanks to XDA!) and I have Tit.backup: can I will my phone still be rooted if I do a factory reset?
Something went probably wrong when rooting it (not neccesarily any errors) and effed up tge EFS folder.
Try to flash back to stock ROM, it might work to restore your.folder.
Sent from my GT-I9100 using xda premium
UPDATE
bruflot said:
Something went probably wrong when rooting it (not neccesarily any errors) and effed up tge EFS folder.
Try to flash back to stock ROM, it might work to restore your.folder.
Click to expand...
Click to collapse
I should have been more clear on that, but I rooted the phone about a month ago and it has worked flawlessly since then, so it couldn't be that.
Anyway, I looked around a little and found this post:
http://androidforums.com/samsung-ga...connectivity-but-no-idea-why.html#post2722784
He seemed to have had the exact same problem that happened to me, so I decided to wait, and sure enough the connection reestablished itself about an hour ago and while I was watching for it, with the signal slowly creeping back up during a couple of minutes, and several hours after I lost it. Very odd.
This surely has to be an Android bug but that only shows up under certain and rare conditions.
To be sure I made a speed test and got 4.84 Mbps/up, 1.19 down, which I guess is fine; I never did one prior to this so I have nothing to compare to.
Again, appreciate the advice!
EDIT: For posterity, I should add that during these hours, even when I briefly apparently had a (non-3G) signal, I had a notification during all this time saying that I could only make emergency call.
I'm having the same issue. No Bars at all most of the time and when I have some, it never connects to 3G, G at most, and can't load any thing at all.
Very frustrating. I have been using Lite'ning rom 6.1 for a few months and had no problems at all until about a week ago.
I flashed back to a stock rom and still having the same issue.
I've also seen the bars drop down one by one in a 5 second window, bizarre!
Anyone find a fix for this? Or could the phone be faulty?
malicedix said:
I'm having the same issue. No Bars at all most of the time and when I have some, it never connects to 3G, G at most, and can't load any thing at all.
Very frustrating. I have been using Lite'ning rom 6.1 for a few months and had no problems at all until about a week ago.
I flashed back to a stock rom and still having the same issue.
I've also seen the bars drop down one by one in a 5 second window, bizarre!
Anyone find a fix for this? Or could the phone be faulty?
Click to expand...
Click to collapse
I was on Lite'ning about 3 weeks ago and actually completely lost signal several times. Reboots and hard resets solved the problem temporarily. I then flashed Batista FH 2.4 with ICS and things were great. I'm now on GingerMod. No issues.
I don't know how it could be kernel related though, especially if you are 100% stock again.
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
Hey guys!
The other day, I picked up an Atrix, mainly to use as an mp3 player so my S3's battery wouldn't drain as much during the day.
So, I took the steps any good android-user would go through. I unlocked the bootloader, rooted, and had Clockworkmod all set up.
This is within 30 minutes of having the phone. During the first while of tinkering with it, I noticed some strange things. There's really too many to list, but I'll try.
The phone at times is completely unresponsive. At seemingly random intervals, the Atrix would freeze, and randomly start selecting things.
For example, whilst using the keyboard, it would stream out random lines of text, like yyyyzzyyzyyzyyzyyyxyyxyyzy. Thinking that it was just a fluke with the rom , I carried on.
Often, the only time I can accurately and reliably select something is immediately after turning the screen off and back on again. And sometimes, that doesn't work either.
Also, there seems to be a 4-5 second latency from pressing the screen, to the device registering it.
Again, at random intervals, the image displayed on the screen begins to shake, and becomes unresponsive. I really wish I could record it happening.
There's also a host of other problems. The wifi hasn't ever worked, and the phone flat out refuses to flash some gapps packages.
So, my Atrix is basically a non-functioning, shivering, nightmare of a phone to work with. None of these issues have been caused by flashing different roms, and I have never touched any of the sbf files.
No matter what I try, it is just unusable. Every thing I have tried has failed, and this phone is out of warranty, so replacement is out of the question. So, is there anything I can do to fix this issue? I really, really need help.
Thanks in advance guys!!
I think we need to know what ROM (ROMS?) you are using. Is the bug recurrent? Have you thoroughly wiped cache, dalvik and did a factory reset before flashing? Are you sure you are flashing the proper Google apps for the ROM you are trying to use? And finally, are you sure your bootloader is unlocked? Does it say unlocked when booting and can you get to clockwork mod?
Those problems might be hardware, but I've experienced some of them myself from bad flashes, or corrupt pds partition, so software is far more likely. Give a little more info and I'll try to help.
Also, does Bluetooth work?
And what do you mean " refuses to flash"? What happens?
Sent from my Nexus 7 using Tapatalk 2
Newbleeto said:
I think we need to know what ROM (ROMS?) you are using. Is the bug recurrent? Have you thoroughly wiped cache, dalvik and did a factory reset before flashing? Are you sure you are flashing the proper Google apps for the ROM you are trying to use? And finally, are you sure your bootloader is unlocked? Does it say unlocked when booting and can you get to clockwork mod?
Those problems might be hardware, but I've experienced some of them myself from bad flashes, or corrupt pds partition, so software is far more likely. Give a little more info and I'll try to help.
Also, does Bluetooth work?
And what do you mean " refuses to flash"? What happens?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Hey! Well, I started on the stock ota 2.3.6
Yes, the bootloader is unlocked, cwm is the recovery, and I can get into it. Before flashing, I did wipe dalvik, cache, and factory reset.
The roms I've installed are in this order:
Stock ota 2.3.6, Cyanogenmod 7 2013/1/1 nightly, TopSmart's final release 1.3 rom, and AOKP 4.1.2 from October 17.
The roms flash just fine,and I always use the correct gapps. The problems have persisted through everything I have tried.
Bluetooth does not work, and neither does anything that requires a radio. (Data, calls, wifi, etc)
Is this a new or used atrix. if it was bought used perhaps has a hardware problem that the seller neglected to tell you about
affiatic said:
Is this a new or used atrix. if it was bought used perhaps has a hardware problem that the seller neglected to tell you about
Click to expand...
Click to collapse
I got it used, but it was still in the box, and even had the plastic screen that says "Don't text and drive" on it. The phone had literally never been booted up.
I think I figured out the problem, and will try to post a video of it.
The touchscreen just freaks out when being used. I found this out through the pointer location in the dev tools in Cyanogenmod 7
I'm on cm10 and random touches happen to me. I just lock and unlock the screen to fix. Only happens to me on cyanogen roms.
Sent using tapatalk
Could it be a foreign phone? that would explain the radio not working. The screen breaking and ghost touches sound like the leaked rom/kernel, was it happening with all the roms you installed?
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.
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