Database Users

Stagefright updates.

Just read that LG is planning on monthly updates for security reasons....
http://phandroid.com/2015/08/06/lg-...ey-too-will-release-monthly-security-updates/
Wish I didn't unlock? Or are we going to have those patches here available?

They better should enable bootloader unlocking for everyone.
Then each LG user can flash his own ROM and solve security issues very quickly with the community.
Nice announcement, but the stagefrighter hole is gaping and gaping...

*justintime* said:
Just read that LG is planning on monthly updates for security reasons....
http://phandroid.com/2015/08/06/lg-...ey-too-will-release-monthly-security-updates/
Wish I didn't unlock? Or are we going to have those patches here available?
Click to expand...
Click to collapse
you have unlocked the bootloader, so you have a custom recovery and could of course install any rom .
Sure at the moment there are not a lot roms available, but the official ones are however posted...
beside that, i don't think that unlocking the bootloader (and rooting the phone) will disable the OTA feature...

alain57 said:
you have unlocked the bootloader, so you have a custom recovery and could of course install any rom .
Sure at the moment there are not a lot roms available, but the official ones are however posted...
beside that, i don't think that unlocking the bootloader (and rooting the phone) will disable the OTA feature...
Click to expand...
Click to collapse
Not? On HTC OTA updates were not possible...
Yes those custom roms.... Sigh... I think we will get them if a can choose another phone[emoji3]

Or... Use an app with built in protection for that issue?

*justintime* said:
Just read that LG is planning on monthly updates for security reasons....
http://phandroid.com/2015/08/06/lg-...ey-too-will-release-monthly-security-updates/
Wish I didn't unlock? Or are we going to have those patches here available?
Click to expand...
Click to collapse
As I read OTA won't work on a unlocked phone.
But you can get the KDZ and flash this - you will need to root again though...
Greetings
Medzinmann

*justintime* said:
Just read that LG is planning on monthly updates for security reasons....
http://phandroid.com/2015/08/06/lg-...ey-too-will-release-monthly-security-updates/
Wish I didn't unlock? Or are we going to have those patches here available?
Click to expand...
Click to collapse
You will still be able to receive the updates, unlocking the bootloader does not stop you receiving OTA updates.

Medizinmann said:
As I read OTA won't work on a unlocked phone.
But you can get the KDZ and flash this - you will need to root again though...
Greetings
Medzinmann
Click to expand...
Click to collapse
the bootloader itself does not change anything to the OTA process
but changing the recovery may block the OTA from working ... the phone may download the update but the custom recovery may not understand it :silly:
but most of the time, people find a way to create a flashable zip to make an update for custom recovery

alain57 said:
the bootloader itself does not change anything to the OTA process
but changing the recovery may block the OTA from working ... the phone may download the update but the custom recovery may not understand it :silly:
but most of the time, people find a way to create a flashable zip to make an update for custom recovery
Click to expand...
Click to collapse
I didn't try it myself, but people in the low effort root thread wrote it didn't work.
They got an error like "update not possible - suspicious root" or something.
http://forum.xda-developers.com/showthread.php?p=62250050
I will try today and see if it works.
I could download the OTA Update, if it works I will try this evening.
Greetings
Medzinmann

Medizinmann said:
I didn't try it myself, but people in the low effort root thread wrote it didn't work.
They got an error like "update not possible - suspicious root" or something.
http://forum.xda-developers.com/showthread.php?p=62250050
I will try today and see if it works.
I could download the OTA Update, if it works I will try this evening.
Greetings
Medzinmann
Click to expand...
Click to collapse
Yeah they couldn't OTA as they had rooted, not because they had unlocked their bootloader.
OTA are still made available to people with unlocked bootloaders, just not to people who have rooted. At the end of the day you can just find the KDZ and flash it to update or make an update zip to do it from custom recovery.

IIIIkoolaidIIII said:
Yeah they couldn't OTA as they had rooted, not because they had unlocked their bootloader.
OTA are still made available to people with unlocked bootloaders, just not to people who have rooted. At the end of the day you can just find the KDZ and flash it to update or make an update zip to do it from custom recovery.
Click to expand...
Click to collapse
That might be right, but as they said a simple unroot wouldn't work.
And BTW what is the point in unlocking the bootloader when you don't want to root?
I mean custom rom maybe but they are usually rooted as well for obvious reasons etc.
Greetings
Medzinmann

