Develop Bugs

Verizon LG G Pad 8.3 system update

I rooted this tablet last week (just rooted, I left it stock) and this morning I notice there is a system update waiting to be installed. I am reading Lollipop is starting to roll out in Asia somewhere now but I am in the US lol. I thought it wasn't possible to get OTA updates once you root? If I allow this to update will I get unrooted, would it even work?
I foolishly allowed it to update after checking in Supersu to not allow the root to be lost and now I keep booting directly into TWRP lol. How do I wipe this tablet from TWRP so that it is fully stock again (NO ROOT)? I see a factory reset option in TWRP do I need to include all the partitions in the advanced wipe or is just the normal wipe method enough? Or will this not work at all? I already tried to restore the phone using TWRP to my backup and that didn't seem to work.

Anthony-m said:
I rooted this tablet last week (just rooted, I left it stock) and this morning I notice there is a system update waiting to be installed. I am reading Lollipop is starting to roll out in Asia somewhere now but I am in the US lol. I thought it wasn't possible to get OTA updates once you root? If I allow this to update will I get unrooted, would it even work? .
Click to expand...
Click to collapse
Simply rooting a device doesn't keep it from TRYing to update via OTA. Rooting can prevent an OTA from succeeding, plus can hard or soft brick if you try to take an OTA, although usually only if you've gone beyond just rooting by installing a custom recovery or changing the contents of any partition besides Data by, fire example, downgrading your bootloader (aboot.img) or modem, running a custom kernel, debloating system apps, etc.
There are at least three variants of the G Pad 8.3. I have the VK810.4G, which do you have?
I know on the VK810.4G, Verizon just released a very, very minor update from LG build #23A to 24A. Still KitKat.
I foolishly allowed it to update after checking in Supersu to not allow the root to be lost and now I keep booting directly into TWRP lol.
Click to expand...
Click to collapse
There's the main problem, you had a custom recovery installed. OTAs are applied with the stock recovery, that's why it (probably soft) bricked it.
How do I wipe this tablet from TWRP so that it is fully stock again (NO ROOT)? I see a factory reset option in TWRP do I need to include all the partitions in the advanced wipe or is just the normal wipe method enough? Or will this not work at all? I already tried to restore the phone using TWRP to my backup and that didn't seem to work.
Click to expand...
Click to collapse
You might not be able to fix it from TWRP. You could try @autoprime 's fix recovery zip available the same page his flash2 scripts are. You'll have to Google:
autoprime flash2
Click to expand...
Click to collapse
.
Otherwise, you'll have to restore to 100% stock unrooted and start from scratch. Two methods.
One is using LG's official Mobile Tool, which will download the latest official ROM in KDZ format (takes 20+ minutes to download) and flash it with your tablet in Download mode (probably with the tablet off, hold both up and down volume buttons in and while holding them, turn the tablet on.
I've got to go do something so hopefully someone else will help further or I can get back to you later, dont know when though.
Good luck!
Sent from my VK810 4G

I did the TWRP terminal commands from the thread listed below and it got me right out of that jam...
http://forum.xda-developers.com/lg-g-pad-83/help/vk810-download-mode-boot-loop-t2991512

OK now that I am up and running fine the system update message keeps popping up. This time I KNOW not to try and upgrade while rooted. Is there any way I can stop the tablet from constantly giving me the upgrade message? Can I do anything from TWRP to stop this?

Anthony-m said:
... This time I KNOW not to try and upgrade while rooted. Is there any way I can stop the tablet from constantly giving me the upgrade message? Can I do anything from TWRP to stop this?
Click to expand...
Click to collapse
Don't install TWRP. I was rooted (w/ stock recovery) with 23A, and the OTA update worked fine (still rooted).

DeanGibson said:
Don't install TWRP. I was rooted (w/ stock recovery) with 23A, and the OTA update worked fine (still rooted).
Click to expand...
Click to collapse
TWRP is already installed..
Can I uninstall TWRP, keep root , do the update and then reinstall TWRP? If so how? Is there any other way around this issue, any way of not having the tablet continue to ask me to upgrade? Thanks BTW...

