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.
Related
Hi
Recently my S2 just stopped reading my SIM when I was going to call someone. Since then it has refused to read my SIM, or any other SIM for that matter.
To fix this problem I've tried resetting the phone to factory settings (in 3 different ways ( hard-reset.com/samsung-i9100-galaxy-s2-hard-reset.html )) with no luck.
I've also tried installing alternative ROM's, but with the same result.
The phone was already rooted with an insecure kernel when this happened, so warranty is long gone.
Though, one thing I did realize was that even though I did hard-reset the phone several times, some of the settings on the phone remained untouched, like my locking pattern and a few other settings. Does this mean that hard-resetting the phone isn't really an actual hard-reset? If that's so, is there any way to properly 100% reset the phone?
In short; I'm running out of options on how to fix this. I refuse to believe it's hardware related, just because I'm stubborn like that.
Any help would be greatly appreciated (really).
Habitats said:
Hi
Recently my S2 just stopped reading my SIM when I was going to call someone. Since then it has refused to read my SIM, or any other SIM for that matter.
To fix this problem I've tried resetting the phone to factory settings (in 3 different ways ( hard-reset.com/samsung-i9100-galaxy-s2-hard-reset.html )) with no luck.
I've also tried installing alternative ROM's, but with the same result.
The phone was already rooted with an insecure kernel when this happened, so warranty is long gone.
Though, one thing I did realize was that even though I did hard-reset the phone several times, some of the settings on the phone remained untouched, like my locking pattern and a few other settings. Does this mean that hard-resetting the phone isn't really an actual hard-reset? If that's so, is there any way to properly 100% reset the phone?
In short; I'm running out of options on how to fix this. I refuse to believe it's hardware related, just because I'm stubborn like that.
Any help would be greatly appreciated (really).
Click to expand...
Click to collapse
You can refuse to believe in gravity too, but falling from high distances will still hurt.
If you tried more than one SIM in the phone and none work, but those same SIMs work in other phones, than more than likely, it is hardware related.
Did you check you imei?
078gregory brings up a good point. So if it's not missing IMEI info, THEN it's likely hardware.
Isn't it funny how everything suddenly works itself out once you cry out for help?
Today I've been trying around 10 different ROM's on the phone. Custom and stock. As one last attempt I gave a random ICS 4.0.3 march ROM a last try, and guess what. I got the SIM prompt. I can not believe it. So yeah, it's working now. I have no idea what caused it, but I believe the phone was stuck in flight mode somehow, and just needed an extra push to get out.
Either way, it's working like a charm now. Thanks for the replies though.
Habitats said:
Isn't it funny how everything suddenly works itself out once you cry out for help?
Today I've been trying around 10 different ROM's on the phone. Custom and stock. As one last attempt I gave a random ICS 4.0.3 march ROM a last try, and guess what. I got the SIM prompt. I can not believe it. So yeah, it's working now. I have no idea what caused it, but I believe the phone was stuck in flight mode somehow, and just needed an extra push to get out.
Either way, it's working like a charm now. Thanks for the replies though.
Click to expand...
Click to collapse
Don,t forget to press THANKS button on ctomgee
Hi people. I have the same problem Habitats decribes. Mi s2 is stuck in flightmode and cant get out! i have reset the phone in every kind of way but no succes. Now i read here on this forum that flashing my phone to ICS 4.0.3 can help solve the problem. I'm on 2.3.6 now. This flightmode thing happened al over sudden. I have done nothing strange with the phone. Its not rooted either. I was planning to go to a samsung servicepoint and let them check whats wrong. But now i read this thread and see that i can relate to this problem of Habitats. I think a also will try to flash ICS 4.0.3 and watch what happens. But theres another problem. KIES don't recognize my phone anymore so what can i do? Can someone please help me out? Thanks in advance
I'm having the exact same problem, could you please tell me which rom worked for you Habitats? Thanks in advance!
Update:Last tuesday i went to the vodafone store were they have a samsung service department also. I explained my problem to them but they don't seem to recognize the problem. Although i read that many people here at xda's and over the internet have similar issues with this phone.Strange! So they sent it to the repair centre. Yesterday i could see in the track and trace menu of the repair centre that my fone was ready and send back to the vodafone store. Status: Boardswap. So they swapped the whole board! Didn't know that the problem was that serious! So i hope i can pickup my galaxy s2 soon this coming week!! I can't wait!I'm on my old HTC Touch HD now. Its ok with the windows but on Android....Arggghh!! Whatsapp is a pain and more. Its so laggy!. I will give an update soon again!
After searching and trying to fix this for a few weeks, I'm finally reaching out for help, I really don't know what else to do.
My vibrate function seems to be completely dead.
I rooted the phone a while back when I first got it and everything was perfect on the first ROM I was using. I then flashed to a different ROM and lost haptic feedback but kept the other vibrate functionality (alarms, texts, etc.) Sorry I don't have specifics on the ROMs but I know the issues may be have been due to the i9100 porting stuff causing haptic issues
My vibrate functionality kind of slowly stopped working.. Sometimes when the headphones were in it would work fine, then I'd take them out it would stop.. and Vice versa.
It does SOUND like it's a hardware error.. But that seems a little silly since there have been multiple issues floating around w/ ROMs and haptic/vibrate problems.
Before I take any further action, anyone have any suggestions? I'm thinking to re-stock the phone entirely (unroot, stock kernel, stock rom) and see if that does it.. I'd rather not send it in to get replaced but I guess that would be an easy option if I can't fix it via software.
I googled vibration not working galaxy s2.
Found this but I didn't watch it as I am not on wifi.
http://www.youtube.com/watch?v=3JA3PXNYjJM
gerbs said:
After searching and trying to fix this for a few weeks, I'm finally reaching out for help, I really don't know what else to do.
My vibrate function seems to be completely dead.
I rooted the phone a while back when I first got it and everything was perfect on the first ROM I was using. I then flashed to a different ROM and lost haptic feedback but kept the other vibrate functionality (alarms, texts, etc.) Sorry I don't have specifics on the ROMs but I know the issues may be have been due to the i9100 porting stuff causing haptic issues
My vibrate functionality kind of slowly stopped working.. Sometimes when the headphones were in it would work fine, then I'd take them out it would stop.. and Vice versa.
It does SOUND like it's a hardware error.. But that seems a little silly since there have been multiple issues floating around w/ ROMs and haptic/vibrate problems.
Before I take any further action, anyone have any suggestions? I'm thinking to re-stock the phone entirely (unroot, stock kernel, stock rom) and see if that does it.. I'd rather not send it in to get replaced but I guess that would be an easy option if I can't fix it via software.
Click to expand...
Click to collapse
Same happened to the last phone I had, the HTC Aria. I ended up just taking it to an AT&T store for replacement. I even tried going back to stock. Nothing worked on mine.
Sent from my GT-I9100 using XDA
jcordova23 said:
Same happened to the last phone I had, the HTC Aria. I ended up just taking it to an AT&T store for replacement. I even tried going back to stock. Nothing worked on mine.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Yeah, already called att for a replacement and its on the way. Finally decided to give up after getting it back to 100% stock (kernel rom bl etc).
I literally tried everything. But in the end it makes sense that it is a hw problem since so many others have run into it too. Poop.
i watched the video you showed. i started to mess around with my settings while i inserted my headphones on. Somehow, everything is fixed but the vibration is not as strong as before.
Furthermore, my aux does not work with this phone sometimes. It would need to be connected a certain in order for it to work.
I probably dropped my phone while I was working out while i have my headphones on. The connector probably got messed up in the process.
I might need to send my phone in for a replacement. Since i'm not under warrenty, i might send my phone to a lab. I'm pretty sure they can do something about it.
iichrisphamii said:
I might need to send my phone in for a replacement.
Click to expand...
Click to collapse
The vibrator turned out to be a hardware issue for me as expected, fyi.
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.
Well, I was running rootbox for i717 and everything was working fine for a month, Then suddenly out of no where for no reason at all my phone got super laggy, apps started crashing, and my sound stopped working, I mean completely not through the headset not through the speaker nothing!!! So my first thought was something was wrong with the rom, so I tried a factory data reset, I tried re-installing it, I tried 3 other roms, cynagenmod10, Jellybeer and xylon, Finally I did the farthest restore to my stock gingerbread rom, and still the problem priests, in fact its getting worse, I don't know what to do at this point I am completely out of ideas. Could this be a hardware issue? its the only conclusion I can come up with, but its still strange, because if it was just my speaker I would understand hardware issue, but my speaker, my earpiece, my headset, and Apps crashing, super Lag, I can barley even get my keyboard to pop-up then it dispersers. What is going on!!! Please help me oh great devs.
Well, assuming you did complete wipes and factory resets as you flashed each Rom, I'd say you eliminated software.
Did you leave the phone somewhere that let it overheat? Or used a non-OEM charger? Or overclocked it?
majicmazo said:
Well, I was running rootbox for i717 and everything was working fine for a month, Then suddenly out of no where for no reason at all my phone got super laggy, apps started crashing, and my sound stopped working, I mean completely not through the headset not through the speaker nothing!!! So my first thought was something was wrong with the rom, so I tried a factory data reset, I tried re-installing it, I tried 3 other roms, cynagenmod10, Jellybeer and xylon, Finally I did the farthest restore to my stock gingerbread rom, and still the problem priests, in fact its getting worse, I don't know what to do at this point I am completely out of ideas. Could this be a hardware issue? its the only conclusion I can come up with, but its still strange, because if it was just my speaker I would understand hardware issue, but my speaker, my earpiece, my headset, and Apps crashing, super Lag, I can barley even get my keyboard to pop-up then it dispersers. What is going on!!! Please help me oh great devs.
Click to expand...
Click to collapse
Your best bet is to go to RootzWiki where the dev work is done for those ROMs .. And post this in the threads... I myself am running root box .... Go there .. XDA doesn't support these roms anymore so that's where you need to go
Sent from my SGH-I717 using xda app-developers app
did you do the 3 wipe procedures when installing the firmware?
there is more than just 3 wipes you can do .....depending on a dirty flash or a clean install or a complete wipe and clean install...you also have android secure ...internal ....external
Sorry for the delayed response
Well, yes I did always do the 3 wipe method, I did the complete wipe as well, and I saw no need to talk to the rootbox dev, (whos name im terrified of mentioning on xda in fear of getting banned lol) because I tried other roms from other devs and the problem still persisted, then I went to the stock rom and still had the problem, then I unrooted the phone and did one last complete wipe, re-installed the stock gingerbread rom, and still had the issue, so finally i gave up and got in contact with the guy on ebay who sold me the phone, and luckily he was more then willing to give me a replacement, then I got the note2 and was (still am) busy trying to sell this one, so I really just forgot I had this post up until I logged in right now so that is why the long delay, Thanks for your help guys but in the end im still pretty sure it was a hardware issue, but since Its back in the hands of the seller and I have new one we will never know for sure
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