Medizinmann said:
That might be right, but as they said a simple unroot wouldn't work.
And BTW what is the point in unlocking the bootloader when you don't want to root?
I mean custom rom maybe but they are usually rooted as well for obvious reasons etc.
Greetings
Medzinmann
Click to expand...
Click to collapse
Unrooting via flashing a clean image worked fine for me, got OTA and then flashed new root.

IIIIkoolaidIIII said:
Unrooting via flashing a clean image worked fine for me, got OTA and then flashed new root.
Click to expand...
Click to collapse
As I said one could always get the most recent KDZ and flash this and reroot. A working OTA would make this just a little more convenient...that's all.
Greetings
Medzinmann

Just unroot, uninstall SuperSu and fire up LG Bridge. Install update. Flash root with twrp. Finish. Did that yesterday.
Sent from outer space using telepathy

does the new update fix stagefright?

On t-mobile it did.
Sent from my LG-H811 using XDA Free mobile app

Alright so I have a problem with the touch functionality of my phone. I have an LG G4 811 T-mobile variant. The new update is supposed to resolve that but I'm not sure how to update on a rooted device with twrp installed (update stagefrieght). I'm looking for a zip file and i have not managed to find it at all. Could someone help? Also if this is misplaced please devs move it or point me in the right direction to which my question can be answered.
---------- Post added at 02:25 AM ---------- Previous post was at 02:24 AM ----------
fpsq said:
Just unroot, uninstall SuperSu and fire up LG Bridge. Install update. Flash root with twrp. Finish. Did that yesterday.
Sent from outer space using telepathy
Click to expand...
Click to collapse
and this for sure worked with you?

Yes, it worked perfectly fine for my LG G4 H815 unlocked! Now on V10d-EUR-XX. Stagefright is fixed. ****ing sim issue (com.android.phone crashes, does NOT restart itself) remains. Support is worthless. Found a workaround myself.

LG lied about that updates. They never repaired these bugs and now it has About 50 stagefright etc vurnerabilities.

What updates you say? I'm still on V20D since January LoL LG is a joke.
Στάλθηκε από το LG-H815 μου χρησιμοποιώντας Tapatalk

Marshmallow

LG is most likely developing the Android 6.0 Marshmallow operating system and may release it for its G3 and G4 flagships via an over-the-air (OTA) update, in the coming weeks. Although the update schedule is yet to be revealed.
The company's Korean support site has listed the Android 6.0 Marshmallow update for some variants of the LG G3 and LG G4 flagships, which include the LG G3 F400S, F400K and F400L as well as the LG G4 F500S, F500K and F500L. All these variants are currently running on Android Lollipop operating system.
Click to expand...
Click to collapse
View full post here: http://www.ibtimes.co.uk/android-6-0-marshmallow-update-lg-g3-g4-likely-be-released-soon-1522322

I'd say it's coming as the T-Mobile support page says it's in testing/already developed. (And that's a US Carrier variant)
https://support.t-mobile.com/community/phones-tablets-devices/software-updates#tmoSUPDocTitle
Sent From My LG G4

I'm guessing this will mean a new root method will be required?

Knowbody42 said:
I'm guessing this will mean a new root method will be required?
Click to expand...
Click to collapse
Also a 6 month+ wait for Telstra to do their "testing". Unless we can simply flash it the way we do now with locked bootloaders and injecting root.

I'm excited for the camera app from the V10 being ported over!!

I hope it has better power managment..battery gets warm to hot with some apps and lag is still a problem on non rooted phone..

I'm hoping that it'll only be a couple weeks before MM is released to the G4, but I'd be happy if it's before the new year. It would make sense to have it out before Xmas so people might buy the G4 as a gift.
I guess not too many of the general public are going to care/know about the latest release of android, whereas people do want something that can handle iOS 9 or whatever version they're on now.

Here's hoping for a fairly quick release and a screen saturation control!
Amazed at how much the price of the G4 has dropped. I bought mine for £360 three weeks ago and it's dropped another £42 since! Probably £299 by Xmas. Why bother waiting for a One Plus/Nexus etc.?

bustervic said:
I'm excited for the camera app from the V10 being ported over!!
Click to expand...
Click to collapse
+1
It is inevitable i believe because both phones use identical sensors...
frnkly said:
I hope it has better power managment..battery gets warm to hot with some apps and lag is still a problem on non rooted phone..
Click to expand...
Click to collapse
+1
We should get much better battery life, especially in stand-by. But i'm hoping for beter power managment
while in use and a better optimised cpu governor... Lag shoulden't be a problem in MM...
daglesj said:
Here's hoping for a fairly quick release and a screen saturation control!
Click to expand...
Click to collapse
+1
That would be great...