Anthony-m said:
TWRP is already installed..
Can I uninstall TWRP, keep root , do the update and then reinstall TWRP? If so how? Is there any other way around this issue, any way of not having the tablet continue to ask me to upgrade? Thanks BTW...
Click to expand...
Click to collapse
Yes, you can do that, but I don't know the steps. Others here do.
Why do you want TWRP? I thought the usual reason was to install custom ROMs (in which case you won't receive any OTA updates). If you just want to root, it's an unnecessary complication (as you have discovered).

DeanGibson said:
Yes, you can do that, but I don't know the steps. Others here do.
Why do you want TWRP? I thought the usual reason was to install custom ROMs (in which case you won't receive any OTA updates). If you just want to root, it's an unnecessary complication (as you have discovered).
Click to expand...
Click to collapse
Thanks Dean, and yes I do agree with you about it being a complication. I was always under the assumption if I rooted a phone that I needed to also use some sort of recovery god forbid I had an issue with the phone not booting up or something so I could possibly fix the issue, make a backup/install a backup etc. Maybe I will ****can it if someone will tell me how to do so without losing my data or root.

Anthony-m said:
Thanks Dean, and yes I do agree with you about it being a complication. I was always under the assumption if I rooted a phone that I needed to also use some sort of recovery god forbid I had an issue with the phone not booting up or something so I could possibly fix the issue, make a backup/install a backup etc. Maybe I will ****can it if someone will tell me how to do so without losing my data or root.
Click to expand...
Click to collapse
FYI I just froze the update using Titanium backup pro and my problem is solved for now..

Flash stock over rooted to get OTA

I wonder is it possible to flash stock unrooted OOS over rooted OOS in order to install small OTAs. After updates plan to root again. Does anyone know whether this is possible or not? And, any side effects could occur?
I search over internet and couldn't find any useful info about this.
Thanks in advance.

Technically you'll be updating your device by flashing the newest stock anyway. No need for OTAs. You can then re-root.

GTRanushka said:
I wonder is it possible to flash stock unrooted OOS over rooted OOS in order to install small OTAs. After updates plan to root again. Does anyone know whether this is possible or not? And, any side effects could occur?
I search over internet and couldn't find any useful info about this.
Thanks in advance.
Click to expand...
Click to collapse
Yes, sounds doable

ABotelho23 said:
Technically you'll be updating your device by flashing the newest stock anyway. No need for OTAs. You can then re-root.
Click to expand...
Click to collapse
Not what i meant. Let's say I'm on rooted OB18. But i want to update it to OB19. all i have is OB18 stock firmware. So, can i flash OB18 over rooted OB18 and then update it to OB19 (ota). Then re-root.
The reason I'm asking this is i have a very limited data internet connection. So i can save GBs if this is doable.

XDRdaniel said:
Yes, sounds doable
Click to expand...
Click to collapse
Yeah. Well.. I'm gonna try this out myself. Thanks! :highfive:

GTRanushka said:
Not what i meant. Let's say I'm on rooted OB18. But i want to update it to OB19. all i have is OB18 stock firmware. So, can i flash OB18 over rooted OB18 and then update it to OB19 (ota). Then re-root.
The reason I'm asking this is i have a very limited data internet connection. So i can save GBs if this is doable.
Click to expand...
Click to collapse
Plan to keep a copy of OB18 around? If so, then yea absolutely it should work. Root will either modify your system or your kernel depending on the method, which both get overwritten if you flash stock.
Issue you'll probably end up having in the future though is that if you always use OB18, when it comes time to install OB20, you'll be downgrading without a wipe, which I don't think is a great idea.

GTRanushka said:
I wonder is it possible to flash stock unrooted OOS over rooted OOS in order to install small OTAs. After updates plan to root again. Does anyone know whether this is possible or not? And, any side effects could occur?
I search over internet and couldn't find any useful info about this.
Thanks in advance.
Click to expand...
Click to collapse
No you can't.
Because OTA will fail for "partition mismatching": the systemless root alters only but anyhow the /boot partition.
You must update with FOTA (Full OTAs), doesn't matter you're using stock or TWRP recovery.
The OxygenOS built-in updater should detects your system as modified and download only FOTAs.

Simone98RC said:
No you can't.
Because OTA will fail for "partition mismatching": the systemless root alters only but anyhow the /boot partition.
You must update with FOTA (Full OTAs), doesn't matter you're using stock or TWRP recovery.
The OxygenOS built-in updater should detects your system as modified and download only FOTAs.
Click to expand...
Click to collapse
Let's say he has open beta 18, rooted and twrp installed, if he flashes ob18 again over it, this will get rid both of the root and twrp, resulting in an untouched system, therefore, ota after this will be possible. He can then flash back twrp and root the device

XDRdaniel said:
Let's say he has open beta 18, rooted and twrp installed, if he flashes ob18 again over it, this will get rid both of the root and twrp, resulting in an untouched system, therefore, ota after this will be possible. He can then flash back twrp and root the device
Click to expand...
Click to collapse
But practically speaking, it's crazy to unroot system only for OTA.
It would be more reliable to download FOTAs on rooted system.
Then, if @GTRanushka is running Magisk (MagiskSU) as root method, it could be working even after firmware update.
Because of its systemless nature.

Simone98RC said:
But practically speaking, it's crazy to unroot system only for OTA.
It would be more reliable to download FOTAs on rooted system.
Then, if @GTRanushka is running Magisk (MagiskSU) as root method, it could be working even after firmware update.
Because of its systemless nature.
Click to expand...
Click to collapse
This would be weird because I always had to flash magisk after a ota update..

GTRanushka said:
I wonder is it possible to flash stock unrooted OOS over rooted OOS in order to install small OTAs. After updates plan to root again. Does anyone know whether this is possible or not? And, any side effects could occur?
I search over internet and couldn't find any useful info about this.
Thanks in advance.
Click to expand...
Click to collapse
In order to flash OTAS has to have stock rom but also recovery stock and bootloader blocked but not installed the OTAS otherwise it tells you that you have something modified and you have to download the complete rom. (That does not suit you)

ajnexus5 said:
In order to flash OTAS has to have stock rom but also recovery stock and bootloader blocked but not installed the OTAS otherwise it tells you that you have something modified and you have to download the complete rom. (That does not suit you)
Click to expand...
Click to collapse
You don't need a locked bootloader for OTA just have to flash stock full ROM zip and stock recovery then you're good to go

Simone98RC said:
But practically speaking, it's crazy to unroot system only for OTA.
It would be more reliable to download FOTAs on rooted system.
Then, if @GTRanushka is running Magisk (MagiskSU) as root method, it could be working even after firmware update.
Because of its systemless nature.
Click to expand...
Click to collapse
Why i try to unroot and do OTAs is the much less download size compared to FOTAs.

Renosh said:
You don't need a locked bootloader for OTA just have to flash stock full ROM zip and stock recovery then you're good to go
Click to expand...
Click to collapse
I tried it with the bootloader open and I did not think that something is not right that it has to download complete the rom.:

Magisk v14 and OTA updates

Hey, guys, I wanted to ask if someone tried OTA updates working with the new method of rooting released with magisk 14- a rooting method in which we do not need root or custom recovery beforehand, we just need to provide stock boot image dump to the magisk manager. This method will do us good because if OTA's still work after root we can be rooted on the stock roms without having to download full OTA's when a new update arrives. If someone can confirm working OTA's on the OOS open beta with this root method, it would be really helpful. Thank you!

As long as you take a backup of system and keep TWRP installed so you have a backup to revert to it should be fine. The risk of issues is just too high unless you don't give a **** about your personal data.

Puddi_Puddin said:
As long as you take a backup of system and keep TWRP installed so you have a backup to revert to it should be fine. The risk of issues is just too high unless you don't give a **** about your personal data.
Click to expand...
Click to collapse
Bro, I know how to work with TWRP. Your comment does not answer the question.

blaze95rs said:
Bro, I know how to work with TWRP. Your comment does not answer the question.
Click to expand...
Click to collapse
Well think of it about this. Magisk is just one big hack on the system partition. An OTA changes files on the system partition aswell. What if the OTA changes files that Magisk needs?
1. Your phone will go into a bootloop.
2. You might end up bricking it.
3. You just have to reflash Magisk.
4. Your phone becomes buggy as hell.
Thats why we also recommend to install the full zips when flashing roms and kernels that modify system because of possible conflicts.

Puddi_Puddin said:
Well think of it about this. Magisk is just one big hack on the system partition. An OTA changes files on the system partition aswell. What if the OTA changes files that Magisk needs?
1. Your phone will go into a bootloop.
2. You might end up bricking it.
3. You just have to reflash Magisk.
4. Your phone becomes buggy as hell.
Thats why we also recommend to install the full zips when flashing roms and kernels that modify system because of possible conflicts.
Click to expand...
Click to collapse
Obviously I would uninstall magisk and then install ota and reinstall magisk. Magisk is systemless so I think there shouldn't be any problem.

blaze95rs said:
Obviously I would uninstall magisk and then install ota and reinstall magisk. Magisk is systemless so I think there shouldn't be any problem.
Click to expand...
Click to collapse
See it for yourself! Its something most people do not recommend.

Puddi_Puddin said:
See it for yourself! Its something most people do not recommend.
Click to expand...
Click to collapse
You have missed the whole point of the post. This is a NEW method. Many people have not tried this method of root. So please, if you have any valuable information then only share. Do not litter. There should be logic to your answer and not general acceptance. Saying that many people do this or do that is not a very solid answer.

blaze95rs said:
You have missed the whole point of the post. This is a NEW method. Many people have not tried this method of root. So please, if you have any valuable information then only share. Do not litter. There should be logic to your answer and not general acceptance. Saying that many people do this or do that is not a very solid answer.
Click to expand...
Click to collapse
That doesn't matter. I get that it can be installed without a custom recovery. But that doesn't mean it won't conflict with possible ota's. Again, see it for yourself. Most people including me do rather play it the safe way.

I have recently updated to the lateset Oxygen OS Beta i had Magisk installed, i use Sparks Latest twrp version, with this you can install OTA updates. I dit not unlinstalled Magisk first, you do need the full rom file, but for me when i wanted to install the OTA, it found i had rooted and autmatacly downloaded the full rom. After you installed the update you can install the latest version of Magisk.

Receiving OTA updates while rooted

I'm planning on rooting my Moto Z Play but staying on the stock ROM as it has better battery life (according to XDA members) compared to LineageOS. I also really like Moto Display and all of the other exclusive features to this ROM.
However, I still want to receive OTAs after doing so. I've read that an app called FlashFire can help me with this.
Question 1: Do the OTAs download even if your system is rooted? I've read that some phones do download the OTAs, but fail when the flashing starts as they have a custom recovery, while some phones don't even download at all once it detects that you're rooted.
Question 2: Will it work even if I have TWRP installed?
Thank you.

Hi i dont think you can receive OTAs after unlocking bootloader and iff you do they will fail on installation as you have said. Secondly in my opinion you are right and i have tried almost all the roms on here and by far the stock N is the best rom for fluidity battery life app compatibility etc so i went back to stock but the deodexed N debloated version because im rooted. Iff i were you i would not root at this time because i think Official Oreo is about to be released for our phone and it would be a good idea to hangon a while but that is entirely your choice.

djdelarosa25 said:
However, I still want to receive OTAs after doing so. I've read that an app called FlashFire can help me with this.
Click to expand...
Click to collapse
Never really tested Flashify and FlashFire. If you succeed please write how it works, which steps to do to be on the safe side
djdelarosa25 said:
Question 1: Do the OTAs download even if your system is rooted? I've read that some phones do download the OTAs, but fail when the flashing starts as they have a custom recovery, while some phones don't even download at all once it detects that you're rooted.
Click to expand...
Click to collapse
Download fine. Install fails, yes.
djdelarosa25 said:
Question 2: Will it work even if I have TWRP installed?
Click to expand...
Click to collapse
No. That's why I never install twrp, I just boot it when needed. You need a computer and a cable every time you want to start twrp, but recovery partition stays untouched using fastboot boot.
Idea is:
1. Take a backup of boot partition before rooting
2. Install the kernel you need to avoid f2fs problems, then Magisk. Both modifies the boot partition, nothing else.
When an OTA arrives, you restore your backup of boot partition and everything is stock. OTA is supposed to work fine.

In theory, if I just run TWRP off from the PC and flash SuperSU on my phone without flashing TWRP, I would be rooted, right? And the OTAs would install, but I will lose root access?

djdelarosa25 said:
And the OTAs would install, but I will lose root access?
Click to expand...
Click to collapse
No. SuperSU modifies boot partition. OTA do not install while boot partition is modified.
You need to restore NANDROID backup of original stock boot partition prior to rooting, then you should be fine for install OTA.
---------- Post added at 11:45 ---------- Previous post was at 11:29 ----------
Just an additional hint: Modifying logo also prevents OTA. If you suppress that unlocked bootloader warning with a different logo, of course you need to restore the original logo partition before applying OTA.

tag68 said:
No. SuperSU modifies boot partition. OTA do not install while boot partition is modified.
You need to restore NANDROID backup of original stock boot partition prior to rooting, then you should be fine for install OTA.
Just an additional hint: Modifying logo also prevents OTA. If you suppress that unlocked bootloader warning with a different logo, of course you need to restore the original logo partition before applying OTA.
Click to expand...
Click to collapse
That's a pity. Oh well, I might just have to wait for Oreo.
Thanks a lot!

"'Just an additional hint: Modifying logo also prevents OTA"
Actually...not my experience. I have an unlocked bootloader, flashed a stock rom file by file, except for logo.bin, which is a modded one to get rid of the annoying "untrustworthy" startup screen.
All worked well and recently got the OTA update all installed as normal by the system.
Will wait now to get the official oreo update before i muck around further.
Actually, on the 22-2-8 build on the phone now it runs really well and battery life is great. Getting over 2 days in my usage pattern easy.
Camera good as well. Got some nice photos of the local beach last night.

You can get back to stock, and get ota's
https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-bootloader-to-lasted-stock-t3718190

Note: Lock of Bootloader is not required to get OTA update. It makes sure that you do no action which prevents OTA, but if you take care this does not happen (for instance not rooting which modifies system or boot partition), you eg can take advantage of Nandroid backup only booting TWRP for this purpose.

Installing OTA update while rooted (Magisk) and with TWRP recovery

I'm on the stock ROM (Build number: OPNS27.76-12-22-3), rooted via Magisk and have the latest TWRP as my recovery. Say, an OTA update arrives (hopefully) in the future, could I just sideload it from my computer via adb? I know that downloading the file and installing it using the phone won't work as I'm on TWRP (it requires stock recovery). Erfan Abdi's website allows the download of the OTA zip from Moto's servers if one wants to sideload it via adb (https://erfanoabdi.000webhostapp.com/). If not, how can I apply the OTA update?

no you can't apply the ota with a custom recovery as you made changes on partitions that ota.zip check if has some changes and i believe twrp is not ready to aply ota in any way because every manufacture has a way to make changes by ota so its almost impossible to made a generic way to apply ota to all the devices that twrp suports

jst98 said:
no you can't apply the ota with a custom recovery as you made changes on partitions that ota.zip check if has some changes and i believe twrp is not ready to aply ota in any way because every manufacture has a way to make changes by ota so its almost impossible to made a generic way to apply ota to all the devices that twrp suports
Click to expand...
Click to collapse
So I should flash the stock recovery back and then sideload the OTA?

djdelarosa25 said:
So I should flash the stock recovery back and then sideload the OTA?
Click to expand...
Click to collapse
flash stock, take the ota's via ota, and then mod system. At least that's what I do. pita but it works. I back up with TBPro and copy backup to PC (ota clears internal storage) before I do that so rebuild is pretty quick.

my last smartphone is just uninstall magisk and flash stock recovery to aply ota, but i never tried this on moto z play, so you should do a clean install of stock rom first, because i can't say with sure if it's gonna work as my last devices stops update on marshmallow , and magisk that i used on this phone is older

jst98 said:
my last smartphone is just uninstall magisk and flash stock recovery to aply ota, but i never tried this on moto z play, so you should do a clean install of stock rom first, because i can't say with sure if it's gonna work as my last devices stops update on marshmallow , and magisk that i used on this phone is older
Click to expand...
Click to collapse
I have to flash stock to take ota. ymmv. Let me know if AUG is out.

I just did an uninstall latest magisk uninstall and pogo doesn't work, so it's not clean, so will need to flash stock.

KrisM22 said:
I just did an uninstall latest magisk uninstall and pogo doesn't work, so it's not clean, so will need to flash stock.
Click to expand...
Click to collapse
there some things that have be analised here, first when you unistall magisk, the safetynet verification is gonna fail, and pogo can broke, and pogo is especially case, the pogo app checks storage to see if has some folder related magisk, that in most cases are left there to backup. and the ota check partition if you change something ota fails too.
stock ota is horrible to install if you have some changes in the device, so in almost all case, especialy if don't have advanced knowledge about all android work, the recomended is reflash system in same version that you are, and after this update.

jst98 said:
there some things that have be analised here, first when you unistall magisk, the safetynet verification is gonna fail, and pogo can broke, and pogo is especially case, the pogo app checks storage to see if has some folder related magisk, that in most cases are left there to backup. and the ota check partition if you change something ota fails too.
stock ota is horrible to install if you have some changes in the device, so in almost all case, especialy if don't have advanced knowledge about all android work, the recomended is reflash system in same version that you are, and after this update.
Click to expand...
Click to collapse
a) right. what I said. uninstall magisk is dirty - it doesn't clean everything up..
b) I could suggest TBPro to back up your system. Then be sure to copy that backup to your PC because flashing the stock will wipe internal storage. Then flash stock. Then use TBPro to restore stuff. At least that's sortof what I do.

