Jump to content

LG G2 Users Thread!


koiulpoi

Recommended Posts

After playing around with kitkat for a few hours. The new baseband seems largely unchanged signal wise. Its behaving the same im losing lte in the normal places and getting it in the normal places. What I did notice though is signal strength doesnt fluctuate no where near as much as it used to.

Link to comment
Share on other sites

The google services framework seemed to work for me too. I restored back to ZV7 and got up to ZVA quickly. Then it wouldn't pull the ZVC update but after force stopping the framework and clearing data then checking for an update about 4 times it finally showed up.

Link to comment
Share on other sites

Well no such luck...

 

I've attempted Force Stop and Cleared Data at least 5 times in Google Service Framework and every time I hit check now on the LG Update software it simple show the current time.

 

Really tempted to simply do a factory reset and see if that works but I'll keep trying....

Link to comment
Share on other sites

Well no such luck...

 

I've attempted Force Stop and Cleared Data at least 5 times in Google Service Framework and every time I hit check now on the LG Update software it simple show the current time.

 

Really tempted to simply do a factory reset and see if that works but I'll keep trying....

 

When you clear the data and go to check for updates does it show something like "Last Checked for Updates on 12/31/1969"? 

 

Again, it took a couple tries for me but it definitely seems to be working for most.

  • Like 1
Link to comment
Share on other sites

When you clear the data and go to check for updates does it show something like "Last Checked for Updates on 12/31/1969"? 

 

Again, it took a couple tries for me but it definitely seems to be working for most.

 

Yes, everytime

Link to comment
Share on other sites

Just as a "you have been warned" kind of thing:

 

http://www.talkandroid.com/185088-google-engineer-explains-why-you-shouldnt-clear-google-services-framework-data/

 

Mav. :cool:

 

Sent from my Sprint Tri-Band LG G2.

 

Edited by VW Maverick
Link to comment
Share on other sites

Well...mine is completely toast...my impatience got the best of me...any one have any step by steps on  going back to the ZV7 updates and starting fresh? 

Link to comment
Share on other sites

Well...mine is completely toast...my impatience got the best of me...any one have any step by steps on  going back to the ZV7 updates and starting fresh? 

 

Boot-loop?  Yeah, I had the same thing.  I found instructions on XDA.  Search for "LG G2 XDA" then go to G2 General -> LG G2 Stock Firmware (Go Back to Stock) 

 

Note:  It does delete everything...  I assume you are aware, but I just wanted to make sure.

 

I used the instructions for AT&T and Sprint which are located a little bit down the first post. 

Link to comment
Share on other sites

Well...mine is completely toast...my impatience got the best of me...any one have any step by steps on  going back to the ZV7 updates and starting fresh? 

No need...

 

ADB Sideload works, but you have to do it 3 times...

 

Do the sideload once... then instead of rebooting the system when it boots back to recovery, do the sideload again.  

 

Again, when it reboots to recovery, do the sideload a third time.... THEN it will do all the patching, etc, and when that's all done, it'll say install from ADB complete.  NOW reboot the system and it boots up to KitKat.

  • Like 1
Link to comment
Share on other sites

You might not need to restore to stock.

 

I got stuck in the bootloop as well and started the firmware download intending to do a restore. I went into download mode, then powered off.

 

When I powered back on, I was back to recovery. I figured since I was going to restore anyway, might as well give the update a try again since I saw the following on XDA: http://forum.xda-developers.com/showpost.php?p=51533599&postcount=612

 

If you can get back to recovery, give it another try.

Link to comment
Share on other sites

You might not need to restore to stock.

 

I got stuck in the bootloop as well and started the firmware download intending to do a restore. I went into download mode, then powered off.

 

When I powered back on, I was back to recovery. I figured since I was going to restore anyway, might as well give the update a try again since I saw the following on XDA: http://forum.xda-developers.com/showpost.php?p=51533599&postcount=612

 

If you can get back to recovery, give it another try.

 

That's what I tried, but my G2 got stuck every time on "Loading Recovery Mode" and would just sit there.  Oh well.  At least my phone is nice and clean like the day I bought it!  I had a ton of junk on there to clean up anyway.  I had my pictures and music backed up..  Just somehow forgot my contacts.  :rolleyes:

Link to comment
Share on other sites

Just as a "you have been warned" kind of thing:

 

http://www.talkandroid.com/185088-google-engineer-explains-why-you-shouldnt-clear-google-services-framework-data/

 

Mav. :cool:

 

Sent from my Sprint Tri-Band LG G2.

 

 

Oh it's not that bad in reading the article. I thought it was catastrophic the way a hand full of people on social networks were describing it. A simple factory reset which I do anyhow after each major software update addresses the issue.

 

Thanks though! :wavey:

Link to comment
Share on other sites

That's what I tried, but my G2 got stuck every time on "Loading Recovery Mode" and would just sit there.  Oh well.  At least my phone is nice and clean like the day I bought it!  I had a ton of junk on there to clean up anyway.  I had my pictures and music backed up..  Just somehow forgot my contacts.  :rolleyes:

 

Yea I'm not sure quite how I was able to get back into recovery. 

 

I saw the same message...multiple times. It was only after I got into download mode(to make sure I actually could), then powered off, then back on that recovery loaded properly.

 

I probably got lucky and it working after download mode, was a coincidence.

Link to comment
Share on other sites