I'm wondering how long it will take Big Red to push this out.

Knowbody42 said:
I'm guessing this will mean a new root method will be required?
Click to expand...
Click to collapse
Possibly, but at the same time, possibly not.
The current low effort root method actually uses a bootloader exploit which COULD not be patched by the new version (This is a BIG IF). If this is the case, we'd be able to use the same exact method as before to inject root.
---------- Post added at 05:57 PM ---------- Previous post was at 05:46 PM ----------
Also, don't want to be a party pooper, but LG promised the Lollipop release "Soon" last year and ended up taking a long time to release it through most vendors... So I don't trust LG on that front.

karendar said:
Possibly, but at the same time, possibly not.
The current low effort root method actually uses a bootloader exploit which COULD not be patched by the new version (This is a BIG IF). If this is the case, we'd be able to use the same exact method as before to inject root.
---------- Post added at 05:57 PM ---------- Previous post was at 05:46 PM ----------
Also, don't want to be a party pooper, but LG promised the Lollipop release "Soon" last year and ended up taking a long time to release it through most vendors... So I don't trust LG on that front.
Click to expand...
Click to collapse
Well said, it's a big if... But nevertheless, someone will find out the way to root, someone always does
About the MM release, i believe it will be out around the new year, probbably in early january :fingers-crossed:

Knowbody42 said:
I'm guessing this will mean a new root method will be required?
Click to expand...
Click to collapse
The M update will be hell for root on bootloader locked devices....Lets assume they close the initial exploit used in Low Effort Root, that means a new exploit must be found (which certainly is possible but will take time). The problem is right now you can't root on M without a custom kernel, the stock M kernel doesnt play nice with SuperSU (causes bootloops), also by default M restricts read/write access to the system partition even with root. So again a custom kernel is needed to defeat these. If you have a bootloader locked device its going to be very difficult to root your device on M. Hopefully the devs can find something but if you need root best move on to a bootloader unlockable device/variant.
---------- Post added at 12:02 PM ---------- Previous post was at 12:01 PM ----------
karendar said:
Possibly, but at the same time, possibly not.
The current low effort root method actually uses a bootloader exploit which COULD not be patched by the new version (This is a BIG IF). If this is the case, we'd be able to use the same exact method as before to inject root.
---------- Post added at 05:57 PM ---------- Previous post was at 05:46 PM ----------
Also, don't want to be a party pooper, but LG promised the Lollipop release "Soon" last year and ended up taking a long time to release it through most vendors... So I don't trust LG on that front.
Click to expand...
Click to collapse
M will likely require a new bootstack, guaranteed that LG patches the backdoor, i'd be very surprised if they left it open. Even if you inject the current SU binary/SuperSU it doesnt play nicely with a stock compiled M kernel, causes bootloops on Nexus Devices, so that means you need a custom kernel unless Chainfire can figure out how to make it work with the default M kernel.

djkinetic said:
The M update will be hell for root on bootloader locked devices....Lets assume they close the initial exploit used in Low Effort Root, that means a new exploit must be found (which certainly is possible but will take time). The problem is right now you can't root on M without a custom kernel, the stock M kernel doesnt play nice with SuperSU (causes bootloops), also by default M restricts read/write access to the system partition even with root. So again a custom kernel is needed to defeat these. If you have a bootloader locked device its going to be very difficult to root your device on M. Hopefully the devs can find something but if you need root best move on to a bootloader unlockable device/variant.
---------- Post added at 12:02 PM ---------- Previous post was at 12:01 PM ----------
M will likely require a new bootstack, guaranteed that LG patches the backdoor, i'd be very surprised if they left it open. Even if you inject the current SU binary/SuperSU it doesnt play nicely with a stock compiled M kernel, causes bootloops on Nexus Devices, so that means you need a custom kernel unless Chainfire can figure out how to make it work with the default M kernel.
Click to expand...
Click to collapse
I'm not really worried about a root method for M... There will be a method by the time M comes out for our phone.
The current exploit, I'd also be surprised if they didn't patch it(as I mentioned) , but then again, I've seen exploits not be patched by major versions, so it's not impossible. Only a release will tell us.

