First of all this phone belongs to my dad. This means I haven't used it and I'm not familiar with many things about it.
The phone is running a stock ROM. It is not rooted, but it does have TWRP.
A software update prompt popped up trying to install "v20p-apr-03-2018" (why is an update for the G4 called v20 lol).
Telling it NOT to download it and NOT check for updates ever doesn't work. The update prompt comes back in 2 days tops. So **** you LG.
Since it's not rooted the easiest option seems to be to flash the update, however it just launches TWRP and does nothing. I found no way to actually download the update and keep it on the device so that I can manually tell TWRP to flash it.
So: Is there a way to download said update and flash it through TWRP? Or should I root it and delete the stupid update tool? I really don't want to flash a stock recovery.
ast00 said:
First of all this phone belongs to my dad. This means I haven't used it and I'm not familiar with many things about it.
The phone is running a stock ROM. It is not rooted, but it does have TWRP.
A software update prompt popped up trying to install "v20p-apr-03-2018" (why is an update for the G4 called v20 lol).
Telling it NOT to download it and NOT check for updates ever doesn't work. The update prompt comes back in 2 days tops. So **** you LG.
Since it's not rooted the easiest option seems to be to flash the update, however it just launches TWRP and does nothing. I found no way to actually download the update and keep it on the device so that I can manually tell TWRP to flash it.
So: Is there a way to download said update and flash it through TWRP? Or should I root it and delete the stupid update tool? I really don't want to flash a stock recovery.
Click to expand...
Click to collapse
Freeze or uninstall Software Update (LG proprietary, i.e., closed source, app) - may require root. That should stop the annoying requests. If you are able to upgrade you will lose TWRP and will have to re-flash TWRP again. You may want to consider that you do not have the latest Google security patches by not doing the update, putting your Dad's phone more at risk.
sdembiske said:
Freeze or uninstall Software Update (LG proprietary, i.e., closed source, app) - may require root. That should stop the annoying requests. If you are able to upgrade you will lose TWRP and will have to re-flash TWRP again. You may want to consider that you do not have the latest Google security patches by not doing the update, putting your Dad's phone more at risk.
Click to expand...
Click to collapse
It's not like LG updates security patches that often so it's not that big of a deal if I can't update it.
It's also fine if I lose TWRP during the process, I just want to avoid flashing stock recovery just for the sake of updating it.
And I still can't download the update and keep it. I don't know where it puts the update after downloading it. I couldn't find it in TWRP.
ast00 said:
It's not like LG updates security patches that often so it's not that big of a deal if I can't update it.
It's also fine if I lose TWRP during the process, I just want to avoid flashing stock recovery just for the sake of updating it.
And I still can't download the update and keep it. I don't know where it puts the update after downloading it. I couldn't find it in TWRP.
Click to expand...
Click to collapse
It helps if you include your phone model when looking for specific firmware updates.
If you're Dad's phone is an H815, there are some v20p downloads available here: https://lg-firmwares.com/lg-h815-firmwares/firmwares/
In order to flash in TWRP without losing TWRP, you would have to remove the stock recovery and create a flashable zip ...
Easiest is to simply freeze or remove the lg Software Update app as I indicated - the annoying update notification should then disappear ...
Note: XDA courtesy is to hit the Thanks button (bottom right of post), when members are trying to help and solve your issues. As a Senior Member you know this.
This update does not contain any security fixes it's just for the new European data protection law..
First thing you should try is:
Upgrade TWRP.
Do a full TWRP backup!
Test android update again.
Second thing:
Have you tried the LG bridge windows software to update?
If so and it fails there too you can find the update when you try to Flash it within the LG folder of your Windows PC afterwards use this KDZ file and lgup to flash it.
There is a chance that when using the internal updater that you can find the update file when in TWRP in /cache in a folder fota but it will likely be in a LG specific format so may don't help you much.
Third thing :
Disable the LG updater within TWRP (search for a howto)
Sent from my LG-H815 using XDA Labs
Related
The lack of a proper forum has made it very hard to find much information regarding the LG G-Slate. I am posting this for those who are having trouble finding the very useful information buried within these forums. This is a very significant mod/hack for the G-Slate and I would like to thank ChiefzReloaded for the amazing work he has put into it!
This was taken directly from our G-Slate project page. If you are unfamiliar with "Fastboot" I recommend reading up on it before proceeding.
In no way am I responsible for your device. This process below assumes that you know what you are doing, so if you do not, PLEASE AVOID THIS!
Unlocking the bootloader
Copy bootloader.zip to /sdcard/
Download Clockwork Recovery 5.5.0.2 (Attached Below)
Reset to Fastboot mode and boot Clockwork Recovery 5.5.0.2.
Code:
fastboot boot recovery.img
Install the bootloader.zip:
Install ZIP from sdcard
Choose ZIP from sdcard
bootloader.zip
Yes - Install update.zip
Let it flash, it will take about 60 seconds, then:
Go Back
Go Back
Reboot System Now
The system will reboot to a "Downloading Now" screen. Let it finish, and it will reboot.
All done!
Click to expand...
Click to collapse
Instructions courtesy of dasunsrule32 from G-Slate IRC.
You now have the ability to flash custom kernels/ROMs/mods/hacks again!
If you are interested in more info, please visit our Project Page!
bootloader.zip
DOWNLOAD
CWR 5.5.0.2
DOWNLOAD
Thank you...so much! LG can go suck a big one.
...
Like STDs and all...I strongly dislike that company.
stuck at lg boot screen after reboot
There's a new OTA update being sent out to G-Slates. Mine downloaded it today, it says:
System SW update to v10p Downloaded and Verified 13.3MB
This important system software update includes security fixes, USB game controller support and a fix for an Android Market download problem.
Click to expand...
Click to collapse
I have not applied it yet. Given they locked the bootloader last time, I'm very leery about what they're securing in this latest update. It is NOT an ICS update. From discussion in a T-Mobile forum thread, I know it does change the radio amoung other things.
But I have not unlocked my bootloader, I am rooted though. I'm wondering:
If I take this OTA update before unlocking the bootloader, will the unlocking process still work for me?
If I unlock the bootloader and then try to install this OTA update, will the update even work or will it try and re-lock my bootloader after being unlocked? (I know I can hide the fact I'm rooted.)
How could we get the benefits of the OTA update without installing the one provided? I mean, might someone turn it into a flashable zip that could be installed via Clockwork Mod Recovery?
If I have to choose, I'll probably unlock the bootloader without ever trying to install the update. But given my current state I'm trying to weigh the options and have the best of both worlds, the update and an unlocked bootloader .
If someone wants a copy of the OTA for investigation, just let me know how to pull it and I'll do it.
Unlocked the bootloader tonight, using the newer version of CWM from here.
Over on that forum, someone plans to make a safe flashable zip of the OTA. The one that came OTA will relock things if used. You can remove the downloaded OTA file by going to /cache and remove the .zip from there that was downloaded. Since they have a dedicated G-Slate forum, it seems more development for our device is going on there, so that's the forum to check out.
The nag screen will continue, but if you stop "LGESystemService" from autostarting, the nags won't be so frequent, just after reboots. I'm not sure how to totally get rid of the nag messages totally yet. I'm hoping maybe after flashing the safter version once one is made that the nags will go away.
Hi, i have some kind of problem with my nexus 7 2013.. I already have lollipop 5.1.1 official on my tablet and have root and unlocked bootloader (root with king root, yes it works and is rooted.. And bootloader unlocked with boot unlocker.. I know you might think that this are not the best way of rooting or unloking the bootloader but it worked for me and im happy) and since yesterday the tablet keeps telling me to update via OTA the 5.1.1 update witch i already have..i press update to install it as normal, it reboot as normal too and when it shows me the parte where it suppose to be installing the update (you know, with the android with the chest open part) the only thing that says is "error" it doesn't install anything..i did this like 3 times now and every one of them says error.. The annoying part is that it keeps showing me the notification to update it..so any solutions? Thanks!
Sorry for bad english blah blah...
You can't take ota updates if you modify system files, you did that with root. Don't know why it's showing you 5.1.1 when you already have it.
Just flash the factory image with fastboot (probably no need to wipe, just flash boot.img and system.img and format cache).
That should fix the problem. It will also remove root. I'd recommend not using that king root **** but whatever. Probably better to just flash the su zip in twrp or use CF-Auto-Root.
When the next update comes remember you won't be able to take the ota. But that doesn't matter since google posts factory images and all you need to do is flash it with fastboot, then root again.
yosmokinman said:
YDon't know why it's showing you 5.1.1 when you already have it.
Click to expand...
Click to collapse
There's a new 5.1.1 = LMY48G
Original 5.1.1 is LMY47V
^Oh yeah, lol.
Still the rest of my post will get it installed for op.
Hello guys
i want your helP guys, i have a rooted stock lolliPoP on my D855 and i want to uPgrade it to marshmellow, so how can i unroot my Phone
because i have read many articles and some guys had a lot of issues when they tried to unroot their devices.
by the way, i have tried to unroot using the "suPerSU" but i didnt work
so is it necessary to install a fresh stock rom for unrooting!
thanks
Marshmallow isn't out yet. Only the source code which is useless for users.
A user asked a similar question with the same purpose:
http://forum.xda-developers.com/lg-g3/general/d855-flash-to-stock-5-0-upcoming-ota-6-0-t3264516
The recommended way is the follow this tutorial:
http://forum.xda-developers.com/showthread.php?t=2785089
([Guide] LG G3 Stock Firmware (Go Back to Stock) KDZ & TOT Method by hyelton)
btw, what you mean is, you want to unroot your phone which is currently with Lollipop so you can later receive the OTA from LG.
thanks for resPonding
but for my Phone it gives that there is a software uPdate and started to download it and it was about 300MB, so is that what you are saying that it is just a source code!
and sorry for this but bexause i dont know but can you exPlain the difference between the source code and the offical rom!
thanks again
MidnightDevil said:
Marshmallow isn't out yet. Only the source code which is useless for users.
A user asked a similar question with the same purpose:
http://forum.xda-developers.com/lg-g3/general/d855-flash-to-stock-5-0-upcoming-ota-6-0-t3264516
The recommended way is the follow this tutorial:
http://forum.xda-developers.com/showthread.php?t=2785089
([Guide] LG G3 Stock Firmware (Go Back to Stock) KDZ & TOT Method by hyelton)
btw, what you mean is, you want to unroot your phone which is currently with Lollipop so you can later receive the OTA from LG.
Click to expand...
Click to collapse
laith1234 said:
thanks for resPonding
but for my Phone it gives that there is a software uPdate and started to download it and it was about 300MB, so is that what you are saying that it is just a source code!
and sorry for this but bexause i dont know but can you exPlain the difference between the source code and the offical rom!
thanks again
Click to expand...
Click to collapse
What country are you in?
laith1234 said:
thanks for resPonding
but for my Phone it gives that there is a software uPdate and started to download it and it was about 300MB, so is that what you are saying that it is just a source code!
and sorry for this but bexause i dont know but can you exPlain the difference between the source code and the offical rom!
thanks again
Click to expand...
Click to collapse
the software update you're seeing might be v21a which is still lollipop, not marshmallow
source code is a bunch of code for developers to use while the official rom is a kdz file released from LG that can be flashed, or OTA from LG.
EDIT: also, if marshmallow update is here it would be v30a or something like that
laith1234 said:
thanks for resPonding
but for my Phone it gives that there is a software uPdate and started to download it and it was about 300MB, so is that what you are saying that it is just a source code!
and sorry for this but bexause i dont know but can you exPlain the difference between the source code and the offical rom!
thanks again
Click to expand...
Click to collapse
If you received an update it was probably 20A like mentioned or a Lollipop update. Source code isn't used update over the air. Its for developers.
When you get Marshmallow update, Im assuming will be bigger than 300mb and it will mention what kind of update it is (stating Marsmhallow).
THANKS A LOT GUYS, YOU WERE ALL RIGHT, IT WAS JUST AN UPDATE FOR THE LOLLIPOP, 21A, AND BY THE WAY FOR THE COMING UPDATE IF ANYONE WANTS TO GET THE OTA UPDATE AND HE HAS ROOTED HIS PHONE HE CAN EASILY FOLLOW THE FOLLOWING STEPS
1. Download LG PC Suite from LG's website - you must select model type before you do so, but as far as I can tell it downloads the same version regardless.
2. Update the app so it recognises the G3 - this should ask you to update automatically on opening the app, if not you can do it from the "help" menu.
(NB: if you have used some of the KDZ flashing methods on here you may have issues updating as your hosts file is probably altered to block the PC Suite gaining a connection).
3. Connect the phone via USB (the app allows for a wifi connection but this is very restrictive, you require a USB connection for this).
*OPTIONAL STEP* If you want to go back to a truly stock experience then unfreeze any apps you have frozen (I am unsure if having apps frozen will effect OTA installations, it should still work fine, in theory).
4. With the device connected go to the "phone" menu in PC Suite and select the option that says "Restore Upgrade Errors".
5. It will then scan your device, download the rom and begin flashing, this is all automatic without any further input from you, do not cancel it.
6. The phone will reboot when finished. You are now unrooted and unmodified and OTA's should work.
*OPTIONAL STEP* If you want to go back to 100% stock then its probably a good idea to factory reset your phone at this point - this will wipe your whole device (of course).
And there you have it, your quick(ish), painless method for being able to unroot to accept OTA's without requiring a wipe.
THANKS FOR "Lennyuk" FOR THESE STEPS,,, THEY ARE FROM HIS PREVIOUS POST,,,
DONT FORGET TO PRESS THE "THANKS" IF I HELPED YOU,,,
Hi, im on 12.5.11.0.RJSEUXM and I want to upgrade to miui 13, but after downloading the zip, and trying to install it with the updater app (choosing a zip from menu) its says "unable to verify, you cant install this stable rom"
Is there any way to fix that and install the rom? putting that zip as "update.zip" at the root of my internal storage and booting into recovery does nothing (in previos versions an option called "update.zip to system" was there)
Or I need to do something more to update?
Thanks.
Each recovery ROM seems to be verified at Xiaomi servers during upgrade process and if they block the installation for whatever reason, you're out of luck. The reason might be that the ROM is supposed to be used only by selected testers, in a specific region or maybe the ROM was pulled due to major bugs (I saw some complaints about SIM/network incompatibility in Europe). I can't install this update as well. It is possible to force the installation via fastboot, but I believe that Xiaomi has a good reason why they prevent us installing this version. I'm waiting until it arrives on its own as an OTA update..
_mysiak_ said:
Each recovery ROM seems to be verified at Xiaomi servers during upgrade process and if they block the installation for whatever reason, you're out of luck. The reason might be that the ROM is supposed to be used only by selected testers, in a specific region or maybe the ROM was pulled due to major bugs (I saw some complaints about SIM/network incompatibility in Europe). I can't install this update as well. It is possible to force the installation via fastboot, but I believe that Xiaomi has a good reason why they prevent us installing this version. I'm waiting until it arrives on its own as an OTA update..
Click to expand...
Click to collapse
Oh..ok yes its safer to wait. Thanks
Just to confirm - I never received 13.0.2.0 EU ROM, nor I was able to install it via sideload/ROM updater. I couldn't install 13.0.4.0 manually either, but today I got the update over OTA and installation went through without any issues.
Having issues installing beta 3.3 on my 6 pro.. did a factory reset then tried installing it. First time it took forever to install and phone rebooted and had missing operating system so I had to factory reset.. second time I got a failed to install message.. rebooted the phone and it said no operating system please visit this link from another device.. rebooted then phone worked normal.. what is going on here ? Phone is purchased from att, so idk if it's considered global version but whatever either way . Is there something stopping it from being installed? Was trying to do all this OTA.. thanks kinda new to it
I'm not sure if it being an att version has anything to do with it or not.. maybe the version google releases is only working on unlocked global models?? Someone shine some light on this..
You can use https://flash.android.com/ to flash with a computer.
So why would the flash tool work but not the ota method ?? Really curious cause when the official comes out hopefully I can flash that ota without any issues.. right now I opted out of the beta cause I really want the ota method to work and it doesn't ..
Can someone tell me why the ota wouldn't install ? Installed it the way I installed any other update on the phone through check for updates.. Id rather get ota working vs hassling with a computer to install it. That can mess things up if done wrong .
Is it failing to ota install the beta cause of a locked bootloader ? It does fine with install ota security patches on Android 12. Trying to install 13 ota on the phone itself fails.. I don't see why that would be though ?
@Redbeardkevv Welcome to XDA. Instead of posting multiple times in a row, please use the Edit button to edit your post and just add to it, in the future.
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
^ That Google site has saved many users on XDA. It has revived or corrected a mistake on their devices (mine too, once) when even flashing the full factory image didn't fix the problem. I have no idea what exactly it does that manually flashing doesn't. I normally use the full factory image zip, and that alone sometimes fixes issues that users have when they have issues flashing via the OTA method.
Oem unlocking toggled on isn't an option on this phone , purchased at att . I'll just wait till they release the official ota. But what would of been holding it up and making the installs corrupt??
Redbeardkevv said:
Oem unlocking toggled on isn't an option on this phone , purchased at att . I'll just wait till they release the official ota. But what would of been holding it up and making the installs corrupt??
Click to expand...
Click to collapse
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Important excerpt:
Android Flash Tool guides you step-by-step through the process of flashing your device—there's no need to have tools installed—but you will need to unlock your device and enable USB Debugging in Developer options.
Click to expand...
Click to collapse
If I remember correctly from other AT&T variant Pixel 6 Pro users in this section, once you pay off the phone and/or own the phone for long enough, AT&T should carrier unlock the phone, and that will likely make it so that you can OEM Unlocking and unlock the bootloader. (this also applies to T-Mobile, but does not apply to Verizon)
Well it's a far ways from being paid off I'll just add that .. what are my flashing options ? Also why would a security patch install just fine, then I enroll into beta ,try to install it, and bam it won't install and is corrupt install. Just doesn't seem right to me.. should I just wait until official release early August and then the OTA install from phone will work ?
Why would a security patch install without any issue , but I go to install this beta 13 and it fails and is corrupt . Same method as installing a security patch , only difference is beta won't install . Will it install correctly OTA when they release the final version in August ???
Redbeardkevv said:
Why would a security patch install without any issue , but I go to install this beta 13 and it fails and is corrupt . Same method as installing a security patch , only difference is beta won't install . Will it install correctly OTA when they release the final version in August ???
Click to expand...
Click to collapse
Firstly, unlocked bootloader is required to flash custom or beta firmware. While you can sideload OTA packages on a locked bootloader, I would highly recommend against doing so as you may end up with no way to recover your device.
When installing a beta, it is generally best to wipe and perform a clean flash. OTA is not recommended because beta software by nature is not yet suitable for public release, and may not appropriately handle everything correctly coming from older firmware.
As has been mentioned before, I recommend you use the Android Flash Tool to flash the beta. To ensure you have a fresh start, tick the Wipe device and Force flash all partitions boxes. Do not re-lock the bootloader.
So in short, wait for the official ota to roll out in August and install from phone then?? Cause I won't be able to unlock bootloader , phones not paid off... Would this explain why it's failing to install an beta from within the phone itself cause the bootloader's locked? So I have to wait for official ota rollout like I said earlier ??
Redbeardkevv said:
So in short, wait for the official ota to roll out in August and install from phone then?? Cause I won't be able to unlock bootloader , phones not paid off... Would this explain why it's failing to install an beta from within the phone itself cause the bootloader's locked? So I have to wait for official ota rollout like I said earlier ??
Click to expand...
Click to collapse
Most likely. I doubt the beta will pass signature verification until it is updated to public release.
So not passing signature verification would be the reason it won't install ( ota ) most likely ? I'm just confused why a patch will install ota but the beta cannot .. must have something to do with bootloader being locked and it not being an official verified release or something
Just curious
Redbeardkevv said:
Just curious
Click to expand...
Click to collapse
Yes, you need the bootloader unlocked. So you cannot use those builds - only officially released OS builds.
NippleSauce said:
Yes, you need the bootloader unlocked. So you cannot use those builds - only officially released OS builds.
Click to expand...
Click to collapse
Well that explains it not installing and saying corrupted install ... Lol
Redbeardkevv said:
Well that explains it not installing and saying corrupted install ... Lol
Click to expand...
Click to collapse
It's a beta, so there will be issues for sure (but your last comment said you are getting an error [device is corrupt] that was common a few months ago so read on). You don't need to have an unlocked bootloader to enroll in the beta. Tons of users on Verizon and AT&T with a locked BL have installed the beta. Most are fine, some have had issues.
I wouldn't install a Beta on a locked BL. Why risk it? If something goes wrong, you'll need to get a warranty replacement. Seems like such a hassle.
For your issue, since you said you're getting a device corrupt message. This message is caused by q few different things (there's a thread on here about it). To fix it, users needed to do a factory reset in recovery mode. If you really wanted to try installing the beta (and you understand the risks), you'd probably need to: go to recovery mode and perform a wipe/factory reset.
From there, you could install the latest stable ota (via recovery mode) then see if the beta will update for you (via beta enrollment like you are trying to do), or directly flash the beta ota (link below). I'm just not sure if you can flash a beta ota image, over a stable build. I haven't tried it but according to xda, you can be on Android 12, and flash the Beta 13 ota (instructions found here).
There's two ways to flash an Android image: ota builds via recovery mode (doesn't require BL unlock) and factory image via fastboot which can be done manually or using Google's web flash tool (flash.android.com) - both if these require BL unlock.
You can find all the latest image downloads here. Google strongly recommends to flash the beta with an unlocked bootloader using their flash web tool. It's a beta so I would stay away until you can unlock your bootloader. Don't risk it. But I still think it might be a good idea for you to eventually perform a factory reset from recovery mode, since you are seeing the device is corrupt error message.
Had same problem, tried installing it twice and gave up