Jump to content

Current Sprint PRLs


halcyoncmdr

Recommended Posts

This also happened to me for both my iPhone 5s & my sister's iPhone 5. Neither of them even scan for LTE anymore.

Yep, 606xx just sounds like an old legacy non LTE PRL to me. Maybe I should let Sprintcare know on Twitter? They will fix it!

 

Let's try this again but without the oops.

  • Like 1
Link to comment
Share on other sites

This also happened to me for both my iPhone 5s & my sister's iPhone 5. Neither of them even scan for LTE anymore.

I'm also on that PRL on my iPhone 5 and I'm not getting LTE anymore either. Must be like digiblur said and it's just a legacy non-LTE PRL.
Link to comment
Share on other sites

Yep, 606xx just sounds like an old legacy non LTE PRL to me. Maybe I should let Sprintcare know on Twitter? They will fix it!

 

Let's try this again but without the oops.

 

Please do! My EVO Shift was on 60651 until I activated it on Ting about 2 weeks ago, so 60657 is definitely a non LTE PRL.

Link to comment
Share on other sites

Please do! My EVO Shift was on 60651 until I activated it on Ting about 2 weeks ago, so 60657 is definitely a non LTE PRL.

I will quote myself again... I would have a better chance at tweeting Obama to get the space shuttle flying again than I would with Sprintcare fixing an issue.

 

Their hands are tied to looking up NV forecasts and telling you how to do a PRL update to get better coverage.

 

Email Dan@sprint, works much better.

 

  • Like 2
Link to comment
Share on other sites

Now you guys got me thinking... LTE started working at work this afternoon. I was getting 2 megabit downloads instead of 1x speeds. Bet this had something to do with it.

 

You should start peddling non-LTE PRLs to all of your friends and neighbors down there, soon enough you'll have the entire network to yourself! ;)

 

-Mike

  • Like 6
Link to comment
Share on other sites

Anyway the prl was updated or someone just push the wrong one?

 

Sent from my HTC0P3P7 using Tapatalk

I think digi is hinting at the iPhone causing issues with Sprint's LTE network, so they're pushing out a non-LTE PRL? If it's from 4 years ago that means it's also pre SMR; maybe that has something to do with it?

Link to comment
Share on other sites

There has to be some sort of jackass reasoning to pushing a non-LTE prl to phones on their network, rendering thousands of devices "blocked" from accessing LTE. A balsy testing process for something? Or, the worst mistake they've ever made.

  • Like 1
Link to comment
Share on other sites

There has to be some sort of jackass reasoning to pushing a non-LTE prl to phones on their network, rendering thousands of devices "blocked" from accessing LTE. A balsy testing process for something? Or, the worst mistake they've ever made.

 

I've sent up a flare.... let's see what happens.  Will keep you posted!

  • Like 6
Link to comment
Share on other sites

 Here is what I posted in one of the threads in the Apple/iPhone/iOS section:

I have tried to update today also, because it seems that 60657 also doesn't allow roaming, considering I'm at school where I always get 5 bars of Extended 1x/3G on my iPhone 5 but right now I am currently getting "No Service" and "Searching" constantly :td::wall:

Kind of frustrated that I can only receive iMessages and can't receive any texts do to having no roaming capability for what I assume is this prl's fault. Hopefully Sprint will get this fixed.

Link to comment
Share on other sites

I look at it this way, there's finally a benefit to living in Cleveland - since we hardly have LTE or 800 anywhere in our market (near me anyway) I'm not missing out on anything sitting here on 60657. Hey, I just like the drama....there haven't been any major updates in my area so at least I have something to get excited about now!

Link to comment
Share on other sites

I've logged an official ticket with Sprint. The customer service rep couldn't get her head around why Sprint would offer a 4 year old PRL for an update.

 

I suggest everybody do the same.

Will do once I get home from school :tu:

  • Like 1
Link to comment
Share on other sites

My Nexus 5 was updated to 60657 when I was connected to a tower around Shawnee Mission PKWY and Metcalf in Kansas City. I was still connected to LTE. When I got home and read about LTE issues on this PRL, I updated again and it went to 55017. That would be when I was connected to a tower on 60th and Roe. Maybe this helps.

 

Sent from my Nexus 5 using Tapatalk

 

 

Link to comment
Share on other sites

If you guys still have 60657 after hitting PRL update on your devices please call into sprint or send an email to dan@sprint.com explaining you received a 60657 PRL update version automatically on your device and now your LTE does not work anymore.  Be sure to include your name and Sprint phone number when sending that email so they can contact you. 

  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Similar Content

  • Posts

    • Since this is kind of the general chat thread, I have to share this humorous story (at least it is to me): Since around February/March of this year, my S22U has been an absolute pain to charge. USB-C cables would immediately fall out and it progressively got worse and worse until it often took me a number of minutes to get the angle of the cable juuuussst right to get charging to occur at all (not exaggerating). The connection was so weak that even walking heavily could cause the cable to disconnect. I tried cleaning out the port with a stable, a paperclip, etc. Some dust/lint/dirt came out but the connection didn't improve one bit. Needless to say, this was a MONSTER headache and had me hating this phone. I just didn't have the finances right now for a replacement.  Which brings us to the night before last. I am angry as hell because I had spent five minutes trying to get this phone to charge and failed. I am looking in the port and I notice it doesn't look right. The walls look rough and, using a staple, the back and walls feel REALLY rough and very hard. I get some lint/dust out with the staple and it improves charging in the sense I can get it to charge but it doesn't remove any of the hard stuff. It's late and it's charging, so that's enough for now. I decide it's time to see if that hard stuff is part of the connector or not. More aggressive methods are needed! I work in a biochem lab and we have a lot of different sizes of disposable needles available. So, yesterday morning, while in the lab I grab a few different sizes of needles between 26AWG and 31 AWG. When I got home, I got to work and start probing the connector with the 26 AWG and 31 AWG needle. The stuff feels extremely hard, almost like it was part of the connector, but a bit does break off. Under examination of the bit, it's almost sandy with dust/lint embedded in it. It's not part of the connector but instead some sort of rock-hard crap! That's when I remember that I had done some rock hounding at the end of last year and in January. This involved lots of digging in very sandy/dusty soils; soils which bare more than a passing resemblance to the crap in the connector. We have our answer, this debris is basically compacted/cemented rock dust. Over time, moisture in the area combined with the compression from inserting the USB-C connector had turned it into cement. I start going nuts chiseling away at it with the 26 AWG needle. After about 5-10 minutes of constant chiseling and scraping with the 26AWG and 31AWG needles, I see the first signs of metal at the back of the connector. So it is metal around the outsides! Another 5 minutes of work and I have scraped away pretty much all of the crap in the connector. A few finishing passes with the 31AWG needle, a blast of compressed air, and it is time to see if this helped any. I plug my regular USB-C cable and holy crap it clicks into place; it hasn't done that since February! I pick up the phone and the cable has actually latched! The connector works pretty much like it did over a year ago, it's almost like having a brand new phone!
    • That's odd, they are usually almost lock step with TMO. I forgot to mention this also includes the September Security Update.
    • 417.55 MB September security update just downloaded here for S24+ unlocked   Edit:  after Sept security update install, checked and found a 13MB GP System update as well.  Still showing August 1st there however. 
    • T-Mobile is selling the rest of the 3.45GHz spectrum to Columbia Capital.  
    • Still nothing for my AT&T and Visible phones.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...