Related
I just installed UCLD2 Smooth ICE 5.0 followed his instructions and I like the Rom, but I have an issue. My home button and search button do not work at all. I've gone into the settings to see if there is anything to change what the buttons do, but I've found nothing.
Does anyone know what could be causing this? Or what I can do to fix it.
I had the same issue with flashing sky is. I did a nandroid recovery, then reflashed the whole thing and allowed the system to settle longer than the suggested 5 minutes. It works great now. Buttons are fine.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Well as it turns out that was only one of a myriad of problems, I may or may not have permanantly bricked my phone. I let the system settle, but now the screen isn't very responsive when I try to do anything on it. I also tried returning to stock, and have had the same problems.
I don't have any idea what happened, but it seems to be like a kernel problem.
CrazyLineman777 said:
Well as it turns out that was only one of a myriad of problems, I may or may not have permanantly bricked my phone. I let the system settle, but now the screen isn't very responsive when I try to do anything on it. I also tried returning to stock, and have had the same problems.
I don't have any idea what happened, but it seems to be like a kernel problem.
Click to expand...
Click to collapse
If it turns on then its far from bricked. What was your method of returning to stock?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
There's been way too much of this nonsense recently. You don't even know what a brick is. All the new guys need to stop flashing everything they can get their hands on. Stop and read before you do this stuff to your phone. I read for almost a whole month, everything I could find before doing anything. Before I even flashed anything, I had everything needed to fix and return to stock, and made sure I completely understood what I was doing. Read and understand before you break stuff so you can fix it!
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I...I....I give up Congrats noobs not just op you have killed my faith in humanity you all have won and destroyed my spirits
Sent from my SGH-T989 using Tapatalk 2
When most of us first installed the leak the fix was to install it again with the 1 click or factory reset.... Are you coming from stock gb or stock ics leak?
Edit: nrm and dx you guys crack me up
CM9 Skyrocket
I didn't flash whatever I could get my hands on thank you. I flashed NexusMod 4.3 Nexus UI first about a week and a half ago. Then I wanted to try and get something a little more like stock, but still ICS so after READING ALL THE INFORMATION on the post for ICS Smoothie v2 I flashed it after wiping data, cache, and dalvik and following the instructions regarding an ICS radio which I had not followed previously with Nexus Mod when I flashed it. Then the problems started.
There is no lockscreen even when the phone decides to work. When I start up the phone. Process.google.acore force closes as does process.google.gapps
Also when I unlock the phone the screen will respond to 1 maybe 2 swipes to find a homescreen then it'll hang.
I used ODIN to return to stock following the instructions on the Stickied post about doing so in the Development section. Also I'm sorry if some of what I said comes off rude I've just been trying to fix this for about 4 days with no luck and I really need some help.
Also I would've responded sooner, but it's finals week at my college so I've only got so much time.
Also I apologize for calling it a brick even though it was not. I do know what a brick is. It's when your device is unresponsive and will not turn on or do anything. It'a a paperweight or a brick.
I was freaking out my bad. I am sort of seasoned I was rooting my HTC Inspire when I got it almost a year ago, and I put ICS on it when the first leaks started coming out. I'm sorry I'm new to this phone. I will be getting better trust me. I just need some time to get used to the different quirks involved in this phone compared to my last one.
CrazyLineman777 said:
Also I apologize for calling it a brick even though it was not. I do know what a brick is. It's when your device is unresponsive and will not turn on or do anything. It'a a paperweight or a brick.
I was freaking out my bad. I am sort of seasoned I was rooting my HTC Inspire when I got it almost a year ago, and I put ICS on it when the first leaks started coming out. I'm sorry I'm new to this phone. I will be getting better trust me. I just need some time to get used to the different quirks involved in this phone compared to my last one.
Click to expand...
Click to collapse
My suggestion still stands use the ics leak 1 click then root see how you like stock ics twiz if you want a more custom rom then goto cwm and wipe cache , factory reset, then in mounts wipe sys, wipe cache and wipe data do all of these 3 times before installing rom and kernel always let.it sit a few minutes to settle....
CM9 Skyrocket
Ok I'm sorry for causing all of these issues I think I found a solution. In the General section and since I can't post links it is entitled:
[FIX] No Power Menu, No Lockscreen, Corrupt Efs FIX! Skyrocket and T989
Sorry I didn't look in General before posting this in Q&A the General section in the HTC Inspire forum wasn't usually gonna have fixes in it maybe root methods, but not fixes for stuff like this.
CrazyLineman777 said:
Ok I'm sorry for causing all of these issues I think I found a solution. In the General section and since I can't post links it is entitled:
[FIX] No Power Menu, No Lockscreen, Corrupt Efs FIX! Skyrocket and T989
Sorry I didn't look in General before posting this in Q&A the General section in the HTC Inspire forum wasn't usually gonna have fixes in it maybe root methods, but not fixes for stuff like this.
Click to expand...
Click to collapse
What radio did you flash?
I did realize I had done it wrong I flashed this: ATT-GALAXY-NOTE UCLC5 radio
but it was the one located in the post for Embryo 2.2 and I didn't flash the embryo rom, so the radio file which Mohan made specifically for his rom didn't go over well with the rom I flashed.
I did get back to stock eventually. It just took a few tries and the efs fix. I'm now putting CWM touch back on my phone and flashing a Gingerbread Rom because ICS on our phone is still a little too iffy for my likeing. I'll probably just wait till Samsung releases source for the kernel and cook my own rom.
CrazyLineman777 said:
I did realize I had done it wrong I flashed this: ATT-GALAXY-NOTE UCLC5 radio
but it was the one located in the post for Embryo 2.2 and I didn't flash the embryo rom, so the radio file which Mohan made specifically for his rom didn't go over well with the rom I flashed.
I did get back to stock eventually. It just took a few tries and the efs fix. I'm now putting CWM touch back on my phone and flashing a Gingerbread Rom because ICS on our phone is still a little too iffy for my likeing. I'll probably just wait till Samsung releases source for the kernel and cook my own rom.
Click to expand...
Click to collapse
I see, the note modem corrupts the efs partition. Glad you read some things and got it fixed!
I have two questions 1) is my only way to fix this to go back to stock ICS using ODIN? 2) Once i get back to that, what do i do in order to get to a working version of JB? is it as simple as trying another ROM? Is it ok to skip ICS and just flash another version of JB?
Background if you want it....
Followed vincon guide : http://forum.xda-developers.com/show....php?t=1773659
Started with Stock ATT 4.0.4
CWM via odin
baseb: UCLI3
I flashed JB [ROM] [4.1.2] [UCLL3] Stock Debloat to my i727 last night. Everything went seemingly smooth, everything worked with a strange exception being my exchange account wouldn't authenticate.Today my service is off about 95% of the time, then it will come on and ill get a text or two, then it goes off. voice calls dont work at all. LTE data is hit or miss.WiFi works
In phone status under network type its toggling: UTMS:3 to HSPA:11 to HSPAP15 to no service...then it drops everything and service state will say out of service and disconnected.
My IMEI is correct, I confirmed that.
It tried dialing the *#*#XXXX#*#* thing, that just said no connection and ended.
I started to go down the path of looking to flash a new radio, but that just doesn't seem like the answer to me... obviously the risk of me being wrong is high. i did check the MD5 numbers on other radios though and they came back as mismatched, so i did nothing there.
Also i wiped cache 3 times, as well as dalvek
Is there a simple solution that Ive missed or do i need to go to stock via ODIN? What, if anything, did i do wrong>
If you didn't flash corresponding UCLL3 baseband - AFAIK intermittent service is expected.
If you need to flash baseband - flash the latest UXUMA7 baseband.
Well i've actually had the exact same problem, in several variations and on several androids and here's my conclusions:
1 Magnetic storms and grid issues with the carrier. There's not much to do about these, except maybe for a making a tin hat for your phone. But, on a second thought this would also kill the signal
2 If the issue persists for more than a couple of days then the other thing for me was = radios that just didn't work with my carrier or rom. Changing these showed instant results.
I actually had this exact problem but for me it was on the carrier end. I tried every ROM and radio out there to no avail. After about a month and my parents also experiencing the issue, we called the carrier and they had it fixed in about two weeks.
Sent from my SGH-I727 using xda app-developers app
thanks for the help -
gonna try latest baseband and see how it goes
bgcole said:
thanks for the help -
gonna try latest baseband and see how it goes
Click to expand...
Click to collapse
It worked. Thanks again to all.
That's good to hear
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.
Hi all -
I recently updated to the 4.4.3 VzW firmware and upgraded from Viper 1.8.0 to Viper 2.5.0. Since upgrading, I have been having troubles with my hotspot. After being on and other devices have been using it for a bit, my M8 begins to rapidly turn on/off the Data Connection. This doesn't stop and the only way to fix the problem is go into airplane mode and back out again. I figured that I may have had a bad flash, so i tried reflashing clean downloads of both the firmware and a full wipe and reinstall of ViperOne, but still seeing the exact same issue. I seem to be also experiencing a problem where my phone is reporting a 4G connection, but data is disconnected and i cannot get anything over the data channel. Voice works fine. Again, to fix it's a cycle through airplane mode.
I tried applying the changes recommended by for the 4G handoff fix, even though the problem described does not seem to be exactly the same as mine. It did not seem to help, and mae it even harder to get a reliable 4G connection.
http://forum.xda-developers.com/verizon-htc-one-m8/general/verizon-4g-handoff-fix-t2868778
Has anyone else seen anything like this and have any recommendations for a fix?
Just realized this would be better in the troubleshooting forum. Is there a way for me to move it there or does that require a moderator?
Check http://forum.xda-developers.com/verizon-htc-one-m8/help/loss-lte-data-using-ap-t2900047
I have had the same thing, going back to 1.55.605.2 FW does seem to be the fix, I think its something with 4.4.3 FW.
One of the so called improvements is Mobile hotspot connectivity, but maybe that's only with phones that don't use the patched default.xml,
the ones that really pay for the mobile hotspot.
kc6wke said:
I have had the same thing, going back to 1.55.605.2 FW does seem to be the fix, I think its something with 4.4.3 FW.
One of the so called improvements is Mobile hotspot connectivity, but maybe that's only with phones that don't use the patched default.xml,
the ones that really pay for the mobile hotspot.
Click to expand...
Click to collapse
Thanks for the reply - do you have a link for the old firmware, so i can flash and revert back to that?
Also - are you still running Viper 2.x or did you roll back to a prior ROM as well?
After some more searching, i found this link for stock 4.4.2 on VzW, but was wondering if anyone has the firmware only, so don't have to restore recovery, and rom afterwards.
http://forum.xda-developers.com/showthread.php?t=2727831
I certainly can and will do it, if necessary, just would prefer to have the firmware only, if someone has it available. Anyone?
Thanks in advance for the help!
Dave
deh2k7 said:
Thanks for the reply - do you have a link for the old firmware, so i can flash and revert back to that?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?w=files&flid=13966
Dl the one without boot img
Thanks, downloaded and reverted. Long boot times, but things working. Now to give the hotspot a few tests. I'll update with my results.
deh2k7 said:
Thanks, downloaded and reverted. Long boot times, but things working. Now to give the hotspot a few tests. I'll update with my results.
Click to expand...
Click to collapse
initial tests are very promising. hotspot seems to be stable and hasn't dumped the data connection yet. Looks like good old VzW managed to screw up the firmware update as usual. Would be nice if they didn't always to be different. Thank god for these forums and the hardworking devs here!
I spoke too soon. Still seeing the same issue after reverting the FW back to 1.55.605.2. Anyone seeing this? Any thoughts on if reverting back to Viper 1.8 would help?
deh2k7 said:
I spoke too soon. Still seeing the same issue after reverting the FW back to 1.55.605.2. Anyone seeing this? Any thoughts on if reverting back to Viper 1.8 would help?
Click to expand...
Click to collapse
I don't think it is the firmware that is the issue, I think it is the kernel. You should be good going back to Viper 1.8 as it uses an older kernel. I would think you would also be fine using the newer firmware and an older ROM version.
jsaxon2 said:
I don't think it is the firmware that is the issue, I think it is the kernel. You should be good going back to Viper 1.8 as it uses an older kernel. I would think you would also be fine using the newer firmware and an older ROM version.
Click to expand...
Click to collapse
I'm starting to believe this as well, that there's something flaky in the 2.x Viper ROMS for VzW and hotspots, and likely in the kernel. I've already reverted back to the old firmware, and I'm going to go back to a clean 1.7.x full install, then OTA to 1.8. Will update with the results.
deh2k7 said:
I'm starting to believe this as well, that there's something flaky in the 2.x Viper ROMS for VzW and hotspots, and likely in the kernel. I've already reverted back to the old firmware, and I'm going to go back to a clean 1.7.x full install, then OTA to 1.8. Will update with the results.
Click to expand...
Click to collapse
Any luck fixing this issue?
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