Update for Verizon

Search This thread

laurasaurisrex

Senior Member
Nov 17, 2012
95
27

pettigrew95

Senior Member
Nov 26, 2006
1,651
141
New Jersey

pettigrew95

Senior Member
Nov 26, 2006
1,651
141
New Jersey
It does, but incorporation of anti-rollback has something in it that prevents downgrading even through a KDZ. I don't know enough of the technical details behind why it doesn't work.

Hm, thanks for that info...I guess I'll wait until there's more feedback on the new update before I take the plunge. Some people are saying it's great and I see others saying it worsens battery life, makes games unplayable, and breaks your notifications on WiFi...
 

ghostbustaj

Senior Member
Jun 20, 2015
99
31
Theses are the supposed fixes:

Calendar enhancements
Battery improvements
Keyboard enhancements
LG Backup
Camera enhancements
GPS enhancements
Exchange Active Sync enhancements
Touch Improvement
Security enhancements

ALSO I hear bluetooth battery drain has been corrected.
 

vo_danh

Senior Member
Jun 26, 2010
95
10
On 11A I was browsing constantly the other day and got 6-7 hours. Which is really damn good actually. I did turn off wifi/bluetooth/gps, and small stuff like touch vibration etc. I would say it does get down to 10-20% in the evening if I use it. Seems to me the screen is taking up the most power. Since I got a quick charger, there has been zero problems. It charges to full in under an hour from 20-30% so if I charge it mid day during a meeting or just while working its full again. I also bought TrendOn batteries, 2 batteries + charger was only $29.99 on amazon. This is great to swap on the go.

I was hoping there would be a better quicker root but it looks like you guys are flashing back to stock pretty easily so i guess its time for me to take the jump and root.

So on 11A, i was using UC browser, and ocasionally it would zoom and resize the page, are you guys telling me this was the touch screen bug? I also noticed I had a ton more spelling mistakes than before. I thought I was just not used to the size, but sounds like it could be this bug as well. sob.
 

Katmeat

Senior Member
Sep 9, 2010
193
68
Columbus
That definitely sounds like a reason to unroot and accept the upgrade to 12a. Like others, my battery problems and overheating issues under a rooted 11a has made the phone almost unusable for me.

Has anyone tried unrooting with SuperSU with success? Or is it necessary to use the flash tool or kdz back to root?

Thanks much.
 

fredderf81

Senior Member
Feb 27, 2010
140
19
  • Like
Reactions: Katmeat

howtogetnexus6

New member
Oct 12, 2015
2
0
until now i have not got a message for OTA, I rooted my device at first,,and flashed 11A KDZ several days ago because of reason. I am not in net of verzion,but a cdma net in China.Anybody kowns that ?
 

drdiehl

Member
Jun 19, 2009
8
0
Phillipsburg
Battery life

I wonder why some phones are different than others? My phone doesn't have any touchscreen issues at all. It's smooth, quick, and responsive.

my rooted 11A battery life took a dive after rooting, but settled down after a day and has been working great ever since. Good life and very fast charging, very responsive etc.
 

xgerryx

Senior Member
May 26, 2011
1,167
285
New Hampshire
To anyone thinking about taking that 12a rooted imagine and going to town, I would wait. Way too many posts about things going wrong with it and even not booting at all. My phone actually works for the moment, I'm not about to screw it up by jumping into an image of a rooted 12a by a non-dev that is having tons of issues. Just my 2 cents.
 

dmeeks72

Member
Feb 15, 2012
49
12
Overheating Issues

For Kat and others who are having overheating issues:

I was having overheating issues as well (not rooted) and found out (in my case) it had something to do with the SD Card and an app or multiple apps.

To fix my overheating issue, I pulled the SD Card for a couple of days and noticed no overheating. I then went ahead and cleared data on several apps I used that had SD Card Data listed. I went back into those apps and let them re-download the data and then stuck my SD Card back in. After several days of usage, I have not had the overheating/battery drain problem. I hope this helps.

That definitely sounds like a reason to unroot and accept the upgrade to 12a. Like others, my battery problems and overheating issues under a rooted 11a has made the phone almost unusable for me.

Has anyone tried unrooting with SuperSU with success? Or is it necessary to use the flash tool or kdz back to root?

Thanks much.
 
  • Like
Reactions: Katmeat

player911

Inactive Recognized Developer
Sep 8, 2006
7,954
1,206
Cincinnati
www.SnapSiteAdmins.com
*LINK REMOVED*

rooted update files from jessi

using one drive

Have you flashed this? I downloaded his rooted 12A and it wouldn't boot (system boot error AFTER LG logo and before Verizon boot logo), forcing me to flash back to 11A. No big deal but curious. I am downloading again now. It doesn't hurt to try. I was able to flash 11A over 12A, so why couldn't we snag a 10A and flash that?

Can you provide a MD5 file if you successfully flashed the one you linked? I got 6FC6B172592BE6BB66F2592FCE1D294C when I downloaded Jessi's file.

EDIT:
I downloaded this file form OneDrive and got the exact MD5 checksum. So I am assuming this is bad too. Please remove the link from your post so people can stop downloading bad files.
 
Last edited:
G

GuestX0011

Guest
Have you flashed this? I downloaded his rooted 12A and it wouldn't boot (system boot error AFTER LG logo and before Verizon boot logo), forcing me to flash back to 11A. No big deal but curious. I am downloading again now. It doesn't hurt to try. I was able to flash 11A over 12A, so why couldn't we snag a 10A and flash that?

Can you provide a MD5 file if you successfully flashed the one you linked? I got 6FC6B172592BE6BB66F2592FCE1D294C when I downloaded Jessi's file.

EDIT:
I downloaded this file form OneDrive and got the exact MD5 checksum. So I am assuming this is bad too. Please remove the link from your post so people can stop downloading bad files.


