Accidental OTA update - LG V20 Questions & Answers

Sorry for the post first.... I am sure the answer is here somewhere and I am going to start reading up.
But if anyone happens to know the quick and easy answer.
My V20 was in a drawer after doing a nice job for a few years. But I pulled it out as a backup phone and got it a cheap MVNO sim on ATT towers.
Didn't think much of it - but apparently I haven't had it on ATT towers for some time and it found a OTA update. It has downloaded it I guess and says it will install it in 10 seconds... no options to quit or delay or nothing.
I am rooted, unlocked and flashed - honestly don't remember exactly where... but I'd guess in the AO Rom at 20H and TWRP.
BTW - Don't need to really update to anything as the use case is backup really. I need WiFi calling so flashing Lineage is out too.
Open to thoughts and ideas.
Thanks in advance.

AT&T has update towers specifically to do updates. They're are fast. Get within range and bam.
Disable the OTA update app or ask AT&T tech support to disable OTA updates on their end... they can.

Yep - thanks but they got me already. It won't complete the update because when they execute the script TWRP loads instead - which is nice. But if I reboot - it stays live for 20 seconds and says rebooting to complete update, to twrp boot, to shutdown to reboot - stays live for 20 seconds and says rebooting....
Not exactly a handy backup phone...
Any ideas how to get out of the boot loop.
Looking at all my old notes now - just gonna flash it again I think but can't remember where/what...
Anyway - thanks and my studying continues.
Oh and - I had no idea folks were pushing uphill on getting Android 12 on the V20. That would be amazing. Great phone to get this on.

What if you disable the updater while in TWRP using adb?

Arealhooman said:
What if you disable the updater while in TWRP using adb?
Click to expand...
Click to collapse
YES - exactly what I am trying to find out how to do?
I'm in TWRP now looking for the file that I presume it downloaded that it is trying to install. Presuming the OS looks for a file and when it is there it does the prompt - "Shutting down in 10 seconds to install update".

Found some notes and TWRP backups - so restored my backup of AlphaOmega.
Then - enabled developer options and disabled automatic updates from there
I think that is all I have to do.

wantpizza said:
Found some notes and TWRP backups - so restored my backup of AlphaOmega.
Then - enabled developer options and disabled automatic updates from there
I think that is all I have to do.
Click to expand...
Click to collapse
On Samsung's that won't do anything except not auto update when the phone restarts. OTA updates is still active and can hijack control of the phone. It has every permission under the sun, might as well be malware.
If the app is still running it's likely going to screw you up...

Yah - I wasn't satisfied either...
I installed Magisk and installed some root app uninstaller. Not exactly sure what I am looking for - but the only apk with OTA in it was something FOTA - so sounded Forced.... I uninstalled.
Heck - haven't customized much yet - figure it is time to try and break it...
We will see what happens.

wantpizza said:
Yah - I wasn't satisfied either...
I installed Magisk and installed some root app uninstaller. Not exactly sure what I am looking for - but the only apk with OTA in it was something FOTA - so sounded Forced.... I uninstalled.
Heck - haven't customized much yet - figure it is time to try and break it...
We will see what happens.
Click to expand...
Click to collapse
Does the update option appear in the settings menu still? If not you got it.

Look for apps with the word update in them

I did completely blow up the phone and biffed it while updating TWRP.
Posted here: https://forum.xda-developers.com/t/bad-day-kernel-panic-trying-to-update-twrp.4534615/
But I have it all back up and running. I didn't delete anything yet but it runs and isn't boot looped in the update cycle. I did disable updates inside developer options. But now I don't have any cell service where I am currently staying so I am probably going to put this aside for a while. Thanks all for the help.

Related

[Q] HowTo disable OTA 4.5.141 Update ?

