Anyone get this yet?
Someone that gets the update notification AND is rooted.. can you pull the update zip and send it to me?
This needs to be done BEFORE you run the update.
File should be in the /cache partition.
Need to know if root changed.. also wanna see if they blocked the loki exploit. Thx :good:
I ws at work today with no WiFi on, and when I pulled the phone out of my pocket this update had already applied itself. I have knock knock on so that could have allowed my nether regions to authorize the update. Anywho, if I can still safely use lg flash tool to go back to 80010d then I can flash back and see if the server will push 10q again. Nothing in stone but it be nice to have some clue from someone with greater understanding if i can flash back to 10d without creating problems from this new update. The AT&T variants have Carrier IQ installed. Is it possible LG is aware of my flashing back and forth from Cymod to stock and forced the update without a prerequisite consent toast popup?
COMROM said:
I ws at work today with no WiFi on, and when I pulled the phone out of my pocket this update had already applied itself. I have knock knock on so that could have allowed my nether regions to authorize the update. Anywho, if I can still safely use lg flash tool to go back to 80010d then I can flash back and see if the server will push 10q again. Nothing in stone but it be nice to have some clue from someone with greater understanding if i can flash back to 10d without creating problems from this new update. The AT&T variants have Carrier IQ installed. Is it possible LG is aware of my flashing back and forth from Cymod to stock and forced the update without a prerequisite consent toast popup?
Click to expand...
Click to collapse
you can certainly downgrade back to 10d using LG Flash without causing issues. That may not ALWAYS be the case with future OTA updates but LG has not yet enforced "anti-rollback"
As for the update being installed.. I have read that you can only delay the update install so many times.. but after a certain amount of time the update is forced. Now I've only read this and can't say from first hand experience.. but maybe thats what happened to you. If that is the case and updates are being forced after a set time.. the only way to get around the update would be to freeze or remove the apk responsible for updates.. not even sure which apk is responsible offhand.
HERE's the link to where I read about the update.
"You can delay the update up to three times for four hours each time. After the fourth delay, the update will automatically get installed on the phone."
The fact that it auto installs at all is worrisome
Thanks for that. The responses in your link indicate they were not asked permission explicitly to apply the update. The fact that this, "paves the way for future updates," worries me that the bootloader has changed. I can confirm the radio has not. I work odd hours. When I'm off in the AM I'll see if i can't warm up LG Flash Tools and revert to 10d from download mode. If so I'll see whats up with root and pulling the update. Considering multiple sources are stating there was no confirmation it gives me a hunch this may have something to do with patching loki exoloit, though I have no emperical evidence of prior statement.
Soooo, if you Google "lg d80010q" there are three entries now. One of which is this
http://csmg.lgmobile.com:9002/csmg/b2c/client/agent_phonesw_notice_list.jsp?country=US
Not being a deepweb database expert I wonder if this might allow the update to be retrieved directly from LG.
COMROM said:
Soooo, if you Google "lg d80010q" there are three entries now. One of which is this
http://csmg.lgmobile.com:9002/csmg/b2c/client/agent_phonesw_notice_list.jsp?country=US
Not being a deepweb database expert I wonder if this might allow the update to be retrieved directly from LG.
Click to expand...
Click to collapse
nope just notifies LG service centers whats newly available.
Was running stock. Used LGFlashTool to go back to 10d and 10o and can't get the server to push the update even after trying to check for it from both cellular data and several different IP's while on WiFi. No dice. Software update 10q simply hasn't come to me yet. Out of time and energy at the moment. Sorry.
This update put my phone into a recovery loop and was unusable. I finally got it back to stock and about 48 hours later it just updated itself . There is barely any warning, a box pops up saying its updating and it does it! I dont like this at all ,any update should require some kind of approval from the user . But at least my phone runs great now!
Anyone with new "q" update....can you confirm that root works? I got stuck in bootloop when it installed and ended up restoring nandroid backup before I fixed it so i'm still on "o" for now.
Thanks,
The other afternoon I was busy pecking away at my laptop with my phone on the charger. All of the sudden my phone has the pretty blue sky over a green, grassy field and it's updating! I did not have the device on WiFi and I did not confirm this update. This update is being forced upon us AT&T users without any confirmation. I suppose it's small size and their over confidence in SHA/CRC checks make them think installing an update loaded over a cellular connection is a good idea. Heck, at least this is rumored to be paving the way for some official form of KitKat. The folks that work on this phone and produce such things as Cyanogenmod and other Android Remixes are amazing! I simply like the clip tray, knock-knock, my back LED working and better bench numbers to much to be swayed from stock. That is just my preference. Y'all still rock chicks off socks with the "ROMs"!
COMROM said:
The other afternoon I was busy pecking away at my laptop with my phone on the charger. All of the sudden my phone has the pretty blue sky over a green, grassy field and it's updating! I did not have the device on WiFi and I did not confirm this update. This update is being forced upon us AT&T users without any confirmation. I suppose it's small size and their over confidence in SHA/CRC checks make them think installing an update loaded over a cellular connection is a good idea. Heck, at least this is rumored to be paving the way for some official form of KitKat. The folks that work on this phone and produce such things as Cyanogenmod and other Android Remixes are amazing! I simply like the clip tray, knock-knock, my back LED working and better bench numbers to much to be swayed from stock. That is just my preference. Y'all still rock chicks off socks with the "ROMs"!
Click to expand...
Click to collapse
Not sure if this helps at all...
I had this update (d80010q) installed and tried to root (for the first time). I was unable to. Superuser was transferred, but did not have root access. Looks like I may have to downgrade before rooting. Is this correct? Thanks!
Can anyone provide tot for the d80010q
Root not working.
I can attest to not being able root my G2 with D80010q on it. Hop4efully a fix soon?
lostangelintx said:
I can attest to not being able root my G2 with D80010q on it. Hop4efully a fix soon?
Click to expand...
Click to collapse
manual iotroot steps for the att 10o update should work just fine.
Hmm
I have Lg G2 (Att) & hours b4 I have reflash'd back 2 stock and applied root about an hour later i got OTA so I click'd 2 recieve OTA it came back sayin Cant download OTA on rooted device if that helps and thatt was almost 24\hrs ago n still runnin smoothly but file was only like 16MB
This is n another thead then I start'd readin here so I thought this should b post's here 2
So will a bigger OTA push current root'd stock rom out n brick my fone¿
autoprime said:
manual iotroot steps for the att 10o update should work just fine.
Click to expand...
Click to collapse
Should I change the command to d80010q on the copy / paste command for this phone? or leave it at d80010o?
lostangelintx said:
Should I change the command to d80010q on the copy / paste command for this phone? or leave it at d80010o?
Click to expand...
Click to collapse
d80010o isnt part of the command. it starts at "adb"
I got this update few days ago.. I was rooted on "d", it went to "o" after i postponed it 4 times, and it went to "q" automatically without asking.
I use pattern as my screen lock, at random times, phone will reboot from AT&T logo.. it's very annoying, and i'm not sure what to do about it.. I can go back to "d" but ATT will eventually update it.
Anyone get TWRP to install after root on this? I used FreeGee with mine. Says installed successfully, but TWRP app is nowhere to be found.
Also, Root Browser never asks for SU access, as the other root apps do, and the apps I can supposedly safely remove are not in the /system/app folder. Very confused now.
---------- Post added at 05:48 PM ---------- Previous post was at 05:05 PM ----------
Root. Checker and terminal emulater both show me to have root access.
However root explorer doesn't show any of the apps that are supposed to be safe to remove, and it never asks for su permission like the other root apps do.
Also there is no/ system/apps folder. There is only/ system/app. Are these folders hidden somehow?
Sent from my LG-D800 using xda app-developers app
Sent from my LG-D800 using xda app-developers app
My phone tried to install this automatically with root the other day, and soft-bricked... Had to delete the files via adb and got back in relatively scot-free. Anyway apparently there is actually a 4.4 update being pushed right now for the d800. I would go for it but I am still rooted and would like to keep my root... And am also waiting for Aospa so I may let it settle before I jump in
LG G2
Related
Will (auto) root & unroot. Work for the new ota 605.7 update for the HTC thunderbolt
My friend wants to root the easy way ....NEED HELP will auto root work or not ...
sent from my rooted tbolt using XDA app
Yes but he should use the manual as most soft bricks occur with auto root.
Sent from my ADR6400L using XDA App
miketoasty said:
Yes but he should use the manual as most soft bricks occur with auto root.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
This. I don't trust "auto" roots.
The manual, ADB method is proven and not NEARLY as difficult as it may seem up front. You just have to follow the steps in jcase's thread, and you'll be done in half an hour. It's at least worth reading through.
TheStick13 said:
This. I don't trust "auto" roots.
The manual, ADB method is proven and not NEARLY as difficult as it may seem up front. You just have to follow the steps in jcase's thread, and you'll be done in half an hour. It's at least worth reading through.
Click to expand...
Click to collapse
Completely agree. You don't even need to learn adb to use it it's all just copy and paste.
Sent from my ADR6400L using XDA App
i was trying to root my friends phone with captains script which holds your hand...
I came across a problem... when trying to flash the downgrade pcimgfile... kept saying "Main version older, update failed"
As per him, he has not flashed anything on his phone, everything is stock andhe got his phone about a month after i did (for it launch day). The script was able to push the files and all seems good, but i have not been able to pin point whats causing the error. (i didnt get to take a screen shot with the firmware and stuff) Ive rooted 2 phones without issues with the script and on this particular phone, it seems to be working fine until i try to flash the update.
will using adb manually help in this case? I am thinking no.... but if anyone encountered this, mind sharing what you did?
I have not had any issue with the script. Its similar to the JCase's method it just issues the commands for you. Capt includes a copy of the commands the scrips runs in his thread so I found it helpful to look at it while I ran the scrip so I knew what it was doing and when. Like any set of instructions its always good to read through it all once before you preform it so you know what to expect. If you just download everything, click start, and expect it all to run smoothly then you are likely to run into problems.
JCase's method is good to learn off of tho and might be easier for people to pin point where errors occur.
The error i am seeing is with the phone itself. I think something may have gotten updated?
the script its doing its job. I also reboot my pc and did a factory restore.
Well Capt's script says it only works with software version 605.6 or 605.9 which I assume from when it was written means 1.12.605.6 or 1.12.605.9. If the phone your using is using software version 1.13.605.7 then you should use JCase's method here
The software is 1.12.605.6
Could it be Jcase maybe also updated the downgrade img file?
That first step is causijg the problem when i try to downgrade (the first time you flash the img file)
*looked at the thread and also went to the original thread, file md info is the same for the ruu on both posts **
I also have all the original exploit files on my pc from when i rooted MY phone... since he had a software version that was on the original root threads, i didnt have to change anything
This may be an issue you would want to ask in the chat room that there is a link to in the Development section. If you look at the scripts contents as well as the manual instructions from JCase they are exactly the same up the the point you are getting stuck at. The MD5's even match. So I wouldnt expect doing one method over the other would solve your problem. Maybe someone on the chat could help you out tho.
yeah... im gonna have to go in there....
Its the same software as mines. I didnt modify any files on my pc.... it should have just worked. thanks for the feed back. Guess i will try when i get home later and have more time to mess with it.
So I had an issue in hboot, i am not sure if something was unconnected or what but i think i am in a bootloop.
It happened during the first round where you unplug you phone, I did and it started to check the sd image and had the expected no image error message.
after it checked them all the phone displayed a error message the the "main version is older" that "update failed" and to press power to reboot.
when i do that it takes me to another screen. I think its the fastboot screen and my only options are bootloader, reboot, reboot bootloader, power down. All of which lead me to the same problem and no way that i can figure out.
I found this while searching for a fix, would i be able to pull the sd card, flash the update, and start over again? (albe it with a different root program)
Thank you before hand for your help.
I need some help, I have been trying to root my Verizon Razr XT912 running Device Software Version: 98.72.165.XT912.Verizon.en.US with the only tool I can find to use on DROID_RAZR_Utility_Jellybean_XT912_WinMacLin
Can anyone guide me in the right direction? thanks
Did you extract tool to desktop and then open it? It will give you all the instructions you need. Make sure you have USB debugging on too.
http://www.youtube.com/watch?v=XDV_72mPt4k
http://droidrazrroot.com/droid-razr-root/how-to-upgrade-to-and-root-jelly-bean-on-droid-razr/
There are two links that might be helpful to you. Hope it helps.
I lost root upon this last Verizon upgrade to 98.72.165. I think it was 98.72.16 before this weekend's update. I am going to try and go back to the original JB (98.72.16), enable root and hopefully find some type of rootkeeper utility that will stop this craziness. I can keep you posted if this works as I don't know what else to do. I use the Tasker application and most of my tasks are not functioning.
Everything worked well. I was able to reinstall the 98.72.16 image and then I applied root. So, I am back at the point before the upgrade of the software. I have root back and just completed a full titatium backup. Now, I need to figure out what others are using to keep root enabled so when a software update is applied I do not lose root. Anyone who can suggest what they use would be helpful.
To the first person who posted, I may be able to walk you through what I did and we can then learn what others are doing to keep root together.
98.72.165.en.US version
I am rooted. Haven't changed from the Moto/Verizon JellyBean update (4.1.2) but have deleted a lot of the programs I don't like or use. When I've tried to let the 98.72.165.en install it starts, then the Droid animation goes "belly up" with a "!"
I know others with root have installed it and I wouldn't mind having the update since I do travel within Canada about once a year. But, if I can't get it to install, then how do I tell the updated I don't want this? It's getting a bit tiresome to tell the installer "Not Now" every twelve hours.
Anybody have an answer?
fredlpage said:
I am rooted. Haven't changed from the Moto/Verizon JellyBean update (4.1.2) but have deleted a lot of the programs I don't like or use. When I've tried to let the 98.72.165.en install it starts, then the Droid animation goes "belly up" with a "!"
I know others with root have installed it and I wouldn't mind having the update since I do travel within Canada about once a year. But, if I can't get it to install, then how do I tell the updated I don't want this? It's getting a bit tiresome to tell the installer "Not Now" every twelve hours.
Click to expand...
Click to collapse
mwyarm said:
Everything worked well. I was able to reinstall the 98.72.16 image and then I applied root. So, I am back at the point before the upgrade of the software. I have root back and just completed a full titatium backup. Now, I need to figure out what others are using to keep root enabled so when a software update is applied I do not lose root. Anyone who can suggest what they use would be helpful.
To the first person who posted, I may be able to walk you through what I did and we can then learn what others are doing to keep root together.
Click to expand...
Click to collapse
How did you go back to 98.72.16?
Can you show me the steps please?
I was able to successfully root my phone after the update without a re-flashing or a wipe with Matt's Utility.
I followed the instruction in the link below. However, once I put the phone into BP Only mode, nothing happened. I let it sit there for about 5 minutes, then rebooted it normally and finished the exploit. It rooted the phone just fine.
http://mobility.forumsee.com/a/m/s/p12-9245-0620611--root-after-ota-165.html
I was rooted with 4.1.2 and haven't rerooted since taking 4.3 which I had to do for work. I know the bootloader is locked forever. I'm okay with touchwiz. But, after taking NC1, I tried saferoot for the first time on 4.3 and I got hung up at "sending files to device". I looked under the covers a bit and tried to just execute the commands manually. I can shell to the phone and do stuff, but if I try the install, it just hangs. And when I looked in /data (the bat file pushes stuff to /data/local/tmp) I see nothing. I tried simply pushing the files somewhere else and that was fine, but when I tried to change the permissions, I got "Operation not permitted".
Needless to say, I'm not rooted. But it seems others get farther than this before failing, even on NC1. So my big question is whether there is something funky with my setup or with adb which is preventing these commands from working properly. My phone initially connects as an installer but then flips to a media device shortly thereafter, even though I have usb debugging enabled, etc, since I can obviously run adb and all.
Any help/insight would be greatly appreciated.
Well, it looks like, despite my different behavior, saferoot doesn't work on NC1 anyway. From what I've read, some kept root after the update and some didn't. At this point, it appears my path would be to odin back to ML1, root there, and then try the update to see if root is maintained (or ignore it).
I noticed on AT&T someone managed to come up with a modified update that could be applied using safestrap that would maintain root for sure, but I don't think that will work here and haven't seem the same for Verizon yet.
doncaruana said:
Well, it looks like, despite my different behavior, saferoot doesn't work on NC1 anyway. From what I've read, some kept root after the update and some didn't. At this point, it appears my path would be to odin back to ML1, root there, and then try the update to see if root is maintained (or ignore it).
I noticed on AT&T someone managed to come up with a modified update that could be applied using safestrap that would maintain root for sure, but I don't think that will work here and haven't seem the same for Verizon yet.
Click to expand...
Click to collapse
You should probably just ignore it unless your going to Canada any time soon. Otherwise you will most likely loose root and need to do it all over again.
People have had luck keeping root by checking the survival mode in the paid version of super su. Just thought I would let you know in case you really want to be on the update. I will be making a pre rooted odin file sometime soon. I gave my main pc to my fiance and am currently on her old crappy laptop. It wouldn't be a problem but I need to install linux before I can do it. You probably don't care but ill be buying a Clevo P150SM-A in a few months so that should fix all my computer problems for the next 6+ years (just in time to upgrade to a graphene processor!).
saferoot on NC1
doncaruana said:
Well, it looks like, despite my different behavior, saferoot doesn't work on NC1 anyway. From what I've read, some kept root after the update and some didn't. At this point, it appears my path would be to odin back to ML1, root there, and then try the update to see if root is maintained (or ignore it).
I noticed on AT&T someone managed to come up with a modified update that could be applied using safestrap that would maintain root for sure, but I don't think that will work here and haven't seem the same for Verizon yet.
Click to expand...
Click to collapse
Do you think there will ever be an update to Saferoot that will allow it to work on NC1 or is that not really possible? I have used Saferoot on earlier firmware versions and it was great how easy it worked.....??
I'm asking for my girlfriend. I have the T-Mobile variant with a custom recovery and I know not to take an OTA because custom recoveries and OTAs don't mix. She, however, has an AT&T variant and she just told me she was prompted to update to Lollipop. She rooted long ago with whatever root for AT&T app was popular at the time.
Doesn't taking an OTA just make you lose root? Nothing else to worry about?
I would not recommend due to the chance it could boot loop. I would wait for a OTA zip and flash through TWRP.
If she is rooted it will break root, If she has a custom recovery (twrp) than it will cause a boot loop.
advice: if she wants lollipop she's gonna have to follow these steps.
http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html
Going to pass the link on to her now.
There is no custom recovery. She used Stump Root originally to get her phone route, if that makes any difference.
martinezma99 said:
I would not recommend due to the chance it could boot loop. I would wait for a OTA zip and flash through TWRP.
Click to expand...
Click to collapse
Is there an ota zip available for the D850. I froze software updates in titanium backup so I won't loose root.
SGE_DEW said:
Is there an ota zip available for the D850. I froze software updates in titanium backup so I won't loose root.
Click to expand...
Click to collapse
You would still lose root
2SHAYNEZ
Yep.. I went through the whole process of going completely back to stock and then rooted before updating to Lollipop hoping it would stay. It didn't and Stump Root says it's already rooted.
Thanks for this cool tool and method. The LGFlashtool gets up the 'Change to download mode' step adn then fails, with a '[16:10:26] can't change to download mode 00000064' error in the box. Any help would be appreciated. In the meantime I'll try another usb port. Also, when I first ran the Flashtool I had to select from three choices: the default checked off one had the word Korea in it, the second had Brazil and the third had the word Global. I left in on Korea--you think I should have gone with global?
Thanks again, Xamadiex.
Rayvin56 said:
Thanks for this cool tool and method. The LGFlashtool gets up the 'Change to download mode' step adn then fails, with a '[16:10:26] can't change to download mode 00000064' error in the box. Any help would be appreciated. In the meantime I'll try another usb port. Also, when I first ran the Flashtool I had to select from three choices: the default checked off one had the word Korea in it, the second had Brazil and the third had the word Global. I left in on Korea--you think I should have gone with global?
Thanks again, Xamadiex.
Click to expand...
Click to collapse
I read somewhere the LG Flashtool had to be modified at installation to avoid what you are going through.
You're right, it's just a matter of overwriting the megalock.dll file after you install the tool. It was a step I didn't miss. But good news for me, I used another pc and when I installed the flashtool it again gave me the three choices (not sure, but the title bar of the window was something like 'DMB').
This time I chose the 'global' selection and ran the tool as before and it completed for me. I'm currently DL'ing the lollipop update right now. Thanks for the quick reply, netomel.
partylikeaninjastar said:
I'm asking for my girlfriend. I have the T-Mobile variant with a custom recovery and I know not to take an OTA because custom recoveries and OTAs don't mix. She, however, has an AT&T variant and she just told me she was prompted to update to Lollipop. She rooted long ago with whatever root for AT&T app was popular at the time.
Doesn't taking an OTA just make you lose root? Nothing else to worry about?
Click to expand...
Click to collapse
I just received my G3 for AT&T yesterday. It had 4.4.2 firmware on it. I rooted and installed titanium backup and froze all of the AT&T bloatware. Got notification last night that I had a system update available so I went ahead and let it update thinking it would be 4.4.4 but I was wrong. End result, I wound up with a perfectly functional Lollipop with all bloatware removed, but did lose root in the process. I can live with that until someone figures root for lollipop out I think.
hitekredneck said:
I just received my G3 for AT&T yesterday. It had 4.4.2 firmware on it. I rooted and installed titanium backup and froze all of the AT&T bloatware. Got notification last night that I had a system update available so I went ahead and let it update thinking it would be 4.4.4 but I was wrong. End result, I wound up with a perfectly functional Lollipop with all bloatware removed, but did lose root in the process. I can live with that until someone figures root for lollipop out I think.
Click to expand...
Click to collapse
So it installed on your rooted G3? It wouldn't on mine - kept saying rooted device detected or something like that and then refuse to update. That's just fine because i have to have root so I was planning to wait anyway...
p0k3y said:
So it installed on your rooted G3? It wouldn't on mine - kept saying rooted device detected or something like that and then refuse to update.
Click to expand...
Click to collapse
+1
p0k3y said:
So it installed on your rooted G3? It wouldn't on mine - kept saying rooted device detected or something like that and then refuse to update. That's just fine because i have to have root so I was planning to wait anyway...
Click to expand...
Click to collapse
Yes, it installed with no problems at all. And I must say that I am loving it. So glad that I froze all of those at&t apps before I lost root. I am looking forward to root for lollipop so that I can freeze a few more. I must say that this is the best stock android rom that I have ever had the pleasure of using. I will probably stick with it for quite some time because of the speed and excellent battery life.
Lolipop upgrade
Hi iam very new on this forum . I got LGg3 AT&t version D85010f and i cannot upgrade to LOLIPOP always i have com that i have latest soft and need to wait 48h to next check ......plz help me
hitekredneck said:
Yes, it installed with no problems at all. And I must say that I am loving it. So glad that I froze all of those at&t apps before I lost root. I am looking forward to root for lollipop so that I can freeze a few more. I must say that this is the best stock android rom that I have ever had the pleasure of using. I will probably stick with it for quite some time because of the speed and excellent battery life.
Click to expand...
Click to collapse
I call bull****. Lolipop OTA will NOT install on a rooted device. Humor me, what root method did you use?
Vess69 said:
I call bull****. Lolipop OTA will NOT install on a rooted device. Humor me, what root method did you use?
Click to expand...
Click to collapse
Call Bull**** all you want, I don't lie. To be honest, I can't even remember what method I used to root when on KitKat. Then I used TiBu to freeze a bunch of apps that I didn't want or need. Shortly thereafter the update hit me so I went ahead and let it do its thing. As stated, I did lose root afterwards but the apps I had frozen with TiBu remained frozen and everything still worked as it should. I waited patiently for a few weeks until the one click root script became available and used it to root lollipop, then installed TWRP and flashed Cloudy G3 stock ROM which is where I am happily at at this moment.
It could possibly have successfully updated due to the fact that I had not installed a custom recovery, that's the only thing I can think of that would have allowed it to happen on mine, yet not on others that were rooted.
EDIT: After reading back through this thread it jogged my memory. I used the Stump Root method to root while on KitKat.
You'd be the first person reported to be able to do this.
It would be a boon to the AT&T G3 community if you could remember the precise details of how you pulled this off as it would save loads of time and hassle for everyone else who has to restore to KK (which means a full wipe), then take the OTA to L, then root there.
Thanks in advance.
*edit
I think you're L is version 20f, not the latest 21l, based on the date of your posts above.
Further, I'd suppose that what may have happened to you, is that the deivce had already downloaded the L update (from 10f to 20f) before you pulled off the root on KitKat. Then you simply acknowledged the install, which perhaps KK would allow to continue through.
Reports are the L will not allow this. So, going forward, someone rooted on L would not be allowed to complete the install even if the package is already downloaded on the device.
Still, it is, interesting.
Need help, did somebody revive this update? If someone know about it please tell me what's new on it.
I just received a notification about a new update today. I'm not doing it until know what's in it.
Sent from my LG-H810 using Tapatalk
---------- Post added at 10:34 AM ---------- Previous post was at 10:30 AM ----------
It appears to be a security update
Sent from my LG-H810 using Tapatalk
I've been having issues with Wi-Fi staying connected to either home or work networks and have to reboot the phone to get them to connect
I have just yesterday got a replacement phone from AT&T after getting bitten by that boot loop found on certain models. Oddly, it took about a year to manifest. I now have LG 810, with Android 6.0 preinstalled, and updated shortly thereafter to H81022b software. So far, it's been okay, but with all my apps and data gone (I did not root the earlier model, out of fear it would brick my very expensive phone) I haven't done much. I am considering rooting it, but ... I need to make sure it will work right. So far though, the phone has not been acting weird, so it's good, I guess?
Baroness1984 said:
I have just yesterday got a replacement phone from AT&T after getting bitten by that boot loop found on certain models. Oddly, it took about a year to manifest. I now have LG 810, with Android 6.0 preinstalled, and updated shortly thereafter to H81022b software. So far, it's been okay, but with all my apps and data gone (I did not root the earlier model, out of fear it would brick my very expensive phone) I haven't done much. I am considering rooting it, but ... I need to make sure it will work right. So far though, the phone has not been acting weird, so it's good, I guess?
Click to expand...
Click to collapse
You wont be able to root your device as you cannot downgrade from latest firmware.
I read some where on XDAdevelopers (I wish I could find it to post the shortcut), that any phone, you can get the image from your phone then add root to that, and finally flash the new image back on your phone. Is anybody familiar with this? I have read so much looking for away to put root onto my phone, even if it means flashing a rom onto it and then rooting. Or the rom comes with root.
H81022B
I have been reading for well over a couple of months, waiting and hoping there is even a lengthy method I could use.
Hey! Did you ever get your phone rooted? Because I have the h81022f. I think I've got a general understanding of what I'm going to have to do but I need to make sure that that last letter they add on there doesn't change a step or add or subtract something through the method of having to root it.
CerberusSnape said:
Hey! Did you ever get your phone rooted? Because I have the h81022f. I think I've got a general understanding of what I'm going to have to do but I need to make sure that that last letter they add on there doesn't change a step or add or subtract something through the method of having to root it.
Click to expand...
Click to collapse
I had my phone repaired because of the bootloop and when they sent it back to me they had installed 6.0. I followed the LG UP instructions to DOWNGRADE back to 5.0, worked perfectly. If I can find the specific post I'll link it here. But should be rather easy to find, but haven't really been in this forum for a bit.
EDIT: I think this is what I did, under the section titled TO GO BACK TO LP FROM MM
https://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803