Jump to content

Google Nexus 5 by LG Users Thread!


nexgencpu

Recommended Posts

I will say, that at first, QPST did not list any ports let alone the port my Nexus was connected on. If that is the case, dont worry. Simply click Add port to add it manually and then once you do that it will show up and you can continue on with the steps just the same.

If you have the Franco kernel loaded you don't have to do that boot from kernel step.

  • Like 1
Link to comment
Share on other sites

I'm stock

 

Yeah, you are stock, and I am bond.

 

AJ

  • Like 2
Link to comment
Share on other sites

 

This is where I can't get it to work. Also you failed to tell me I had to be rooted. I rooted my device, got su then when I get here and type step 8 my device under nexus 5 disappears from my computer. I have to restart my phone to get it back. QPST does not see my Nexus 5
 
8.  Type: setprop sys.usb.config diag,adb
Note: You will not see any activity on the command prompt or phone after this step, but you should hear a should from your computer, if your volume is on, to signify that your computer is installing the diag drivers.
 
9. Open QPST Configuration
 
10. You should see that there are a couple active ports in QPST.  Highlight the one that has some number under the phone tab and has USB for the link.
 
11. In the menu bar: Start Client > Service Programming
 
12. Select your phone with your phone number and hit okay.
 
13. Go to the Roam tab and select "Read from phone".  You will then have to enter your MSL number.
 
14. In the Roam tab, look in the Preferred Roaming section and browse for your .prl file.  Select it and then click "Write to Phone"
 
15. Don't freak out... You should have gotten an error stating that your phone returned a permanent error and you will now notice that your phone does not have a signal.  Close out of QPST- don't save any changes. 
 
16. Type: adb reboot
 
17.  When your phone reboots check in the Settings>About>Status page to be sure that your PRL took.  Enjoy!
Link to comment
Share on other sites

 

This is where I can't get it to work. Also you failed to tell me I had to be rooted. I rooted my device, got su then when I get here and type step 8 my device under nexus 5 disappears from my computer. I have to restart my phone to get it back. QPST does not see my Nexus 5
 
8.  Type: setprop sys.usb.config diag,adb
Note: You will not see any activity on the command prompt or phone after this step, but you should hear a should from your computer, if your volume is on, to signify that your computer is installing the diag drivers.
 
9. Open QPST Configuration
 
10. You should see that there are a couple active ports in QPST.  Highlight the one that has some number under the phone tab and has USB for the link.
 
11. In the menu bar: Start Client > Service Programming
 
12. Select your phone with your phone number and hit okay.
 
13. Go to the Roam tab and select "Read from phone".  You will then have to enter your MSL number.
 
14. In the Roam tab, look in the Preferred Roaming section and browse for your .prl file.  Select it and then click "Write to Phone"
 
15. Don't freak out... You should have gotten an error stating that your phone returned a permanent error and you will now notice that your phone does not have a signal.  Close out of QPST- don't save any changes. 
 
16. Type: adb reboot
 
17.  When your phone reboots check in the Settings>About>Status page to be sure that your PRL took.  Enjoy!

 

 

Just a little addition: When I finally got flashing the PRLs to work, I did about 3 or 4 that I would have ever wanted to use and did a TWRP backup of only the EFS partition.  You can just simply restore this partition and go back to whatever PRL was there.  Saves you the hassle of having to go through all these steps again.

Link to comment
Share on other sites

This is where I can't get it to work. Also you failed to tell me I had to be rooted. I rooted my device, got su then when I get here and type step 8 my device under nexus 5 disappears from my computer. I have to restart my phone to get it back. QPST does not see my Nexus 5

 

8.  Type: setprop sys.usb.config diag,adb

Note: You will not see any activity on the command prompt or phone after this step, but you should hear a should from your computer, if your volume is on, to signify that your computer is installing the diag drivers.

 

9. Open QPST Configuration

 

10. You should see that there are a couple active ports in QPST.  Highlight the one that has some number under the phone tab and has USB for the link.

 

11. In the menu bar: Start Client > Service Programming

 

12. Select your phone with your phone number and hit okay.

 

13. Go to the Roam tab and select "Read from phone".  You will then have to enter your MSL number.

 

14. In the Roam tab, look in the Preferred Roaming section and browse for your .prl file.  Select it and then click "Write to Phone"

 

15. Don't freak out... You should have gotten an error stating that your phone returned a permanent error and you will now notice that your phone does not have a signal.  Close out of QPST- don't save any changes. 

 

16. Type: adb reboot

 

17.  When your phone reboots check in the Settings>About>Status page to be sure that your PRL took.  Enjoy!

I know for me I had to click write to phone and go thru the errors around 5 times before sticking.
Link to comment
Share on other sites

I have 1x800 and LTE but now evdo does not work at all. Help

Do you have evdo when you set it to evdo only?
Link to comment
Share on other sites

Yes

 

Sent from my Nexus 5 using Tapatalk

I know when I messed with PRL,s it had a weird tendency to stick on 1x for data. Usually airplane toggles fixed it. But I rarely see evdo anymore because we have full LTE completion. But even if I set it to 3g/1x mode, I haven't had any issues in awhile. Try doing a profile update? I know I've had issues with airwaves and itll get stuck looking for it and every time I did a profile update away from home it usually fixed my issue.
Link to comment
Share on other sites

