Develop Bugs

Rooted and Unlocked can't install OTA update

So I'm running the stock OS and now it won't install the OTA update. I'm unlocked and rooted and the update downloads, then the phone reboots. I see the install starts and runs for about 3 seconds and then it stops with the red triangle exclamation point.
What's going on, anyone else having this issue?

How many times per day does this thread need to be made?
You're either going to have to flash just the update via fastboot on your own, or unroot and accept the OTA normally.

Well I appreciate the answer, sorry to be a bother...
Anyway, is this the way it's always going to be since I'm rooted and unlocked? Where will I be able to download the OTA updates so I can flash manually with fastboot?

It won't work if you have ClockworkMod's recovery, you need the stock recovery.
Sent from my Galaxy Nexus using XDA App

105437 said:
So I'm running the stock OS and now it won't install the OTA update. I'm unlocked and rooted and the update downloads, then the phone reboots. I see the install starts and runs for about 3 seconds and then it stops with the red triangle exclamation point.
What's going on, anyone else having this issue?
Click to expand...
Click to collapse
Dowload from http://code.google.com/android/nexus/images.html. It needs 7Zip to uncompress the file. Once decompressed it has a file with no extension, decrompress that again and you will have the several file.
The just power the phone off and power back on with the volume up and down pressed. Same as when you rooted it.
Then run these commands:
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot reboot-bootloader
sleep 5
fastboot update image-yakju-icl53f.zip
This will not wipe your phone!
You will need to root it again.
This is what I just did and works prefectly!

Root and unlocked bootloader shouldn't prevent you from installing if you still have stock recovery. If you have ClockworkMod recovery instead, you can use that to flash it manually. If your phone downloaded the update zip, it should be located in /cache.
You'll probably have to re-root after applying the update, regardless of how you install it.

Thanks for the replies guys! I guess I'd like to stay unlocked & rooted and be able to get OTA updates. Is there any risk in doing this? If not, how do I uninstall CWM?
Thanks again!

105437 said:
Thanks for the replies guys! I guess I'd like to stay unlocked & rooted and be able to get OTA updates. Is there any risk in doing this? If not, how do I uninstall CWM?
Thanks again!
Click to expand...
Click to collapse
I believe that in rom manager you should be able to set the recovery back to the default.

Bad Liar said:
I believe that in rom manager you should be able to set the recovery back to the default.
Click to expand...
Click to collapse
ROM Manager only has the option to flash ClockworkMod, not stock recovery. But the stock recovery can be extracted from the Google factory images and flashed with fastboot.

I have same problem like yours, how can i solved it? my device is SE WT19i

Happened to me as well - but I also ran into problems initially trying to do the image upgrades, because I had ended up changing a couple values in the build.prop file (wifi scan time, and disabling the boot animation). I'm assuming changes like that would cause the OTA update to fail, if doing it manually fails as well?
Also remember when trying to resolve my issue, reading through other people who went through similar sequences.
Had unlocked/rooted. Tried OTA - got the red warning symbol.
Tried installing the zip from sdcard through CWM but ran into various warnings/errors because of minor tweaks that either they had done, or something that had been installed had done.

Try mskip's GNex Toolkit. Super easy to use and everything explained in the thread. The guy's a genius!
http://forum.xda-developers.com/showthread.php?t=1392310
Think option 10 will reflash stock recovery.
Dark Tapatalk (GSM Galaxy Nexus)

+1. GNex Toolkit made my life worth living, I got the OTA 4.0.4 update (IMM76I), and I'm rooted and unlocked.

I also highly recommend GNex Toolkit. It has an option to restore the factory recovery and also helps you to get root again after update.
Voodoo OTA Root Keeper only helps partially.

ceribaen said:
Happened to me as well - but I also ran into problems initially trying to do the image upgrades, because I had ended up changing a couple values in the build.prop file (wifi scan time, and disabling the boot animation). I'm assuming changes like that would cause the OTA update to fail, if doing it manually fails as well?
Also remember when trying to resolve my issue, reading through other people who went through similar sequences.
Had unlocked/rooted. Tried OTA - got the red warning symbol.
Tried installing the zip from sdcard through CWM but ran into various warnings/errors because of minor tweaks that either they had done, or something that had been installed had done.
Click to expand...
Click to collapse
Each if those warnings that you are getting is because something is not stock. You will need to download the appropriate stock file for each of those warnings. I have already posted the stock build.prop and boot image in the main IMM76I update thread. If you need others, instructions can be found in the update link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2

philipdeane said:
Try mskip's GNex Toolkit. Super easy to use and everything explained in the thread. The guy's a genius!
http://forum.xda-developers.com/showthread.php?t=1392310
Think option 10 will reflash stock recovery.
Dark Tapatalk (GSM Galaxy Nexus)
Click to expand...
Click to collapse
bingefister said:
+1. GNex Toolkit made my life worth living, I got the OTA 4.0.4 update (IMM76I), and I'm rooted and unlocked.
Click to expand...
Click to collapse
toxaris said:
I also highly recommend GNex Toolkit. It has an option to restore the factory recovery and also helps you to get root again after update.
Voodoo OTA Root Keeper only helps partially.
Click to expand...
Click to collapse
All of you guys recommending using a toolkit: do you even understand the OP's issue? I don't think so, otherwise you would know that a toolkit won't do what he needs done.
My opinion:
On an unrelated note: you need to figure out how to do things manually before you start using toolkits, otherwise you will never learn anything. There is a reason they teach you long division in school before letting you use a calculator...
Sent from my Galaxy Nexus using Tapatalk 2

[Q] Problem updating to 4.0.2 with a rooted GSM Galaxy Nexus

I have an error updating with the OTA 4.0.2. GSM Galaxy Nexus.
I have only my phone rooted, and no Wallet installed or something. The error it's only that when the device restarts, it starts the installation, and then a "dead" Android appears with an exclamation sign on it. It fully block the device, and I have to put the battery out and restart.
I have tried so many times, each time OTA comes up.
Some help? Thank you.

Chaosblast said:
I have an error updating with the OTA 4.0.2. GSM Galaxy Nexus.
I have only my phone rooted, and no Wallet installed or something. The error it's only that when the device restarts, it starts the installation, and then a "dead" Android appears with an exclamation sign on it. It fully block the device, and I have to put the battery out and restart.
I have tried so many times, each time OTA comes up.
Some help? Thank you.
Click to expand...
Click to collapse
Are you sure you are not in standard recovery mode? When the droid appears: push Volume up+power and you should have the stock recovery mode...

Diger36 said:
Are you sure you are not in standard recovery mode? When the droid appears: push Volume up+power and you should have the stock recovery mode...
Click to expand...
Click to collapse
I'm sure. When the droid appears (I've attached the image) it doesn't respond to any button. I've tried V.up + Power, V.down + Power, and V.up+V.down+Power. Nothing happens.
I have ClockworkMod installed, version 5.5.0.2.

Chaosblast said:
I'm sure. When the droid appears (I've attached the image) it doesn't respond to any button. I've tried V.up + Power, V.down + Power, and V.up+V.down+Power. Nothing happens.
I have ClockworkMod installed, version 5.5.0.2.
Click to expand...
Click to collapse
Now that IS weird. The screenshot you took is indeed the screen you get in Stock Recovery and pressing Volume up + Power simultaniously should bring you into the recovery menu.
If not: I'm afraid this problem is over my head. Sorry about that... Maybe anyone else?

Chaosblast said:
I have an error updating with the OTA 4.0.2. GSM Galaxy Nexus.
I have only my phone rooted, and no Wallet installed or something. The error it's only that when the device restarts, it starts the installation, and then a "dead" Android appears with an exclamation sign on it. It fully block the device, and I have to put the battery out and restart.
I have tried so many times, each time OTA comes up.
Some help? Thank you.
Click to expand...
Click to collapse
You can use OTA updates when your phone is rooted. When you try to install the OTA update it looks for the stock bootlader. Because you have rooted the install wont complete when it gets to your modded bootloader.
The only way to update is put a 4.0.2 or 4.0.3 rom on your sd card and flash using CWM.

jd1001 said:
You can use OTA updates when your phone is rooted. When you try to install the OTA update it looks for the stock bootlader. Because you have rooted the install wont complete when it gets to your modded bootloader.
The only way to update is put a 4.0.2 or 4.0.3 rom on your sd card and flash using CWM.
Click to expand...
Click to collapse
Is that true? Even if you didn't install CWM, are on Stock recovery and all you did was unlock fastboot and root the phone? I guess then you should be able to install the OTA updates flawlessly or am I wrong?

jd1001 said:
You can use OTA updates when your phone is rooted. When you try to install the OTA update it looks for the stock bootlader. Because you have rooted the install wont complete when it gets to your modded bootloader.
The only way to update is put a 4.0.2 or 4.0.3 rom on your sd card and flash using CWM.
Click to expand...
Click to collapse
Unlocked bootloader doesn't prevent OTA updates.
---------- Post added at 08:47 AM ---------- Previous post was at 08:46 AM ----------
Diger36 said:
Is that true? Even if you didn't install CWM, are on Stock recovery and all you did was unlock fastboot and root the phone? I guess then you should be able to install the OTA updates flawlessly or am I wrong?
Click to expand...
Click to collapse
If all you did was unlock the bootloader and root and didn't install CWM recovery, different modem or anything else like that than you should be able to do the OTA.

jhuynh said:
Unlocked bootloader doesn't prevent OTA updates.
---------- Post added at 08:47 AM ---------- Previous post was at 08:46 AM ----------
If all you did was unlock the bootloader and root and didn't install CWM recovery, different modem or anything else like that than you should be able to do the OTA.
Click to expand...
Click to collapse
Oh ok I thought that was the issue! So it's when you install a custom recovery that the OTA updates won't work. Sorry for the incorrect info.

Having a custom recovery allows you to flash packages that are not signed by the same party as the ROM on your phone. What this means is that if you don't have a custom recovery, you can only install updates from your ROM signer. Pure yakju builds are released from Google. The other yakju derivatives are carrier and OEM releases.
AFAIK, only Google (yakju) has released the 4.0.2 update for GSM, so you can only install the update on yakju if you have a stock recovery. If you have a custom recovery you have the option to bypass the signature verification process...

danger-rat said:
Having a custom recovery allows you to flash packages that are not signed by the same party as the ROM on your phone. What this means is that if you don't have a custom recovery, you can only install updates from your ROM signer. Pure yakju builds are released from Google. The other yakju derivatives are carrier and OEM releases.
AFAIK, only Google (yakju) has released the 4.0.2 update for GSM, so you can only install the update on yakju if you have a stock recovery. If you have a custom recovery you have the option to bypass the signature verification process...
Click to expand...
Click to collapse
Thanks for that. I got bootloader and recovery mixed up!

Thanks all of you guys. That should be the problem. Then I delete the CWM and then update with the OTA. Then I reinstall the CWM and that should be fine.
It's weird because I my cousin has installed the OTA, and he had also rooted his Galaxy Nexus, and I think he also changed the recovery.
Anyway, it's good to know. Thanks again.

I don't think you understood me:
Having CWM let's you flash the update, but you may have to turn off signature verification to do so.
The problem is, the update has only been released for the yakju firmware, so if you want the update you probably want to make sure that you have the yakju firmware installed (use Android System Info or similar app).
It's possible that the update can be forced to flash on other non-yakju builds, but I can't say for sure...

danger-rat said:
I don't think you understood me:
Having CWM let's you flash the update, but you may have to turn off signature verification to do so.
The problem is, the update has only been released for the yakju firmware, so if you want the update you probably want to make sure that you have the yakju firmware installed (use Android System Info or similar app).
It's possible that the update can be forced to flash on other non-yakju builds, but I can't say for sure...
Click to expand...
Click to collapse
I don't want to flash any update via CWM for now. I prefer doing that by the official way until I see some ROM that I like.
I understand what you mean of the firmware. But I think I haven't changed the firmware. I mean, I have only unlocked the bootloader, rooted, and then installed CWM. I don't think that changes my firmware.
By the way, I have installed Android System Info, and checked it. But I don't know how to stay sure. I have attached the screenshot.
Thank you.

Understood.
Looks like you have yakju...
If you want the update to auto install, then yes, you will need the stock recovery.
Personally, I find it easier to flash the update manually than to switch recovery...

danger-rat said:
Understood.
Looks like you have yakju...
If you want the update to auto install, then yes, you will need the stock recovery.
Personally, I find it easier to flash the update manually than to switch recovery...
Click to expand...
Click to collapse
It's true, but where can I find the exact update (not the full ROM) in a zip package? I don't know how to get it from the OTA, and didn't find it on the forum either.
I want to be sure it's the correct update for my version and only the 4.0.1 to 4.0.2 package.

Bump! Could you answer my last question? It's the last one and all this thread is done.
Thank you.

I have exactly the same problem that Chaos, i tried to do the same as you told him but the problem persist, each time that i try to upgrade 4.04 by OTA it stopped and appair the android with the red exclamation on it.
I have the Nexus rooted and the stock recovery flashed

[Q] Keeping Root with OTA Update

As far as I know, there is no way to keep root if you get the OTA 4.3 update, right? I want to just get the OTA and not deal with the roms. Unlocked bootloader here...
According to Voodoo OTA Rootkeeper, it doesn't work with the 4.3 update: http://forum.xda-developers.com/showthread.php?t=1241517&page=6
That's a true bummer.

Gbcue said:
As far as I know, there is no way to keep root if you get the OTA 4.3 update, right? I want to just get the OTA and not deal with the roms. Unlocked bootloader here...
According to Voodoo OTA Rootkeeper, it doesn't work with the 4.3 update: http://forum.xda-developers.com/showthread.php?t=1241517&page=6
That's a true bummer.
Click to expand...
Click to collapse
If your bootloader is unlocked then it's easy... you just flash SuperSU in recovery after the update. No ROMs to deal with. On a Nexus device with an unlocked bootloader root is never an issue.

phazerorg said:
If your bootloader is unlocked then it's easy... you just flash SuperSU in recovery after the update. No ROMs to deal with. On a Nexus device with an unlocked bootloader root is never an issue.
Click to expand...
Click to collapse
Even with stock recovery this is possible? I don't want to re-root and lose data.

Gbcue said:
Even with stock recovery this is possible? I don't want to re-root and lose data.
Click to expand...
Click to collapse
Not with stock recovery. But if you have an unlocked bootloader it's still no problem. You can boot to a custom recovery without even having to actually flash it if you want to keep stock recovery. So you just let the OTA install as normal then use fastboot to boot CWM or TWRP and flash SuperSU and you're done and rooted.
If your bootloader is unlocked, you might as well take advantage of it even if you want to remain mostly stock

Just keep in mind that SuperSU runs a daemon all the time can result in 70% cpu usage peaks. Don't blame 4.3 for it.

madd0g said:
Just keep in mind that SuperSU runs a daemon all the time can result in 70% cpu usage peaks. Don't blame 4.3 for it.
Click to expand...
Click to collapse
Do we have any idea what triggers that? Thankfully I haven't had that experience and haven't had any extra CPU usage before or after flashing 4.3 yesterday.

phazerorg said:
Do we have any idea what triggers that? Thankfully I haven't had that experience and haven't had any extra CPU usage before or after flashing 4.3 yesterday.
Click to expand...
Click to collapse
No, it seems fairly random so far. I have seen it once but can not reproduce it.
Chainfire is working on the issue though.

Questions in the Q&A, this is the general forum..
Read the rules sticky..
Beamed from my Maguro.

GldRush98 said:
No, it seems fairly random so far. I have seen it once but can not reproduce it.
Chainfire is working on the issue though.
Click to expand...
Click to collapse
SuperSU 1.43 update

add3421 said:
So is there a like guide on how to keep root when doing a system update? I have STOCK 4.2 Rooted and it is saying I should download an update. I do have TWRP installed. Is there another stock already rooted 4.3 I can download? Any help would be great so I dont have to factory reset.
Thanks!
Click to expand...
Click to collapse
Why even bother with this crap, flash the update, boot, flash custom recovery after and flash new SuperSU. You would be done before even typing this post.

I used the Nexus Root Toolkit by WugFresh to root my Galaxy Nexus on 4.3, and didn't lose any data...

All I did as usual was:-
1) Flash the update
2) Boot into TeamWin recovery (I keep the stock recovery installed)
3) Flash SuperSU 1.43
Simple, no issues.

If I have CMW Touch recovery can I install the OTA? I have received the notification but I don't know if I will be able to install it. Is there any way to revert back to Google's recovery just like installing a custom recovery? I mean not loosing data or having to so a factory reset.
Enviado desde mi Galaxy Nexus

str355 said:
All I did as usual was:-
1) Flash the update
2) Boot into TeamWin recovery (I keep the stock recovery installed)
3) Flash SuperSU 1.43
Simple, no issues.
Click to expand...
Click to collapse
How do you boot into twrp without flashing it? I know "fastboot flash recovery twrp.img" permanently overrides the built in recovery, but how would you boot into it just once?

AMKhatri said:
I used the Nexus Root Toolkit by WugFresh to root my Galaxy Nexus on 4.3, and didn't lose any data...
Click to expand...
Click to collapse
Which version of the toolkit?

krackers said:
How do you boot into twrp without flashing it? I know "fastboot flash recovery twrp.img" permanently overrides the built in recovery, but how would you boot into it just once?
Click to expand...
Click to collapse
This is the command you want "fastboot boot twrp.img"
---------- Post added at 08:45 PM ---------- Previous post was at 08:41 PM ----------
add3421 said:
ok cool, do you happen to have a link to the exact update i can download? for some reason when i click install it says restarting now.. but never does.
Click to expand...
Click to collapse
I used the link in this thread --> http://forum.xda-developers.com/showthread.php?t=2377390
SuperSU.zip from here (v1.45 now) --> http://forum.xda-developers.com/showthread.php?t=1538053

Gbcue said:
Which version of the toolkit?
Click to expand...
Click to collapse
1.6.4 after running update.
FWIW: Even though I've successfully used this kit a dozen times on four different devices, root was not working correctly (no su binary found) for me so I had to load the app via twrp which did correctly load from the toolkit after the kit installed 4.3.

Gbcue said:
Which version of the toolkit?
Click to expand...
Click to collapse
1.6.4 and it worked perfectly for me

[Q] Update Rooted Tablet

Hiya, I just got my tablet and the first thing I did was root it.
I now want to apply the firmware update that came along with it but it's saying my device is modified. Is there anyway of manually applying this update via the recovery? The tablet itself is pretty laggy and I heard this update fixes majority of the issues, so it would be pretty sweet if I can get this going.
Thanks.

Protocol 7 said:
Hiya, I just got my tablet and the first thing I did was root it.
I now want to apply the firmware update that came along with it but it's saying my device is modified. Is there anyway of manually applying this update via the recovery? The tablet itself is pretty laggy and I heard this update fixes majority of the issues, so it would be pretty sweet if I can get this going.
Thanks.
Click to expand...
Click to collapse
assuming you have SuperSU you can try using the Permanent Unroot option in that app then try it but keep in mind that after rebooting from recovery TWRP (if that's what you have) will either 1. prompt you to fix root which will do the obvious, or 2. automatically do it. can't remember which.
the update, if you do manage to install it, will most likely overwrite TWRP with the stock recovery
I have a question for you now lol
I flashed TWRP with Odin 3.09 as directed and cannot figure out how to boot into recovery
how do you do this?

Protocol 7 said:
Is there anyway of manually applying this update via the recovery?
Click to expand...
Click to collapse
Yes there is and normally you never should try to update via OTA after your root an Android device or flash a custom recovery or ROM. This can brick your devices (at least for other brands).
You can download the update via samMobile and SamsungIs and flash the corresponding update via Odin.
You can try to re-flash the firmware via Kies and then use the normal OTA update function. Maybe you have to fake the system status before. This can be done with the Wanam Xposed module which is in evert way a duty.
In both cases you have to re-root and/or flash the custom recovery afterwards again.
---------- Post added at 10:34 AM ---------- Previous post was at 10:29 AM ----------
Sterist said:
I flashed TWRP with Odin 3.09 as directed and cannot figure out how to boot into recovery
Click to expand...
Click to collapse
You can try:
Make the finger exercise and press the power- and volume-up-button together until you see the "Samsung Galaxt" text, release both keys and press them again
Use Wanam Xposed modul and use the system setting "Enable 4 way reboot menu". Then you can reboot into recovery via the power menu.
Use the adb tool and the command:
Code:
adb reboot recovery
Now you have only the trouble to choose

Root and update OTA?

Hello ,
I will have a ONE PLUS 5T.
I would like to root this one to have adblocker...
First question : How could root this?
Second question: If my phone is rooted, is it possible to have update OTA (or like samsung, impossible after)?
Thank you;

If you replace the stock recovery with a custom recovery, like TWRP, OTAs will not work. However, if retain the stock recovery and simply boot TWRP in fastboot mode, you will be able to root your stock phone and receive OTAs. Just use the ADB command <fastboot boot twro_xxx.img> or simply flash back to a stock recovery image every time an OTA comes in.

jim262 said:
If you replace the stock recovery with a custom recovery, like TWRP, OTAs will not work. However, if retain the stock recovery and simply boot TWRP in fastboot mode, you will be able to root your stock phone and receive OTAs. Just use the ADB command <fastboot boot twro_xxx.img> or simply flash back to a stock recovery image every time an OTA comes in.
Click to expand...
Click to collapse
it's chinese for me your answer... is there a tutorial for that?

ilan78 said:
it's chinese for me your answer... is there a tutorial for that?
Click to expand...
Click to collapse
Guide: https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592
You can't use OTAs after you root. You'll need to download the full update every time one is released and flash it in TWRP.

ilan78 said:
it's chinese for me your answer... is there a tutorial for that?
Click to expand...
Click to collapse
If that is a major issue for you, use the TWRP recovery from blu_spark, otherwise, simply go into your TWRP settings and set the language to English or... Either way the language has nothing to do with functionality and it operates the basically the same.

jim262 said:
If that is a major issue for you, use the TWRP recovery from blu_spark, otherwise, simply go into your TWRP settings and set the language to English or... Either way the language has nothing to do with functionality and it operates the basically the same.
Click to expand...
Click to collapse
Jim your answer wasn't Chinese to me and made perfect sense thank you. I have a doubt, if I just use "fastboot boot *TWRP*.IMG" and root and flash exposed too, will I be able to receive otas and update offically and redo boot TWRP and root and flash exposed again without problems?

santor said:
Jim your answer wasn't Chinese to me and made perfect sense thank you. I have a doubt, if I just use "fastboot boot *TWRP*.IMG" and root and flash exposed too, will I be able to receive otas and update offically and redo boot TWRP and root and flash exposed again without problems?
Click to expand...
Click to collapse
No. You should NEVER take an OTA if you have root. You can dirty flash the full update zip in TWRP when they're released though.

shadeau said:
No. You should NEVER take an OTA if you have root. You can dirty flash the full update zip in TWRP when they're released though.
Click to expand...
Click to collapse
If we root our device.can we install ota manually via twrp ??
If yes, then how??

Amanpreetsingh said:
If we root our device.can we install ota manually via twrp ??
If yes, then how??
Click to expand...
Click to collapse
Let me clarify: OTA stands for Over-The-Air and implies that you're going to download the partial update from OnePlus and install it in stock recovery. Do NOT do this.
OnePlus usually publishes full zips of their updates when the OTA is released. Currently a mirror for them exists in the guides section. You can flash those (>1 GB) safely in TWRP to update OOS.

santor said:
Jim your answer wasn't Chinese to me and made perfect sense thank you. I have a doubt, if I just use "fastboot boot *TWRP*.IMG" and root and flash exposed too, will I be able to receive otas and update offically and redo boot TWRP and root and flash exposed again without problems?
Click to expand...
Click to collapse
Here is the reality. YES. You can still receive OTAs with root, However, the OTA will break the root and you will need to reroot your device. Those who are saying no are wrong. It is very simple. To process an OTA, your phone needs stock recovery. TWRP will not process an OTA. So if you have stock recovery in your recovery partition and you reboot your phone into fastboot mode and from your PC, run the ADB command, <fastboot boot twrp_xxx.img>, you will boot up the TWRP image and will be able to run it as one normally would, but you will still have stock recovery loaded in the recovery partition.[QRCODE][/QRCODE]
---------- Post added at 10:05 PM ---------- Previous post was at 10:02 PM ----------
shadeau said:
No. You should NEVER take an OTA if you have root. You can dirty flash the full update zip in TWRP when they're released though.
Click to expand...
Click to collapse
What's the difference? You still need to reroot.

jim262 said:
Here is the reality. YES. You can still receive OTAs with root, However, the OTA will break the root and you will need to reroot your device. Those who are saying no are wrong. It is very simple. To process an OTA, your phone needs stock recovery. TWRP will not process an OTA. So if you have stock recovery in your recovery partition and you reboot your phone into fastboot mode and from your PC, run the ADB command, <fastboot boot twrp_xxx.img>, you will boot up the TWRP image and will be able to run it as one normally would, but you will still have stock recovery loaded in the recovery partition.[QRCODE][/QRCODE]
---------- Post added at 10:05 PM ---------- Previous post was at 10:02 PM ----------
What's the difference? You still need to reroot.
Click to expand...
Click to collapse
I apologize if I'm out of the loop. When I first read about OTAs with root I was on a Samsung device and everyone said that it would either brick the phone or upgrade the OS with no way to re-root the device. Looking through your answer it's obvious that that fear probably only applies to Samsung devices. Thanks for correcting me on this.

jim262 said:
Here is the reality. YES. You can still receive OTAs with root, However, the OTA will break the root and you will need to reroot your device. Those who are saying no are wrong. It is very simple. To process an OTA, your phone needs stock recovery. TWRP will not process an OTA. So if you have stock recovery in your recovery partition and you reboot your phone into fastboot mode and from your PC, run the ADB command, <fastboot boot twrp_xxx.img>, you will boot up the TWRP image and will be able to run it as one normally would, but you will still have stock recovery loaded in the recovery partition.[QRCODE][/QRCODE]
---------- Post added at 10:05 PM ---------- Previous post was at 10:02 PM ----------
What's the difference? You still need to reroot.
Click to expand...
Click to collapse
Thanks Jim , I can confirm this works without problems on op5t. I had TWRP flashed and rooted with xposed installed.
I clean flashed the 4.7.1 stock ROM and got stock recovery and fresh os.
Just booted to TWRP using fastboot boot and rooted / installed xposed.
I got OTA updated to 4.7.2 and rerooted using fastboot boot TWRP and now rooted with xposed on stock ROM and stock recovery. ?

I have a question :
I would like to root without lost everything.
Is it possible? if yes , how?

ilan78 said:
I have a question :
I would like to root without lost everything.
Is it possible? if yes , how?
Click to expand...
Click to collapse
Exactly like I said. Rooting, by itself, does not wipe your storage. The only time your storage is wiped is when you unlock your (bootloader) phone, when you manually choose to wipe storage in TWRP or when you do a factory reset. If you do not have an unlocked bootlader, you must make a backup of your files first, as once you unlock it does a factory reset. You can then run TWRP and restore your files. You are now rooted with your files and ability to take OTAs. There are plenty of tutorials here on XDA describing the process step by step. May I suggest you do a search first. You are very likely to get all the answers to these questions as they have been asked many, many times.

Thank you.
so my question is FOR ROOTING, i HAVE TO UNLOCK BOOTLOADER?
And how Back up my data, my apps, all my settings without root or TWRP?

ilan78 said:
Thank you.
so my question is FOR ROOTING, i HAVE TO UNLOCK BOOTLOADER?
And how Back up my data, my apps, all my settings without root or TWRP?
Click to expand...
Click to collapse
Look through the Magisk forum. They have a method of rooting that doesn't require a custom recovery.
I use helium backup for my non-root app backup needs. Settings are trickier and I typically do them over every time. Super backup & restore is good for call logs, texts, and contacts.

ilan78 said:
Thank you.
so my question is FOR ROOTING, i HAVE TO UNLOCK BOOTLOADER?
And how Back up my data, my apps, all my settings without root or TWRP?
Click to expand...
Click to collapse
Did you read my post? The answers are all there. SEARCH! This question has been asked several times a day. You need to back up your data to another site, such as cloud, other device or PC. Then unlock bootloader, run TWRP and root file, then restore data. Tutorials are online. Now SEARCH!

ilan78 said:
Thank you.
so my question is FOR ROOTING, i HAVE TO UNLOCK BOOTLOADER?
And how Back up my data, my apps, all my settings without root or TWRP?
Click to expand...
Click to collapse
Man seriously! You got your answers and still you keep asking. Makes me wonder if you are just trolling

Non-trolling question - I am experienced when it comes to flashing/rooting. So if I want to stay with TWRP, I have to sacrifice OTA's, but it will be possible to flash the new updated zips and still keep my data via dirty flashing? Any negatives to doing this?

Tefzors said:
Non-trolling question - I am experienced when it comes to flashing/rooting. So if I want to stay with TWRP, I have to sacrifice OTA's, but it will be possible to flash the new updated zips and still keep my data via dirty flashing? Any negatives to doing this?
Click to expand...
Click to collapse
Yes, as far as I know, if on stock OOS, you download the full zip (over 1GB in size), flash that in TWRP, and then flash root solution right after (before leaving TWRP) to prevent it being overwritten by the stock recovery.
I don't think dirty flashing has any downsides, but if you do end up running into issues, a clean flash usually solves them