o_O i matched the md5 my bad. took the link down
 

player911

Inactive Recognized Developer
Sep 8, 2006
7,954
1,206
Cincinnati
www.SnapSiteAdmins.com
No problem guys, I know everyone is at work and crap. No harm no foul for me. I am back working on 11A like nothing ever happened.

Honestly it would probably be a good idea to post both the unrooted IMG file and the rooted IMG file. I don't have much to do tonight. So maybe I'll KDZ back to 11A, factory wipe, grab the OTA, grab the system IMG, post it. Then root it and post it.

I also want to try to flash back to 11A from 12A because I did it a few times already.
 
Last edited:

ghostbustaj

Senior Member
Jun 20, 2015
99
31
This update is great for the phone. But I am no longer getting notifications over WiFi anymore....just like the G3 problem.

I'm on the phone with Verizon as we speak.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    I can confirm root injection DOES work with 13B. I am running it now. I'm working on integrating some ported V10 system apps into the system image as well as removing a bunch of bloatware from the system partition and making a stock rooted debloated 13B system image.......

    Talking about this http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586

    ---------- Post added at 08:13 PM ---------- Previous post was at 08:12 PM ----------


    Nice, thanks for taking the plunge. Please let us know asap if root injection works. Fingers crossed!
    5
    This is moderately exciting, as bad as this is for us. I'm sure you mentioned this site and the huge number of people who are (unrooted) having this problem. Very very interested to hear what they have to say.
    At first, they did kind of try and give me the deal of how its an individual, just my phone, issue problem.

    I absolutely mentioned this forum and how multitudes of people are complaining of the problem. I also told both reps that I am passing every piece of information given to me along to this community.

    ---------- Post added at 02:05 AM ---------- Previous post was at 01:26 AM ----------

    Update:
    Verizon rep called me back. Basically told me that it is a waiting game to hear back from LG. It is LGs problem. He got the problem escalated to LGs higher ups. His email address was attached to the escalation so LG will be contacting him directly with an answer. He told me I will be the first to know what their response is.

    Verizon tech also gave me his own phone number so I can contact him with any information LG provides me and vise versa.

    That being said, when I briefly spoke to the LG rep that called me asking about my phone information, he DID say someone at LG will be contacting me "in a bit." I am still waiting for that call.
    3
    I spoke to a Verizon rep yesterday about the notification issue associated with the 12a update. She put me on with an lg rep, who told me that there is no fix for this issue and that the 6.0 update would roll out to our device by the end of Oct. Not sure how much truth there is to this, but that's what I was told.

    End of Oct from LG....Next year probably before Verizon gives it its blessing and pushes out to us...
    3
    UPDATE: LG contacted me.

    The representative stated that it is not LG's problem. They are confident that the issue lies with the developer of the software (Google) and the carrier (Verizon.) The representative stated that it is Google whom develops the updates for the device. Once those updates have been made, they are then handed to the carrier whom pushes the update out and does what it wants with it. LG is only the maker of the phone, they stated, and once the phone is released they have no part in developing updates for that device.

    And so the circle continues....

    Google and Verizon (again) will be contacted by me.

    ---------- Post added at 03:40 AM ---------- Previous post was at 02:59 AM ----------

    UPDATE: LG contacted me.

    The representative stated that it is not LG's problem. They are confident that the issue lies with the developer of the software (Google) and the carrier (Verizon.) The representative stated that it is Google whom develops the updates for the device. Once those updates have been made, they are then handed to the carrier whom pushes the update out and does what it wants with it. LG is only the maker of the phone, they stated, and once the phone is released they have no part in developing updates for that device.

    And so the circle continues....

    Google and Verizon (again) will be contacted by me.

    Alright, contacted another level 2 Verizon tech....

    The tech told me Verizon absolutely knows of the problem but he did find a piece of information stating the developer is working on a fix for the problem. Basically, he was meaning Google. There is no time frame stated for when the fix will take place.

    I asked him when our G4's get updated to 6.0 if that could be the possible fix and he said it could be possible but he was not sure. I countered by asking when the 6.0 update will take place...no time frame given.

    I also asked him about why Verizon limited the features of our phones. As everyone is aware, our Verizon phones do not have the features that other providers give (Smart settings, etc.) I went further by stating there is no doubt Verizon obviously messes with the software Google provides them or else we would have access to those features. So could it be possible that it is Verizon's tweaking of the update, to suit Verizon's wants, be the cause of the problem. And further, if in that piece of information stating there is a fix, could it be the developers at VERIZON working on the fix.

    He couldn't really give an explanation why Verizon limits features nor if the "developer" mentioned is Google or Verizon.

    That said....HIIII GOOGLE! :)
    3
    So it's confirmed you can roll back?

    I didn't see anyone make a correction on this... DO NOT TRY TO INSTALL THE 11A KDZ IF YOU UPDATED TO 12A. You will hard brick, indeed. It seems that the new boot version for 12a is "v2".

    The original user who created that rooted 12a system image tried it and bricked. Flashing the wrong system.img for your bootstack (a 12a system on a 11a bootloader, etc) doesn't brick, just fails to boot - and you can easily correct by reflashing the correct system for whatever bootloader you have. But rolling back by KDZ will run afoul of anti-rollback.

    http://forum.xda-developers.com/showpost.php?p=63290800&postcount=90

    autoprime offers a solution in that post however. If you have 12a, you can apparently get back to 11a by flashing both the system.img and the boot.img. I don't know if this works in reverse, too? Edit: he stated it should, I overlooked that part of his post. What I'm most interested in is if I can flash the system and boot images to be on different OTAs while retaining my ability for a bootloader unlock... I've been staying on 10b for that reason.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone