Related
The Problem/Symptoms: I've been running a version of last CM10.2 for the past year. On February 20th, I was able to send a single SMS and then subsequent texts failed. I could still receive SMS, send/receive MMS, send/receive calls and send/receive data. If I toggle airplane mode/reboot I can send another SMS and then subsequent sms are undeliverable.
What wont work: Flashing to CM11 does not change the issue.
Disabling Voice+ does not change the issue
Factory Reset does not change the issue
Workarounds: Toggle Airplane mode
Switching Mobile Network to CDMA only (not permanent)
Change your number to a different area code
Going back to a Touchwiz based ROM
The Solution
net-cat said:
Alright. I think I've refined my process and it results in having a newer radio as well as not having to ODIN things or do dd commands.
NOTE: This isn't fully tested. When I did this, my phone wasn't showing the issue. I did this after doing my original procedure, but the GPS stopped working after I updated the radio from VRALF2 to VRBMB1. You shouldn't need to do the original procedure for this to work, but I haven't tested that. At the very least, the original procedure still works and this one can be used afterward if you need the newer radio. (GSM support...)
Ideally, we'll want to get to a procedure that doesn't use ODIN or dd. Hopefully this is a step in that direction.
Requirements:
A rooted stock ROM of the VRUCML1/4.3 vintage. I used Scott's Stock Rooted Knox Free VRUCML1 - 4.3 - DeOdex - V2. (Thread here.)
VRBMB1 AIO Flash, available here. (Thread here.)
I'm going to assume you know how to boot into and use recovery.
NOTE: Do NOT let the stock ROM install any updates.
Starting with my CM11 M3 install, I did a nandroid backup. (Recovery is CWM Touch 6.0.4.5, but I doubt that matters.)
Flash the VRBMB1 AIO.
Wipe data and cache.
Flash the stock ROM.
Boot into the stock ROM.
The reprovisioning seems to happen as a part of ROM's initial boot up.
Send a few text messages to test. (I sent them to Twitter.)
Launch the Maps application, turn on your GPS and let it get a lock. If you don't, when you boot back into your ROM, you probably won't have working GPS.
This would be a good time to back up your IMEI if you haven't already done so.
Reboot into your recovery, wipe data/cache and restore your nandroid backup.
At this point, you'll be running your preferred ROM with a less archaic radio than my previous post.
DO NOT UPGRADE YOUR RADIO. The moment I upgraded my radio, the problem came back!
CM11 M3 will work just fine with the old radio. I've rebooted several times over the last few hours and it still works fine. (Time will tell if it's a long term fix or not.)
Click to expand...
Click to collapse
buffal0b1ll said:
I put a MB1 aoi zip in my dropbox for you. It's from invisblek.org which isn't working now for some reason https://www.dropbox.com/s/7b1aqspo40fxl00/VRBMB1.aio.zip
Click to expand...
Click to collapse
Notes: There are threads for the S4 with this identical problem. All updated information I have seen is listed above. If anyone knows more please post as I am going to keep this updated. If this does/doesn't work for you please post and let the community know. Feel free to hit the thanks button if it works for you.
This exact thing happened to me. I tried many fixes with no luck. After hours of hacking around in settings, I found a ROM of verizon's 4.3 OTA update and flashed that through ODIN. My texts are working just fine again. Kind of a cheap method of fixing my problem. I wish I could have taken more time to find a fix, but I needed to be able to communicate with people that day.
Stock 4.3 is kind of lame:
-4.3 is killing my battery faster than ever. CM11 had me going for days without charging and now I've needed to charge everyday.
-Stock 4.3 is laggier/slower than CM11. It tends to stutter for me.
-4.3 came with a new boot loader which no developers have exploited to install custom ROMs yet. This leaves you stuck with Verizon bloat. I hate all these damn apps. Going to try to safe root & see if I can't do some cleanup work.
Enough ranting. Just wanted to let you know you are not alone with this problem. Hopefully someone will figure it out. Missing my cyanogen mod already
It seems this problem has happened on other phones also running Cyanogenmod. I found this thread http://forum.xda-developers.com/showthread.php?t=2654822
It looks like the symptoms have all showed up at the same time approximately. (February 19th, 2014). Still looking for a better answer than going back to stock TW...
Edit: And another thread http://forum.xda-developers.com/showthread.php?t=2659280 This one suggests its all AOSP roms. But it seems many people are unaffected... I don't understand why/how.
edit2: and another thread http://forum.xda-developers.com/showthread.php?p=50627899
Just looking for more info
Sent from my SCH-I535 using Tapatalk
Dex954 said:
Just looking for more info
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
SO this is the current status that I know.
The problem happens for everyone with a 570/717 area codes + on verizon + running Cyanogenmod (possibly any AOSP) + while connected to LTE which started on Feb 20th (the day before KitKat came out offically).
Current Workarounds:
Switch to TouchWiz based Roms
Switch your radios to be CDMA only
Call verizon and switch your number to a different area code
I know the workarounds all suck but that all I know for now. Switching SIM cards won't work. If I anyone knows anything more please feel free to let me know.
I'm 717
Sent from my SCH-I535 using Tapatalk
I have still be unable to find a solution for this issue. I think I have to give up on CM and go back to a TW based. If I hear anything new I'll update the post but I don't have the time to be wasting on my phone at the moment. If someone finds or hears of a fix or if it magically goes away as it started, please post it.
And spread the word if there are any other ROMs that this is occurring on. It seems the pool of those affected is just too small.
I have already had to give up. Been running slows tw. I take it Verizon didn't get back to you?
Sent from my SCH-I535 using Tapatalk
Here is my thread guys. Same issue. I am gonna get on the fog horn with some Verizon buddies I have http://forum.xda-developers.com/showthread.php?t=2662658
DreamFX said:
Here is my thread guys. Same issue. I am gonna get on the fog horn with some Verizon buddies I have http://forum.xda-developers.com/showthread.php?t=2662658
Click to expand...
Click to collapse
Godspeed my friend.
Anyone try aosp to see if fixed yet?
Nope. Still having issues. Tried gummy and cm. TW based roms are fine. In 717.
capt730 said:
Nope. Still having issues. Tried gummy and cm. TW based roms are fine. In 717.
Click to expand...
Click to collapse
I try every other day. 717 for me. Remaining hopeful it's fixed... One day...
What gapps are you using? I have been using the PA 0Day gapps. Going to try the gapps package from invisblek and see if that makes a difference.
Sent from my GT-N5110 using XDA Premium 4 mobile app
capt730 said:
What gapps are you using? I have been using the PA 0Day gapps. Going to try the gapps package from invisblek and see if that makes a difference.
Sent from my GT-N5110 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It won't. It isn't software dependent. People who had already flashed builds prior to the 20th magically had issues starting on that date, so it isn't a problem with new builds, and it only happens to those in the 717-570 areas so it isn't a problem with AOSP code. It has to be a Verizon network issue, I just have no idea how.
Sent from my SCH-I535 using XDA Premium 4 mobile app
I have run TW base roms almost 100% of the time. Prior to the 20th, I had flashed cm11 3 or 4 times to see if camera worked and was never on it more than a day. I also had issues where music in my sd card wasn't being found but it was fine on TW. Could it be the unified build causing an issue? I have no issues on Clean Rom 8, wicked sensations or old and slows stock based roms.
*Edit* I have installed Gummy and CM 11 with PA Mini Modular apps and the CM Gapps from Invisiblek, let it set up. I then shut it down, removed battery and sim and then put everything back in and still the same issue. 1st text message goes through, then the rest after that just fail. I tried regular message app, Hangouts and Verizon messaging. All same results. I go back to my CR8 backup and all is fine. It's bizarre because everything else seems to be working fine and is very fast & smooth.
capt730 said:
I have run TW base roms almost 100% of the time. Prior to the 20th, I had flashed cm11 3 or 4 times to see if camera worked and was never on it more than a day. I also had issues where music in my sd card wasn't being found but it was fine on TW. Could it be the unified build causing an issue? I have no issues on Clean Rom 8, wicked sensations or old and slows stock based roms.
*Edit* I have installed Gummy and CM 11 with PA Mini Modular apps and the CM Gapps from Invisiblek, let it set up. I then shut it down, removed battery and sim and then put everything back in and still the same issue. 1st text message goes through, then the rest after that just fail. I tried regular message app, Hangouts and Verizon messaging. All same results. I go back to my CR8 backup and all is fine. It's bizarre because everything else seems to be working fine and is very fast & smooth.
Click to expand...
Click to collapse
It can't be an issue with the unified builds because going back and flashing an older build yields the same results. If you're willing to make the trade-off, you can set your phone to CDMA only. Texts will send, but you'll have no 3G or 4G.
I'm ok with using CR8, Beans or other stock roms. Can't see paying for LTE and not using it lol. Was curious to see how aosp has been coming along and sms was really the only issue I was having.
Obaterista93 said:
It can't be an issue with the unified builds because going back and flashing an older build yields the same results. If you're willing to make the trade-off, you can set your phone to CDMA only. Texts will send, but you'll have no 3G or 4G.
Click to expand...
Click to collapse
I was using masta's 10.2 build for over 6 months without even thinking about flashing new builds. The 20th is when the problem started for me. Upgrading to CM11 didn't change it. I just installed Hyperdrive and everything is back to normal.
I wish I could go back to CM but it just doesn't work in this area. And I don't know what I can do about it,
Whisk_33 said:
I was using masta's 10.2 build for over 6 months without even thinking about flashing new builds. The 20th is when the problem started for me. Upgrading to CM11 didn't change it. I just installed Hyperdrive and everything is back to normal.
I wish I could go back to CM but it just doesn't work in this area. And I don't know what I can do about it,
Click to expand...
Click to collapse
Basically. I've talked to a few friends who have worked for carriers and stuff, and everyone is stumped as to how something like this can even happen. Luckily I'm pretty much always in WiFi so I can survive on CDMA only.
I'm having major issues with reception in my house, and only on my 16 GB OnePlus One. When switching to my Windows Lumia 635 or my HTC One X+, I get fine reception-- but as soon as my SIM's in my OnePlus One, I start receiving texts extremely late, which is a problem with apps like WhatsApp which require text verification.
I'm running stock ROM. That's CM 12.0-YNG1TAS17L. Stock kernel, unrooted even (ever since I flashed it back to stock to try and fix the reception issues). I've also tried OxygenOS, BlissPop, and Exodus and none of those have fixed my reception woes. Thanks in advance!
toohsieh said:
I'm having major issues with reception in my house, and only on my 16 GB OnePlus One. When switching to my Windows Lumia 635 or my HTC One X+, I get fine reception-- but as soon as my SIM's in my OnePlus One, I start receiving texts extremely late, which is a problem with apps like WhatsApp which require text verification.
I'm running stock ROM. That's CM 12.0-YNG1TAS17L. Stock kernel, unrooted even (ever since I flashed it back to stock to try and fix the reception issues). I've also tried OxygenOS, BlissPop, and Exodus and none of those have fixed my reception woes. Thanks in advance!
Click to expand...
Click to collapse
You ever get this fixed? I recently took a trip to San Diego and noticed the poor reception there.. a friend of mine, who's also on T-Mobile, has excellent reception with his new HTC One. I, on the other hand, had horrible reception; sometimes none at all. I've manually flashed the latest radio and still no dice.
silentcovenant said:
You ever get this fixed? I recently took a trip to San Diego and noticed the poor reception there.. a friend of mine, who's also on T-Mobile, has excellent reception with his new HTC One. I, on the other hand, had horrible reception; sometimes none at all. I've manually flashed the latest radio and still no dice.
Click to expand...
Click to collapse
Yeah-- here's what I did:
1. Flash stock ROM.
2. Update to latest stock ROM version via the CM updater.
3. Install TWRP again if needed.
4. Followed steps here: http://forum.xda-developers.com/oneplus-one/help/fix-cm12-calls-sms-mms-deep-sleep-t3103193
I flashed both the modem and proximity packages after updating to latest stock, and I reflash every time there's a new stock update. Hopefully this works for you!
toohsieh said:
Yeah-- here's what I did:
1. Flash stock ROM.
2. Update to latest stock ROM version via the CM updater.
3. Install TWRP again if needed.
4. Followed steps here: http://forum.xda-developers.com/oneplus-one/help/fix-cm12-calls-sms-mms-deep-sleep-t3103193
I flashed both the modem and proximity packages after updating to latest stock, and I reflash every time there's a new stock update. Hopefully this works for you!
Click to expand...
Click to collapse
Wait, isn't the stock from still on 4.4 or something? How does that fix 5.0+ issues? Anyways, I'll give it a try, can't hurt, right? Thanks, I'll let you know how it goes.
silentcovenant said:
Wait, isn't the stock from still on 4.4 or something? How does that fix 5.0+ issues? Anyways, I'll give it a try, can't hurt, right? Thanks, I'll let you know how it goes.
Click to expand...
Click to collapse
Well, stock is 4.4, but when you use the stock CM updater you'll be brought to CM12, 5.0.2. You don't have to stay on 4.4
silentcovenant said:
Wait, isn't the stock from still on 4.4 or something? How does that fix 5.0+ issues? Anyways, I'll give it a try, can't hurt, right? Thanks, I'll let you know how it goes.
Click to expand...
Click to collapse
(Though presumably you could just try flashing modem and prox packages without flashing back to stock-- I just wanted to be sure as possible that nothing would interfere with the packages.)
toohsieh said:
(Though presumably you could just try flashing modem and prox packages without flashing back to stock-- I just wanted to be sure as possible that nothing would interfere with the packages.)
Click to expand...
Click to collapse
Flashed an old backup of stock, baseband stayed the same. Also, when I check for ROM updates, it says there are none. Currently on 4.4.4
silentcovenant said:
Flashed an old backup of stock, baseband stayed the same. Also, when I check for ROM updates, it says there are none. Currently on 4.4.4
Click to expand...
Click to collapse
That's really odd. You're on XNPH05Q? Or another one?
I used http://www.droidviews.com/restore-oneplus-one-stock/ to restore to stock instead of using a backup.
toohsieh said:
That's really odd. You're on XNPH05Q? Or another one?
I used http://www.droidviews.com/restore-oneplus-one-stock/ to restore to stock instead of using a backup.
Click to expand...
Click to collapse
The stock version they gave me was: XNF9XBS28K
silentcovenant said:
The stock version they gave me was: XNF9XBS28K
Click to expand...
Click to collapse
I can't say I've ever seen that version before but it looks like someone else had the same issue: https://forums.oneplus.net/threads/xnf9xbs28k-ota-updates.315441/
Hi there,
Everything was working just fine, but since I switched to a new carrier I can't get the network back as soon as my OP looses it (subway for example). I have 4G as my favorite internet mode and my APNs are good.
Only a full reboot fixes it, not even a soft one. What can I do?
I use the lastest CM 12.1 S rom (YOG4PAS3JL)
Maybe I should try to flash Oxygen's modem? http://forum.xda-developers.com/one...dio-updated-modem-radio-files-oxygen-t3072516
It seems many users are affected by the problem but I didn't find a real solution, hence my post.
Thank you!
After a long investigation, it seems that the OPO is having trouble switching for and from 4G. I solved it using 3G as my preferred network, but I'd have loved using 4G
reinstall the system... u can google fastboot images for opo... flash them through CMD
I've tried 3 ROMS and at least 4 modems so I think I've tried eveything that's available atm
I have had the same problem for some time now. But no reliable solutions found. Have tried various versions of ROM and Radio. Currently using 44S and CM 12.1 S (YOG4PAS3JL).
Lamner said:
Hi there,
Everything was working just fine, but since I switched to a new carrier I can't get the network back as soon as my OP looses it (subway for example). I have 4G as my favorite internet mode and my APNs are good.
Only a full reboot fixes it, not even a soft one. What can I do?
I use the lastest CM 12.1 S rom (YOG4PAS3JL)
Maybe I should try to flash Oxygen's modem? http://forum.xda-developers.com/one...dio-updated-modem-radio-files-oxygen-t3072516
It seems many users are affected by the problem but I didn't find a real solution, hence my post.
Thank you!
Click to expand...
Click to collapse
kingalpha said:
I have had the same problem for some time now. But no reliable solutions found. Have tried various versions of ROM and Radio. Currently using 44S and CM 12.1 S (YOG4PAS3JL).
Click to expand...
Click to collapse
For how long have you been using that? Did that fix the problem?
This is very annoying!!!!
xupi said:
For how long have you been using that? Did that fix the problem?
This is very annoying!!!!
Click to expand...
Click to collapse
Didn't fix the problem. Finally reverted back to Oxygen OS. Complete reinstall, including bootloader, storage, everything. Got it done at OPO service centre. Much better reception now.
Hey guys, i needed some help! I have flashed lineage OS several times today. Not just lineage, i flashed aicp rom too, forgetting that its built on lineage. Whenever I flash it, I don't get cellular network. It shows full signal, but once in maybe 2-3hrs I get the signal for 5mins or so max. Does anybody know what the problem is? I asked several guys and also googled it, but the only problems I have seen or heard is having trouble with the phone app crashing and people installing Zip files to rectify that. Any sort of help would be appreciated.
PS: I have checked whether my sim card is sitting perfectly and it is. If I flash cm14, cm14.1 or aicp 12.1 unofficial which was built on cm14, I can receive calls and texts too.
Thanks
abhirammk said:
Hey guys, i needed some help! I have flashed lineage OS several times today. Not just lineage, i flashed aicp rom too, forgetting that its built on lineage. Whenever I flash it, I don't get cellular network. It shows full signal, but once in maybe 2-3hrs I get the signal for 5mins or so max. Does anybody know what the problem is? I asked several guys and also googled it, but the only problems I have seen or heard is having trouble with the phone app crashing and people installing Zip files to rectify that. Any sort of help would be appreciated.
PS: I have checked whether my sim card is sitting perfectly and it is. If I flash cm14, cm14.1 or aicp 12.1 unofficial which was built on cm14, I can receive calls and texts too.
Thanks
Click to expand...
Click to collapse
flash another modem.
Mr.Ak said:
flash another modem.
Click to expand...
Click to collapse
Thank you. But the error was in the sim card xd
It would detect mine but I do not know why it never received signal. But it worked for other sims. So theres probably a fault with my sim and I'm getting it exchanged. Thanks!
abhirammk said:
Thank you. But the error was in the sim card xd
It would detect mine but I do not know why it never received signal. But it worked for other sims. So theres probably a fault with my sim and I'm getting it exchanged. Thanks!
Click to expand...
Click to collapse
Jio?
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