I downloaded the OTA 4.5.141 on my unlocked and rooted Atrix, when I was advised to do this (only a few days ago), but stopped the installation of it.
After reading all the threads here in xda forum, this might be the best idea. I do not see the advantages of 4.5.141, only a lot of the disadvantages. Loosing root, high possibility of a brick ... ... better to wait for ICS as my Atrix is running perfect. Really love this little masterpiece.
But since I downloaded the OTA my Atrix advises my hourly that I should install the download. This annoing, how can I disable this ? Please help.
Use a root file manager and go to the /system/app folder and freeze the "Updater.apk " by adding a ".bak " to the end of it and rebooting.
If you have the paid version of the TiBu then you can freeze it with that.
1.ATRIX-in-PT said:
I downloaded the OTA 4.5.141 on my unlocked and rooted Atrix, when I was advised to do this (only a few days ago), but stopped the installation of it.
After reading all the threads here in xda forum, this might be the best idea. I do not see the advantages of 4.5.141, only a lot of the disadvantages. Loosing root, high possibility of a brick ... ... better to wait for ICS as my Atrix is running perfect. Really love this little masterpiece.
But since I downloaded the OTA my Atrix advises my hourly that I should install the download. This annoing, how can I disable this ? Please help.
Click to expand...
Click to collapse
What's wrong with 4.5.141? I installed it and just rerooted/unlocked/flashed
Hi live4nyy !
Thanks. The file is /system/app/Upgrader.apk ?
Hi ericc191 !
Probably you are right and nothing is "wrong" with 4.5.141 and "no risk, no fun". But it seems, that it includes just some little improvements.
It's not a real system update, so I am not very much in the mood for all this struggle to get my Atrix back to normal after the update (rooted, unblocked and not bricked).
Yeah, upgrader or updater. One of those
1.ATRIX-in-PT said:
Hi live4nyy !
. The file is /system/app/Upgrader.apk ?
Click to expand...
Click to collapse
If you're freezing it through a root file manager, then look for BlurUpdater.apk; do not change the "Upgrader."
If you're in Titanium Backup, then it's called Updater 2.3.4.
If you've already downloaded the update, then you might also need to boot into recovery and wipe the cache partition to erase the update file.
live4nyy said:
Use a root file manager and go to the /system/app folder and freeze the "Updater.apk " by adding a ".bak " to the end of it and rebooting.
Click to expand...
Click to collapse
this didnt work for me
das8nt said:
If you're freezing it through a root file manager, then look for BlurUpdater.apk; do not change the "Upgrader."
Click to expand...
Click to collapse
this did the trick
Yesss! No more annoying notifys!
hi all,
since the update was popping up from time to time and never really researched how to turn it off today, I friggin accidentally pressed on "install update" and automatically tried to reboot the phone, when I realized the mistake, I quickly pulled the battery out and waited for a few minutes then switched it back on.
it booted up fine but once it completes its bootup sequence, it would again prompt for an auto restart and try to install the update. Seems like the update is on the auto startup items (if there's such a thing).
I tried booting into safemode but can't get to do it maybe because I'm using an Alien build rom.
Any ideas on how to solve the problem? Please note that the phone boots but it tries to restart as soon as I can use it.
I have booted up now to recovery and will try to delete the updater apk and see if that will work. thanks in advance!.

[How-To] Install OTA Update on after Root/Custom Recovery

*Now Working for 4.3 Update* Will require an up-to-date install of 4.1.x first and then after re-boot, it will update to 4.3 (read post on next page).
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here https://www.dropbox.com/s/9wbux6a4kn0ndz9/StockRecovery-signed.zip
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
jay_ntwr said:
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here http://www.androidrevolution.nl/downloader/download.php?file=Flash_recovery_2.17.401.1.rar
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
Click to expand...
Click to collapse
I appreciate you writing this up. It seems like I've never been able to find a good solution to installing the OTA updates post-root. That being said, do you have any idea what happened in Step 7 that made it finally work? I just don't understand how doing the same thing over and over finally just worked. I want to try installing an update, but I'm a little nervous to do it. And I don't know how else to make the pesky update notification go away without installing it.
trickinit said:
I appreciate you writing this up. It seems like I've never been able to find a good solution to installing the OTA updates post-root. That being said, do you have any idea what happened in Step 7 that made it finally work? I just don't understand how doing the same thing over and over finally just worked. I want to try installing an update, but I'm a little nervous to do it. And I don't know how else to make the pesky update notification go away without installing it.
Click to expand...
Click to collapse
I really have no idea why Step 7 got so strange. The only thing that gave me a warm fuzzy whatsoever was that others were reporting that it was hanging and they just rebooted the phone over and over until it got all the way through the process. It could have something to do with the stock recovery for all I know--a bug perhaps. Again, it made me nervous and I won't do it again. I only did the write up so folks could see what happens and make a call whether or not they wanted to try it themselves and see the steps all on one page instead of getting stuck like I did and then finding the rest of the steps. That part sucked. At least you'll know what you're getting into though. Good luck one way or the other. Please post up if you do go through with it and what your results are.
Thank you for the info! Does sound like an awful lot of work though
jay_ntwr said:
I really have no idea why Step 7 got so strange. The only thing that gave me a warm fuzzy whatsoever was that others were reporting that it was hanging and they just rebooted the phone over and over until it got all the way through the process. It could have something to do with the stock recovery for all I know--a bug perhaps. Again, it made me nervous and I won't do it again. I only did the write up so folks could see what happens and make a call whether or not they wanted to try it themselves and see the steps all on one page instead of getting stuck like I did and then finding the rest of the steps. That part sucked. At least you'll know what you're getting into though. Good luck one way or the other. Please post up if you do go through with it and what your results are.
Click to expand...
Click to collapse
I'm thinking I'll give it a go. I'll do a nandroid backup and store it on my pc. Worst case scenario, I'll just start over from scratch, re-root, and restore my backup. I'll make sure to report my results.
I just makes me wonder why bother using the OTA update if you already went through rooting and flashing custom recovery? It's just one step more to flash the custom ROM and at least you will get constant updates with the developer who created the custom ROM. To me it seems like you either stay stock if you want OTA updates or go the whole hog and use custom ROMs. Just my 2 cents.
shadowboy23 said:
I just makes me wonder why bother using the OTA update if you already went through rooting and flashing custom recovery?
Click to expand...
Click to collapse
Well, in my case, I purchased the Dev edition straight from HTC so I automatically have a de-bloated OS from HTC instead of the ATT ROM that I would have gotten had I purchased the phone from the ATT Store. In that case, I'd no question have a custom ROM from the forum. I just didn't see the need this time around. I would have left the stock recovery, but I do like to make backups so ClockworkMod is something I can't live without. I suppose there are others in that same boat but they are probably few and far between. Really, I just hate to update my ROM since the phone is working how I want at the moment. It's hard to justify just blowing away a functioning OS, setting up everything again, etc. but I may do it again if the OTAs come frequently and/or the process is as strange as it was this past go around.
jay_ntwr said:
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here http://www.androidrevolution.nl/downloader/download.php?file=Flash_recovery_2.17.401.1.rar
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
Click to expand...
Click to collapse
hi,
one question. this recovery.img i also can use for my htc one 802w? i use the original rom (4.1.2) on my htc one. i make s-off over htcdev.com install cwm802w.img . i become the info the system update to 4.2.2 is available but the phone cant install the update.
any people like help me?
best regards,
ps: sorry for my bad english
Does sound like an awful lot of work though
greengoose_at said:
hi,
one question. this recovery.img i also can use for my htc one 802w? i use the original rom (4.1.2) on my htc one. i make s-off over htcdev.com install cwm802w.img . i become the info the system update to 4.2.2 is available but the phone cant install the update.
any people like help me?
best regards,
ps: sorry for my bad english
Click to expand...
Click to collapse
Just find a stock recovery for 802w, flash it to your phone and you should be fine to to OTA. The original post didn't mention if he's using 802w. If he's not, then the recovery.img can't be used for 802w.
How to get s_off , supercid 11111111
and return to s_on with supercid ?please tell me quickly
Thanks for all friends
Sent from my HTC One using xda premium
Sent from my HTC One using xda premium
I haven't been able to get this to work. I flashed back to the stock recovery, but when I attempt to install the update it gets about half way through before rebooting. It goes back into recovery, starts installing again, but then stops and just shows a red triangle with an exclamation mark. I can get the phone to reboot by holding the power button for 10 seconds, which boots it up normally. When it gets up and running, it's like nothing ever happened, but then the update notification reappears.
trickinit said:
I haven't been able to get this to work. I flashed back to the stock recovery, but when I attempt to install the update it gets about half way through before rebooting. It goes back into recovery, starts installing again, but then stops and just shows a red triangle with an exclamation mark. I can get the phone to reboot by holding the power button for 10 seconds, which boots it up normally. When it gets up and running, it's like nothing ever happened, but then the update notification reappears.
Click to expand...
Click to collapse
I'm experiencing the same thing, can't seem to find anything about it...
With the new 4.3 rolling out on the Dev editions, I decided it was time to try this again. What I found was I had to update to a something prior to the new 4.3. In other words, it was still one of the 1.29 streams that updated first and did just like the last time I did this. The thing stopped, locked up, had to hold the power button down, locked up again, reset again, then it was fine. As soon as the phone booted, the 4.3 update was available and I installed that without any issues. So, the method above still works and even with the weirdness I felt a little better this go around.
Good luck.
sunnyyen said:
Just find a stock recovery for 802w, flash it to your phone and you should be fine to to OTA. The original post didn't mention if he's using 802w. If he's not, then the recovery.img can't be used for 802w.
Click to expand...
Click to collapse
I haven't really checked this thread in weeks. I'm not sure what an 802w is. If you can clarify, I'll check and post.
Totally ran just fine
I had to as stated roll back to the attached recovery, did that with fastboot and no problems, then restarted the phone, then had it start the OTA update, then read around debating if I want CWM or TeamWin, but before I notice, the progress bar got up past half way. Looked away for what must've been less than 5 minutes until it vibrated and was restarting itself. It restarted again, and then it loaded and updated all the apps... Seemed like the smoothest rooted update I've ever done, no forced restarting or anything!
I just bought my HTC One last friday, and I think I screwed up things a little bit, because the first thing I did after I charged it, was updating everything to 4.3, before unlocking the bootloader, getting s-off and before rooting the phone. So I ended up with the latest 4.3 on my phone, but it was a pain in the ass to root it properly. I was able to unlock the bootloader, but something must be different with the way 4.3 treats the internal storage distribution, because I was only able to get root, using TWRP and the latest version of SuperSu, but I wasn´t able to install Busybox.
It's a little bit weird, because although I was able to use Titaniumbackup to install some apps, apps like OTA Rootkeeper don't work properly. I also lost the stock calculator, flashlight and voice recorder, but I was able to install older versions again.
I think the only thing I regret is not getting s-off first, but I think this will only mean that I will have to wait for a revone update, or I will have to flash the boot.img after flashing a custom rom as I always did with my One X.
jay_ntwr said:
I haven't really checked this thread in weeks. I'm not sure what an 802w is. If you can clarify, I'll check and post.
Click to expand...
Click to collapse
802w is Chinese dual sim version with different radio frequency
Sent from my HTC One dual sim using xda app-developers app
deepforest said:
802w is Chinese dual sim version with different radio frequency
Sent from my HTC One dual sim using xda app-developers app
Click to expand...
Click to collapse
That is not the one I have then.
I have a rooted HTC one with stock rom. I relock the bootloader and I also have stock recovery.
I am on 4.19.401.5 version.
So, will it be possible for me to have new OTA update including Sense 6?
Should I install the missing applications also, like calculator and flashlight?

[GUIDE] Unroot for OTA using LG PC Suite (PC Only)

This guide is for use on rooted stock roms to restore the phone to a position where it will accept OTA updates.
Please note the following:
1. It does not wipe the /data/ partition of your device.
2. It will reinstall any bloat you have uninstalled including those apps that you carrier put into /data/
3. It will remove any files you have added to /system/ including root or other modifications
4. Any files you have "frozen" will stay disabled, you cannot unfreeze them without rooting again - this guide will be for a "full unroot" so there is an optional step below to unfreeze apps.
The Guide
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.
Nice thanks Lenny, that may be handy. I'm supposed to receive mine today from Amazon.de, will play around a lot with root / unroot
Strange. Every time I click on restore errors it hangs for 30 secs and then LGpcsuite exe stopped working message and it stops. Any ideas ? I'm using windows 7 64bit and all drivers installed, pc recognizes phone.
Tarzan- said:
Strange. Every time I click on restore errors it hangs for 30 secs and then LGpcsuite exe stopped working message and it stops. Any ideas ? I'm using windows 7 64bit and all drivers installed, pc recognizes phone.
Click to expand...
Click to collapse
Could be a conflict with something else - to get it working for me I had to delete all traces of LG from the pc - all LG apps, drivers (including using USBDeview) and start over.
First of all, thank you for your detailed tutorial. Yesterday I have had the same idea... can someone confirm this theory... though there is no update for international version yet, someone with the korean model?
medicus07 said:
First of all, thank you for your detailed tutorial. Yesterday I have had the same idea... can someone confirm this theory... though there is no update for international version yet, someone with the korean model?
Click to expand...
Click to collapse
I tested this theory yesterday, albeit without an OTA - it does replace all modified and removed files in /system/ as well as removing any files you have added such as root or xposed.
There is no reason for the phone to continue to report that it has been modified, certainly if you take my final optional step and couple this restore with a factory reset.
Gotta love it when manufacturers make it simple to go back to 100% stock without any real messing around. Thanks for this :good:
Lennyuk said:
I tested this theory yesterday, albeit without an OTA - it does replace all modified and removed files in /system/ as well as removing any files you have added such as root or xposed.
There is no reason for the phone to continue to report that it has been modified, certainly if you take my final optional step and couple this restore with a factory reset.
Click to expand...
Click to collapse
Ok I fixed my issue, PC suite crashing by running it as admin on windows. When I run to "fix errors" it says I'm running latest version. When I check OTA on my phone there is an update which obviously don't run after download because I'm rooted. I'm out of ideas
Tarzan- said:
Ok I fixed my issue, PC suite crashing by running it as admin on windows. When I run to "fix errors" it says I'm running latest version. When I check OTA on my phone there is an update which obviously don't run after download because I'm rooted. I'm out of ideas
Click to expand...
Click to collapse
fixing errors is a reflash to fix a problem, it shouldn't matter what version your on, are you sure you didn't click the check for updates button by error?
Tarzan- said:
Ok I fixed my issue, PC suite crashing by running it as admin on windows. When I run to "fix errors" it says I'm running latest version. When I check OTA on my phone there is an update which obviously don't run after download because I'm rooted. I'm out of ideas
Click to expand...
Click to collapse
You should't have root access after using the fix upgrade function...
medicus07 said:
You should't have root access after using the fix upgrade function...
Click to expand...
Click to collapse
No, before fix upgrade. Actually I never get to download the firmware.
Lennyuk said:
fixing errors is a reflash to fix a problem, it shouldn't matter what version your on, are you sure you didn't click the check for updates button by error?
Click to expand...
Click to collapse
As I said I never get this option. It keeps on saying you have the latest version and that is it.
Tarzan- said:
No, before fix upgrade. Actually I never get to download the firmware.
As I said I never get this option. It keeps on saying you have the latest version and that is it.
Click to expand...
Click to collapse
Can you screenshot the "phone" menu you are seeing on LG PC Suite and upload it here?
Lennyuk said:
Can you screenshot the "phone" menu you are seeing on LG PC Suite and upload it here?
Click to expand...
Click to collapse
Attached both, before running and after running.
Tarzan- said:
Attached both, before running and after running.
Click to expand...
Click to collapse
The latter screenshot, did it give you that message after "scanning the device"? It might be that it scanned your device, found nothing altered so then said you were ok?
Perfect
Lenny thx alot. I was waiting for that. Because I wanted to make sure I can have OTA and root.
great :highfive::good:
Lennyuk said:
The latter screenshot, did it give you that message after "scanning the device"? It might be that it scanned your device, found nothing altered so then said you were ok?
Click to expand...
Click to collapse
See update available and I'm rooted.
Sent from G3
Tarzan- said:
See update available and I'm rooted.
Sent from G3
Click to expand...
Click to collapse
What happens if you go "check for updates" from PC Suite?
Lennyuk said:
What happens if you go "check for updates" from PC Suite?
Click to expand...
Click to collapse
Same, You have the latest version.
Tarzan- said:
Same, You have the latest version.
Click to expand...
Click to collapse
Weird, no idea why it won't be working for you, I have only been able to test on the D855 and have had no such issues.
Hopefully someone else who has the FK versions can shed some light.
Thats the thing. If its the phone version's (using Korean version) issue then how come the PC Suite recognizes it ?

New OTA update today

Hey guys, thought I would make a discussion thread about the new update today for the Sprint S5's. Looks like todays update was just over 200 MB. I don't know if it affects the latest chainfire root yet or not.
But yeah, make your stock S5 search for a update and you should find one waiting.
I've noticed:
The Android Security Patch Level is now December 1, 2016
Software version is now G900PVPU3CPL2
Do we know how long Samsung will continue to update our phone OTA? I appreciate that we still have support. It's not so bad being 1 month behind in security updates since even with security updates we are still vulnerable to 0-day exploits anyway.
Does anyone have a copy or link to this update? I want to see if it helps with signal on nougat based roms.
Thanks in advance
KIES
The~Skater~187 said:
Does anyone have a copy or link to this update? I want to see if it helps with signal on nougat based roms.
Thanks in advance
Click to expand...
Click to collapse
The best way to actually try and get this is through Kies or SmartSwitch apps. Sam Mobile does not have this, and it would be, about another month from now, till they even have it... Been there too many times looking for this so call update.
I know that is does state 01dec2016 security update. I also know, that Knox is added to (at least, all Knox is added data (Kbs, not Mbs) I also believe, they (Samsung, tech side phone updates) have added more apps for Knox. However, we don't have anything that is related to these new updates. heck 2 of them, state they have DATA. Through the stock app manager, you have an option, to erase this, because it is not installed....
not sure if this helps you find what you are looking for. ...
( me 2cents on this),... Why extra apps and data../. Why do we have to download a complete new Stock Rom, when we already were stock anyway ???) (Me dog did a real number on the phone. had to be a good eBay and Amazon shopper... Completely rebuild my S5.
Wondering if the S5 will be having A real update, such as 7.1... ??? !!!) we S5, was not on or in the press release early this month, regard the Samsung, Android updates... 7.0, 7.1 NOUGAT !!!
I certainly believe that they will in time update the S5 to 71 Nougat
This may just be a hunch but I have a feeling that if the Note 8's don't blow peoples faces off that the S5 probably won't be seeing Nougat officially (from Sammy).
Well there's a new update today for me anyways. This one is just over 27 MB's. 2 new updates in one month!
The new software version is called G900PVPS3CQA2
New antutu score updated.
It's very unlikely that S5 will receive an official N OTA from any carrier(or any msm8974, for that matter) as Qualcomm had planned 'no official support' for msm8974 past M. It was already very late in the cycle for M, and may not have made it onto the list for M had the msm8994 sucked less.
Does anybody know if we are still able to root our phone model with this new update?
LEN671 said:
Does anybody know if we are still able to root our phone model with this new update?
Click to expand...
Click to collapse
I don't know for sure myself, as I have not gotten the update bring on aftermarket firmware. But I would imagine if you flash twrp and apply the latest supersu, it should work. I know that's how I did it with the cpk1 update.
Someone please correct me if I am wrong. I don't want anyone bricking their device based on what I've said.
LEN671 said:
Does anybody know if we are still able to root our phone model with this new update?
Click to expand...
Click to collapse
Yes.. I did
I ran into some issues and factory reset, deleted my Internal Storage, and then ODined PK1 Stock onto my Sprint S5. I then got a prompt that G900PVPU3CPL2 update was available. After the phone restarted I was then prompted to update to G900PVPS3CQA2 After that one installed and restarted.. I successfully rooted using CFAutoroot and then put the latest TWRP Recovery on.
Now.. what screwed me up is me trying to put a 7.1.1 Rom on (LOS and even Resurrection Remix). Phone froze and would not allow me to enter any info in or select Wifi. When it did.. I had ZERO signal/data. I then re-odined.. PK1.. without the updates, rooted, and Twrped, then flashed the 7.1.1 (LOS and RR) with no problems. Made back-ups of both (within TWRP) and was able to Restore all three at will. I am currently back on the STOCK/ROOTED w/all updates including the QA2.. as I didn't feel like doing the customization of the 7.1.1. Roms with the game (SuperBowl) getting ready to come on.
Personally I like the Stock- Rooted -Updated- Twrp config as the only thing that bothers me is the heading theme being that Samsung Aqua blue. If I could theme it.. I might stay with it
Cmicasa the Great XvX said:
Yes.. I did
I ran into some issues and factory reset, deleted my Internal Storage, and then ODined PK1 Stock onto my Sprint S5. I then got a prompt that G900PVPU3CPL2 update was available. After the phone restarted I was then prompted to update to G900PVPS3CQA2 After that one installed and restarted.. I successfully rooted using CFAutoroot and then put the latest TWRP Recovery on.
Now.. what screwed me up is me trying to put a 7.1.1 Rom on (LOS and even Resurrection Remix). Phone froze and would not allow me to enter any info in or select Wifi. When it did.. I had ZERO signal/data. I then re-odined.. PK1.. without the updates, rooted, and Twrped, then flashed the 7.1.1 (LOS and RR) with no problems. Made back-ups of both (within TWRP) and was able to Restore all three at will. I am currently back on the STOCK/ROOTED w/all updates including the QA2.. as I didn't feel like doing the customization of the 7.1.1. Roms with the game (SuperBowl) getting ready to come on.
Personally I like the Stock- Rooted -Updated- Twrp config as the only thing that bothers me is the heading theme being that Samsung Aqua blue. If I could theme it.. I might stay with it
Click to expand...
Click to collapse
Thank you for the info!! This is what I wanted to hear!! Someone who had the newest update and then went into detail of what they encountered. Thank you again!! Much appreciated!!
You can always see the latest official stuff for our phones here: https://www.sammobile.com/firmwares/database/SM-G900P/SPR/
The only way we'll ever see Nougat on the S5 is via rom ports, or CM14/CM14.1 Official, which is supporting the S5.
LEN671 said:
Thank you for the info!! This is what I wanted to hear!! Someone who had the newest update and then went into detail of what they encountered. Thank you again!! Much appreciated!!
Click to expand...
Click to collapse
No problem. After using the STOCK/ROOTED MM version with all the updates , I have decided that I really am just gonna stay on it. It is smooth, fast, and has all the things I need. I killed Bloatware so outside of the pull-down bar being aqua blue.. and background being white I'm very content.
Anyone know of an app for rooted phones that will allow me to rectify those things?
Cmicasa the Great XvX said:
No problem. After using the STOCK/ROOTED MM version with all the updates , I have decided that I really am just gonna stay on it. It is smooth, fast, and has all the things I need. I killed Bloatware so outside of the pull-down bar being aqua blue.. and background being white I'm very content.
Anyone know of an app for rooted phones that will allow me to rectify those things?
Click to expand...
Click to collapse
@cmicasa the Great, I keep getting a failed when using Odin, CFAutoroot, KingoRoot, KingRoot, and even when I try to use TWRP. I also read somewhere that I would have to unlock the Bootloader in order for this to work? Do you mind sending me a message in PM about how you did your rooting? If you don't mind sir. Thank you again for your time and assistance.
LEN671 said:
@cmicasa the Great, I keep getting a failed when using Odin, CFAutoroot, KingoRoot, KingRoot, and even when I try to use TWRP. I also read somewhere that I would have to unlock the Bootloader in order for this to work? Do you mind sending me a message in PM about how you did your rooting? If you don't mind sir. Thank you again for your time and assistance.
Click to expand...
Click to collapse
This is everything I did including putting PK1 on my phone, letting it then upgrade to G900PVPU3CPL2 and then update to G900PVPS3CQA2 After that one installed and restarted.. I proceeded to Root and put custom recovery on. Because U will not get the OTA updates once U root
Here are my steps Len:
1) First make sure U have the ODIN 3.10 or above> Links are here SamsungOdin or here Odin Download
2) Then go into Download Mode by pressing the "Volume down +home and then Power buttons" Once device boots hit the volume up button and Android dude should appear
3) open ODIN (I used 3.10) and plug phone to computer.
Load the PK1 tar in the PDA Slot, put your phone in Download Mode (power off, hold Vol Down, Home, and Power), and connect your phone to the PC. (I checked F.Reset and Auto Reboot)
Then after that is successful run CF Auto Root or whatever root injector you have in the PDA slot again. Once that finishes (wait until Odin tells you it was a Success before doing anything), get ROM Toolbox or something of that nature and remove any app with Knox in the title or that has the Knox symbol.
Load your phone into Download Mode one last time and then put whatever recovery you have (I use TWRP, make sure you grab the .tar format instead of the zip) and put that in the Bootloader slot in Odin. Then you're good to go, rooted and custom recovery, sky's the limit.
-I found a perfect site that does exactly what I did using CFAUTOROOT. It explains everything including TWRP
then for Root http://www.stechguide.com/root-samsung-galaxy-s5-android-marshmallow/
then for Recovery http://www.stechguide.com/install-twrp-recovery-samsung-galaxy-s5/
Cmicasa the Great XvX said:
This is everything I did including putting PK1 on my phone, letting it then upgrade to G900PVPU3CPL2 and then update to G900PVPS3CQA2 After that one installed and restarted.. I proceeded to Root and put custom recovery on. Because U will not get the OTA updates once U root
Here are my steps Len:
1) First make sure U have the ODIN 3.10 or above> Links are here SamsungOdin or here Odin Download
2) Then go into Download Mode by pressing the "Volume down +home and then Power buttons" Once device boots hit the volume up button and Android dude should appear
3) open ODIN (I used 3.10) and plug phone to computer.
Load the PK1 tar in the PDA Slot, put your phone in Download Mode (power off, hold Vol Down, Home, and Power), and connect your phone to the PC. (I checked F.Reset and Auto Reboot)
Then after that is successful run CF Auto Root or whatever root injector you have in the PDA slot again. Once that finishes (wait until Odin tells you it was a Success before doing anything), get ROM Toolbox or something of that nature and remove any app with Knox in the title or that has the Knox symbol.
Load your phone into Download Mode one last time and then put whatever recovery you have (I use TWRP, make sure you grab the .tar format instead of the zip) and put that in the Bootloader slot in Odin. Then you're good to go, rooted and custom recovery, sky's the limit.
-I found a perfect site that does exactly what I did using CFAUTOROOT. It explains everything including TWRP
then for Root http://www.stechguide.com/root-samsung-galaxy-s5-android-marshmallow/
then for Recovery http://www.stechguide.com/install-twrp-recovery-samsung-galaxy-s5/
Click to expand...
Click to collapse
Thank you very much for breaking it down dummy style. Haha. It definitely helps. I will try it out when I get to my house and PC.
LEN671 said:
Thank you very much for breaking it down dummy style. Haha. It definitely helps. I will try it out when I get to my house and PC.
Click to expand...
Click to collapse
LOL.. no issues. Definitely go to those bottom links. They even have pictures. Be careful though.. I tried to experiment and see what checking the "Nand and Erase" in odin.. and damn near bricked my phone. Had to get PIT file and rebuild. Working smoother than ever now.. and like I said.. I'm sticking to Stock/Rooted and Xposed
Cmicasa the Great XvX said:
LOL.. no issues. Definitely go to those bottom links. They even have pictures. Be careful though.. I tried to experiment and see what checking the "Nand and Erase" in odin.. and damn near bricked my phone. Had to get PIT file and rebuild. Working smoother than ever now.. and like I said.. I'm sticking to Stock/Rooted and Xposed
Click to expand...
Click to collapse
So just to clear, there is no need to unlock the Bootloader? Also, if my phone has a password, does it need to be disabled? I.e. lock security feature such as creating a pattern in order to unlock the device to use.
LEN671 said:
So just to clear, there is no need to unlock the Bootloader? Also, if my phone has a password, does it need to be disabled? I.e. lock security feature such as creating a pattern in order to unlock the device to use.
Click to expand...
Click to collapse
I'm confused on that. Your phone will be booted into DOWNLOAD mode during the time of ODIN. Your Password will be inconsiquential
Cmicasa the Great XvX said:
I'm confused on that. Your phone will be booted into DOWNLOAD mode during the time of ODIN. Your Password will be inconsiquential
Click to expand...
Click to collapse
Okay, I am just making sure as I am not sure if that was one of reasons why Odin came back saying "FAIL". Thank you again.

