Nexus S with broken (?) 3G/GSM - Nexus S Q&A, Help & Troubleshooting

Hi,
I'm having trouble with my Nexus S, and it might have started after installing Jelly Bean (though probably not). The phone is somtimes unable to connect to 3G, and sometimes unable to call/receive calls. More often not working than working, both of them. I tried factory resetting and I also tried my SIM card in another phone (and another SIM card in my phone), with the same result. Something must be wrong with my phone, the only question is if it is a software error or hardware error.
Anyone have any tips? Perhaps how to check if the radio hardware is working (some app perhaps?)? Any ideas on what else I might try? The phone has been working perfectly for more than a year, so it's really odd it suddenly has problems. Anyone had similar problems?
Thanks in advance!

1. Are your NS is rooted...??
2. did you try another JB Custom Rom..???
or
3. is it still working good when you downgrade to ICS or other ICS Custom ROM...???
Then, if thats way still have same result, its might be hardware problem.

novelys said:
1. Are your NS is rooted...??
2. did you try another JB Custom Rom..???
or
3. is it still working good when you downgrade to ICS or other ICS Custom ROM...???
Then, if thats way still have same result, its might be hardware problem.
Click to expand...
Click to collapse
I rooted it yesterday to be able to try custom roms (tried Cyanogenmod 9). Same problem. I then returned it to stock, which made it reflash everything, and still the same problem. I'm starting to believe it's a hardware error. Are there any diagnostic tools available to check the radio module?
Thanks for answering!

jeinor said:
I rooted it yesterday to be able to try custom roms (tried Cyanogenmod 9). Same problem. I then returned it to stock, which made it reflash everything, and still the same problem. I'm starting to believe it's a hardware error. Are there any diagnostic tools available to check the radio module?
Thanks for answering!
Click to expand...
Click to collapse
Well, just try a radio that's for your model, search for nexus s radios in xda you should be able to find a thread which has all The radios, and choose appropriately.
Xxx oops! accidentally beamed from my awesome NEXUS S! xxX

Maybe you have to get the correct access point name from your provider. If I do a clean flash I have to input it by hand as otherwise I cannot connect as well.
Sent from my Nexus S

kwibis said:
Maybe you have to get the correct access point name from your provider. If I do a clean flash I have to input it by hand as otherwise I cannot connect as well.
Sent from my Nexus S
Click to expand...
Click to collapse
That may explain the data connection but not the calls.
Xxx oops! accidentally beamed from my awesome NEXUS S! xxX

Billchen0014 said:
That may explain the data connection but not the calls.
Xxx oops! accidentally beamed from my awesome NEXUS S! xxX
Click to expand...
Click to collapse
True, I read the post to quickly!
Sent from my Nexus S

Thanks everyone for all tips, help and suggestions! I ended up replacing my Nexus S (a... questionable reseller bought it for $120, maybe to use for spare parts for other phones becuase I told him about the problems I was having) with a used Galaxy Nexus. Must have been a hardware error.
Sorry for the late reply/checkback!

Related

GSM stops working on Condemned CM 7.2

Hi, everyone. I'm using this ROM on HTC Incredible 2 (rooted and s-off):
http://forum.xda-developers.com/showthread.php?t=1435312
It's very good except one issue. GSM randomly (from my POV) mostly after rebooting stops working and the only thing I can do to make it work is to reflash my device. I attached my logs (maybe i had to do it in another way, but spoiler tag didn't work and i decided this one is the best). Also I will try to answer your questions that will help to find the problem as fast as possible.
Log-file:
https://www.evernote.com/shard/s14/sh/6af447c3-e911-4762-b3f2-db6ffd317600/d5b06f035b3c21ff39244809b13d75fa
Flash a new radio and see if it solves the problem
Here you go http://forum.xda-developers.com/showthread.php?t=1068236
AndroidAddiction said:
Flash a new radio and see if it solves the problem
Here you go http://forum.xda-developers.com/showthread.php?t=1068236
Click to expand...
Click to collapse
I tried one, didn't help, tried another one and now it's flashing about 20 mins and still in progress, should I worry?

[MIRO] Problem with the SIM card