karendar said:
I'm not really worried about a root method for M... There will be a method by the time M comes out for our phone.
The current exploit, I'd also be surprised if they didn't patch it(as I mentioned) , but then again, I've seen exploits not be patched by major versions, so it's not impossible. Only a release will tell us.
Click to expand...
Click to collapse
I'm not as optimistic as you. Yes, the exploit we used to root may still be open (after all, they left it open on the G3 -> G4). But a new problem is present: Starting with Android 6.0 all kernels now use a forceencrypt flag. Even all Nexus users have had to flash a custom kernel which flips the flag to noforceencrypt before they could root - that was never the case in the past and Nexus users could just flash SuperSU on the stock kernel and be done with it. Not anymore. Google is locking things down in the interest of security.
You can try it yourself if you have a Nexus. Flash SuperSU on the stock 6.0 kernel. You'll bootloop as the kernel won't allow the system to boot while SuperSU is installed. Only way to root is to flash a custom kernel with the proper modifications to allow root.
The reason this is a problem for us G4 users is, since we have locked bootloaders (with the exception of a few international units), we cannot flash custom kernels. No kernel flashing = no way to flip noforceencrypt in the kernel = no root on M Sure, you can maybe find a way to get SuperSU and the root binaries in there, but when you try to boot you'll just bootloop as the system won't let you in.
Maybe a workaround will be found, but this new kernel security is a seriously blow to our ability to attain root on the G4 running M.

biff6789 said:
I'm not as optimistic as you. Yes, the exploit we used to root may still be open (after all, they left it open on the G3 -> G4). But a new problem is present: Starting with Android 6.0 all kernels now use a forceencrypt flag. Even all Nexus users have had to flash a custom kernel which flips the flag to noforceencrypt before they could root - that was never the case in the past and Nexus users could just flash SuperSU on the stock kernel and be done with it. Not anymore. Google is locking things down in the interest of security.
You can try it yourself if you have a Nexus. Flash SuperSU on the stock 6.0 kernel. You'll bootloop as the kernel won't allow the system to boot while SuperSU is installed. Only way to root is to flash a custom kernel with the proper modifications to allow root.
The reason this is a problem for us G4 users is, since we have locked bootloaders (with the exception of a few international units), we cannot flash custom kernels. No kernel flashing = no way to flip noforceencrypt in the kernel = no root on M Sure, you can maybe find a way to get SuperSU and the root binaries in there, but when you try to boot you'll just bootloop as the system won't let you in.
Maybe a workaround will be found, but this new kernel security is a seriously blow to our ability to attain root on the G4 running M.
Click to expand...
Click to collapse
Yea with the current changes that Google made with M at the kernel level bootloader locked devices have very little hope of being rooted, the reason why we can still root on nexus devices is because our bootloaders are unlockable you take that away and we would be in the same boat, this release of android has pretty much signaled the end of me buying any carrier phones that i know will be locked down. its simply too much hassle for most devs to bother with finding new exploits in the coming android versions.

Rydah805 said:
I'd say it's coming as the T-Mobile support page says it's in testing/already developed. (And that's a US Carrier variant)
https://support.t-mobile.com/community/phones-tablets-devices/software-updates#tmoSUPDocTitle
Sent From My LG G4
Click to expand...
Click to collapse
Man. Sweet.
Sent from my LG-H811 using Tapatalk

Rydah805 said:
I'd say it's coming as the T-Mobile support page says it's in testing/already developed. (And that's a US Carrier variant)
https://support.t-mobile.com/community/phones-tablets-devices/software-updates#tmoSUPDocTitle
Sent From My LG G4
Click to expand...
Click to collapse
It does? It looks to me like it says both the g3 and g4 are in Manufacturer Development not testing. The nexus 6 is the only device I see that's in testing. I would be shocked if it comes out before December and I would not be shocked if we don't see it until next year.

biff6789 said:
The reason this is a problem for us G4 users is, since we have locked bootloaders (with the exception of a few international units), we cannot flash custom kernels. .
Click to expand...
Click to collapse
Please, most of the world has unlocked bootloaders.

Mad_Duke said:
Please, most of the world has unlocked bootloaders.
Click to expand...
Click to collapse
Just Europe and T-Mobile USA (AFAIK) at the moment.
The percentage of G4's with unlockable bootloaders is pretty small.

[DISCUSSION] System-less technology