Android 10 Verizon Variant update!

I had to manually check, but it's here on my phone .
For some reason the screenshot wouldn't upload, so here it is on imgur.
http://imgur.com/a/09FTqvK
Yep. Here in the Seattle area, the Verizon Android 10 update is here for the Moto Z4. Update went without a hitch...phone runs well and smoothly.
Anyone know how to get rid of this? It just started after the updated lol.
I think they put that there to remind us that once Android 11 is released, we'll be stuck on Android 10.
jwhistler said:
I think they put that there to remind us that once Android 11 is released, we'll be stuck on Android 10.
Click to expand...
Click to collapse
?. Trolled by Moto lol
slaytanic said:
Anyone know how to get rid of this? It just started after the updated lol.
Click to expand...
Click to collapse
It's there because developer tools are enabled, if you turn them off that message disappears.
I had the update last week, but was waiting for it to come up on Software update center since I have retail version, but now update is gone and it hasn't been released on the update center.
Could someone pull the update and post it here for the rest of us to manually update??
There is a new one today, it said critical, and applied itself, no option to delay it, it's called Update 5+.
I agree we really need the system image for this update. My phone will not update using the update system option, it only tells me it's already up to date. I tried using the tool from Verizon, same thing, up to date. I called verizon, after the second tech they want to send a new phone. But I don't really want a new phone. Also they had me do a factory reset just to be sure. I had a lot of apps disabled, and had other modifications through adb. Turns out those weren't the issue.
Pretty Please with Sugar on Top.
I'm sure all it would take is for someone to use the Verizon update tool or whatever it's called and select reinstall but keep my days then it'll download and extract. You just have to grab it once it starts extracting the zip and copy it somewhere so that when it finishs extracting it doesn't get removed. The app deletes the system image/zip when it finishes extracting. You could also unplug your phone when it starts extracting and it would touch your device.
Edit...... Then upload it anywhere.
This is an excellent idea, however it'll only work for people already on 10. Myself and others cannot update neither OTA or using the update tool. Using this aforementioned method of extraction would be absolutely fabulous, and I myself would buy some beers for anyone that would pull the update whatever way they can and upload???
Just manually checked and the update was there. I didn't think of it but there used to be an app that a Dev put out for Moto phones that would copy the update. Probably to old to work anymore though.
I did the same thing a couple days ago.
It's finally in the repository
shane1 said:
Just manually checked and the update was there. I didn't think of it but there used to be an app that a Dev put out for Moto phones that would copy the update. Probably to old to work anymore though.
Click to expand...
Click to collapse
Ive used LMSA (lenovo motorola smart assistant). Just set the download folder to someplace you recognize, then copy it out of that folder before lmsa extracts the zip
There is a new update, QDFS30.130-42-1-2, or System Update 6, installing now
Edit: It's May 1st security patch
moxtrom said:
There is a new update, QDFS30.130-42-1-2, or System Update 6, installing now
Edit: It's May 1st security patch
Click to expand...
Click to collapse
Be careful that build of Android 10 has problems with blue tooth according to forums.motorola.com.
pan815kev said:
Be careful that build of Android 10 has problems with blue tooth according to forums.motorola.com.
Click to expand...
Click to collapse
%#*%^$^%$#$(&!! I've been scouring the web all evening trying to figure out why my bluetooth stopped functioning recently...all worked fine until this new update that came across on my phone yesterday. I haven't been able to find any info on this, I was starting to think I was the only one having issues after that update. Is there a fix for this?

Categories

Resources