what i did to update to latest security patch:
- flash uninstall magisk zip
- flash stock recovery
- take official ota
- reflash f2fs fix and magisk

JonasVFC said:
what i did to update to latest security patch:
- flash uninstall magisk zip
- flash stock recovery
- take official ota
- reflash f2fs fix and magisk
Click to expand...
Click to collapse
what security date are you on? Thanks.

KrisM22 said:
what security date are you on? Thanks.
Click to expand...
Click to collapse
june

JonasVFC said:
june
Click to expand...
Click to collapse
Thanks. That's what I'm on. I was wondering if Aug was out...

KrisM22 said:
Thanks. That's what I'm on. I was wondering if Aug was out...
Click to expand...
Click to collapse
Damn, Motorola's taking so long again.

djdelarosa25 said:
Damn, Motorola's taking so long again.
Click to expand...
Click to collapse
and then there's Pie... Apparently with Treble. I think a lot of new stuff coming at us soon...
I think it's about time for me to do some serious playing and looked and i see that Alberto97 is working on 9 ... hmmmmmmm.

JonasVFC said:
what i did to update to latest security patch:
- flash uninstall magisk zip
- flash stock recovery
- take official ota
- reflash f2fs fix and magisk
Click to expand...
Click to collapse
August security patch is out so I tried these steps.
It didn't work. While I sideloaded the update through adb, it showed that the system was modified and that it was mounted as R/W 40 times, also showing the most recent date and time that it happened. Keep in mind, I flashed the Magisk and Xposed uninstallers and cleared Dalvik and cache before the attempt to sideload.
I just flashed the original June build (omitting the 'fastboot erase userdata' command to save myself from a potential pain in the ass) and then did I proceed to sideload the update via adb. After that, I flashed the latest TWRP and rooted using the latest Magisk (and f2fs fix as well). My data is intact (except for the root modifications and Magisk modules) but that is miles better than starting from scratch off a factory data reset.
I guess I answered my own question, then . You can't

