Hi all, I aren't a new user but have attached my Google account on this log in so....meh.
I understand that from update 4.4.3 and upwards many N5 users experience loss of their mobile network where switching to aeroplane mode then back again is the only way to rectify this? I was fine until I recently swapped to Virgin (UK) which uses the EE network, ever since this my calls go straight to voicemail unless I manually select the provider myself.
I was having a whale of a time with CM11 and only found out this issue after tearing my hair out for a couple of weeks but it is something I cannot have because I need my phone to be available *always* due to issues with my mum. So what I have now done is backdated my system to 4.4.2 which seems to have worked *but* I now get the system update notifications which I have dealt with but I now seem to have messed up the Play Store
Is there any one solution for this problem where I can have everything actually working as it should? 4.4.2 stock seems to run a lot better and seems a lot quicker in all honesty, quicker than even CM11 than is the gods honest truth.
Please help I dearly love this phone and need it to work for personal reasons and I aren't in a position to buy another right now (quit joib to look after mum etc) have I tugged at your heart strings enough yet?
Flash 4.4.4 but flash the 4.4.2 radio then?
On my carrier in Australia, I've never had a single drop issue, on all versions of the radio.
I live in Ohio and my connection is awesome with ATT. The only problem I have with network is my house and church. Lol Everywhere else like work is awesome. I think the network you choose is the major player in this. The phone itself is great on network.
Lethargy said:
Flash 4.4.4 but flash the 4.4.2 radio then?
On my carrier in Australia, I've never had a single drop issue, on all versions of the radio.
Click to expand...
Click to collapse
I tried a search for this but it was a confusing minefield for a novice like me. I dont suppose you have any pointers as to where and how I get to do the 4.4.2 radio fix do you please?
tremlar said:
I tried a search for this but it was a confusing minefield for a novice like me. I dont suppose you have any pointers as to where and how I get to do the 4.4.2 radio fix do you please?
Click to expand...
Click to collapse
Factory images. Then use fastboot to flash it while in bootloader. Link to tutorials are in the first link of my signature.
Lethargy said:
Factory images. Then use fastboot to flash it while in bootloader. Link to tutorials are in the first link of my signature.
Click to expand...
Click to collapse
To 100 % prove it to myself I did the stock system updates, first to 4.4.3 then to 4.4.4 straight after I rang myself from a landline and it went immediately to voicemail. I then tried to install Cyanfox and that fails on the set up wizard as did liquid
linaro, both using the correct gapps and several versions.
So my next try is an older CM M3 iirc because I think doing the radio thing is a bit beyond my skills Lethargy
tremlar said:
To 100 % prove it to myself I did the stock system updates, first to 4.4.3 then to 4.4.4 straight after I rang myself from a landline and it went immediately to voicemail. I then tried to install Cyanfox and that fails on the set up wizard as did liquid
linaro, both using the correct gapps and several versions.
So my next try is an older CM M3 iirc because I think doing the radio thing is a bit beyond my skills Lethargy
Click to expand...
Click to collapse
theres an easier solution than that...! grab a baseband/radio here http://forum.xda-developers.com/goo...t/modem-nexus-5-flashable-modems-efs-t2514095 download the zip file to your phone then flash it in your custom recovery. it takes seconds and can flash as many radios as you like until you find the perfect one for you
simms22 said:
theres an easier solution than that...! grab a baseband/radio here http://forum.xda-developers.com/goo...t/modem-nexus-5-flashable-modems-efs-t2514095 download the zip file to your phone then flash it in your custom recovery. it takes seconds and can flash as many radios as you like until you find the perfect one for you
Click to expand...
Click to collapse
simms22 you may just be the sexiest person alive, just updating cm then I shall give this a try.
Will report back, appreciated massively so far guys.
Edit - well, it seems to of worked, I am getting some weird google log in errors but I aren't sure if that is related. Letting it download the apps etc then will mess some more tomorrow but the phone definitely rang and didn't go to voicemail. simms 22 you are a gem, thank you very much.
Related
Please bare with me since this is the first time having to post for an issue since I usually find an answer on your forums
So here's the situation.
I bought the photon q 4g lte from ebay and it came with the unlocked bootloader.
Needless to say it was with the stock ics and i tried to find a jellybean update because it wasn't taking the ota and ended up going with cyanogen since i had no problems before. However those phones i had before were with sim cards not cdma.
I found out i couldn't update prl or profile manually without having to do something on the pc.
So after searching left and right i found i could use rsl lite (I used 6.1.5) and eventually found the "stock" file from this post
http://forum.xda-developers.com/showthread.php?t=2095536&highlight=rsd+lite
I did the stock jellybean, got it to go through the process and it booted up with no errors.
However, when it boots into the os it pops up a force close on omadmclient_sprint_dataservice and eventually also on the process com.android.phone.
I tried putting it in airplane mode to see if the service error would go away but it didn't work for the process part crashing.
I tried re-flashing, deleting cache in recovery, doing a data/factory reset in recovery and the one time i was able to do a data factory reset within the settings menu.
I could not find anyone that said they had a rom that worked with sprint and updating prl within the rom, if anyone knows of one let me know and i will flash it through rsd.
Otherwise does anyone have an idea of what could be happening because googling the omadmclient part did not pull up anything specific and pulling up the process issue for other phones has not helped me either.
Was this a hacked GSM phone, or are you using it as CDMA?
I've never heard of people having FC issues after flashing a FXZ from RSD. Which one did you flash? Android 4.1.2 - Sprint US - 9.8.2Q-122_XT897_FFW-5 (No simlock) ?
If you are on stock, you should be able to update the PRL within the ROM.
I was trying to use it with cdma network through sprint. and yeah that was the file i downloaded, had to remove the getvar to get it working but flashed with no errors after doing that.
As for updating the prl i can barely navigate through the phone, there is no home page loading and the process pop comes up often enough that its hard to go through the settings
crispy6 said:
I was trying to use it with cdma network through sprint. and yeah that was the file i downloaded, had to remove the getvar to get it working but flashed with no errors after doing that.
As for updating the prl i can barely navigate through the phone, there is no home page loading and the process pop comes up often enough that its hard to go through the settings
Click to expand...
Click to collapse
Sounds like something went wrong mate. Are you already activated on Sprint? I don't know if that would matter, it might.
I would honestly redownload and redo the RSD process.
arrrghhh said:
Sounds like something went wrong mate. Are you already activated on Sprint? I don't know if that would matter, it might.
I would honestly redownload and redo the RSD process.
Click to expand...
Click to collapse
I originally tried to activate the phone through cyanogen and then when the rep said he couldnt do it because of the lack of prl to update within the rom we just setup the activation back on the old phone/ That phone is working on the network.
I re-downloaded the file just in case and re-flashed but same problem. The only thing i thought of was maybe updating the radio but since its a stock rom it should work out of the gate. whats also weird is i tried turning wifi on but it didnt work either.
Anychange you know of a rom that works with sprint. I dont care if its stock since i would probably root later again.
crispy6 said:
I originally tried to activate the phone through cyanogen and then when the rep said he couldnt do it because of the lack of prl to update within the rom we just setup the activation back on the old phone/ That phone is working on the network.
I re-downloaded the file just in case and re-flashed but same problem. The only thing i thought of was maybe updating the radio but since its a stock rom it should work out of the gate. whats also weird is i tried turning wifi on but it didnt work either.
Anychange you know of a rom that works with sprint. I dont care if its stock since i would probably root later again.
Click to expand...
Click to collapse
Which one are you flashing?
Try another perhaps...? I honestly have never heard of this. It sounds like the phone might be damaged, or the RSD process just did not flash correctly.
I guess I should ask, was the phone modified at all for the GSM SIM slot mod? I wonder if having a non-Sprint SIM in is messing with it... That is just a shot in the dark.
arrrghhh said:
Which one are you flashing?
Try another perhaps...? I honestly have never heard of this. It sounds like the phone might be damaged, or the RSD process just did not flash correctly.
I guess I should ask, was the phone modified at all for the GSM SIM slot mod? I wonder if having a non-Sprint SIM in is messing with it... That is just a shot in the dark.
Click to expand...
Click to collapse
so far the only rom i tried was 10.1 cyanogen and the stock rom for jellybean. However for the stock rom it doesnt let me downgrade to ics with rsd 6.1.5 do you think if i downloaded an old version i could downgrade to a lower stock rom?
Also I honestly had not looked for the cdma roms since most of what i saw was troubleshooting related for this phone but i just saw this rom -AOKP 4.2.2 (Android Open Kang Project) (CDMA&GSM) that you created - http://forum.xda-developers.com/showthread.php?t=2293892
I re-rooted and installed that one and it looks great, just wondered how you got sprint to activate the phone or if you had done it before changing the rom? Also how would the prl and profile be updated.
Lastly the wifi wasn't turning on this time either, it did work initially when i got the phone so that has me stumped.
crispy6 said:
so far the only rom i tried was 10.1 cyanogen and the stock rom for jellybean. However for the stock rom it doesnt let me downgrade to ics with rsd 6.1.5 do you think if i downloaded an old version i could downgrade to a lower stock rom?
Also I honestly had not looked for the cdma roms since most of what i saw was troubleshooting related for this phone but i just saw this rom -AOKP 4.2.2 (Android Open Kang Project) (CDMA&GSM) that you created - http://forum.xda-developers.com/showthread.php?t=2293892
I re-rooted and installed that one and it looks great, just wondered how you got sprint to activate the phone or if you had done it before changing the rom? Also how would the prl and profile be updated.
Lastly the wifi wasn't turning on this time either, it did work initially when i got the phone so that has me stumped.
Click to expand...
Click to collapse
To downgrade to ICS, you need to remove some additional lines. See this post for more information on that.
However, you should be able to update the PRL on either stock ROM.
I think I said this before, but I will say it again. You need to do PRL updates, activate the phone, and get EVERYTHING working on stock BEFORE you flash ANY custom ROM. This is just standard practice - you don't want to put the cart before the horse! Get the phone working, then play with custom ROM's.
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.
As the title says, I am on T-mobile now with my D850. My phone is currently unlocked and rooted using stock rom.
the last phone i flashed a custom rom was with my htc one x and frankly i forgotten all the little details and never bothered because it took a lot of time. i know i need bootloader unlocked to install a custom recovery to flash the rom then back up, install gapps, etc etc. I don't have time or the patience to relearn everything.
I got interested in learning that CM11 is available and i checked out the CM website and was surprised to hear all i have to do is install the installer on both my phone and PC and boom, everything else is automated. This is what i want to try. Here are my questions:
- do i have to manually install any apn, radio, etc. things of that nature to get the proper t-mobile network signal for voice, LTE data, and text messaging?
- is an official D850 released so that once i install, i can simply keep up to date into CM12 via automatic updates through the software? (one click update OTA)
- do i need to make a titanium back up or will all my apps and settings stay when i flash CM?
I appreciate any and all answers. I have not unlocked bootloader via bump yet. but my main worry is will i have to custom install/input all the t-mobile apn and radios because that will require me to manually find and install and risk messing things up.
chillsen said:
As the title says, I am on T-mobile now with my D850. My phone is currently unlocked and rooted using stock rom.
the last phone i flashed a custom rom was with my htc one x and frankly i forgotten all the little details and never bothered because it took a lot of time. i know i need bootloader unlocked to install a custom recovery to flash the rom then back up, install gapps, etc etc. I don't have time or the patience to relearn everything.
I got interested in learning that CM11 is available and i checked out the CM website and was surprised to hear all i have to do is install the installer on both my phone and PC and boom, everything else is automated. This is what i want to try. Here are my questions:
- do i have to manually install any apn, radio, etc. things of that nature to get the proper t-mobile network signal for voice, LTE data, and text messaging?
- is an official D850 released so that once i install, i can simply keep up to date into CM12 via automatic updates through the software? (one click update OTA)
- do i need to make a titanium back up or will all my apps and settings stay when i flash CM?
I appreciate any and all answers. I have not unlocked bootloader via bump yet. but my main worry is will i have to custom install/input all the t-mobile apn and radios because that will require me to manually find and install and risk messing things up.
Click to expand...
Click to collapse
You just need to install Bump! And a backup is recommended in case something goes wrong, as far as connecting to tmobile all you need is the APN, i have a D850 and i live in mexico and CM11 and 12 work fine with just the apn, also everything will get wiped except for pics and music if you dont wipe internal storage
SmokeyTech1 said:
You just need to install Bump! And a backup is recommended in case something goes wrong, as far as connecting to tmobile all you need is the APN, i have a D850 and i live in mexico and CM11 and 12 work fine with just the apn, also everything will get wiped except for pics and music if you dont wipe internal storage
Click to expand...
Click to collapse
errr i am not comfortable with adb to install bump! would the automated installer on pc and phone do all this for me? i guess i can try? i just love how CM installer does everything for you. also thanks for confirming all i need to do is input the APN which i'm familiar with when i had switched to t-mobile after i had unlocked my phone. lastly will i have to install gapps separately? Thank you so much, i wish i didn't have to use adb to bump!
chillsen said:
errr i am not comfortable with adb to install bump! would the automated installer on pc and phone do all this for me? i guess i can try? i just love how CM installer does everything for you. also thanks for confirming all i need to do is input the APN which i'm familiar with when i had switched to t-mobile after i had unlocked my phone. lastly will i have to install gapps separately? Thank you so much, i wish i didn't have to use adb to bump!
Click to expand...
Click to collapse
Dont need to use adb, just download flashify from the play store, does it all by itself, very easy, the automated installer is just for the rom, you need a recovery first, the gapps should be installed at the same time as the rom, but ive never used the auto installer, i would flash it with the recovery, i like to things manually
Just to let you know that with every AOSP ROM with a T-Mobile Sim you will get a kernel panic if using LTE. I have the D850 but using a T-Mobile Sim. I have to have it on 3g instead of LTE. No ones been able to figure it out I'm guessing because there is only one or two of us using a T-Mobile Sim with this phone. Bummer huh
???CAUTION???
May ruin other ROMS after this
because nothing compares
coletague said:
Just to let you know that with every AOSP ROM with a T-Mobile Sim you will get a kernel panic if using LTE. I have the D850 but using a T-Mobile Sim. I have to have it on 3g instead of LTE. No ones been able to figure it out I'm guessing because there is only one or two of us using a T-Mobile Sim with this phone. Bummer huh
???CAUTION???
May ruin other ROMS after this
because nothing compares
Click to expand...
Click to collapse
Well then have you thought of changing carriers? It is a d850 for Att ..... Does it kernel panic on stock Roms ? You might just be **** out of luck cause I'm pretty sure everyone here uses Att. I use straight talk with no issues. You have slim choices..... Change carriers. .... Quit using T-Mobile if you are unhappy with the custom ROM and LTE kernel panics. Or buy a T-Mobile g3..... Lol suck eh... But just telling you what you need to hear.
Or maybe if you are ballsy try to see if a Dev for T-Mobile can help you with this cause I'm thinking that may be your beat bet cause none of us use T-Mobile. :thumbup::beer:
2SHAYNEZ
It's fine with stock based ROM s which I'd rather be on AOSP with HSPA
???CAUTION???
May ruin other ROMS after this
because nothing compares
coletague said:
It's fine with stock based ROM s which I'd rather be on AOSP with HSPA
???CAUTION???
May ruin other ROMS after this
because nothing compares
Click to expand...
Click to collapse
Maybe it will iron itself out after a while. Good luck
2SHAYNEZ
Do you have a beef with him or what?
4ndroid4Life said:
Do you have a beef with him or what?
Click to expand...
Click to collapse
You chose to say this for your first post on XDA ....... Wow...
2SHAYNEZ
coletague said:
Just to let you know that with every AOSP ROM with a T-Mobile Sim you will get a kernel panic if using LTE. I have the D850 but using a T-Mobile Sim. I have to have it on 3g instead of LTE. No ones been able to figure it out I'm guessing because there is only one or two of us using a T-Mobile Sim with this phone. Bummer huh
Click to expand...
Click to collapse
interesting note, will update you, LTE seems to be working fine, speeds are fine, but i need to use LTE longer to see the kernel problem. I'm on the CM 11, dec 6 nightly currently. how about you?
Latest nightly of cm12. Try downloading a ROM over LTE
???CAUTION???
May ruin other ROMS after this
because nothing compares
It's always recommended to use WiFi to download any Roms anyways ..... Do you have a crap ton if data or something ...
2SHAYNEZ
I don't have Internet.
I have literally unlimited data. My phone was free and my service is free
coletague said:
I don't have Internet.
I have literally unlimited data. My phone was free and my service is free
Click to expand...
Click to collapse
That's crazy... You must work for tmo
2SHAYNEZ
Is it now understandable why I use T-Mobile? Lol
???CAUTION???
May ruin other ROMS after this
because nothing compares
coletague said:
Is it now understandable why I use T-Mobile? Lol
???CAUTION???
May ruin other ROMS after this
because nothing compares
Click to expand...
Click to collapse
Oh yeah absolutely... Hook me up jeez.... Straight tall is good and all but unlimited unthrottled just isn't fair lol. Jeeez
2SHAYNEZ
Ha I can only have two Sims the way I do and that one is occupied. Fix my kernel panics lol I'll give you a last kmsg
???CAUTION???
May ruin other ROMS after this
because nothing compares
I need some assistance please! I am truly baffled by what I am experiencing and would like to know why and hopefully how to fix it. Here's the details:
CARRIER: Verizon
MODEL: HTC One M8
S-OFF: Yes (Sunshine)
ROOT: Yes
HBOOT: 3.19
RADIO: 1.09.20.0926
OpenDSP: 46.2.2
OS: 3.28.605.4
First off, sorry for the book, but I figured more details would be better at this point to figure out what is up, so I appreciate any assistance in advance! PS: I bolded the key items to the story for those that like to skim.
Prior to S-Off and Root, I was on OTA version 4.4.4 waiting in anticipation for 5.0 to come to my device. Was unsure about spending $25 for Sunshine's method, but finally decided to take the plunge. At first things seemed great and very smooth. Following all instructions from Sunshine I was finally with S-Off status. I then used WeakSauce2 to gain temp root of the Stock ROM so that I could install Flashify and TWRP. Rebooted and loaded up TWRP Recovery and completed the first Nandroid. SUCCESS! Next up was Titanium Backup and such and copied everything off to my computer for safe keeping. So far so good and then loaded up a few ROM files and whatnot to the External SD Card so I could start flashing a new ROM. Feeling good up to this point, but here's where the troubles begin...
I have had great success with CyanogenMod in the past on previous devices and always very pleased. I read CM12 for others was great and stable and performed well, so I decided to grab the latest CM12 Nightly and the GApps package. Did the normal Wipe / System Wipe for initial flash of a new ROM and then installed both ZIPs no problem. The ROM boots up and everything seems okay, only I do not have LTE at all, only 3G. I also tried the GPE rom by Digitalhigh and experienced the same thing! Restoring from Nandroid also did not fix LTE, so at this point I got worried I broke my phone somehow.
To make a long story short after lots of testing I found a fix for getting LTE back on my original ROM. I found the 4.4.4 RUU and placed the 1.7 GB zip file (0P6BIMG.zip) on the root of my external SD Card, booted into HBOOT and ran the update. It did it's thing and booted up into the Stock ROM. Still no LTE! So then I found a comment somewhere about once that is done, do a Factory Reset from HBOOT using the Stock Recovery and it is supposed to reset the NV Radio Partition, so I did this and when it booted back up, SUCCESS! I have LTE back.
Once that was done I can now flash GPE, (but unusable because SMS is not working for some reason... I am using Google Voice BTW), so I am back to my original 4.4.4 TWRP Recovered ROM. I tried just for kicks to see if after the "fix" if I could make CM12 work, but again will bring it down to an unworking LTE status. Rinse and repeat the "fix" and got LTE back and did Nandroid Recovery. I paid the money to get S-Off and Root access so I could enjoy the Custom ROM's, but now I feel I am stuck...
All that being said... Can someone please explain to me what is going on?? And is there any way I can fix this so I can use CM12 and have LTE, and even then some other ROMs? I will post in Digitalhigh's forum for resolution to the SMS issue, but I have never had this much trouble with a device before and do not know enough about the different partitions and how they work and such. Any assistance and advice is MUCH appreciated!
Thank you!
Nobody has any advise or explanation?
I don't know the version numbers you posted from you bootloader off the top of my head but did you update your firmware to one of the unofficial ones around before flashing one of the lollipop roms? Is so, are you sure it took completely as sometimes you have to flash it twice.
Alternatively you could wait for our official firmware to drop any minute now and have pretty good odds of working for you.
cntryby429 said:
I don't know the version numbers you posted from you bootloader off the top of my head but did you update your firmware to one of the unofficial ones around before flashing one of the lollipop roms? Is so, are you sure it took completely as sometimes you have to flash it twice.
Alternatively you could wait for our official firmware to drop any minute now and have pretty good odds of working for you.
Click to expand...
Click to collapse
Yes I did use official firmware, and flashed twice per recommendations. I have it working with GPE, but every time I flash CM12 it breaks LTE. I have seen articles and posts of others running CM12 on their M8's with VZW and stating "zero issues"... Lack of LTE sounds like an issue to me. So my big question at hand is, why does CM12 break LTE, and is there a fix? Everything else seemed to work great otherwise.
kjparenteau said:
So my big question at hand is, why does CM12 break LTE, and is there a fix? Everything else seemed to work great otherwise.
Click to expand...
Click to collapse
I was reading the CM12 m8 thread earlier this week and many reported that LTE did not work on builds from late Feb. early March. CM12 is in no way stable and results will vary from phone to phone. Even the speaker issues have not been fully resolved. Bummer, because I'd really like it to be more stable.
http://forum.xda-developers.com/htc...genmod-12-0-nightlies-htc-one-t2998070/page75
Thank you for your reply. Definitely wanting CM since I used to run that regularly on my older devices with no troubles at all. The speed and simplicity are what I am going for. Sense is okay, but the difference of less than 300 megs with CM compared to over a gig for stock is unreal. WAY less overhead.
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