Database Info

[Q] Does rooting affect OTA?

Hi guys,
I was wondering if rooting the phone interferes with the ability to receive OTA's?
I know OTA doesn't work with most other devices after rooting but I'm hoping it works with the OnePlus One as it comes with CM as stock rom...
Thanks!
Regards

Pihkal said:
Hi guys,
I was wondering if rooting the phone interferes with the ability to receive OTA's?
I know OTA doesn't work with most other devices after rooting but I'm hoping it works with the OnePlus One as it comes with CM as stock rom...
Thanks!
Regards
Click to expand...
Click to collapse
Just got my Oneplus today. My experience through 4 updates is that SuperSU gets uninstalled, which unroots your phone. You just need to boot into TWRP and reflash SuperSU after the updates and you're rooted again.

jtchinoy said:
Just got my Oneplus today. My experience through 4 updates is that SuperSU gets uninstalled, which unroots your phone. You just need to boot into TWRP and reflash SuperSU after the updates and you're rooted again.
Click to expand...
Click to collapse
As long as it installs the OTA I'm fine with reflashing SuperSU.
And judging from your reply TWRP also doesn't interfere with installing the OTA, great! :good:
Guess I'll be unlocking my bootloader (and having my phone wiped, damned) and rooting it.
Can't live without the Xposed Framework. :laugh:
Thanks!

Pihkal said:
As long as it installs the OTA I'm fine with reflashing SuperSU.
And judging from your reply TWRP also doesn't interfere with installing the OTA, great! :good:
Guess I'll be unlocking my bootloader (and having my phone wiped, damned) and rooting it.
Can't live without the Xposed Framework. :laugh:
Thanks!
Click to expand...
Click to collapse
could of searched and found the answer... question has been asked quite a few times. also there is a setting in SuperSu to keep root in upgrades. Either way OTA or just wait for a rooted version which you probably would get faster than OTA in most cases
https://forums.oneplus.net/threads/persistent-root-after-ota.49868/
http://forum.xda-developers.com/oneplus-one/help/ota-updates-root-t2848715
http://forum.xda-developers.com/oneplus-one/help/ota-updates-root-unlock-t2873263
http://forum.xda-developers.com/oneplus-one/help/to-root-stay-stock-getting-ota-s-t2809334
http://www.reddit.com/r/oneplus/comments/2eyf2t/ota_after_root/
and there's more......

Lollipop-No more OTAs for rooted devices. How will you update rooted stock devices?

I By now everyone must be aware that Lollipop has a new way of checking for system mods that will prevent rooted devices from taking OTAs. Has anyone thought through what the easiest and best procedure will be for updating the firmware going forward? I've applied the lollipop OTA but have been holding back on root until I have a firm hold on how updates will work. I feel there must be many less technical people out there with the same concerns.
From Android Police:
With Lollipop, this has all been turned on its head because now, the OTA script no longer patches individual files. Instead, it patches the system block directly and treats it as one enormous blob. Here's a look at the update script in a recent Nexus 9 OTA:
image
From a technical standpoint, the reason behind the change has to do with verified boot, which was first introduced in KitKat. Even though Google has yet to enable this feature on a Nexus device, this move seems to indicate that the company could be preparing to go that route in the future.
Even outside of verified boot, though, it makes all the sense in the world to do OTAs this way. Patching the system block directly is far faster than trying to patch a lot of individual files. That said, if you're one of those who like to tinker with your devices, you'll have to flash a completely stock system image before applying an update because changing anything by so much as one byte will throw off the signature and make it so the OTA will fail.
http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/
Also here's chain fire....
http://forum.xda-developers.com/showthread.php?p=36316945

Does it matter when we have access to the factory images?

If you're just rooted you can still apply an OTA as you've not changed any of the files the OTA checks. If you've changed any system files then the OTA will fail the same way it'd fail on any previous version of Android. Nothing's changed

