Develop Bugs

OTA update failed

This morning I excitedly got a notification to update to 4.02. Installing update failed when phone rebooted to recovery and I got a red exclamation mark over the little Android.
My phone has been rooted with CMW installed. I know I lot of you will be thinking "just flash a different ROM" but the truth is I don't like any of the Roms currently available.
Did my update fail because of CWM? Or am I making a super noob mistake? Please help
Sent from my Galaxy Nexus using XDA App

wynthewun said:
This morning I excitedly got a notification to update to 4.02. Installing update failed when phone rebooted to recovery and I got a red exclamation mark over the little Android.
My phone has been rooted with CMW installed. I know I lot of you will be thinking "just flash a different ROM" but the truth is I don't like any of the Roms currently available.
Did my update fail because of CWM? Or am I making a super noob mistake? Please help
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
yes CWM will cause update to fail the install. Flash the stock recovery img through fastboot if you want OTA's
---------- Post added at 03:13 AM ---------- Previous post was at 03:05 AM ----------
download the stock system image files from google and extact it to find the recovery.img
- copy the recovery.img file to the directory that contains your fastboot utility
- start-up a terminal/command session
- put your phone into fastboot / bootloader mode
- type the following fastboot command to flash the stock recovery:
Code:
fastboot flash recovery recovery.img

badassirocz said:
yes CWM will cause update to fail the install. Flash the stock recovery img through fastboot if you want OTA's
---------- Post added at 03:13 AM ---------- Previous post was at 03:05 AM ----------
download the stock system image files from google and extact it to find the recovery.img
- copy the recovery.img file to the directory that contains your fastboot utility
- start-up a terminal/command session
- put your phone into fastboot / bootloader mode
- type the following fastboot command to flash the stock recovery:
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Thank you very much, i had the same problem this morning, the update disappeared so will it get back when i flash the recovery?
plus my launcher is modified will it affect the update?

it should come back if you check for updates in the system menu. If not it might take a few days to show back up from what I have heard. The launcher will not effect OTA's.
Please hit the thanks button if I helped

having this issue
I am having this issue also, but I didn't flash cwm into my phone, I only fastboot it, will this also cause this problem, or because I rooted my phone and on locked it, really need help.
thanks.

formula1210204 said:
I am having this issue also, but I didn't flash cwm into my phone, I only fastboot it, will this also cause this problem, or because I rooted my phone and on locked it, really need help.
thanks.
Click to expand...
Click to collapse
It won't work because you are rooted. The install looks for the stock bootloader. You don't have the stock bootloader because you rooted.

jd1001 said:
It won't work because you are rooted. The install looks for the stock bootloader. You don't have the stock bootloader because you rooted.
Click to expand...
Click to collapse
You are WRONG. Stop telling people wrong info. CWM is what caused the failure. Root doesn't mean you changed your bootloader.

jhuynh said:
You are WRONG. Stop telling people wrong info. CWM is what caused the failure. Root doesn't mean you changed your bootloader.
Click to expand...
Click to collapse
Yeah apologies! I got my wires crossed. Thanks for clearing it up for me. I wasn't sure if it was the bootloader or the custom recovery. Thanks again and sorry for misleading anyone.

reply
thanks for reply, but as I said, I didn't flash CWM into my phone, I just boot it, in this case, it will also making this problem?

So, to clear this up for noobs (like me!)
If I root my Nexus, but keep it all stock, will I still get OTA updates?
If so, will an OTA update remove the root?
Thanks

The update won't work because you will be using a different recovery when you root. So the update does not install at all.
However the benefits of rooting will allow you to have the latest Google updates thanks to the hard work of devs here. So root and get romming!!!

formula1210204 said:
thanks for reply, but as I said, I didn't flash CWM into my phone, I just boot it, in this case, it will also making this problem?
Click to expand...
Click to collapse
brypie said:
So, to clear this up for noobs (like me!)
If I root my Nexus, but keep it all stock, will I still get OTA updates?
If so, will an OTA update remove the root?
Thanks
Click to expand...
Click to collapse
If you just root the Phone and keep it complete stock (including Stock recovery, so not CWM) then OTA should work. I'm not sure about removing root though but I guess the OTA would not remove root. And if it does: It is easy to re-root isn't it?

The OTA should work if you didn't install CWM recovery or something like flashing a different radio. It removes root but you can easily re-root. I have not received 4.0.2 yet but when I received the volume fix update OTA I did not have any issues with it even though I was rooted. I just had to re-root after the update.

[Q] Can you root ICS4.04?