FINALLY!!!!!!!!!!!!!!!!!!!!!!!!!!! :wall::drool::ty:

 

 

http://imgur.com/RnB3d2u

 

Apparently I wasn't allowing enough time between Force Stop/Clearing Data and systems update/LG Software Update check. So this time after stopping and clearing Google Service Framework I headed to Systems update/LG Software Update and waited 5-10 minutes before I tapped on Check Update.

 

Viola it worked.

  • Like 2
Link to comment
Share on other sites

anyone received KK update today? it was announced sprint was pushing it out today

That's been the entire mornings discussion :). Most of us have had success getting the update by clearing the data from google services framework.

  • Like 2
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

    • So, in summary, here are the options I tested: T-Mobile intl roaming - LTE on SoftBank, routes back to the US (~220ms to 4.2.2.4) IIJ physical SIM - LTE on NTT, local routing Airalo - LTE on SoftBank and KDDI (seems to prefer SoftBank), routed through Singapore (SingTel) Ubigi - 5G on NTT, routed through Singapore (Transatel) US Mobile East Asia roaming - 5G on SoftBank, routed through Singapore (Club SIM) Saily - 5G on NTT, routed through Hong Kong (Truphone)...seems to be poorer routing my1010 - LTE on SoftBank and KDDI (seems to prefer KDDI), routed through Taiwan (Chunghwa Telecom) I wouldn't buy up on the T-Mobile international roaming, but it's a solid fallback. If you have the US Mobile roaming eSIM that's a great option. Otherwise Ubigi, Airalo, or my1010 are all solid options, so get whatever's cheapest. I wouldn't bother trying to find a physical SIM from IIJ...the Japanese IP is nice but there's enough WiFi that you can get a Japanese IP enough for whatever you need, and eSIM flexibility is great (IIJ as eSIM but seems a bit more involved to get it to work).
    • So, the rural part of the journey still has cell service for nearly all the way, usually on B18/19/8 (depending on whether we're talking about KDDI/NTT/SoftBank). I think I saw a bit of B28 and even n28 early on in the trip, though that faded out after a bit. Once we got to where we were going though, KDDI had enough B41 to pull 150+ Mbps, while NTT and SoftBank had B1/B3 IIRC. Cell service was likewise generally fine from Kawaguchiko Station to Tokyo on the express bus to Shinjuku Station, though there were some cases where only low-band LTE was available and capacity seemed to struggle. I also figured out what I was seeing with SoftBank on 40 MHz vs. 100 MHz n77: the 40 MHz blocks are actually inside the n78 band class, but SoftBank advertises them as n77, probably to facilitate NR CA. My phone likely preferred the 40 MHz slices as they're *much* lower-frequency, ~3.4 GHz rather than ~3.9, though of course I did see the 100 MHz slice being used rather often. By contrast, when I got NR on NTT it was either n28 10x10 or, more often, 100 MHz n78. As usual, EMEA bands on my S24 don't CA, so any data speeds I saw were the result of either one LTE carrier or one LTE carrier plus one NR carrier...except for B41 LTE. KDDI seems to have more B41 bandwidth live at this point, so my1010 or Airalo works well for this, and honestly while SoftBank and NTT 5G (in descending order of availability) have 5G that's readily available it may be diminishing returns, particularly given that I still don't know how to, as someone not from Hong Kong, get an eSIM that runs on SoftBank 5G that isn't the USM "comes for free with the unlimited premium package" roaming eSIM (NTT is easy enough thanks to Ubigi). In other news, I was able to borrow someone's Rakuten eSIM and...got LTE with it. 40 Mbps down, 20 Mbps up, 40ms latency to Tokyo while in Tokyo...which isn't any worse than the Japan-based physical SIMs I had used earlier. But not getting n77 or n257 was disappointing, though I had to test the eSIM from one spot rather than bouncing around the city to find somewhere with better reception. It's currently impossible to get a SIM as a foreigner that runs on Rakuten, so that was the best I could do. Also, I know my phone doesn't have all the LTE and 5G bands needed to take full advantage of Japanese networks. My S24 is missing: B21 (1500 MHz) - NTT B11 (1500 MHz) - KDDI, SoftBank B42 (3500 MHz) - NTT, KDDI, SoftBank n79 (4900 MHz) - NTT Of the above, B42/n79 are available on the latest iPhones, though you lose n257, and I'm guessing you're not going to find B11/B21 on a phone sold outside Japan.
    • T-Mobile acquiring SoniqWave's 2.5 GHz spectrum  Another spectrum speculator down! T-Mobile is acquiring all of their BRS/EBS licenses and their leases. Details are lacking but it looks like T-Mobile might be giving them 3.45GHz in exchange in some of the markets where they're acquiring BRS/EBS to sweeten the deal and stay below the spectrum screen. Hopefully NextWave is at the negotiating table with T-Mobile so NYC can finally get access to the full BRS/EBS band as well.  — — — — — Edit: Turns out this is a spectrum swap where T-Mobile is basically giving them DoD spectrum in a bunch of markets in exchange for all of SoniqWave's BRS/EBS. SoniqWave will likely turn around and sell the DoD spectrum to AT&T whenever the FCC removes the 40MHz cap.
    • Maybe. The taller buildings on one side of the street all have Fios access and the NYCHA buildings are surrounded by Verizon macros that have mmWave. I don’t think this site will add much coverage. It’d be better off inside the complex itself.
  • Recently Browsing

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