Jump to content

PRL 602 Error


Marv1

Recommended Posts

I've been getting this error frequently lately, especially when being in an LTE location most of the day due to work. When I leave, and go into a 3G network, and want to browse the internet, I have no data connection to browse, even though I still see the 3G icon, and SignalCheck Pro shows there is a network connection. It's getting frustating! I reset my phone off and on, and still get this error.

 

At home connecting to WiFi, I don't this error. Being in a 3G network at home, the next day is fine until I leave work, and back into this 602 error when on way home. What's causing this to happen? I read yhe PRL articles here a while back, and have a good understanding it has nothing to do with connecting to towers. I called Sprint about this, and a couple I spoke to said I'm not connecting to a nearby tower, and one said it my be the radio/antenna in my phone that my need checking out at a Sprint repair store.

Screenshot_2013-07-18-21-21-10.png

Link to comment
Share on other sites

Likely just an issue with LTE device provisioning in your area.

 

Our repeater in our store is having that exact issue with provisioning devices. Connecting them to WiFi works perfectly as it's a different provisioning server in use to program them. The main network here though works fine for provisioning, just something about how our repeater is being backhauled through the network.

Link to comment
Share on other sites

I just had a huge issue with the past 24 hours after Modem & Kernel flash wiped all my activation info. I replaced MSID and data login info but still no data connection with after going back to Stock, a Hard Reset, Hands Free Activation or Profile Update (which is where error showed up).

 

Long -> Short Sprint rep said it was a Samsung only error and needs to be elevated to manufacturer.  Give Sprint a call and have them send off a ticket, mine was fixed within a couple hours after having no data all day.

Link to comment
Share on other sites

Thanks for responding. As for Deval's question, I didn't do a hard reset, but restarted a couple of times.

 

halcyoncmdr, that makes makes a lot sense after reading up on provisioning info for telecommunications. And when I get the error, it's always at the same exact location arriving at, or passing through it.

 

AJ, when I called Sprint a couple of times, some reps said it's a tower connection issue, and 1 tech said it's my device antenna/radio that may need attention. Nobody mentioned a Samsung only error. Then again, reps tell us all sorts of things. I will call again, and mention provision and/or Samsung error.

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

  • Posts

    • Yes! That does keep it from wandering off Dish and most importantly, reconnecting immediately (at least where their is n70). Thanks!
    • I have my Dish phone locked to NR-only.  That keeps it on Dish and only occasionally will it see T-Mobile NR SA for brief periods before going to no service. I also don't have mine band locked beyond that, except that I have some of the unused bands turned off just to try to reduce scan time.  Fortunately, my Dish phone is the one with the MediaTek chipset, so it has NR neighbor cells, and I can usually see n71, n70, n66, and sometimes n29 (market-dependent) through those regardless of which band it's connected to as primary. - Trip
    • Excuse my rookie comments here, but after enabling *#73#, it seems that the rainbow sim V2? requires n70 (I turned it off along with n71 - was hoping to track n66) to be available else it switches to T-Mobile.  So this confirms my suspicion that you need to be close to a site to get on Dish.  Have no idea why they don't just use plmn. To test, I put it into a s21 ultra, rebooted twice, came up on T-Mobile (no n70 on s21).  Tried to manually register on 313340, but it did not connect (tried twice). I am on factory unlocked firmware but used a s22 hack to get *#73# working.  Tried what you were suggesting with a T-Mobile sim partially installed, but that was very unstable with Dish ( I think they had figured that one out).  [edit: and now I see Boost sent me a successful device swap notice which says I can now begin to use my new device.  Sigh.  Will try again later and wait for this message - too impatient.]
    • Hopefully this indicates T-Mobile hasn't completely abandoned mmwave and/or small cells? But then again this is the loop, so take that as you will. Hopefully now that most macro activity is done (besides rural colo/builds), they will start working on small cells.   
    • This has been approved.. https://www.cnet.com/tech/mobile/fcc-approves-t-mobiles-deal-to-purchase-mint-mobile/  
  • Recently Browsing

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