Related
So for a while now I have not been able to update my PRL or Profile. It hasn't bothered me because for the most part the phone has worked fine until recently. A friend texted me and said he was going to call me. He text back a few minutes later and ask why I didnt answer. Phone was next to me the whole time and it didnt ring or so any kind of notification that he had tried to call. Took him 3 calls before my phone rang and he got through.
I have applied for a few jobs within the past few weeks and have heard nothing from anyone which I am surprised because I was referred to one company by and friend who put in a good word for me and said that his supervisors were really impressed with my resume. So now I feel like this issue could possibly be costing me job opportunities and I want to get it figured out.
The errors are 6602 and 407. I've tried to do it over 4G and put my phone just in CDMA mode for 3G only and get the 407 code for 3G and the 6602 over 4G.
I am running Stock rooted/odexed MK2 and I just did a clean flash of the rom again clearing data/cache and dalvik seeing if that would help which it didn't. I have reflashed the modem seperately also with no help.
I have seen many threads of others having this issue but no answers on a fix. Has anyone experienced this and actually done something that has resolved the issue?
If you feel it may be costing you a job, why not flash a nand of a stock rom, assuming you have one
Sent from my SPH-L720 using XDA Free mobile app
I did, I flashed back to MF9 using this http://www.rwilco12.com/Files/Devic...H-L720)/Stock ROMs/MF9/Full Restore/Unrooted/
Which should be a stock factory restore, still would not update profile or prl. From there I updated to NG2 with Samsung Kies and I am still not able to update either.
tenaciousj said:
I did, I flashed back to MF9 using this http://www.rwilco12.com/Files/Devic...H-L720)/Stock ROMs/MF9/Full Restore/Unrooted/
Which should be a stock factory restore, still would not update profile or prl. From there I updated to NG2 with Samsung Kies and I am still not able to update either.
Click to expand...
Click to collapse
What kernel do you use?
(I fixed this issue I my phone, but SERIOUSLY, what seemed to fix it MADE NO SENSE, so I'm not going to to relate it again, you can look up my posts if you want, but I wouldn't waste your time. I'm more interested in what kernel you are using... if it isn't KT-SGS4, then it doesn't matter.)
Other than that, have you tried the ##72786# dialer code, which is supposed to reset that stuff (didn't fix it for me personally)? You may have to reactivate your phone though (I did), which isn't that much of an issue...
rsngfrce said:
What kernel do you use?
(I fixed this issue I my phone, but SERIOUSLY, what seemed to fix it MADE NO SENSE, so I'm not going to to relate it again, you can look up my posts if you want, but I wouldn't waste your time. I'm more interested in what kernel you are using... if it isn't KT-SGS4, then it doesn't matter.)
Other than that, have you tried the ##72786# dialer code, which is supposed to reset that stuff (didn't fix it for me personally)? You may have to reactivate your phone though (I did), which isn't that much of an issue...
Click to expand...
Click to collapse
For kernel version it shows 3.4.0-2162929 which I'm guessing is the stock NG2. I haven't flashed anything else since updating through Kies to NG2.
I've done the 72786 dial code a handful of times and it still didn't help. The only thing that solved was a issue I had after I first updatd to NG2 I had no working 4G. Phone would only connect to 3G and that was when it was in CDMA only mode. Aside from that it hasn't helped with the PRL/Profile update issue I'm having.
tenaciousj said:
For kernel version it shows 3.4.0-2162929 which I'm guessing is the stock NG2. I haven't flashed anything else since updating through Kies to NG2.
I've done the 72786 dial code a handful of times and it still didn't help. The only thing that solved was a issue I had after I first updatd to NG2 I had no working 4G. Phone would only connect to 3G and that was when it was in CDMA only mode. Aside from that it hasn't helped with the PRL/Profile update issue I'm having.
Click to expand...
Click to collapse
Yeah, that does sound like a stock kernel to me. Have you tried updating it through the Sprint Zone app? In Settings, More Networks, Mobile Networks, Network Mode, if it is not set to Automatic, you can try setting it to that and see if it lets you update after reboot, I have heard that can help but did not fix it for me (I have it set to LTE/CDMA). Have you seen this thread: Galaxy S4/Note 3/Mega - Update Profile/PRL/HFA Fix for Sprint/Boost/Virgin Mobile/etc? It is complex (don't IGNORE steps 5, 6, 7 and 8, which most people in the thread seem to...). I have not personally used this method, I was planning to before my issue resolved itself, but I didn't have a donor GS4 either (damn it, I JUST remembered that I DO, I f*ed up the USB port on my first one and completely forgot about that! BLOW MY MIND! But anyways...).
rsngfrce said:
Yeah, that does sound like a stock kernel to me. Have you tried updating it through the Sprint Zone app? In Settings, More Networks, Mobile Networks, Network Mode, if it is not set to Automatic, you can try setting it to that and see if it lets you update after reboot, I have heard that can help but did not fix it for me (I have it set to LTE/CDMA). Have you seen this thread: Galaxy S4/Note 3/Mega - Update Profile/PRL/HFA Fix for Sprint/Boost/Virgin Mobile/etc? It is complex (don't IGNORE steps 5, 6, 7 and 8, which most people in the thread seem to...). I have not personally used this method, I was planning to before my issue resolved itself, but I didn't have a donor GS4 either (damn it, I JUST remembered that I DO, I f*ed up the USB port on my first one and completely forgot about that! BLOW MY MIND! But anyways...).
Click to expand...
Click to collapse
Thanks for the link I'll check it later. My account is actually a SERO account but I did have working updates when I first got the phone. The phone was also new and activated on the account as soon as I got it.
Sent from my SPH-L720 using Tapatalk
tenaciousj said:
Thanks for the link I'll check it later. My account is actually a SERO account but I did have working updates when I first got the phone. The phone was also new and activated on the account as soon as I got it.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Yeah, I honestly don't really understand what that thread means when it talks about flashing to legacy accounts. I believe I have a SERO account (I don't know, my wife pays the bill... :silly: ) and the updates worked fine until I think messing with the APNs to try to fix my inability to send MMS messages messed things up. I never flashed any legacy accounts or anything.
So... at this point, even though IT MAKES NO SENSE, I will tell you what SEEMED to fix the issue for me. I STRESS, this MAKES NO SENSE TO ME, but after months of being unable to update my PRL/PROFILE, after doing the following, I was suddenly able to update them. It is likely an EXTREME coincidence, but for the hell of it I will now tell you.
Using the Pro version of Solid Explorer, I copied the Carrier folder from the root of my phone to my external SD card. THAT IS IT. YES... THAT IS IT. NOTHING MORE. I did NOT copy it back, I did not change anything. HOW this could possibly have cured the problem would seem to make very little sense, I can only conjecture that Solid Explorer, in the act of copying the folder to my external SD card, somehow 'refreshed' something in the carrier folder in the root of my phone... and I am grasping at straws here. I think you can probably understand WHY I did not want to reveal that this is what SEEMED to cure my issue, because it is so unlikely, and more likely an extreme coincidence and something else happened that I am not aware of, but that is the only thing I know of that I did related between when it was not working to when it was. So now you know at least (and as I have told a few others, there is no point in not trying, other than the crushing disappointment of it almost certainly not working)...
I should add as well however, now that it occurs to me, that I use the KT-SGS4 KitKat 4.4 TouchWiz kernel, and had for a long time suffered from a loss of mobile connection and GPS. requiring a reboot to get them back (within a similar time period to my PRL/PROFILE issues). I seem to have fixed the mobile connection/GPS loss by choosing the 'correct' governor to use with that kernel for my ROM, and it is not IMPOSSIBLE that THIS occurred at the time I was able to update my PRL/PROFILE, but I do not remember exactly, and I'm PRETTY CERTAIN I still had the issue with the mobile connection/GPS loss after updating my PRL/PROFILE, so I think that likely rules out KT-SGS4 as a culprit in this issue. (But then, I was forgetting that we already established that you were on a stock kernel...)
KNOWN issues with KT-SGS4 Sprint KitKat 4.4 TouchWiz kernel
rsngfrce said:
Yeah, I honestly don't really understand what that thread means when it talks about flashing to legacy accounts. I believe I have a SERO account (I don't know, my wife pays the bill... :silly: ) and the updates worked fine until I think messing with the APNs to try to fix my inability to send MMS messages messed things up. I never flashed any legacy accounts or anything.
So... at this point, even though IT MAKES NO SENSE, I will tell you what SEEMED to fix the issue for me. I STRESS, this MAKES NO SENSE TO ME, but after months of being unable to update my PRL/PROFILE, after doing the following, I was suddenly able to update them. It is likely an EXTREME coincidence, but for the hell of it I will now tell you.
Using the Pro version of Solid Explorer, I copied the Carrier folder from the root of my phone to my external SD card. THAT IS IT. YES... THAT IS IT. NOTHING MORE. I did NOT copy it back, I did not change anything. HOW this could possibly have cured the problem would seem to make very little sense, I can only conjecture that Solid Explorer, in the act of copying the folder to my external SD card, somehow 'refreshed' something in the carrier folder in the root of my phone... and I am grasping at straws here. I think you can probably understand WHY I did not want to reveal that this is what SEEMED to cure my issue, because it is so unlikely, and more likely an extreme coincidence and something else happened that I am not aware of, but that is the only thing I know of that I did related between when it was not working to when it was. So now you know at least (and as I have told a few others, there is no point in not trying, other than the crushing disappointment of it almost certainly not working)...
I should add as well however, now that it occurs to me, that I use the KT-SGS4 KitKat 4.4 TouchWiz kernel, and had for a long time suffered from a loss of mobile connection and GPS. requiring a reboot to get them back (within a similar time period to my PRL/PROFILE issues). I seem to have fixed the mobile connection/GPS loss by choosing the 'correct' governor to use with that kernel for my ROM, and it is not IMPOSSIBLE that THIS occurred at the time I was able to update my PRL/PROFILE, but I do not remember exactly, and I'm PRETTY CERTAIN I still had the issue with the mobile connection/GPS loss after updating my PRL/PROFILE, so I think that likely rules out KT-SGS4 as a culprit in this issue. (But then, I was forgetting that we already established that you were on a stock kernel...)
KNOWN issues with KT-SGS4 Sprint KitKat 4.4 TouchWiz kernel
Click to expand...
Click to collapse
Yeah that copying the carrier folder don't seem like it would do anything but maybe I'll give it a try. Whats the best way to root right now? I just want to make sure it will let me unroot the phone if it dont work and no trip knox incase I have to bring this in.
Do you know what bootloader you are on? You said you were on Sys MK2, then went back to MF9 and now are on NG2. When you went to NG2, unless you took very specific steps to keep the MF9 bootloader, you would be on the NG2 bootloader now, which includes Knox, and you can no longer go back beyond NAE I think. If you don't know what bootloader you have, get DeviceInfo https://play.google.com/store/apps/details?id=com.jphilli85.deviceinfo from the Play Store and under the Software heading, see what it shows for the last 3 digits for Bootloader. This makes a difference on the best root method.
rsngfrce said:
Do you know what bootloader you are on? You said you were on Sys MK2, then went back to MF9 and now are on NG2. When you went to NG2, unless you took very specific steps to keep the MF9 bootloader, you would be on the NG2 bootloader now, which includes Knox, and you can no longer go back beyond NAE I think. If you don't know what bootloader you have, get DeviceInfo https://play.google.com/store/apps/details?id=com.jphilli85.deviceinfo from the Play Store and under the Software heading, see what it shows for the last 3 digits for Bootloader. This makes a difference on the best root method.
Click to expand...
Click to collapse
Bootloader and software version both show up as NG2 on Device Info.
tenaciousj said:
Yeah that copying the carrier folder don't seem like it would do anything but maybe I'll give it a try. Whats the best way to root right now? I just want to make sure it will let me unroot the phone if it dont work and no trip knox incase I have to bring this in.
Click to expand...
Click to collapse
I'm not an EXPERT on this subject, but if you are on NG2 stock unrooted right now, I believe you can use: CF-Auto-Root to root it. Or, here is a stock rooted version of the NG2 ROM:
[ROM][NG2] Stock Rooted NG2 (which mentions that it has Knox removed).
As far as tripping stuff, I'm somewhat unsure about that to be honest. I have always used Triangle Away on my phone, but it has a warning now not to use it with a custom kernel (which I use). My counter is at 3, but I am out of warranty anyway.
I spent a few hours on chat with Sprint. They couldn't figure it out so I'm bringing it in tomorrow. Guessing I'll get a new phone. The people at the Sprint store seem rather limited in their knowledge, at least they were last time I was there.
Sent from my SPH-L720 using Tapatalk
tenaciousj said:
I spent a few hours on chat with Sprint. They couldn't figure it out so I'm bringing it in tomorrow. Guessing I'll get a new phone. The people at the Sprint store seem rather limited in their knowledge, at least they were last time I was there.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I guess if there are no signs that it has been rooted, that's probably a good way to go. You apparently had a phone pre-Knox and now I think you will get one with a Knox system, but it doesn't matter in your case since went beyond the point of no return already with the bootloader... I don't know if you have the new Spark model (tri-band), I don't know if the still make the old plain one like I have anymore...
rsngfrce said:
I guess if there are no signs that it has been rooted, that's probably a good way to go. You apparently had a phone pre-Knox and now I think you will get one with a Knox system, but it doesn't matter in your case since went beyond the point of no return already with the bootloader... I don't know if you have the new Spark model (tri-band), I don't know if the still make the old plain one like I have anymore...
Click to expand...
Click to collapse
I got the phone I have now about a month after the GS4 came out so its non sparks. I stayed on MK2 for so long because I couldn't find a newer rom that looked to be stable and not have to jump through a bunch of hoops to install it. The Odin screen shows everything being zero and offical software so I should be good. I am going to sign out of all of my accounts before I bring it in being I have a lot of apps bought through the store that only work on rooted phones. I hope I can get a tri band to replace it. My friend has a triband GS4 and it gets much better data speeds than mine.
Yeah, I mentioned elsewhere here before that I actually didn't know of the existence of the "Sparks" version of the G4. I screwed up the USB port on my G4 before upgrade time, so I had to buy another G4 on Amazon. Upgrade time has come up, so I was just looking and saw my phone listed as "Non-Sprint Sparks", which I thought meant that they called it the "Sparks" model because I hadn't bought it from Sprint... took me a while to figure out what that actually meant... :laugh:
Sprint online nor the store could fix it so I got a new one.
No rooting but error 407
As titled, I've not rooted the phone. I'm getting error code 407 on attempts to update PRL and Update profile. Download updates manually does nothing. Note I'm on a Samsung Note 4, Sprint. Had updated to Marshmallow 6.0.1 late March but then above actions persist since then. I'm using Wi-Fi only, Sprint service disconnected as I couldn't pay bill when I lost job during a disabling illness.
I haven't been able to update prl profile or firmware for over 8 months. I am not rooted never have been I have called customer service over and over replaced SIM card did the ## stuff nothing has helped. The phone works although service isn't as good as it could be and says there is a prl update available but I always get connection error 6 on all 3. I also have serious battery draining issues as far as my data I do get a strong 4g lte connection just service is low and sometimes drops when I am close to a sprint tower every other phone gets full bars really on any network especially sprint. I hope someone can help I like my sph-720 other that that and honestly I can't afford to keep up with the Joneses. Hopefully this is enough info please help
00Lee said:
I haven't been able to update prl profile or firmware for over 8 months. I am not rooted never have been I have called customer service over and over replaced SIM card did the ## stuff nothing has helped. The phone works although service isn't as good as it could be and says there is a prl update available but I always get connection error 6 on all 3. I also have serious battery draining issues as far as my data I do get a strong 4g lte connection just service is low and sometimes drops when I am close to a sprint tower every other phone gets full bars really on any network especially sprint. I hope someone can help I like my sph-720 other that that and honestly I can't afford to keep up with the Joneses. Hopefully this is enough info please help
Click to expand...
Click to collapse
Have you done a factory reset via recovery? Or you might want to flash latest full stock
I'm New to the forums here everyone.
Greetings!
I'm running NRD90U but I'm experiencing some issues with the recent radio update that came with nougat on Verizon. I've searched everywhere on the xda forums and found suggestions to others experiencing similar issues (simultaneous voice and data). With the 03.61 radio, everything worked just fine whereas with 03.72 I have to toggle airplane mode after every reboot in order to have simultaneous voice and data. I have performed all of the suggested things to no avail. HD voice is enabled on my line and I've tried taking it off and putting it back on. Enhanced LTE is set to on and I've toggled that. I've factory data reset. I've wiped cache. I've Tested SIM in another Verizon device and it works fine. I've Put another Verizon SIM in my device and still have the issue. I even gotten a new replacement device. I've sideloaded OTAs. I've flashed factory images. I've literally tried everything suggested here.
All said, I'm wondering if it's possible to flash the older 03.61 radio while keeping everything otherwise the same on my phone with stock Nougat-NRD90U.
I would appreciate input.
Thanks.
[email protected] said:
I'm New to the forums here everyone.
Greetings!
I'm running NRD90U but I'm experiencing some issues with the recent radio update that came with nougat on Verizon. I've searched everywhere on the xda forums and found suggestions to others experiencing similar issues (simultaneous voice and data). With the 03.61 radio, everything worked just fine whereas with 03.72 I have to toggle airplane mode after every reboot in order to have simultaneous voice and data. I have performed all of the suggested things to no avail. HD voice is enabled on my line and I've tried taking it off and putting it back on. Enhanced LTE is set to on and I've toggled that. I've factory data reset. I've wiped cache. I've Tested SIM in another Verizon device and it works fine. I've Put another Verizon SIM in my device and still have the issue. I even gotten a new replacement device. I've sideloaded OTAs. I've flashed factory images. I've literally tried everything suggested here.
All said, I'm wondering if it's possible to flash the older 03.61 radio while keeping everything otherwise the same on my phone with stock Nougat-NRD90U.
I would appreciate input.
Thanks.
Click to expand...
Click to collapse
If you are bootloader unlocked, you can fastboot flash any radio.img you want. If you are not bootloader unlocked, no you can't. The radio.img is universal btw, not specific to a carrier.
Edit: the guide below will help you unlock the bootloader and learn fastboot if you are unfamiliar.
http://forum.xda-developers.com/showthread.php?t=3206928
Sent from my Nexus 5X using Tapatalk
Thanks. I will do that. I appreciate the help.
Is this a problem for other Verizon users too? If so, I just won't upgrade the radio firmware on mine either.
I would highly suspect that the problem is for everybody on Verizon especially since I replaced my device and did all this SIM card changes and things. It is very unnoticeable in that the only time you experience it or see it is if you are making a call on the new nougat radio 03.72, you will see the LTE icon disappear as soon as you make your call, regardless of whether you are on an 'HD call' or not. If you are on the older radio 03.61 that is on marshmallow, then you never experience that problem, ever, ever. Everything is perfect with that "radio." I've done a lot of testing on it, as I said, up to replacing my device, all to no avail. unless using 03.61 which is again, perfect. I wouldn't change if you can avoid it. If you do get the nougat radio though (03.72), it's a nuisance because after the majority of reboots overall, you will come up with everything normal-'looking' with the LTE icon there but when trying to make a call it will disappear and you'll have an exclamation point there until you hang up from the call and LTE comes right back. (unless you're on wifi off course in which case none of this apples). The solution if you find yourself with the 03.72 nougat radio with this happening, is to toggle airplane mode and then you're good to go until the next time you have to reboot. I always check afterwards by calling voicemail to make sure the LTE icon stays while on the call. It will disappear immediately.
I'm going to assume there is some sort of an "initial-boot-handshake" that's not taking place correctly, but DOES communicate correctly coming out of airplane mode when the device is already booted.
Regards
Edit: This may be a regional VZW issue and not a phone or baseband issue.
Verizon has had issues where I live for more than a week.
I live in Northern Ca and they just sorted things out.
Funny, I flashed the Nougat radio on top of 6.x to see if my issue was fixed.
It's not the radio. Mine is finally stable. Not sure what VZW did.
tech_head
Everything was working fine on mine with the marshmallow radio. I didn't have an issue until I updated to nougat.
Hearing what happened with yours makes me think that it's a regional Verizon thing. Hopefully they will fix soon. I'm not holding my breath because it's been about a month here in Central Kentucky
I'm glad yours is working now man.
Cheers!
I'm having a similar problem for the last couple days after flashing the latest update. I may try stepping back to the older radio to see if that fixes my problem. I just hope it doesn't affect my bluetooth, as that's finally working fine again.
heffe2001 said:
I'm having a similar problem for the last couple days after flashing the latest update. I may try stepping back to the older radio to see if that fixes my problem. I just hope it doesn't affect my bluetooth, as that's finally working fine again.
Click to expand...
Click to collapse
Best of luck. Let us know how it goes if you get the chance. Thanks!
Holy crap, I thought it was just me! I did the exact same things (minus an RMA) as the OP to fix the issue with no luck, even downgrading to MTC20F and upgrading to MTC20L and finally Nougat, just to make sure something wasn't getting jacked in the flashing process. I spent an hour on the phone last night w/ a tier 2 tech guys from Verizon and the only issue he could see was that my PRL had an update for my SIM which should happen automatically. He pushed it through from their end but it didn't fix the issue. Normally I don't care about browsing/downloading when I'm on the phone since I hate talking on the phone and get off as soon as possible but it causes another problem which is not acceptable: if I am browsing chrome or doing anything with data, incoming calls go straight to voicemail. Tried switching the phone from "global" to "LTE/CDMA" with no luck-a reboot always kills simultaneous voice and data. I can rule out this being a Verizon issue on my end as when I flashed the MM images to update via OTA this morning, all worked perfectly fine.
Edit: I have called multiple people in my area that are on VZW after having them reboot their phones and all of them maintained simultaneous voice and data. I think it is safe to state that this issue is software/device specific.
bjoostema said:
Holy crap, I thought it was just me! I did the exact same things (minus an RMA) as the OP to fix the issue with no luck, even downgrading to MTC20F and upgrading to MTC20L and finally Nougat, just to make sure something wasn't getting jacked in the flashing process. I spent an hour on the phone last night w/ a tier 2 tech guys from Verizon and the only issue he could see was that my PRL had an update for my SIM which should happen automatically. He pushed it through from their end but it didn't fix the issue. Normally I don't care about browsing/downloading when I'm on the phone since I hate talking on the phone and get off as soon as possible but it causes another problem which is not acceptable: if I am browsing chrome or doing anything with data, incoming calls go straight to voicemail. Tried switching the phone from "global" to "LTE/CDMA" with no luck-a reboot always kills simultaneous voice and data. I can rule out this being a Verizon issue on my end as when I flashed the MM images to update via OTA this morning, all worked perfectly fine.
Edit: I have called multiple people in my area that are on VZW after having them reboot their phones and all of them maintained simultaneous voice and data. I think it is safe to state that this issue is software/device specific.
Click to expand...
Click to collapse
I have done and agree with what you said - other devices(non NEXUS 6p) work fine and 6p works fine on marshmallow. However, tech_head posted above that his I'd all good now and that it was a Verizon issue. I'm not sure where you live but based on tech_head's post, I can't rule out VZW as the problem. One thing is for sure it is an issue here in Central Kentucky on the two NEXUS 6ps that I have had and tried EVERYTHING, like you, on both of them to no avail without marshmallow radio. I haven't tried flashing marshmallow radio on top of nougat. I may just wait and see if VZW or Google work something out to fix it soon with a possible update. Not holding my breath but I believe it will eventually get fixed in the future, OFFICIALLY.
Thanks man.
I appreciate your input.
**
As mentioned earlier in the thread, the radio is independent of the OS version, so why not take 1 or 2 minutes and flash an earlier radio? There is a radio / modem repository thread on XDA with all versions you can just grab and try out. Literally takes less than a minute and if you don't like the results, then just flash it right back. I use Fastboot, but TWRP, FF, NRT, etc. all work equally well. You may also post what you find under "Phone Settings" when typing " *#*#4636#*#* " into the dialer. Report back on your findings.
Here are the screenshot links for my phone settings.
Thanks
OP
http://forum.xda-developers.com/attachment.php?attachmentid=3882483&stc=1&d=1474502181
http://forum.xda-developers.com/attachment.php?attachmentid=3882482&stc=1&d=1474502181
tech_head said:
Verizon has had issues where I live for more than a week.
I live in Northern Ca and they just sorted things out.
Funny, I flashed the Nougat radio on top of 6.x to see if my issue was fixed.
It's not the radio. Mine is finally stable. Not sure what VZW did.
Click to expand...
Click to collapse
Are You running stock nougat now. If so, what is your simultaneous voice and data status with respect to my post.
Thanks
OP
[email protected] said:
I have done and agree with what you said - other devices(non NEXUS 6p) work fine and 6p works fine on marshmallow. However, tech_head posted above that his I'd all good now and that it was a Verizon issue. I'm not sure where you live but based on tech_head's post, I can't rule out VZW as the problem. One thing is for sure it is an issue here in Central Kentucky on the two NEXUS 6ps that I have had and tried EVERYTHING, like you, on both of them to no avail without marshmallow radio. I haven't tried flashing marshmallow radio on top of nougat. I may just wait and see if VZW or Google work something out to fix it soon with a possible update. Not holding my breath but I believe it will eventually get fixed in the future, OFFICIALLY.
Thanks man.
I appreciate your input.
Click to expand...
Click to collapse
No problem bud! I haven't flashed another radio yet either. I will report back after I test a few more things.
Has anyone determined the cause of the problem? Was it the radio firmware after all? There seem to be conflicting answers here.
chaoticyeshua said:
Has anyone determined the cause of the problem? Was it the radio firmware after all? There seem to be conflicting answers here.
Click to expand...
Click to collapse
It is still kind of up in the air. What I do know is that there is a software incompatibility somewhere within nougat here in Lexington, KY, at least. I assume it's the radio software but I'm not certain. I'm not bootloader unlocked at this point so I haven't yet tried to flash marshmallow radio on to stock nougat. I will probably try this in a few days when I have the time to deal with the factory reset it involves. Please refer back to the original post for questions about my reasoning.
It's quite interesting, the problem, as everything with stock nougat - voice and data-wise, works just like marshmallow after I toggle airplane mode after reboot. With marshmallow, it just worked. Very weird. But given I can just toggle airplane mode 1 time for every time I boot, it's just a slight nuisance. Once I toggle airplane mode, everything is good just like marshmallow, as if nothing was ever wrong. It could be something about the boot sequence. It's very interesting. I'm open to ideas at this point.
Thanks.
My 2¢
When i was on 6.0.1 didn't have and issue with radio. i flashed the 7.0 radio while still on 6.0.1, still no issues.
Then i flashed 7.0 OS and that's when the issue started and it was only affecting upload speed download was great. Then i flashed the last radio from 6.0.1 and the issue went away.
P.S.
the data going off during a call is VZW. i had to call to have them fix this even before 7.0 they dont like the fact that we are using a non vzw branded cell.
I'm back on 6.0.1, never signed on to be a beta tester for 7.0?. These days its about profit and quantity and the hell with quality
Sent from my Nexus 6P using XDA-Developers mobile app
spjetrovic said:
My 2¢
When i was on 6.0.1 didn't have and issue with radio. i flashed the 7.0 radio while still on 6.0.1, still no issues.
Then i flashed 7.0 OS and that's when the issue started and it was only affecting upload speed download was great. Then i flashed the last radio from 6.0.1 and the issue went away.
P.S.
the data going off during a call is VZW. i had to call to have them fix this even before 7.0 they dont like the fact that we are using a non vzw branded cell.
I'm back on 6.0.1, never signed on to be a beta tester for 7.0?. These days its about profit and quantity and the hell with quality
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
I appreciate your input. It doesn't sound like our issues are quite the same. I'm not sure though.
What is it that Verizon did for you. That may be the answer to my problems.
Thanks. Best Regsrds.
Hi,
I have seen some posts here with lost cell connectivity. However my issue is slightly different and started to appear few weeks back. I was rooted running stock 7.1.1 OS with Franco kernel. My phone started to loose signal all the time. You can just look at the signal bar and see the signal strength going all the way from 100% to 0% in every few seconds. I have tried different radio versions, new ROMs, restoring my Nandroid backup etc. Nothing seems to work. Changing to 3g shows the same issue and I have no signal on 2g only mode. I am in AT&T.
Also wanted to add that I can make out going calls from my phone. The issue is when its idle. I don't get any incoming calls due to this issue.
Any help will be highly appreciated. Currently using my office iPhone and feels terrible.
amith007 said:
Hi, I have seen some posts here with lost cell connectivity. However my issue is slightly different and started to appear few weeks back. I was rooted running stock 7.1.1 OS with Franco kernel. My phone started to loose signal all the time. You can just look at the signal bar and see the signal strength going all the way from 100% to 0% in every few seconds. I have tried different radio versions, new ROMs, restoring my Nandroid backup etc. Nothing seems to work. Changing to 3g shows the same issue and I have no signal on 2g only mode. I am in AT&T. Also wanted to add that I can make out going calls from my phone. The issue is when its idle. I don't get any incoming calls due to this issue. Any help will be highly appreciated. Currently using my office iPhone and feels terrible.
Click to expand...
Click to collapse
I'd run up to AT&T and ask for a new SIM. It's free and you rule out something on their end, and the SIM too when they provision it. Is your phone carrier (SIM) locked to AT&T? If so, I'd see about getting it unlocked so you can test other carriers. If already carrier unlocked have you tried borrowing a friends SIM on another network? If signal continues to drop it could be a hardware issue.
v12xke said:
I'd run up to AT&T and ask for a new SIM. It's free and you rule out something on their end, and the SIM too when they provision it. Is your phone carrier (SIM) locked to AT&T? If so, I'd see about getting it unlocked so you can test other carriers. If already carrier unlocked have you tried borrowing a friends SIM on another network? If signal continues to drop it could be a hardware issue.
Click to expand...
Click to collapse
I have tried with another sim. The issue still persist. Also I have tried my sim on a new device and it seems to work fine. So I am almost certain that the issue is with my phone. All I wonder is whether its hardware or software.
amith007 said:
I have tried with another sim. The issue still persist. Also I have tried my sim on a new device and it seems to work fine. So I am almost certain that the issue is with my phone. All I wonder is whether its hardware or software.
Click to expand...
Click to collapse
You sound proficient enough with flashing ROMS, radios, restoring Nandroids to know this already.... you are probably just postponing the inevitable: Back up and pull off all your data, format the partitions, and flash the latest full factory image from your PC using flash-all.bat. You will have your answer very quickly- in fact you will know even before you begin to set up your phone. If you are still under warranty this will be step number one with Google or Huawei.
v12xke said:
You sound proficient enough with flashing ROMS, radios, restoring Nandroids to know this already.... you are probably just postponing the inevitable: Back up and pull off all your data, format the partitions, and flash the latest full factory image from your PC using flash-all.bat. You will have your answer very quickly- in fact you will know even before you begin to set up your phone. If you are still under warranty this will be step number one with Google or Huawei.
Click to expand...
Click to collapse
My Nandroid backup was actually a vanilla 7.0 image. I will give this a try with the flash-all.bat and update here
Any update?
Wow, seeing that this is quite the phenomena. It seems everyone has this in some form since that December update
I'll skip the small talk because this issue is widespread enough... here's what HASN'T worked
- *#*#4636#*#* (Trying to use "Phone information" leads me immediately to "this application does not work on this device")
- Taking out SIM and battery for 30min
- Swapping SIM
- Factory Reset
- Praying that anyone at T-Mobile has attained a level higher than "Totally clueless"
- Praying that anyone at LG would provide a working solution
- Dialing ##UPDATE# (Afaik, this only works on Sprint)
- Five hours of googling
As it stands, I'm stuck with a phone that's awesome at doing everything but being a phone. Apparently I can flash a radio file... but I haven't the slightest idea how to do any of that.
Any idea how to fix this?
*UPDATE* looking into the dirtysanta method of flashing the modem.img, it appears that's not even an option for the T-Mobile variant.
Sounds like LG's solution is to have you send it in... I've already seen other users go through that and end up having their phone hostage for a $21 diagnostic or a $378 proposed HARDWARE fix for a SOFTWARE problem _they_ caused.
While I personally have had good experiences with LG in the past, looking into this really kicked the hornet's nest on others who've had this issue. Many coming from the V10 who were told a V20 would save them from this.
Sounds like it's time to sick the social media beast on a company to make them stop being shady.
I have a tmobile v20 and I have not had any issues with service and I have not seen much on the forums. What issue are you having exactly? Were you rooted? Any errors besides no service?
darkknight1812 said:
I have a tmobile v20 and I have not had any issues with service and I have not seen much on the forums. What issue are you having exactly? Were you rooted? Any errors besides no service?
Click to expand...
Click to collapse
Basically that's it. Phone worked perfectly, did an OTA update, and now it's like my cellular radio just doesn't work at all. Which means I now have a WiFi only media player that can't make calls, SMS, MMS or utilize cellular data.
Goes straight to "no service". I can go under Network settings and it displays that my phone's radio is off. T-Mobile rep confirmed that my SIM didn't shoot craps, and that none of theirs work in this phone either. They actually showed that the phone was even detecting my SIM by showing me that it's picking up my phone number.
Surprised you aren't hearing about this, I'm seeing this reported all over the place. This is just a couple of links. Been going at this all since the OTA hit me at 6PM yesterday.
https://community.giffgaff.com/t5/Help-Support/LG-V20-No-Service-after-update/td-p/21190404
https://forum.xda-developers.com/v20/how-to/guide-us996-service-radio-off-ota-kdz-t3727126
https://forum.xda-developers.com/v20/help/lg-v20-us996-radio-off-security-update-t3718507
https://forum.xda-developers.com/v20/help/lg-v20-us996-network-radio-button-off-t3727986
An XDA user sent his in, and ended up having to either pay a $21 diagnostic fee, or pay $400 for them to shove a bunch of aftermarket parts in his phone (which is insane given that the only thing between the phone features working and not working was an OTA).
Have you tried reflashing a kdz? It is possible that something happened during the update. Make sure you flash a kdz with the same anti rollback number (most likely 1 if it took the recent ota). I believe the patched LGUP can flash just the modem partition.
Yeah. I heard about this. For the other xda user, he had purchased a refurbished device from a third party seller of some sort. Some where along the way the internal parts (motherboard) were replaced with cheap knock offs. LG flagged the phone for having non-LG parts inside. The upgraded firmware didn't play nice with the hardware, since it wasnt built to LG's specifications. Anyways not entirely LG's fault on that. A kdz could help but I doubt it will do anything. For people who have lost radio functions entirely to just a simple ota, most of them have had to get hardware replaced to fix. All around bummer. Hopefully lgup can bring it to life.
I'm having a similar issue and can say that for us with ARB=1 (i.e those with the Security Patch past 01/01/18) aren't going to find salvation this way
It's coincidental this thread popped up, because I'm trying to diagnose a similar nature as well. I've been swapping out parts and testing to see what's going on as part of my phone repair. After swapping between different plastic bumpers (this is the antenna bumpers). I can say this is not a hardware issue for us DIY'ers. I've taken the picture in the Settings > About Phone > Network to show that my antenna signal is just as normal without a SIM inserted. (Picture 1). I believe this is not an IMEI issue because it comes up clean for both ESN and Tmobile's side. If it was a blacklisted phone, then I shouldn't be able to connect to Wifi Calling. However, multiple instances: I've gotten a Notification from Call Services yet still able to call/sms test but only with Wifi Calling enabled; which reinforces the observation that this isn't hardware-related. (Picture 2).
LTE Discovery confirms a working radio, as the EARFCN information populates with connecting cell tower activity that's typical of SIM activity; with the sole exception of my Data/Voice Network Types coming up UNKNOWN (Picture 3). MCC+MNC Information proves our phones are talking to Tmobile, at the least, which further shows this being less of a hardware issue. I've KDZ'd my phone with LGUP as far back as 10P to no success.
If there is a problem relating to OTAs; someone else has to investigate before the ARB = 1(Anti-RollBack) to discover more information. Those of us on 10P aren't allowed to test out previous modems due to our bootloaders; which incidentally is all of us with this No Service problems. Ack!
texasaggie1 said:
.....
.....
10p Warnings based on what we know:
WARNING #1 You must flash the 10p modem and bootloader for this to work. If you don't you will soft brick.
WARNING #2 Once you go to 10p modem and bootloader you can't go back to previous versions. If you try you will HARD brick your device.
WARNING #3 10P rom only works with 10p modem and 10p bootloader. Any other combo SOFT bricks.
WARNING #4 TWRP backups of previous versions will not restore correctly once you are on 10p. When you restore a previous version (10k and before) you will soft brick. You can unbrick by just installing the 10p ROM, modem, and bootloader over the top of your restore *****Restores and Backups of 10p roms work just fine.
BOTTOM LINE: Going to 10p is a TOTAL commitment and there probably will never be a way to go back. That said, I'm on 10p and so far it works great.
https://forum.xda-developers.com/v20/development/rom-10p-debloated-rom-beta-flashable-zip-t3656616
Click to expand...
Click to collapse
Same sentiments can also be verified here as well..
[FIRMWARE] [H918] [10p] [10k] [10j] [10i] [10d] TWRP Flashable Bootloader and Modem
I'm having problems with a VS995. Bought it new on ebay, received it today 10/27/2018. I did get signal, then upgraded via phone software update, but it failed, and failed, and failed. so i used the verizon software via pc. Successfully upgraded to 7. then NO SIGNAL. so i updated via phone, but the download kept disconnecting. so i downloaded the 8 bin, upgraded via LGUP, success. Still NO SIGNAL. =( . Returning the phone now. buying a used one, might be better.
Was this problem solved? Because I have the same thing, radio off & really slow charge (phone has to be off in order to charge, when on the battery drains faster than it charges). I've flashed 10p with lgup & it's the same thing, right now I'm rooted with TWRP recovery, Magisk & the H91810u rom. I've done factory reset, flashed modem zip file, installed a network app that trys to manually start the radio (radio on) but it fails & stays "radio off". Any suggestions would be greatly appreciated, I'm almost ready to give up on this thing.
mgzavala said:
Was this problem solved? Because I have the same thing, radio off & really slow charge (phone has to be off in order to charge, when on the battery drains faster than it charges). I've flashed 10p with lgup & it's the same thing, right now I'm rooted with TWRP recovery, Magisk & the H91810u rom. I've done factory reset, flashed modem zip file, installed a network app that trys to manually start the radio (radio on) but it fails & stays "radio off". Any suggestions would be greatly appreciated, I'm almost ready to give up on this thing.
Click to expand...
Click to collapse
If you read you'd know it wasn't, as stated by earlier posters the only fix is to send to LG for repair, you probably got one of those knock off phones
Sent from my LG-H910 using XDA Labs
cnjax said:
If you read you'd know it wasn't, as stated by earlier posters the only fix is to send to LG for repair, you probably got one of those knock off phones
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
How could that be this phone was bought from T-Mobile, I would doubt that they would pull a stunt like that. And wouldn't it have had the same problem before when I rooted the first time? Or am I missing something here?
mgzavala said:
How could that be this phone was bought from T-Mobile, I would doubt that they would pull a stunt like that. And wouldn't it have had the same problem before when I rooted the first time? Or am I missing something here?
Click to expand...
Click to collapse
Return it to, Tmobile, or send it LG to be repaired, scrap it and buy a new phone.
Sent from my LG-H910 using XDA Labs
Here on my LG V50 ThinQ am having same issue after an OTA update which lasted for like 4 days, I've kdz'ed my phone with different variant of the LG V50 stock ROM even has to crossflash to an EU stock ROM yet no way and i can say for sure it's no hardware issue but rather LG been messed up somehow
I recently moved to the 6T from a 3XL because of several hardware issues with that device. So far this device has been a beast. After spending about a week with it, I have a few questions I'm hoping some of you can answer for me!
1. I noticed the lock screen reverts night light if enabled, so the fingerprint scanner can work efficiently. Just wondering if there is any way night light can remain on during the lock screen/fingerprint scan? Or is this impossible because will it impact success rate of fingerprint unlocks?
2. Because of the lack of fingerprint scanner on custom ROMs, I've decided to stay on OOS. This is a long shot but is there any way Substratum overlays can be shown without having to reboot? It's a bit of a hassle to build and update overlays, reboot, apply them, and reboot for full changes to take effect.
3. I don't know if this one is by design, but I noticed my display will wake during calls - if the lift to wake display option is enabled. Anyone else have this issue and know of a fix (other than disabling lift to wake)?
4. My notification bar is tough to pull down while I'm in a call. The only way to get it down is if I drag my finger almost all the way down the screen. Is this also by design?
5. Another call-related issue - sometimes people will tell me they can hear their own voice during a call. Has anyone else experienced this?
6. I'm in Canada with Fido, and OnePlus ensured me VoLTE and VoWiFi will both be an option for me since the device is "globally unified". I'm not seeing any VoLTE icon during calls. I've tried the dialer key combo and enabling VoLTE there, as well as the VoEnabler Magisk Module. Neither of those seem to result in a VoLTE icon. Could anyone confirm if it's just not possible with Fido in Canada, or maybe another solution is out there?
7. This one seems a bit more widespread - some apps using the wrong mic during audio/video records. I've only experienced this in making a video in WhatsApp so far, and I'm wondering if anyone knows of a fix? Or do we just need to wait for OnePlus to come out with an update? Or, do the apps themselves need to be updated to better work with the 6T?
I apologize for so many questions, but if any of you could even answer some, if not all of these questions, I would greatly appreciate it! And I also apologize if some of these questions have already been addressed in previous threads.
Interesting post... Will subscribe because I have experienced some of the issues mentioned. I am also on my first week of use.
Sent from my ONEPLUS A6013 using Tapatalk
@rickysidhu_
1. I'm pretty sure this is by design and it's supposed to be that way. When there were early builds of Havoc for the 6T, some users got FP to work on an all white background with the brightness all the way up. So I'm assuming it's so it can read your fingerprint.
2. Sadly, not that I know of. Swift Installer is the same way. Apply overlays, reboot, reboot again to finish themeing.
3. Due to the notch being a teardrop design, there's little space to pack every sensor into the notch. Happens to me all the time when on a call. I'm pretty sure it's because of the proximity sensor. Once you move the phone from your face just a tad, the screen kicks on. No fix that I know of, yet.
4. Again, proximity sensor I'm assuming. Haven't really tested this too extensively mainly because if I have to use my phone for anything while in a call, I'll put it on speakerphone and use it.
5. I haven't heard anything from the other person. However, I do sometimes hear myself like an echo when talking to someone.
6. I have the T-Mobile variant of the device and immediately switched to International firmware as soon as I got the device, can't remember if it showed those icons or not when I was running the T-Mobile branded software, I do have VoLTE and VoWiFi icons on International firmware.
7. Haven't had this issue since I don't use WhatsApp. I do not seem to have the problem when making calls via Facebook Messenger. It's a known problem since the 6 and OnePlus knows about it, they just haven't issued a fix yet. Sorry I can't be more help with this.
GLHF.
TheKnux said:
@rickysidhu_
1. I'm pretty sure this is by design and it's supposed to be that way. When there were early builds of Havoc for the 6T, some users got FP to work on an all white background with the brightness all the way up. So I'm assuming it's so it can read your fingerprint.
2. Sadly, not that I know of. Swift Installer is the same way. Apply overlays, reboot, reboot again to finish themeing.
3. Due to the notch being a teardrop design, there's little space to pack every sensor into the notch. Happens to me all the time when on a call. I'm pretty sure it's because of the proximity sensor. Once you move the phone from your face just a tad, the screen kicks on. No fix that I know of, yet.
4. Again, proximity sensor I'm assuming. Haven't really tested this too extensively mainly because if I have to use my phone for anything while in a call, I'll put it on speakerphone and use it.
5. I haven't heard anything from the other person. However, I do sometimes hear myself like an echo when talking to someone.
6. I have the T-Mobile variant of the device and immediately switched to International firmware as soon as I got the device, can't remember if it showed those icons or not when I was running the T-Mobile branded software, I do have VoLTE and VoWiFi icons on International firmware.
7. Haven't had this issue since I don't use WhatsApp. I do not seem to have the problem when making calls via Facebook Messenger. It's a known problem since the 6 and OnePlus knows about it, they just haven't issued a fix yet. Sorry I can't be more help with this.
GLHF.
Click to expand...
Click to collapse
I really appreciate you taking the time to reply to all my questions! Very kind of you.
As for the VoLTE stuff, maybe I'll continue to do more digging since you say you're seeing the icon but I'm not. That tells me VoLTE is not properly enabled on my device (I assume). Thanks again, much appreciated :highfive:
I can't find it, but there are several threads on enabling VoLTE & VoWIFI.
One involves entering the hidden menu, via *#808#, then toggling the appropriate settings.
That's what I did (USA version). I was on the 9.07 firmware, which didn't support it, but VoLTE
popped up and started working, when the 9.11 version hit.
rickysidhu_ said:
I really appreciate you taking the time to reply to all my questions! Very kind of you.
As for the VoLTE stuff, maybe I'll continue to do more digging since you say you're saying the icon but I'm not. That tells me VoLTE is not properly enabled on my device (I assume). Thanks again, much appreciated :highfive:
Click to expand...
Click to collapse
You are very welcome. You may want to try using the MSM Tool found here. https://forum.xda-developers.com/oneplus-6t/how-to/t-mobile-6t-to-international-t3888307
That's should fix some problems you may be having, especially the VoLTE and VoWiFi issues. I know you're not using the T-Mobile version of the phone, so I'm not sure if this will help you much or not, but a MSM Tool that's meant for your device should work.
OP, I have enabled volte on op6t on Rogers. Fido should work, too. It seems nobody enables WiFi calling on op6t in Canada.
https://forum.xda-developers.com/on...-volte-vowifi-german-carriers-t3817542/page75
Sent from my SM-G935W8 using Tapatalk
p51d007 said:
I can't find it, but there are several threads on enabling VoLTE & VoWIFI.
One involves entering the hidden menu, via *#808#, then toggling the appropriate settings.
That's what I did (USA version). I was on the 9.07 firmware, which didn't support it, but VoLTE
popped up and started working, when the 9.11 version hit.
Click to expand...
Click to collapse
ma678 said:
OP, I have enabled volte on op6t on Rogers. Fido should work, too. It seems nobody enables WiFi calling on op6t in Canada.
https://forum.xda-developers.com/on...-volte-vowifi-german-carriers-t3817542/page75
Click to expand...
Click to collapse
Gave both of these a try and still don't see the volte icon. It's hard to tell if it's enabled even though the icon isn't showing.
I appreciate both your guys' responses though! I didn't know about these additional menus!!
I have the T-Mobile version on T-Mobile and also don't see the VOLTE icon, but if I go to Settings/About Phone/SIM Status, it shows Mobile voice network type LTE. I assume that means VOLTE is enabled.
Telyx said:
I have the T-Mobile version on T-Mobile and also don't see the VOLTE icon, but if I go to Settings/About Phone/SIM Status, it shows Mobile voice network type LTE. I assume that means VOLTE is enabled.
Click to expand...
Click to collapse
I'm in the US and I have TMobile as my carrier, and both of VoLTE/VoWiFi enabled by default
Looks like you have the International version of the OP6T. My T-Mobile version doesn't have the Enhanced Communications section in Settings/Wi-Fi & internet/SIM & network and I don't see an Icon Manager screen anywhere either, though I have the WiFi Calling switch.
Telyx said:
Looks like you have the International version of the OP6T. My T-Mobile version doesn't have the Enhanced Communications section in Settings/Wi-Fi & internet/SIM & network and I don't see an Icon Manager screen anywhere either, though I have the WiFi Calling switch.
Click to expand...
Click to collapse
Mine is TMobile version but I converted it to OOS using this tool: https://forum.xda-developers.com/oneplus-6t/how-to/t-mobile-6t-to-international-t3888307 in case you're interested.
I've read about that but after rooting/custom ROMing just about every Android device I've ever had (up to the ZTE Blade V8 Pro, anyway), I just don't have the inclination to do it with this phone. Everything works and VoLTE is enabled by default, so I'm fine with that.
I've tried to enable as much as I could (full port switch, VoLTE provisioning, enabled in settings) and still don't see the icon.
Very strange and at this point I'm almost prepared to just accept I won't see that icon lol
Telyx said:
I've read about that but after rooting/custom ROMing just about every Android device I've ever had (up to the ZTE Blade V8 Pro, anyway), I just don't have the inclination to do it with this phone. Everything works and VoLTE is enabled by default, so I'm fine with that.
Click to expand...
Click to collapse
I hear ya! I quit rooting since I got the Essential phone. Android stock rom now a days much better so I don't need root either. I just converted this phone so I can use the dual SIM cards and faster updates rather than waiting for TMO.
After making some videos via WhatsApp and Snapchat, my question #7 is starting to become a bigger issue than enabling VoLTE/WiFi
It's very obvious the wrong mic is being used during video records because the audio just sounds terrible.
Seems like a widespread issue since there are many articles about it. Is there any known fix out there for us rooted users?