To start of, I have been into rooting, installing custom ROMs and everything regarding it for quite a while but never ran into a problem like this. After Love posted his MIUI V5 I downloaded it and installed it. When it booted up I couldn`t unlock my SIM card due to a resolution error, you can`t see the "OK" nor "0" button. Then I switched to the Paranoid Android ROM ported and it booted up successfully. I went into options and changed settings regarding interface from "Phone mode" to "Phablet mode" as much as I remember it was the only thing I have done... Then when I had to reboot the phone, when it booted up, I inserted my PIN, but it showed something like "SIM card not inserted" and there was a popup which allowed me to reboot the phone. Now I can`t do anything about the problem. Tried switching back to the stock firmware and there I can unlock the SIM card without the "Reboot" prompt but still have no 3G access nor access to my contacts. I am asking you if you know anything about such a problem and if you have a fix for it. I also tried inserting a SIM from another phone, same problem- its not my SIM that is causing the problem. I think that it could do something with the radio, perhaps a component got corrupted somehow. Would really appreciate your help!
i also have the same problem on tipo caused from touchwiz rom, i am afraid only sony center are fixing this problem
I have spoken with my bro that has a Sony Erricsson Xperia X8 about the problem. He had the exactly same problem and he tried the same things as I did, but managed to fix the problem by relocking the bootloader and again unlocking it for further ROM installing. I will try and keep you updated.
Still nothing, nothing seems to help. Not even relocking the bootloader. Come on devs, can anyone at least try to assist us here? There seems to be something wrong with updating to another ROM. I would really appreciate some help here!
well yes i have also tried that locking and unlocking the BL, not just once about 10 times but still nothing, i tried almost everything and still have no clue,how to fix this
There is a fault in the ROMs, whichever caused this problem. I also saw the same thing happened to a Xperia J user with the MIUI v4.
Came across this today, I think some bring to light the issue:
http://forum.xda-developers.com/showthread.php?p=39845122
Nice find mate. So basically we need the stock radio files that we can flash in order for the SIM card to work again? Correct me if I am mistaken, in case I am not, can any of the devs look into it to try providing us with the radio file? I am not really keen in waiting a month until the phone gets repaired... Anyone?
I think that i have the same problem with my Xperia TIPO. After unlocking the bootloader and try some ROMs i found that i can´t do any calls.
I have try with a stock rom and another rom, but it doesn´t work. And the problem is not the sim card...
I am going to try relocking the bootloader, but it looks that the problem is going to stand there.
P.S: Sorry about my English
Well, it certainly seems you have the same problem. I would like to point out at this problem as it seems that everyone will have this problem when flashing a couple of ROMs...
Here is a topic regarding the same problem but with the exception that it is a problem the guy has on an Xperia S instead of Miro. It seems that the MIUI v4 3.1.11 ROM fixed the problem for another user(reply number 3 or 4 in the link). One of the repliers copy-pasted a probable fix but the download link for the provided radio modules are down. I sent a PM to Love if he can get his MIUI V4 3.1.11 download link back online. Will post for further updates!
Any luck with this? I have the same problem on my Tipo, and have had it for a while now. I outlined my problem here. I have had contact with devitrified, who has the same problem, and he has some more details here.
In any case, it is heartening to know there's more people with this problem.
i believe there are many people with this problem... i didnt figured out fix almost 2 months
STEELBAS said:
Any luck with this? I have the same problem on my Tipo, and have had it for a while now. I outlined my problem here. I have had contact with devitrified, who has the same problem, and he has some more details here.
In any case, it is heartening to know there's more people with this problem.
Click to expand...
Click to collapse
First of all thanks for posting something so everyone get to know that this problem exists, it seems like devs don`t really care or aren`t doing much to fix it. I hope that by time a lot of people will get this problem and that it will be fixed soon.
Is there any fix for this already?
It's really weird that no one said anything about this yet, since it's a problem that's being more and more widespread.
I have got a confirmation from the above poster that the problem stated in this topic started after flashing the Paranoid Android ROM for Sony Xperia Miro device. Can anyone else confirm the same thing?
WhiteHawkgrr said:
I have got a confirmation from the above poster that the problem stated in this topic started after flashing the Paranoid Android ROM for Sony Xperia Miro device. Can anyone else confirm the same thing?
Click to expand...
Click to collapse
mine problem became after installing touchwiz rom for tipo
This happened to me on Tipo (ST21i). I Flashed paranoid android fine, could a make call. Went looking around the settings and saw the page of DOOM, as i'm calling it, and there was no box checked, so I hit Phone mode and it asked whether it should reboot. I said yes, and then it broke. I thought it was the kernel so flashed pure CM10 kernel, which is what this port of P.A. was based on, and that didn't work, so I flashed MIUI port, but didn't do the kernel flashing, so it was on the CM10 Kernel. That didn't work and I couldn't enter my sim pin to try anyway, So I've flashed it again after flashing the kernel properly. Still didn't work. My grandad & mum are gonna be so angry. and it looks like I can't revert to stock, and Without stock it will cost a fortune to send it to sony. :crying::crying::crying::crying::crying: :crying::crying::crying::crying::crying::crying::crying: :crying: . Keep me posted if you find a download for the modules.
WhiteHawkgrr said:
I have got a confirmation from the above poster that the problem stated in this topic started after flashing the Paranoid Android ROM for Sony Xperia Miro device. Can anyone else confirm the same thing?
Click to expand...
Click to collapse
My problems came after flashing xperia z fire 5 ROM on xperia jlo.
I think my phone has water damage and thus not able to get warranty
Verstuurd vanaf mijn GT-P7510 met Tapatalk 4

[Q] Bizarre Sound Issue with New Phone??

Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Try flashing a stock UCMC1 ROM and doing a factory reset after your flash finished successfully and Odin rebooted your phone.
3 things you need:
1- skyrocket windows drivers from Samsung website
2-Odin
3-stock ucmc1 tar ball.
Refer to this page:
http://forum.xda-developers.com/showthread.php?t=2228247
Good luck.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
sjbonner said:
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Click to expand...
Click to collapse
You don't need to install a custom rom. Try updating to official jellybean with kies, if that doesn't work then try C64's advice above with either UCMC1 or UXUMA7 (uxuma7 is less bloated).
The issue you're having is odd and I haven't encountered it before..
lingowistico said:
You don't need to install a custom rom. Try updating to official jellybean with kies, if that doesn't work then try C64's advice above with either UCMC1 or UXUMA7 (uxuma7 is less bloated).
The issue you're having is odd and I haven't encountered it before..
Click to expand...
Click to collapse
Thanks for the suggestions, C64 and lingowistico. Upgrading to JB was going to be my next move, but I wanted to know if anybody had seen this behavior first. I don't want to mess with the phone too much in case the seller will take it back (I may be on a loser there). I'll try the official upgrade and let you know.
Custom ROM not necessary -- true, but I've been running CM on my bravo for a couple of years and can't go back to a stock ROM. I'll try the de-bloated version of the official JB release, but I'd like something I can have more control over.
Cheers...
sjbonner said:
Thanks for the suggestions, C64 and lingowistico. Upgrading to JB was going to be my next move, but I wanted to know if anybody had seen this behavior first. I don't want to mess with the phone too much in case the seller will take it back (I may be on a loser there). I'll try the official upgrade and let you know.
Custom ROM not necessary -- true, but I've been running CM on my bravo for a couple of years and can't go back to a stock ROM. I'll try the de-bloated version of the official JB release, but I'd like something I can have more control over.
Cheers...
Click to expand...
Click to collapse
when phone is doing odd things the best way to ts is a complete wipe, formatting/removing sdcards then returning to stock w/odin, but you could try the debloated rom 1st just to test it out, if its resolved then its prob not hw related, just make a backup of ur current rom if planning on returning it but since you install an official stock it should also be returnable
vincom said:
when phone is doing odd things the best way to ts is a complete wipe, formatting/removing sdcards then returning to stock w/odin, but you could try the debloated rom 1st just to test it out, if its resolved then its prob not hw related, just make a backup of ur current rom if planning on returning it but since you install an official stock it should also be returnable
Click to expand...
Click to collapse
Thanks Vincom. I don't have access to a Windows machine at the moment so haven't been able to try the upgrade.
One question -- how is it possible to make a backup of the current ROM without first rooting and installing a custom recovery? I suppose that I could install the custom ROM and create a nandroid backup. Then if I needed to restore I could restore the nandroid and reinstall the stock recovery. Is there an easier way?
Apologies, I just saw that you have information on reinstalling the stock recovery on your Newb Guide.
BTW, I want to say thanks for your work on the Newb Guide. One of the things that sold me on this phone was the support that it has here. Amazing to have all of the information on installing the custom recovery, rooting, etc. all in one place.
sjbonner said:
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Click to expand...
Click to collapse
I believe I had this kinda issue once before, it was when I flashed CM10 or something. No incoming sound, sound did not work whatsoever, but installed a different kernel solved the issue, or flashing a new different rom.
econan1214 said:
I believe I had this kinda issue once before, it was when I flashed CM10 or something. No incoming sound, sound did not work whatsoever, but installed a different kernel solved the issue, or flashing a new different rom.
Click to expand...
Click to collapse
UPDATE:
So, I managed to upgrade to the official JB 4.1.2 this evening. Had to do it twice.
First time the boot got stuck at the AT&T logo and PC wouldn't detect the device. I followed the directions in another post http://forum.xda-developers.com/showpost.php?p=34682377&postcount=9 to repeat the upgrade and the same thing happened.
On a whim I decided to try rebooting a few times to see what would happen -- and it worked! Sort of...
I'm repeatedly rebooting the phone and sometimes it will start without problem. However, most of the time it gets stuck when the AT&T logo appears exactly where it should play the start up sound, except it freezes and the sound never plays.
I'm guessing that wiping the data before had nothing to do with fixing the problem and I was simply getting lucky on reboot.
I realize that this is a hard question without having the phone in hand -- but does this sound like a hardware issue?
Thanks again to everyone for their help.
Boot into recovery and factory reset from there. That should clear up the boot loop issue.
theesotericone said:
Boot into recovery and factory reset from there. That should clear up the boot loop issue.
Click to expand...
Click to collapse
Just a quick note to let you know how this was resolved. I returned the phone to the seller who provided a full refund.
Thanks again to those who respondend.:highfive:

[Q] Crazy insane inverted touchscreen issue

crazy touchscreen problem
After flashing a ROM my touchscreen x axis seems to have inverted itself, so right is left on the screen.
This problem happens during the recovery screen also
I have tried changing recovery's,Kernals,flashed ROM's that I know work
I have even returned the phone back to stock nothing fixed it.
I have even went as far as removing the motherboard and installing one out of a working phone and guess what it does the same thing.
So i ask all you knowledgeable people WTF wold cause this and how can I fix it ?
these are the last two ROM's I was trying out when all this happened
they both ran without a problem I just didn't like them
MokeeOS 44.2 24/12/2013 [UNOFFICIAL],
UNOFFICIAL AOKP][4.4.2] [S4] [12/26/13]
I'm in no way blaming the ROM developers for this issue I just need a little help
Strange problem. I think you should flash firmware, it is worth to try i guess
Sent from my One S using xda app-developers app
mines actually doing the same, and from what i've been reading, i believe it has to do with your hboot version and ics not being compatible with it. try flashing your original ruu if you can. that's what i'm trying to do as we speak. if i ever get my problem figured out, i'll let you know if it works.
HomieOneKinobi said:
mines actually doing the same, and from what i've been reading, i believe it has to do with your hboot version and ics not being compatible with it. try flashing your original ruu if you can. that's what i'm trying to do as we speak. if i ever get my problem figured out, i'll let you know if it works.
Click to expand...
Click to collapse
This was my test phone I had flashed just about everything you can think of before I would install it on the phone I use every day
I guess my luck ran out
I ended up flashing the phone back to the original firmware and OS version using the factory RUU without a problem
If I try to install anything over 4.04 it goes right back to the same crap
I tried different firmware, kernels, roms with sense/ no sense doesn't matter.
the phone is being sold as I type this and I'm leaving my other two One S phones alone for now on
Nobody should have to go through this much bull for newer OS version so I'm saving for a Nexus 5
Thank you for the suggestion

[q] need help with no service and no mobile network available

I have no service and no cellular network problem on my N5, running dark rom 7.1.2 aosp, with franco kernel ( never had issues before ), newest radio and bootloader. This started happening when i got my new sim card from my provider and i got 4g signal in my area for the first time. I tried manually selecting radio by going in the hidden menu by entering *#*#4636#*#* and i got lte and full bars signal after selecting band 8 ( 1800 hz ) but only for a minute then it went back to empty triangle. Tried selecting 3g only in preffered network, tried manually selecting provider, tried toggling airplane mode on/off a bunch of times nothing works. Any suggestion would be highly appreciated, i love my N5 very much and i would hate to throw it in a drawer somewhere. Thanks in advance
Flash back to a stock ROM and test it worth your new new.
Does the sim work in another phone?
audit13 said:
Flash back to a stock ROM and test it worth your new new.
Does the sim work in another phone?
Click to expand...
Click to collapse
Yes the sim is working fine on any other phone. I will try gping back to stock thanks
EmilChurle23 said:
Yes the sim is working fine on any other phone. I will try gping back to stock thanks
Click to expand...
Click to collapse
Were you ever able to get this rectified? I have recently been having this problem as well. I have flashed back to ROMs I was previously using and flashed back to stock to no avail. My SIM card works in other devices as well. I really do not want to have to drop on a new phone, but I have tried every solution I have found online to no avail. I think it's fair to say that I am desperate right now.
edit: I found another thread on XDA that I'm looking into, I'll edit again if it works. I'm unsure how it took me so long to find that thread.
edit2: https://forum.xda-developers.com/go...getting-cdma-networks-to-nougat-roms-t3534679 is the thread that I found useful; I am now running Pure Nexus 7.1.2 with a full connection. Specifically, his second comment about installing 6.0.1 stock, backing up the efs, flashing the desired ROM, then restoring the efs is what ended up fixing it for me.
iamxaq said:
Were you ever able to get this rectified? I have recently been having this problem as well. I have flashed back to ROMs I was previously using and flashed back to stock to no avail. My SIM card works in other devices as well. I really do not want to have to drop on a new phone, but I have tried every solution I have found online to no avail. I think it's fair to say that I am desperate right now.
edit: I found another thread on XDA that I'm looking into, I'll edit again if it works. I'm unsure how it took me so long to find that thread.
edit2: https://forum.xda-developers.com/go...getting-cdma-networks-to-nougat-roms-t3534679 is the thread that I found useful; I am now running Pure Nexus 7.1.2 with a full connection. Specifically, his second comment about installing 6.0.1 stock, backing up the efs, flashing the desired ROM, then restoring the efs is what ended up fixing it for me.
Click to expand...
Click to collapse
Gonna try this fix now and I'll edit the result thanks for some hope
EmilChurle23 said:
Gonna try this fix now and I'll edit the result thanks for some hope
Click to expand...
Click to collapse
This morning it's not sticking with Pure Nexus, so I'll be trying DarkRom. I really don't want to use a CAF if I can avoid it, but it may become a necessity. Do people on T-Mobile have this problem?
iamxaq said:
This morning it's not sticking with Pure Nexus, so I'll be trying DarkRom. I really don't want to use a CAF if I can avoid it, but it may become a necessity. Do people on T-Mobile have this problem?
Click to expand...
Click to collapse
I wil try aosp by santosh m and see if it sticks
EmilChurle23 said:
I wil try aosp by santosh m and see if it sticks
Click to expand...
Click to collapse
So I've hit a point where I have 3G and nothing else. I can't yet get LTE to work. I'm using LineageOS CAF. How about yourself?
iamxaq said:
So I've hit a point where I have 3G and nothing else. I can't yet get LTE to work. I'm using LineageOS CAF. How about yourself?
Click to expand...
Click to collapse
No luck with aosp by santosh m and pure nexus 7.1.2 , can't even get it to connect. I guess my last hope is caf based i will try lineageos caf. All i need is the efs backup from stock? If i can get it to work with 3g i will be satisfied because i did some digging and found out that my network provider which is Vip MK has no lte support for nexus 5 d820 ( my model ) only 3g, but i can't even connect with 3g selected. I guess because this one is for US frequencies it will not work whatever i try but i will give lineageos caf a chance.
EmilChurle23 said:
No luck with aosp by santosh m and pure nexus 7.1.2 , can't even get it to connect. I guess my last hope is caf based i will try lineageos caf. All i need is the efs backup from stock? If i can get it to work with 3g i will be satisfied because i did some digging and found out that my network provider which is Vip MK has no lte support for nexus 5 d820 ( my model ) only 3g, but i can't even connect with 3g selected. I guess because this one is for US frequencies it will not work whatever i try but i will give lineageos caf a chance.
Click to expand...
Click to collapse
I was able to get 3G only to work on my Nexus 5 by reflashing the EFS from 6.0.1; I'm trying right now to see if I can install PureNexus 6.0.1 then dirty flash to PureNexus 7.1.2 with any success. Also, I might just switch to T-Mobile, but I have to wait until later this week for that.
Hi,
LTE band 8 is not in 1800 MHz but first of all you can check your N5 model - US model is D820 and is not supported for LTE on 1800 MHz (band 3). For 1800 Mhz band you need D821 model.
Regards,
iamxaq said:
Were you ever able to get this rectified? I have recently been having this problem as well. I have flashed back to ROMs I was previously using and flashed back to stock to no avail. My SIM card works in other devices as well. I really do not want to have to drop on a new phone, but I have tried every solution I have found online to no avail. I think it's fair to say that I am desperate right now.
edit: I found another thread on XDA that I'm looking into, I'll edit again if it works. I'm unsure how it took me so long to find that thread.
edit2: https://forum.xda-developers.com/go...getting-cdma-networks-to-nougat-roms-t3534679 is the thread that I found useful; I am now running Pure Nexus 7.1.2 with a full connection. Specifically, his second comment about installing 6.0.1 stock, backing up the efs, flashing the desired ROM, then restoring the efs is what ended up fixing it for me.
Click to expand...
Click to collapse
To clarify that:
You had the problem with not recognizing the sim or having no service at all. And you solved this by flashing the sstock 6.0.1 backing up the efs, flashing to Pure Nexus 7.1.2 and restoring the efs immediatley after flashing the rom (+kernel+root+etc)?
This solves this mysterious no sim/no service bug, which many (?) N5 owners experience? If this is true, I'd be really happy
Iced-Earth said:
To clarify that:
You had the problem with not recognizing the sim or having no service at all. And you solved this by flashing the sstock 6.0.1 backing up the efs, flashing to Pure Nexus 7.1.2 and restoring the efs immediatley after flashing the rom (+kernel+root+etc)?
This solves this mysterious no sim/no service bug, which many (?) N5 owners experience? If this is true, I'd be really happy
Click to expand...
Click to collapse
It didn't stick. After I lost it I was unable to get it back. I gave up and switched to T-Mobile, where it is no longer a problem. Apologies for not having more testing information. I was able to get solely 3G on multiple instances, but getting the elusive 4G was beyond me.
I've had this problem before in two nexus, one of them running latest stock and the other a customized ROM. I tried to flash a stock ROM image in both of them with no luck. I was pretty sure that the image I was flashing was the latest, so the radio & bootloader should be flashed to the latest versions. But it didn't worked.
Finally I found on a XDA thread where someone was posting only the latest bootloader & radio to flash. I did it with NRT (in Advanced Utilities) and it worked:
View attachment 4196236
I can't remember or find the thread, so I post the images here:
- Bootloader-hammerhead-hhz20h.img
- Radio-hammerhead-m8974a-2.0.50.2.30.img
I think I had to flash them twice because the first time it wasn't right, but there were 4 months since then and still no failure
ochoceros said:
I've had this problem before in two nexus, one of them running latest stock and the other a customized ROM. I tried to flash a stock ROM image in both of them with no luck. I was pretty sure that the image I was flashing was the latest, so the radio & bootloader should be flashed to the latest versions. But it didn't worked.
Finally I found on a XDA thread where someone was posting only the latest bootloader & radio to flash. I did it with NRT (in Advanced Utilities) and it worked:
View attachment 4196236
I can't remember or find the thread, so I post the images here:
- Bootloader-hammerhead-hhz20h.img
- Radio-hammerhead-m8974a-2.0.50.2.30.img
I think I had to flash them twice because the first time it wasn't right, but there were 4 months since then and still no failure
Click to expand...
Click to collapse
Thanks for your input. I'll check that when I have some time. This is really weird as it looks like a hardware problem but if you can fix it with this method it's clearly a software issue...
best regards

Categories

Resources