Hi all,
Bit of a noob query, apologies.
I had never rooted a device until last night when I took the plunge with WugFresh's (thankyou so much) program. Great program had an issue with the adb drivers (turned out I needed more power for the USB port) hence I plugged the USB into the rear port and it magically appeared and installed, thus if you have problems installing the driver make sure you are plugged into the rear.
But I am now on the 4.04 google factory flash.
Now my query is, now I am on this 4.04, I presume I am no longer rooted. Can I use WugFresh's program to root the phone again or do I have to wait for another update to the program?
I was rather twitchy during rooting, expecting power cuts across the UK, earth tremor to knock the lead out at the wrong time, aliens to come down and screw it up etc that I dare not try it (don't really understand what I did even though it has worked)...
There is a program on now called superuser, but does not seem to have root access, so I presume I am not rooted now??
Any help would be appreciated.
Thanks
Darren
I did refer to a guide but can't post the link to it.

this is why you don't use toolkits... when you use them you dont know what's going on.
fastboot oem unlock (bootloader unlocked already?)
fastboot flash recovery <get clockwork recovery img>
get su.zip (find it on forum)
flash it in clockwork
you have root.
alternatively, you can flash a custom rom.

zephiK said:
this is why you don't use toolkits... when you use them you dont know what's going on.
fastboot oem unlock (bootloader unlocked already?)
fastboot flash recovery <get clockwork recovery img>
get su.zip (find it on forum)
flash it in clockwork
you have root.
alternatively, you can flash a custom rom.
Click to expand...
Click to collapse
Yip, I can agree with the statement, I don't know what was happening.
However, I could follow some of it, I think the bootloader is unlocked (can boot into with vol and off switch), I have clockwork and su, the installer did flash with clockwork.
Wonder if I am indeed rooted then???

pittnuma said:
Yip, I can agree with the statement, I don't know what was happening.
However, I could follow some of it, I think the bootloader is unlocked (can boot into with vol and off switch), I have clockwork and su, the installer did flash with clockwork.
Wonder if I am indeed rooted then???
Click to expand...
Click to collapse
When you boot the phone is there an unlocked lock at the bottom of the Google screen? That means your bootloader is unlocked. You can always get into the bootloader using the volume buttons and power.
Once again...using toolkits suck. Now you're stuck in limbo. Try installing an app that needs root like Titanium Backup and see if it works.

zephiK said:
this is why you don't use toolkits... when you use them you dont know what's going on.
fastboot oem unlock (bootloader unlocked already?)
fastboot flash recovery <get clockwork recovery img>
get su.zip (find it on forum)
flash it in clockwork
you have root.
alternatively, you can flash a custom rom.
Click to expand...
Click to collapse
Actually no, not with 4.04
I flashed su.zip with CWM and no dice and I used 3 toolkits as well as that method and still no root.

foreman31 said:
Actually no, not with 4.04
I flashed su.zip with CWM and no dice and I used 3 toolkits as well as that method and still no root.
Click to expand...
Click to collapse
does the toolkit update itself to include the 4.0.4 root? no, so download the new toolkit..also u dont need to try 3 toolkits, u need the latest and select gsm 4.0.4
if u use the su.zip, u need the latest working with the 4.0.4
again what make u say "still no root"? with no details we can't help u

foreman31 said:
Actually no, not with 4.04
I flashed su.zip with CWM and no dice and I used 3 toolkits as well as that method and still no root.
Click to expand...
Click to collapse
Download Superuser-3.0.7-d-signed.zip from here: Link
and flash that through CWM... It definately works on 4.0.4.

hEaTLoE said:
When you boot the phone is there an unlocked lock at the bottom of the Google screen? That means your bootloader is unlocked. You can always get into the bootloader using the volume buttons and power.
Once again...using toolkits suck. Now you're stuck in limbo. Try installing an app that needs root like Titanium Backup and see if it works.
Click to expand...
Click to collapse
Thanks, yes there is, so the bootloader is unlocked.
I am flashed correctly so just the root I presume

pittnuma said:
Thanks, yes there is, so the bootloader is unlocked.
I am flashed correctly so just the root I presume
Click to expand...
Click to collapse
If you see a superuser app in your app drawer then you have a proper root. If not then something went wrong.

Hi guys, just curious but is there anyway to gain root temporarily in 4.0.4 without unlocking bootloader? Similar to the escalation of privileges hack that worked on 4.0.1/4.0.2.
I want to remove the /system/bin/su and /system/app/Superuser.apk files on the device to get rid of the "Unsupported Device" warning in Google Wallet.
Thanks in advance.

jonnyg1097 said:
If you see a superuser app in your app drawer then you have a proper root. If not then something went wrong.
Click to expand...
Click to collapse
Ahh right, I have the Superuser, however when I tried the app suggested earlierit stated device not rooted...

Got it...
Installed new SU.zip, I had a slightly older version and the recovery-clockwork-5.5.0.4
Thanks all.
Can't post links yet but this is the link for the su I used just add the www etc
box.com/s/jvcf196j7x8f8vrc9cyt

jonnyg1097 said:
If you see a superuser app in your app drawer then you have a proper root. If not then something went wrong.
Click to expand...
Click to collapse
This is not entirely true. You can have the Superuser app in your app drawer and still not have root. The permissions on su need to be set properly.

Diger36 said:
Download Superuser-3.0.7-d-signed.zip from here: Link
and flash that through CWM... It definately works on 4.0.4.
Click to expand...
Click to collapse
pittnuma said:
Got it...
Installed new SU.zip, I had a slightly older version and the recovery-clockwork-5.5.0.4
Thanks all.
Can't post links yet but this is the link for the su I used just add the www etc
box.com/s/jvcf196j7x8f8vrc9cyt
Click to expand...
Click to collapse
A look at the first page.... Ah well, glad you sorted it out...
Sent from my Galaxy Nexus using xda premium

If I root?

Will I lose the ability to get the 4.4 ota update when available?

If you just root, then no. What would prevent it from installing is if you have a custom recovery. Then it would fail to install. If your just rooted and take the OTA though you may loose root.

Are you sure? lol.
Well if you lose root, you can always re-root?
Are you rooted and have a custom recovery?

REDFOCZ said:
If you just root, then no. What would prevent it from installing is if you have a custom recovery. Then it would fail to install. If your just rooted and take the OTA though you may loose root.
Click to expand...
Click to collapse
Custom recovery is fine (from the standpoint of the OTA verification check). Custom kernel will cause OTA to fail, as would any changes/modifications/removals to/from /system (ie the ROM)

To root I need an unlocked bootloader?

SysAdmNj said:
To root I need an unlocked bootloader?
Click to expand...
Click to collapse
Yes. Unlocking bootloader just sets a flag so signature checks aren't performed. For security reasons it also clears your user data so someone can't just bypass your login.

Until I see the next version of Android and a few weeks of user comments on its abilities, I'm not sure whether I'll ever want to upgrade...

sfhub said:
Yes. Unlocking bootloader just sets a flag so signature checks aren't performed. For security reasons it also clears your user data so someone can't just bypass your login.
Click to expand...
Click to collapse
Wish I knew this before I installed all my apps lol. Its easy to unroot and lock back up in case?
alpine101 said:
Until I see the next version of Android and a few weeks of user comments on its abilities, I'm not sure whether I'll ever want to upgrade...
Click to expand...
Click to collapse
You mean 4.3 is fine with you? Battery life and performance?

Or just wait until your current Custom ROM gets updated to the 4.4, and then flash with that newly created ROM. Boom. 4.4.

I just got this yesterday and I like it so far, reading on it isnt bad. Even at night, some apps have night mode etc. I dont feel like rooting/unlocking just yet, let alone custom rom'ming, until I'm sure I'm keeping it. Would like to hear the nexus 10 announcement but honestly the size of the nexus 7 is comfortable to carry around. The weight is good, and it kind of fits it in my old nexus 7 rubber case. If I do keep it, definitely looking forward to 4.4 custom roms and a better fitting case.

REDFOCZ said:
If you just root, then no. What would prevent it from installing is if you have a custom recovery. Then it would fail to install. If your just rooted and take the OTA though you may loose root.
Click to expand...
Click to collapse
The problem is that to have root you have to install a custom recovery first, since the root file (supersu) is installed from a custom recovery.
So how can we root without a custom recovery?

I haven't rooted my N7, just going off my experience with other devices.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Sensamic said:
The problem is that to have root you have to install a custom recovery first, since the root file (supersu) is installed from a custom recovery.
So how can we root without a custom recovery?
Click to expand...
Click to collapse
Does this method not work?
http://forum.xda-developers.com/showthread.php?t=2467014
It involves unlocking your device by putting your device in bootloader/fastboot mode, but I dont see anything about installing a custom recovery.
REDFOCZ said:
I haven't rooted my N7, just going off my experience with other devices.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Whats your primary use for your n7?

Web browsing, video watching, and reading magazine's.

Sensamic said:
The problem is that to have root you have to install a custom recovery first, since the root file (supersu) is installed from a custom recovery.
So how can we root without a custom recovery?
Click to expand...
Click to collapse
You don't need to "install" custom recovery. Booting custom recovery (leaving stock recovery on the tablet) is good enough.
The key to everything is you need to unlock the bootloader. Once you do that, any number of methods of installing root are possible.
If you don't want to unlock bootloader, then you need to wait for an exploit to be found which could arrive anytime between now and never.
---------- Post added at 10:52 AM ---------- Previous post was at 10:48 AM ----------
SysAdmNj said:
Does this method not work?
http://forum.xda-developers.com/showthread.php?t=2467014
It involves unlocking your device by putting your device in bootloader/fastboot mode, but I dont see anything about installing a custom recovery.
Click to expand...
Click to collapse
It works.
From a technique standpoint, it is equivalent to booting custom recovery and installing root, except everything is automated for you.
The key is you need to unlock.
In the most published method, after unlocking, you boot (or install) custom recovery and manually select the SuperSU or Superuser install update.zip
In CF-AutoRoot, there is a custom kernel that you boot whose job is to install root (essentialy taking care of the manual selection of the SuperSU/Superuser install update.zip), then after a subsequent reboot, you are back to using your original kernel, except root is installed.

sfhub said:
You don't need to "install" custom recovery. Booting custom recovery (leaving stock recovery on the tablet) is good enough.
The key to everything is you need to unlock the bootloader. Once you do that, any number of methods of installing root are possible.
If you don't want to unlock bootloader, then you need to wait for an exploit to be found which could arrive anytime between now and never.
---------- Post added at 10:52 AM ---------- Previous post was at 10:48 AM ----------
It works.
From a technique standpoint, it is equivalent to booting custom recovery and installing root, except everything is automated for you.
The key is you need to unlock.
In the most published method, after unlocking, you boot (or install) custom recovery and manually select the SuperSU or Superuser install update.zip
In CF-AutoRoot, there is a custom kernel that you boot whose job is to install root (essentialy taking care of the manual selection of the SuperSU/Superuser install update.zip), then after a subsequent reboot, you are back to using your original kernel, except root is installed.
Click to expand...
Click to collapse
Thanks for the explanation. I think I'm just going for it as I didnt see any announcements of the nexus 5 or kit kat, let alone nexus 10 I'll just keep my nexus 7 2013. I did more reading on this device the past two days then I've done on my previous nexus 7 and nexus 10 tabs. In other words I like it, good enough to keep. Comfy size, weight etc. Now to find the best rom for battery life with a kernel that would let me double tap to wake

SuperSU and Stock Recovery

is there away to install SuperSU when you have stock recovery? I'm thinking that we have to have either CWM/TWRP to install the zip. or am I having a brain fart on this.....
Thanks for whomever can clear my cobwebs..

You need a custom recovery (TWRP or CWM).

bkeaver said:
is there away to install SuperSU when you have stock recovery? I'm thinking that we have to have either CWM/TWRP to install the zip. or am I having a brain fart on this.....
Thanks for whomever can clear my cobwebs..
Click to expand...
Click to collapse
You can install it if you have the bootloader unlocked.
Use boot command instead of flash to boot into custom recovery and install su.
e.g
Fastboot boot twrp.img

uronfire said:
You can install it if you have the bootloader unlocked.
Use boot command instead of flash to boot into custom recovery and install su.
e.g
Fastboot boot twrp.img
Click to expand...
Click to collapse
Yes, this.
However, why bother keeping stock recovery at all? Stock recovery is effectively neutered once rooted, as you can no longer install an OTA.

uronfire said:
You can install it if you have the bootloader unlocked.
Use boot command instead of flash to boot into custom recovery and install su.
e.g
Fastboot boot twrp.img
Click to expand...
Click to collapse
Thanks this worked :good:

so when I go into recovery now I get a image of a htc one with a red triangle and exclamation mark inside of it?? since I have never went into recovery on this phone before isn't it supposed to look like any other stock recovery??? and if this isn't right I have tried flashing the recovery already and still get the same result... can someone expand on this for me pls

bkeaver said:
so when I go into recovery now I get a image of a htc one with a red triangle and exclamation mark inside of it?? since I have never went into recovery on this phone before isn't it supposed to look like any other stock recovery??? and if this isn't right I have tried flashing the recovery already and still get the same result... can someone expand on this for me pls
Click to expand...
Click to collapse
You have stock recovery.

BenPope said:
You have stock recovery.
Click to expand...
Click to collapse
so it doesn't give you flash update and wipe and all that anymore.. sorry like I said I have never went into recovery on this phone.. just making sure...

bkeaver said:
so it doesn't give you flash update and wipe and all that anymore.. sorry like I said I have never went into recovery on this phone.. just making sure...
Click to expand...
Click to collapse
I think you have to hold volume up and hit power or something.

ok I am good.. thank you... I'm putting everything back to stock because someone bought my phone and I just want to make sure everything is correct on it now.. thanks!!

redpoint73 said:
Yes, this.
However, why bother keeping stock recovery at all? Stock recovery is effectively neutered once rooted, as you can no longer install an OTA.
Click to expand...
Click to collapse
i sold the phone and this is what they requested. I know the OTA wont work and I never keep stock recoveries on my phones but.... I guess they will find out for themselves

and btw thanks everyone for the help. I hit my thanks button but on my browser it it isn't showing it just to let you know....

bkeaver said:
i sold the phone and this is what they requested. I know the OTA wont work and I never keep stock recoveries on my phones but.... I guess they will find out for themselves
Click to expand...
Click to collapse
Sounds like somebody that is a bit ill-informed. They want root, but they probably also want OTA (the 2 don't go together, IMO) and heard that you need stock recovery for OTA. I suppose they can change everything back that they modified with root, and unroot or hide root to install the OTA. But it just seems they are making life more complicated than it needs to be.
Also sounds like its a person that wants root, but not willing to do it themselves. But I suppose that's not really your problem!

Option to root and have ota is very easy :
Stock rom (unmodified but rooted)
Stock recovery
And you can ota. The ota will probably delete superuser but that's about it. The ota will not fail because its rooted as long as the stock rom/apps are unmodified

Mr Hofs said:
Option to root and have ota is very easy :
Stock rom (unmodified but rooted)
Stock recovery
And you can ota. The ota will probably delete superuser but that's about it. The ota will not fail because its rooted as long as the stock rom/apps are unmodified
Click to expand...
Click to collapse
yeah this is what I did for them so who knows.. I've never tried it that way but i guess it would work like that

redpoint73 said:
Yes, this.
However, why bother keeping stock recovery at all? Stock recovery is effectively neutered once rooted, as you can no longer install an OTA.
Click to expand...
Click to collapse
Rooting doesn't affect ota's, at least not in my experience.

ashyx said:
Rooting doesn't affect ota's, at least not in my experience.
Click to expand...
Click to collapse
Only if absolutely nothing was changed with the stock ROM.
Its more my point there is little point to installing OTAs on a rooted device.

redpoint73 said:
Only if absolutely nothing was changed with the stock ROM.
Its more my point there is little point to installing OTAs on a rooted device.
Click to expand...
Click to collapse
I don't understand that statement. I still run stock sense, but with a few additions that don't affect ota's. So I still get updates while having things configured the way I want. I can also run things that require root such as titanium backup and a few others.

ashyx said:
I don't understand that statement. I still run stock sense, but with a few additions that don't affect ota's. So I still get updates while having things configured the way I want. I can also run things that require root such as titanium backup and a few others.
Click to expand...
Click to collapse
Because once you accept an OTA, you will be unrooted. You will have to root again, either by installing custom recovery (than back to stock recovery so you can OTA) or the trick of booting custom recovery via adb to flash SU (as described here). Its just a lot of jumping through hoops with little added value.
On the other hand, if you have custom recovery installed, you can flash any of the array of stock rooted or awesome custom ROMs posted here. This includes stock rooted ROMs taken from OTA updates from lots of versions (often posted within days of the OTA starting to roll out), not just your carrier, so you can possibly get an update much faster than waiting for the OTA to roll out from your carrier (although that depends on what carrier version you have). You also don't have to constantly be worried "well, if I change this I won't get OTAs". You can do whatever the heck you want, and isn't that really the whole point of root?
Its just my opinion. And a lot of this may stem from the fact that I'm on AT&T, who are not only agonizingly slow about rolling out OTAs (sometimes 3-4 months or even later than other carriers on my past HTC device) and have even went to the effort to close exploits and prevent unlocking of bootloaders when rolling out new OTAs (on the One X EVITA). In fact there was even a bug (I assume it was a bug - others may accuse that it was intentional) where installing the Jellybean OTA with SuperCID and S-on bricked the phone.
As I said, its just an opinion. But there are many others on XDA that will agree that OTAs have no place on rooted Android devices.
And to be fair, I did cover myself and stated "there is little point" instead of "there is no point"

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