KrisM22 said:
and then there's Pie... Apparently with Treble. I think a lot of new stuff coming at us soon...
I think it's about time for me to do some serious playing and looked and i see that Alberto97 is working on 9 ... hmmmmmmm.
Click to expand...
Click to collapse
lol we are done. nothing new will come to us (owners of z1 play)

JonasVFC said:
lol we are done. nothing new will come to us (owners of z1 play)
Click to expand...
Click to collapse
yeah, lol, I'm playing with Pie. - Nothing new... HAH! silly rabbit.

djdelarosa25 said:
While I sideloaded the update through adb, it showed that the system was modified and that it was mounted as R/W 40 times, also showing the most recent date and time that it happened.
Click to expand...
Click to collapse
Do you have an idea how to easily display if system is modified (when, how often etc.)? I'd like to know if OTA could succeed after restoring boot partition for some Moto X Play and Moto Z Play with installed Magisk.

tag68 said:
Do you have an idea how to easily display if system is modified (when, how often etc.)? I'd like to know if OTA could succeed after restoring boot partition for some Moto X Play and Moto Z Play with installed Magisk.
Click to expand...
Click to collapse
Nope, sorry. Though, I failed to mention that I did flash the original boot.img after encountering the error and tried again. You guessed it, it still failed. Maybe try flashing both boot and oem to see if it would work?