EddyOS said:
If you're just rooted you can still apply an OTA as you've not changed any of the files the OTA checks. If you've changed any system files then the OTA will fail the same way it'd fail on any previous version of Android. Nothing's changed
Click to expand...
Click to collapse
That's not at all what I'm reading. I'll post links later when I get home
Edit: see updated OP

/facepalm

I wrote a thread about other ways to update. Its in my signature

[Deleted]

DamnItLukasz said:
I don't know what that link says but thats not true lolz
Rooted and I got the OTA 3 days ago, just flashed stock 4.4.4 kernel over ElementalX et voilá.
Click to expand...
Click to collapse
The OTA you got was lollipop but it was applied to kitkat. This is about post kitkat. Or maybe it wasn't lollipop but to my knowledge there hasn't been an OTA yet released that updates lollipop

NCguy said:
The OTA you got was lollipop but it was applied to kitkat. This is about post kitkat.
Click to expand...
Click to collapse
Ups, forgive me then

Altrezia said:
Does it matter when we have access to the factory images?
Click to expand...
Click to collapse
For the less skilled hacker who doesn't want to wipe it requires more knowledge, more risk and more reliance on modified OTAs, and 3rd party stock builds. Otherwise they're into dirty flashing and that requires more skill and knowledge.

rootSU said:
I wrote a thread about other ways to update. Its in my signature
Click to expand...
Click to collapse
I'll have a look, thanks. That's really what I was hoping this thread would be about since it looks like plain OTAs may be out.

EddyOS said:
If you're just rooted you can still apply an OTA as you've not changed any of the files the OTA checks. If you've changed any system files then the OTA will fail the same way it'd fail on any previous version of Android. Nothing's changed
Click to expand...
Click to collapse
please read updated OP

NCguy said:
please read updated OP
Click to expand...
Click to collapse
That article is for the Nexus 9. People on here have successfully updated to 5.0 from 4.4.4, with root, by just sideloading the OTA in the stock recovery. If not, just flash the factory image but leave out the userdata partition

EddyOS said:
That article is for the Nexus 9. People on here have successfully updated to 5.0 from 4.4.4, with root, by just sideloading the OTA in the stock recovery. If not, just flash the factory image but leave out the userdata partition
Click to expand...
Click to collapse
It mentions the N9 only because it was the first 5.0 device that was officially released.
I mentioned before this problem is going to exist for updates to devices that already have lollipop, not for those updating from kitkat to lollipop.

rootSU said:
I wrote a thread about other ways to update. Its in my signature
Click to expand...
Click to collapse
Excellent post. With your level of experience you must be familiar with the problems stated in the Android police article regarding the new way google will be checking for system mods before processing the OTA?

NCguy said:
Excellent post. With your level of experience you must be familiar with the problems stated in the Android police article regarding the new way google will be checking for system mods before processing the OTA?
Click to expand...
Click to collapse
I haven't read it yet to be honest. I'm not an OTA fan, so I don't spend much time reading up on it. I will though, at some point and update the thread. There is also an OTA help-desk thread but I haven't read that yet. Apparently latest OTA doesn't work with custom recovery either

Vzw unlocked bootloader after nov. Update??

Sent from my Pixel using XDA Free mobile app

Has any on with A VZW PIXEL with an unlocked bootloader taken the NOVEMBER UPDATE AND if so what was the result????
Sent from my Unlocked Pixel

key Hole said:
Has any on with A VZW PIXEL with an unlocked bootloader taken the NOVEMBER UPDATE AND if so what was the result????
Sent from my Unlocked Pixel
Click to expand...
Click to collapse
That's a good question. I unlocked my bootloader and immediately disabled automatic system updates. Really curious if anyone has tried it. I know there are supposedly issues if you unlock then try to run custom firmware and then relock the bootloader (don't know why one would do that, but to each their own). I'm sure someone will tell us soon.

In the November update discussion on the XL forum, dePixel8 is reported to still work. They're expecting the next update will stop it from working.
http://forum.xda-developers.com/showpost.php?p=69513504&postcount=182

Just completed the November update with no adverse effects... Way cool
Sent from my Pixel using XDA Free mobile app

Sent from my Still unlocked Pixel

It's time to look at ROOT

Been reading all the threads here about this before I install the update.
I know this is a repeat, but I figured I might save some people the time digging.
My Device: Pixel XL Verizon NDE63P , Unlocked Bootloader, Root SU 2.78 SR3, ElementalX 0.05, WETA Battery, Center Clock, NavBar Height 36px
My Findings: Things should be fine. WETA just verified in a reply to me that the mods still work.
Update: Kernel update went fine kept root too.
Working on Installing the OTA now. I might make a guide for this if I don't get to frustrated. Right now its almost winning.
Feel free to PM me for help or directions. If there is interest I will write it all up. I just feel like maybe I'm the n00b here and everyone else is better than me. Been out of android for about 2 years...

jp712 said:
Been reading all the threads here about this before I install the update.
I know this is a repeat, but I figured I might save some people the time digging.
My Device: Pixel XL Verizon NDE63P , Unlocked Bootloader, Root SU 2.78 SR3, ElementalX 0.05, WETA Battery, Center Clock, NavBar Height 36px
My Findings: Things should be fine. WETA just verified in a reply to me that the mods still work.
Update: Kernel update went fine kept root too.
Working on Installing the OTA now. I might make a guide for this if I don't get to frustrated. Right now its almost winning.
Feel free to PM me for help or directions. If there is interest I will write it all up. I just feel like maybe I'm the n00b here and everyone else is better than me. Been out of android for about 2 years...
Click to expand...
Click to collapse
I'd be interested in a write up if you have time. Or even just a PM would be greatly appreciated. I tried sending a PM but apparently it's not going through. I'm currently unlocked and rooted using the same methods as you and also running EX-P-0.07 kernel. I currently have the OTA zip downloaded and ready to side load. Just wondering if I can just side load it normally without doing anything else. Or should I sideload, then install EX-P-0.07 kernel, then boot to root again? Thanks in advance.
Alphonse

I too would be interested in written out directions just to verify what I think I know because I'm not always right

key Hole said:
I too would be interested in written out directions just to verify what I think I know because I'm not always right
Click to expand...
Click to collapse
+1

ihierbal said:
I'd be interested in a write up if you have time. Or even just a PM would be greatly appreciated. I tried sending a PM but apparently it's not going through. I'm currently unlocked and rooted using the same methods as you and also running EX-P-0.07 kernel. I currently have the OTA zip downloaded and ready to side load. Just wondering if I can just side load it normally without doing anything else. Or should I sideload, then install EX-P-0.07 kernel, then boot to root again? Thanks in advance.
Alphonse
Click to expand...
Click to collapse
You will have to reinstall the kernel after the OTA runs. I shut down after the OTA finished instead of booting and then installed the kernel and root again. I also had to add the weta mods again too.
I made notes for a write-up as I did it. I can send them to you when I get home later this evening.

If you could send me a copy of that also I would greatly appreciate it.

key Hole said:
If you could send me a copy of that also I would greatly appreciate it.
Click to expand...
Click to collapse
I ended up just winging it and was able to sideload, install custom kernel, and root with no problems. Let me know if you still need a simple write up.

T-Mobile LG V20 update

Just received this update, but it doesn't look like it is updating just yet, waiting until 11PST, but i am thinking this is 7.1.1. Has anyone else received this or is this old news?
Sent from my LG-H918 using XDA Premium HD app

Yoshi1221 said:
Just received this update, but it doesn't look like it is updating just yet, waiting until 11PST, but i am thinking this is 7.1.1. Has anyone else received this or is this old news?
Sent from my LG-H918 using XDA Premium HD app
Click to expand...
Click to collapse
It's new. Got this about an hour ago. Same....won't allow me to start it yet.
Good to see us finally getting an update. Took a while. Not sure if it's 7.1.1 or what. Glad to see the security patch getting current.
*Edit: I just turned off network time and time zone. Set it to Eastern time...And the update is now downloading No need to wait.

This is new, did not receive this update notification from OTA, but LG Bridge detects the update with the id as "H91810j". I did update to 10i on friday after getting the v20 recently, weird how I don't get OTA's though.

Anyway to update while rooted on TWRP?

BROKEN1981 said:
Anyway to update while rooted on TWRP?
Click to expand...
Click to collapse
Not yet. This seems to be new, as this update was not available on Friday, when I updated to 10i. Wait for Rom developers to update their Rom base to "10j" or wait for someone to make a flashable zip.

FQuimson23 said:
Not yet. This seems to be new, as this update was not available on Friday, when I updated to 10i. Wait for Rom developers to update their Rom base to "10j" or wait for someone to make a flashable zip.
Click to expand...
Click to collapse
I would rather get a zip since I'm on stock. I tried flash fire, but it will not update.

It's still 7.0 and it includes the December security patch.
Other than that...Haven't noticed anything thing yet. Performance or otherwise. Who knows what that audio quality patch is. We'll maybe find out when Tmo updates the info on their site.

Where is the OTA located?

Will it be rootable?

Until I know the update is rootable I'm still staying on 10I.

View attachment 4006669
Got a small update this morning. Had to manually change the time to 11pm for the download to initiate.
H91810j, still on Android 7.0
One thing I can say for sure about this update, is that the audio quality has been greatly improved.
Sent from my LG-H918

For those have already installed, may you post the pic of the information of the ROM version.
I'd like to see the date of the patch. If it's still December 1, it should be able to regain root using dirty cow method.
If not, we have to wait until somebody developed a flashable zip for TWRP.

it is indeed rootable as i just did it with dirty cow.
however do not do the ota update unless you are on stock 10i, which is easy to do. then take the update. and when it's done. use this to root it. instructions included and all needed files.
recowvery exploit files - again this contains everything you will need to gain root on a t-mobile h918 v20 on 10j firmware

OvrDriVE said:
it is indeed rootable as i just did it with dirty cow.
View attachment 4006806View attachment 4006807
however do not do the ota update unless you are on stock 10i, which is easy to do. then take the update. and when it's done. use this to root it. instructions included and all needed files.
recowvery exploit files - again this contains everything you will need to gain root on a t-mobile h918 v20 on 10j firmware
Click to expand...
Click to collapse
Hey OvrDrive, what if i'm on stock "rooted" 10i already? Is it the same process or do i wait for a flashable zip?

OvrDriVE said:
it is indeed rootable as i just did it with dirty cow.
View attachment 4006806View attachment 4006807
however do not do the ota update unless you are on stock 10i, which is easy to do. then take the update. and when it's done. use this to root it. instructions included and all needed files.
recowvery exploit files - again this contains everything you will need to gain root on a t-mobile h918 v20 on 10j firmware
Click to expand...
Click to collapse
Good!
I will check out LG Bridge once I got home.

nymikey said:
Hey OvrDrive, what if i'm on stock "rooted" 10i already? Is it the same process or do i wait for a flashable zip?
Click to expand...
Click to collapse
you'll need to restore stock recovery and boot or it'll fail and bootloop to recovery. i had to fix mine by redoing 10i
it's not hard.
just use uppercut with the stock 10i kdz

ugh, so basically for root/TWRP 10i users, we have to backup data, flash 10i KDZ, update to 10j, restore backup?

dimm0k said:
ugh, so basically for root/TWRP 10i users, we have to backup data, flash 10i KDZ, update to 10j, restore backup?
Click to expand...
Click to collapse
Or you could put Ovrdrive's ROM on you phone when he bakes the updates into his ROM.