As many of you should know, Super SU and Xposed framework have recently developed a new technique called "system-less installation" on Android 6.0. The purpose for it is said to be letting user to receive OTA from the OEM. However, when I am in quite a belief that this technique will enable us receive and install OTAs, suddenly I thought of a problem which many posts in this sub-forum have had mentioned, which is HTC OTAs requires a clean and untouched system in order to install OTA successfully. And my status in HBOOT still says "Modified" and "Unlocked". My question is can I really receive and install OTAs ( if any ) onto my device with the two system-less patches and the status in HBOOT remain unchanged?
Sent from my HTC Desire 820u via Tapatalk

I think your bootloader status say moodified because you edited the system while your phone is S-ON
You can flash the RUU and you will get the official status back
And the Unlocked bootloader does not affect OTA installition
My phone is S-Off and i have modified system but the status still official

Kellwa said:
I think your bootloader status say moodified because you edited the system while your phone is S-ON
You can flash the RUU and you will get the official status back
And the Unlocked bootloader does not affect OTA installition
My phone is S-Off and i have modified system but the status still official
Click to expand...
Click to collapse
You mean after I S-OFF my phone then my worry should be gone?
Sent from my htc_a51dtul using XDA Labs

iSaidyiu said:
You mean after I S-OFF my phone then my worry should be gone?
Sent from my htc_a51dtul using XDA Labs
Click to expand...
Click to collapse
Am not 100% sure but yes when your S-OFF you can do anything with your phone
Note : anything you do is your responsability and no one else

Kellwa said:
Am not 100% sure but yes when your S-OFF you can do anything with your phone
Note : anything you do is your responsability and no one else
Click to expand...
Click to collapse
Well I m going to S-OFF it today, let see what I can do in the system or with the OTA packages and I will keep you guys posted asap.
Sent from my htc_a51dtul using XDA Labs

iSaidyiu said:
Well I m going to S-OFF it today, let see what I can do in the system or with the OTA packages and I will keep you guys posted asap.
Sent from my htc_a51dtul using XDA Labs
Click to expand...
Click to collapse
Even if you are s-off and edited the system you will no be able to install OTA

Is Xposed is officially supported with system-less?
HTC OTA checks integrity of system files before it starts update process. I don't know if it's checks boot partition. I think it may be work. But after update you will have stock boot partition and you will have to root again.
Wysłano z Tapatalk / Sent with Tapatalk

QkiZMR said:
Is Xposed is officially supported with system-less?
HTC OTA checks integrity of system files before it starts update process. I don't know if it's checks boot partition. I think it may be work. But after update you will have stock boot partition and you will have to root again.
Wysłano z Tapatalk / Sent with Tapatalk
Click to expand...
Click to collapse
Xposed is NOT YET officially supported with systemless arch but rovo89 has shown his interest in implementing this feature into the official channel. As up to my knowledge, there are su.img and xposed.img under /data wich may be served as auto recovery after OTA update. Well I have to get around the Xposed General longer to try my best to gather as much info. as I can so that I can have a throughout understanding of the whole situation.
Btw, I have S-OFFed my phone ( finally ) at a local retail shop for about HKD$100 ( about USD$12 ) . Finally I can modify my build.prop and /system! Whoa!
Sent from my htc_a51dtul using XDA Labs

So what does this SystemLess thing do? I couldnt actually get what you said in OP
what ota does it give to you?

Kianush said:
So what does this SystemLess thing do? I couldnt actually get what you said in OP
what ota does it give to you?
Click to expand...
Click to collapse
Systemless allows you to install OTAs released by the OEM as it wont modify /system and so it can pass OTAs system completeness test so as to install them successfully.
You may head to the unofficial systemless xposed post for more details.
Sent from my htc_a51dtul using XDA Labs

Just got a software update

Looks to be some type of security updates.

Just popped on mine. Installed the update.
Matches this Software Version: MMB29M.N910VVRU2CPG2
https://www.verizonwireless.com/support/samsung-galaxy-note-4-update/
Kernel 3.10.40
Android Version 6.0.1
Android Patch Level September 1,2016
Baseband Version N910VVRU2CPG2

Will this update break Foxfi for Verizon Note 4?

Anyone know if PG2 does anything to the bootloader to prevent rolling back?
Sent from my SM-N910V using Tapatalk

subzero2000 said:
Anyone know if PG2 does anything to the bootloader to prevent rolling back?
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
It appears to be a boot.img update. Flashfire rejected it as a safe OTA and I proceeded to freeze System Updates with Titanium Backup to eliminate future notifications. A bootloader update for sure.