The first thing i did was airplane mode and second,was,a profile update lol. Its still not connecting. Even rebooted the device.

I know when I messed with PRL,s it had a weird tendency to stick on 1x for data. Usually airplane toggles fixed it. But I rarely see evdo anymore because we have full LTE completion. But even if I set it to 3g/1x mode, I haven't had any issues in awhile. Try doing a profile update? I know I've had issues with airwaves and itll get stuck looking for it and every time I did a profile update away from home it usually fixed my issue.

Link to comment
Share on other sites

I have 1x800 and LTE but now evdo does not work at all. Help

Try reflashing the PRL. I'm assuming you are using 512 or 513? Also, EVDO is working fine on another Sprint device in the same area?

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

Works fine on the G2. It was 513 that I want.

Try reflashing the PRL. I'm assuming you are using 512 or 513? Also, EVDO is working fine on another Sprint device in the same area?

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

Everything is good now. Reflashed the prl. Thanks for your help man. I am in your debt.

Try reflashing the PRL. I'm assuming you are using 512 or 513? Also, EVDO is working fine on another Sprint device in the same area?

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

Everything is good now. Reflashed the prl. Thanks for your help man. I am in your debt.

 

Glad I could help.  I am actually noticing that on 513 my phone doesn't seem to want to find EVDO either.  I'm going to reflash it or go back to 512.

Link to comment
Share on other sites

Glad I could help.  I am actually noticing that on 513 my phone doesn't seem to want to find EVDO either.  I'm going to reflash it or go back to 512.

Could it be possible the 513 PRL is searching for non existent evdo channels? So that's why it has trouble?
Link to comment
Share on other sites

Could it be possible the 513 PRL is searching for non existent evdo channels? So that's why it has trouble?

Not sure. When I went downstairs and connected to my nearest 1x1900 site it also connected to EVDO just fine.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

Yeah looks to be an issue just when connecting to 1x800. Not sure why though.

 

Sent from my Nexus 5 using Tapatalk

I am thinking it could be market dependent, if that is even possible. I live in a Samsung market with the 513 PRL flashed, and I have never had an issue connecting to eHRPD or EVDO. If I am not on LTE, which is rare nowadays, I am always on 1x800 and eHRPD.

Link to comment
Share on other sites

Like I said my g2 works fine with that prl so its not a market.

I am thinking it could be market dependent, if that is even possible. I live in a Samsung market with the 513 PRL flashed, and I have never had an issue connecting to eHRPD or EVDO. If I am not on LTE, which is rare nowadays, I am always on 1x800 and eHRPD.

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

    • Bribery. No discussion yet on whether the two laws will be revoked (which should happen). https://arstechnica.com/tech-policy/2024/05/att-paid-bribes-to-get-two-major-pieces-of-legislation-passed-us-govt-says/
    • https://www.fierce-network.com/wireless/t-mobiles-appetite-more-25-ghz-alive-and-well?__cf_chl_tk=E8B8E2cXIEfkSd2I6oKIMlE1.2OR2YbUh7Dl9Kkt_Os-1715722620-0.0.1.1-1770 Discusses pending deal for more 2.5Ghz for T-Mobile that may ultimately benefit AT&T.
    • If they're splitting it up, there's nothing stopping T-Mobile from doing a deal first and then the rest of the company being bought by Verizon or AT&T at a later date.  I can't see why you'd have to have both lined up at once. I'm reminded of when nTelos shut down.  They sold off the PCS spectrum they had in the "eastern market" (Richmond/Norfolk) to T-Mobile where they didn't have the Sprint deal first, and then later did the sale to Sprint and Shentel. - Trip
    • Reportedly Verizon has backed out, but that could be a negotiating tactic. T-Mobile needs another purchaser. They are doing a mmWave spectrum swap with AT&T, so maybe them. Could always go with a spectrum speculator.  The duo may not want the debt on their books until 2026.  I think the towers and customers may be dumped (handled separately).
    • I'm wondering which geographic areas T-Mobile might be interested in obtaining, or if it's strictly a spectrum sale of some kind.  In Virginia, US Cellular got three of the B41 licenses, including two in areas I frequent.  These two are in an area where US Cellular is severely spectrum constrained--just one block of CLR (B5) and one 5x5 in AWS-3 (B66), all running LTE.  (So 10x10 and 5x5.  Select towers also have B48 LTE on them, which is clearly at least 20 dB weaker than B5/66.)  I could definitely see interest from T-Mobile in the B41 licenses, but would have a hard time picturing US Cellular trying to continue serving these areas if it can't use spectrum to beef up its already-overwhelmed cell sites with more capacity.  (They keep adding towers to this very rural area to make up for it.)  Would T-Mobile buy out the area entirely to get a hold of the B41 licenses (and the B66 couldn't hurt either)?  Given US Cellular's strangehold over the area, would it even sell in that eventuality?  And then what would happen to the B5 spectrum?  Lots of questions.  Got my fingers crossed for T-Mobile obtaining the area and keeping most or all of the sites, as it could quickly and easily make reliable rural broadband a thing in the area, especially given how the Shentel merger went.  But I really have no sense of how likely it actually is. - Trip
  • Recently Browsing

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