OvrDriVE said:
you'll need to restore stock recovery and boot or it'll fail and bootloop to recovery. i had to fix mine by redoing 10i
it's not hard.
just use uppercut with the stock 10i kdz
Click to expand...
Click to collapse
I just gathered the nerve to root this past sunday, i'm still recovering from the nervous breakdown I almost had while rooting. :crying: :laugh:

I'll stick with OvrDrives 10i custom rom and until he can update his rom.
But my question is...how in the hell do I get rid of the notification to update? I've already deleted the update file from "Root/Cache" folder but the notification persists even after a reboot. I do NOT want to hide the notification because it is tied to "Google Play Services" which means it'll block all things that have to do with that service.

Question Update factory rom and keep root-How to?

I guys, i'm on 13.0.0 (TD1A.221105.001, Nov 2022) and its working fine with root and magisk hidden (for google pay).
My phone reminds me to update.
I red a lot of things to do it but i dont want to mess anything.
Can somoene explain me simply all the steps to update to january factory from the beginning and keep root and with magisk hidden.
Thank you for your help.

oceliome said:
I guys, i'm on 13.0.0 (TD1A.221105.001, Nov 2022) and its working fine with root and magisk hidden (for google pay).
My phone reminds me to update.
I red a lot of things to do it but i dont want to mess anything.
Can somoene explain me simply all the steps to update to january factory from the beginning and keep root and with magisk hidden.
Thank you for your help.
Click to expand...
Click to collapse
Look for Pixel flasher on XDA , allows you to update and everything will be as you had it afterwards. Simplest and easiest in my opinion. Been using for every update

Question, when updating using Pixel Flasher, do i have to tick the disable verity and disable verification when flashing for every update?

Wmateria said:
Question, when updating using Pixel Flasher, do i have to tick the disable verity and disable verification when flashing for every update?
Click to expand...
Click to collapse
If you want those to stay disabled yes. If you don't do it and decide you want to disable them later on. You'll have to wipe again.

easy to folow with easy steps did al my updates without losing anything

boontje3 said:
easy to folow with easy steps did al my updates without losing anything
Click to expand...
Click to collapse
Thanks for sharing this video. But this also means this 'OTA Upgrade Guide' from Magisk website doesn't work with the Pixel devices/ Android 13? I was using the OnePlus 7T before since 2020 (to last month) and I think since then itself I was following the above mentioned official Magisk guide to update to the latest OOS OTA's and major Android firmware upgrades too to keep the data and also the root. So doesn't this official guide work anymore?

niyonsv said:
Thanks for sharing this video. But this also means this 'OTA Upgrade Guide' from Magisk website doesn't work with the Pixel devices/ Android 13? I was using the OnePlus 7T before since 2020 (to last month) and I think since then itself I was following the above mentioned official Magisk guide to update to the latest OOS OTA's and major Android firmware upgrades too to keep the data and also the root. So doesn't this official guide work anymore?
Click to expand...
Click to collapse
i dont know never followd the official Magisk guide that you linked on my pixel7 pro , i yust followd the youtube that i linked en worked like a charm never lost root/data

niyonsv said:
Thanks for sharing this video. But this also means this 'OTA Upgrade Guide' from Magisk website doesn't work with the Pixel devices/ Android 13? I was using the OnePlus 7T before since 2020 (to last month) and I think since then itself I was following the above mentioned official Magisk guide to update to the latest OOS OTA's and major Android firmware upgrades too to keep the data and also the root. So doesn't this official guide work anymore?
Click to expand...
Click to collapse
It's hit or miss as to whether installing to inactive slot via Magisk during an OTA update will work. Some have been successful while many others have not. But if you want to keep root while updating, I would suggest Pixel Flasher.

Lughnasadh said:
It's hit or miss as to whether installing to inactive slot via Magisk during an OTA update will work. Some have been successful while many others have not. But if you want to keep root while updating, I would suggest Pixel Flasher.
Click to expand...
Click to collapse
Thanks, just went through the thread.

Definitely Pixel Flasher. Only took my 153 seconds to flash Feb update and booting up with all mod, root and data retained.