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
Okay, so, yes, I know to use the Search function, but alas all information is either outdated or there is no concise answers / solutions to be found. Trust me, I have scoured.
Overview: Okay so Thursday I bought an SGH-i337, being the nerd that I am knowing that I use MetroPCS (can't beat unlimited 4G LTE for $60) I scoured the net and researched ALL models of the S4 and G3. Decided the screen size of the G3 too big coming from a 5C. Decided Sprint's version might work, but not on 4G. Verizon, would switch from LTE to 2G with no 3G support, so that would be a desperation act, haha.
So, my main options were T-Mobile, then AT&T, because MetroPCS and T-Mobile were one and the same. All the people that had T-Mobile based phone sellers were being a pain in the butt to deal with... so, I found an AT&T owner that was ready.
The tragic love story: So on once I used the MicroSIM card in the S4 to cut an old full-size SIM to scale a border around my Nano SIM and finally got it placed perfectly to read... I was happy... which faded quickly as it was locked, how could I be so dumb!
So, the previous owner is now awaiting an unlock code as I found EVERY method to use the UMTS Menu is impossible to get to "[6] Phone Control" option. Due to that silly Auto Updating AT&T bloatware and Kernel upgrade/Firmware.
Okay, I should wait, but... does anyone know a way to get to the Phone Control menu using a secret code?? I have noticed some of the many codes go straight to the Debug Screen or go straight to the other menu options... so could there be one for Phone Control?
Also, maybe is there a way to get the phone to output the NCK Key manually connecting it to a computer and using a prompt? I may have heard about such a thing on SureWest routers through TelNet, to get the administration password... not that I personally have done this. Just feel like if these websites are able to use an IMEI number to charge you for a code... it has to be stored on the phone somewhere right?
Rooting and Downgrading
Also, has anyone tried the Odin way of downgrading and rooting these phones, has personally worked for them? I have found the threads on here and it seems pretty interesting... when I look at previous versions of Droid they look to allow more functionality for more advanced users than this 5.0, so if that be the case I am interested in taking this back to stock and beginning removal of all AT&T programs.
Maybe I am sounding like an idiot, but I have been on a Jailbroken 5C for... probably 2 years now and even with that it seems limiting to the curious, nerdy, mess with things side of me.
Summary:
- Should I just wait the 2-5 days for the code? / Would downgrading firmwares negate the entered NCK code if used prior to downgrade?
- Are there any known ways to unlock this model fully upgraded?
- Should I use the Odin methods of downgrading to stock? / Do you prefer previous versions over 5.0?
- What problems should have you guys faced / should I consider prior to doing anything?
- Should I just try to find a T-Mobile model of the S4??
Phew, sorry, if you read all of that and hate me for it, haha. Please, be knowledgable and not tell me how dumb I am for being so antsy to be able to use this phone w/o WiFi! Haha, you guys try using a 5C forever and see the screen difference / abilities you've been missing out on for so long!
Thanks!
The method of downgrading to 4.4.2 (aka NB1) then rooting and then going to lollipop by keeping the root has worked for me. There is no direct way, to root lollipop atm.
First downgrade to stock rootable 4.4.2. You can do this from any base, and/or use it if you mess your phone up (bootloops, etc). Link here. Second post on that thread, step 1. Make sure you download the rootable one.
To root it use TowelRoot. Run it - Tap make it ra1n - After a succeseful root, install SuperSU.
The follow this post here to goto stock rooted lollipop 5.0.1 (aka OC4). I recommend downloading the deodexed version, so you can install xposed if you want in the future.
Thats it for rooting lollipop. And now that you have root you can get rid of that bloatware.
-------------------------------------------------------------------
I personally, don't really fancy lollipop. High Ram usage.
Secondly, i bought this phone on eBay and it came unlocked, and even after flashing different firmwares, its still unlocked. I think if you unlock using that NCK code, the phone will stay unlocked forever.
Thirdly, the T-Mobile version has an unlocked bootloader, which is a big up in comparison to the i337. We are restriced to only using one costum recovery, that is SafeStrap. Others, don't work.
Thank you
I will probably have to go through that whole process. Got it unlocked thankfully, but am feeling as though based on specs and the little apps I have installed the phone should be a bit smoother in basic functionality especially Web browsing.
So yeah definitely already feeling your point in resource hog and though I disabled the bloatware, I don't think it helps being installed.
Also, figuring out after using the phone in my car that Galaxy has very quiet audio output via the 1/8" headphone jack. Seems that you can find volume controlled headphones easier than just straight cords! However, found this a known issue for all Galaxies and rooting it may be the easiest workaround.
Thanks for the organized list of information/insight! Now I will have some more stuff to geek out on... ?
Peptobismal said:
Also, figuring out after using the phone in my car that Galaxy has very quiet audio output via the 1/8" headphone jack. Seems that you can find volume controlled headphones easier than just straight cords! However, found this a known issue for all Galaxies and rooting it may be the easiest workaround.
Thanks for the organized list of information/insight! Now I will have some more stuff to geek out on...
Click to expand...
Click to collapse
You're welcome
I don't know, but cranking the volume to full on my phone using earphones, makes my ears hurt . The audio output on mine is great, nothing modified.
Oh, if you decide to stick with kitkat, check out these posts. I'm sure they will come in handy for stock roms. Simply to make life easier.
Remove AT&T carrier name from the notification bar
Restore Mobile Data Toggle in Notifications Bar (First method - apk on third post)
TheJuli said:
You're welcome
I don't know, but cranking the volume to full on my phone using earphones, makes my ears hurt . The audio output on mine is great
Click to expand...
Click to collapse
Yeah, I'd say it's probably fine with headphones, but through a car's auxiliary it is probably 25-30% quieter than my iPhone even at "full" volume.
Read that there are files to modify, but you have to be rooted.
What is this Mobile Data Toggle? Would it be really at all useful seeing as I have MetroPCS? * I assume that ridding AT&T is just a general tweak, which I do like getting rid of the carrier.
Peptobismal said:
What is this Mobile Data Toggle? Would it be really at all useful seeing as I have MetroPCS? * I assume that ridding AT&T is just a general tweak, which I do like getting rid of the carrier.
Click to expand...
Click to collapse
Mobile data toggle is used to enable Internet from your carrier/sim. Ridding the AT&T thing is sorta general because you need to have root.
Im a long time reader first time poster... i first want to thank everyone here for finding the time and patience to help others by sharing your knowledge ideas and expertise, This is by far the best resource for trustworthy information for Android on the Web. I've been able to help my loved ones and myself by using information i found here through the years and so for that I sincerely thank all of you.
Now onto the issue at hand. .
I have a cricket wireless Samsung sgh-i337z 4.4.2 i337ztuuboa3 I first
Soft rooted with kingoroot, but later i was able to full root using towel root.
No issues until about maybe a month ago when messages i was sending sometimes wouldn't go through until 3 or 4 tries. Its getting progressively worse, to where now have trouble sending emails occasionally also. Keeping the messaging cache cleared is the only way I've found to send them, still not until the 2nd or 3rd or 4th try. . Installed a different messaging app, same thing. It's not a weak signal thing, I've deleted all unneeded stored messages, and I'm not sure what to do next. it's starting to make me crazy. I send a text it goes thru, send another then go about my business, wonder why I never got a response till I pick up my phone an hour later and see that damn failed notification again. It's maddening i tell you! Could it be a network problem because I haven't updated past kitkat? Or is there something else I'm not seeing? I wanted to ask before jumping in trying to update to lollipop, as I am still unable to connect and use adb and I'm guessing updating and keeping root probably won't be like a click 1 and done thing on top of it also wiping my phone, seems like fun all around. I'm open to any feedback and appreciate any help/ advice given....
Thanks so much for all you do and I hope you have a great day!
Well mate, I don't think its a problem to do with you not being on Kitkat, but have you considered factory resetting or talking to your carrier?
I had that problem regularly on my i337 running Hyperdrive RLS 19 which was Android KitKat 4.4.2 but created from a ROM that was originally on Verizon's CDMA network. I found that when I was on Wi-Fi, most of the time my MMS would send about 50% of the time and regular texts would send about 90% of the time. When I shut off wi-fi and used AT&T's network exclusively they sent with a much greater reliability, MMS closer to 90% and normal texts around 100%. My guess is that, since Cricket is switching to AT&T's GSM infrastructure from years of being on a CDMA (Verizon) there is some issue in the hand-off from a CDMA rom that doesn't translate right to the GSM network. What that might be, I couldn't say because I just don't have the background or knowledge (and good luck explaining that to a Cricket rep), but I think I'm right as the the cause at least. That being said, if there is a newer ROM that can be flashed on your phone, or even the same one over with the modems, I'd do it to see if it would fix the issue. I finally flashed my i337 to a stock GSM ROM and it resolved the problem.