Hopefully someone can tell if it's locking the bootloader down to prevent downgrading or the bootloader unlock method. Is there a way to freeze the update prompts if I'm not rooted yet? Just got the phone and haven't had a chance to unlock and root this bad boy.
Sent from my VS990 using Tapatalk

corporal_hades said:
Hopefully someone can tell if it's locking the bootloader down to prevent downgrading or the bootloader unlock method. Is there a way to freeze the update prompts if I'm not rooted yet? Just got the phone and haven't had a chance to unlock and root this bad boy.
Sent from my VS990 using Tapatalk
Click to expand...
Click to collapse
buy package disabler. it is well worth the $1 price tag

Use Debloater, then freeze SDM.apk.
Root not required, very easy.

No, it does not break Foxfi.

Could someone please upload the ota zip file

Could you provide more details on how to do this please? I download it and disabled the package listed in the post below yours but I still get the stupid notification to update. Thanks
Edit. Oops, meant to quote hwaa18, not sure why it didn't let me, thanks

Nobody around here anymore?

PapaDocta said:
Could someone please upload the ota zip file
Click to expand...
Click to collapse
I'm relatively new here, with regard to uploads. I am on a vzw Note 4, running Jasminerom 7.0, with an unlocked bootloader. I don't even have an SDM, as it wasn't present on the ROM, however I found a post for shutting off Samsung updates that required shutting off two system update modules, and one or two other software and security modules. I'm beginning to think Samsung is in collusion with the carriers to make our phones obsolete, and prevent further mods. If you let me know how and where to upload to you, I can send you the file, if you still want it.
Sent from my SM-N910V using XDA-Developers Legacy app

Renegade_2k said:
I'm relatively new here, with regard to uploads. I am on a vzw Note 4, running Jasminerom 7.0, with an unlocked bootloader. I don't even have an SDM, as it wasn't present on the ROM, however I found a post for shutting off Samsung updates that required shutting off two system update modules, and one or two other software and security modules. I'm beginning to think Samsung is in collusion with the carriers to make our phones obsolete, and prevent further mods. If you let me know how and where to upload to you, I can send you the file, if you still want it.
Click to expand...
Click to collapse
Thank you so much, I already sold my Note 4 and got s7 edge till they release note 8.

What happens if I update being rooted?

Hey guys, what happens if I update while I get rooted? My phone suggests me the 139.50 update, but I'm rooted, will it work? Do I need to root it again after the update?
Thank you I'm sorry for the stupid questions. This is my first post with this account, I'm not that newbie but I've never had a Motorola phone.

Guygiorge said:
Hey guys, what happens if I update while I get rooted? My phone suggests me the 139.50 update, but I'm rooted, will it work? Do I need to root it again after the update?
Thank you I'm sorry for the stupid questions. This is my first post with this account, I'm not that newbie but I've never had a Motorola phone.
Click to expand...
Click to collapse
Since you're rooted, I'm assuming you probably have a custom recovery like TWRP installed.
Any official update (OTA) will work only with a stock Android recovery installed.
This means no, you cannot have an OTA update once you root. However, there is a thread on this forum somewhere which has a very reliable but slightly complicated method of getting OTA updates even of rooted.
You may refer to that. And ya, welcome to the XDA family!
Sent from my Moto G (4) using Tapatalk

1chrome said:
Since you're rooted, I'm assuming you probably have a custom recovery like TWRP installed.
Any official update (OTA) will work only with a stock Android recovery installed.
This means no, you cannot have an OTA update once you root. However, there is a thread on this forum somewhere which has a very reliable but slightly complicated method of getting OTA updates even of rooted.
You may refer to that. And ya, welcome to the XDA family!
Sent from my Moto G (4) using Tapatalk
Click to expand...
Click to collapse
Thank you so much. It looks way harder than I thought. You need to update each version til the latest one. SMH. I'm not trying to be spoon fed here. But do you remember the keywords to this thread?
LOL it seems like it's gonna be a long day to update my phone.

https://r.tapatalk.com/shareLink?ur...share_tid=3472658&share_fid=3793&share_type=t
[GUIDE] Sucsessful OTA-Update after Rooting + other system changes
Sent from my Moto G (4) using Tapatalk
---------- Post added at 05:33 PM ---------- Previous post was at 05:31 PM ----------
Thread name:
[GUIDE] Sucsessful OTA-Update after Rooting + other system changes
Sorry not able to paste link from my app!
Sent from my Moto G (4) using Tapatalk