Develop Bugs

[Q] Root With OTA?

Hero guys
I just want to know, is there any way to root and keep getting OTA ?
And what is the best method to root?
Sent from my HTC One_M8 using Tapatalk

ahmadsraj said:
Hero guys
I just want to know, is there any way to root and keep getting OTA ?
And what is the best method to root?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
You still can OTA, even your phone is rooted.
Only their is some tips you need to know:
1. Don't delete or change any files and apps that is build-in on system.
Even you want to delete apps made from telecom operators IS NOT PERMITTED!
2. Recovery need flash back to original version.
For these two tips, you can do OTA even your phone is rooted.
But note that YOU NEED TO ROOT AGAIN every OTA.

missile0407 said:
You still can OTA, even your phone is rooted.
Only their is some tips you need to know:
1. Don't delete any files and apps that is build-in on system.
2. Recovery need flash back to original version.
For these two tips, you can do OTA even your phone is rooted.
But note that YOU NEED TO ROOT AGAIN every OTA.
Click to expand...
Click to collapse
Speaking to point 2:
I recommend not flashing a custom recovery at all. You can boot to TWRP/CWM/Philz from fastboot without flashing, and this leaves your stock recovery intact.
To do this: download your preferred recovery image. Let's say it's called "openrecovery-2.7.0.3-m8.img"
Copy this file to the same folder your "fastboot" executable is in on your computer.
Boot your phone into fastboot and connect it to your computer via USB.
Type in the following on your computer:
Code:
fastboot boot openrecovery-2.7.0.3-m8.img
Now your phone will boot into TWRP without touching your partitions or anything else that might affect OTAs. Apply your root.zip update and reboot!
EDIT: Once you've booted into your custom recovery from fastboot, you can disconnect the USB, so you're not stuck at your PC.

craig0r said:
Speaking to point 2:
I recommend not flashing a custom recovery at all. You can boot to TWRP/CWM/Philz from fastboot without flashing, and this leaves your stock recovery intact.
To do this: download your preferred recovery image. Let's say it's called "openrecovery-2.7.0.3-m8.img"
Copy this file to the same folder your "fastboot" executable is in on your computer.
Boot your phone into fastboot and connect it to your computer via USB.
Type in the following on your computer:
Code:
fastboot boot openrecovery-2.7.0.3-m8.img
Now your phone will boot into TWRP without touching your partitions or anything else that might affect OTAs. Apply your root.zip update and reboot!
EDIT: Once you've booted into your custom recovery from fastboot, you can disconnect the USB, so you're not stuck at your PC.
Click to expand...
Click to collapse
Hello,
I have the same question as the OP. Everything seems to make sense when following this post. My question is even though I will just boot into recovery without ever flashing the recovery am I really able to disconnect my phone from the computer? It seems like the recovery files are actually on the computer so I would need to keep the phone connected while I install the supersu.zip
Thank you for the help

I don't see why you would want to disconnect it but the image should be loaded into ram so I assume it would be safe to disconnect. I have never tried it though :/

exad said:
I don't see why you would want to disconnect it but the image should be loaded into ram so I assume it would be safe to disconnect. I have never tried it though :/
Click to expand...
Click to collapse
Ok I guess I should just leave it connected since I just need to install the supersu.zip file.
Every time an OTA update is applied will I just need to boot into TWRP recover and reinstall the supersu.zip file in order to regain root access?

SouthBayBruin said:
Ok I guess I should just leave it connected since I just need to install the supersu.zip file.
Every time an OTA update is applied will I just need to boot into TWRP recover and reinstall the supersu.zip file in order to regain root access?
Click to expand...
Click to collapse
There's no reason you *can't* leave it plugged in, but yeah, when you run the fastboot command it loads the custom recovery into RAM, and the connection to your computer is doing nothing for you. I give my personal guarantee that it's 100% safe to disconnect after recovery's loaded. But again, if leaving it plugged in makes you more comfortable, it won't hurt.

I can confirm it, that with root OTA is possible
I had a device with root, s-off, unlocked etc... but stock recovery, stock rom,..
today I got the ota, updated without any problems... I just needed to boot into custom recovery afterwards and install the root.zip

zimilaci said:
I can confirm it, that with root OTA is possible
I had a device with root, s-off, unlocked etc... but stock recovery, stock rom,..
today I got the ota, updated without any problems... I just needed to boot into custom recovery afterwards and install the root.zip
Click to expand...
Click to collapse
Did you just install the regular supersu file?
I read this thread (http://forum.xda-developers.com/showthread.php?t=2755657) and it seems that if I install the regular supersu root file the OTA update will fail.
Just wondering if you just used the regular files in order to root your phone.

SouthBayBruin said:
Did you just install the regular supersu file?
I read this thread (http://forum.xda-developers.com/showthread.php?t=2755657) and it seems that if I install the regular supersu root file the OTA update will fail.
Just wondering if you just used the regular files in order to root your phone.
Click to expand...
Click to collapse
http://download.chainfire.eu/396/SuperSU

zimilaci said:
I can confirm it, that with root OTA is possible
I had a device with root, s-off, unlocked etc... but stock recovery, stock rom,..
today I got the ota, updated without any problems... I just needed to boot into custom recovery afterwards and install the root.zip
Click to expand...
Click to collapse
Can you please guide me through the entire process on how to install the OTA update and not lose root, I don't have much knowledge when it comes to flashing into recovery, etc. I do have an HTC One M8 with S-Off. I would be eternally grateful if you could help me out.

KaranNavani said:
Can you please guide me through the entire process on how to install the OTA update and not lose root, I don't have much knowledge when it comes to flashing into recovery, etc. I do have an HTC One M8 with S-Off. I would be eternally grateful if you could help me out.
Click to expand...
Click to collapse
Dude, do the research yourself. I don't know how many more times this has to be said. There's nothing special you have to do, just apply the OTA update when prompted

update problem

Hi, I have bought used here in Italy a op3, when turn on in the display I can see a message about the bootloader unlock, and so I think that the previously owner have unlocked the unit. Now I have a problem with the update, I have tried with ota and with USB but the phone stop the update and show me the message installation failed, then I can only reboot. How I can relock the Bootloader? Thanks in advance for your help.

before you re-lock the bootloader you should make sure that you are running the stock oxygenOS rom and receovery, see below:
https://forums.oneplus.net/threads/...lus-3-and-go-back-completely-to-stock.456232/

thanks for your reply, I, think that the phone now running with OxygenOS 3.2.2 stock, so I can directly relock the bootloader? If I do an hard reset the bootloader will be relocked?

alchemist76 said:
thanks for your reply, I, think that the phone now running with OxygenOS 3.2.2 stock, so I can directly relock the bootloader? If I do an hard reset the bootloader will be relocked?
Click to expand...
Click to collapse
you might be running OOS 3.2.2 stock but still have a custom recovery - boot into recovery first just to confirm that you have the stock recovery as well

still if you have a custom recovery, it's easier to get update. Just download the full rom and flash it with TWRP (I don't think there is another custom recovery), it won't wipe the data. Even if the previous owner did a slight modification on OOS 3.2.2, it will overwrite it.
updates can be downloaded many days before the OTA appear on the phone.

Ok I think that I have a custom recovery, TWRP working with non rooted phone? I have checked and my phone not have root. Please can you explain how I can update through TWRP?

if you want to stay unlocked and use TWRP that's fine, but note that you will need to MANUALLY UPDATE every time if you're on the stock OOS ROM.
if you are not comfortable with this, follow the instructions on the link i sent you to get back to full stock with stock recovery as well, so updates OTA work correctly.
https://forums.oneplus.net/threads/...lus-3-and-go-back-completely-to-stock.456232/

2x4 thanks for your help, I not have any problem to keep my phone unlocked, but I don't able to update not even in manual way, maybe I wrong something.
I have enabled usb debug on op3, have connected the phone to my laptop and opened minimal ADB, then have downloaded the oxygenOS 3.2.4 put the phone in sideload mode, cecked the connection with adb devices command and the phone is connected. Then writed adb sideload and have dragged the oxigenOs .3.2.4 . but nothing happen in adb minimal and on the phone. After a bit the phone give me the same message that appears when I try to uptade through ota, installation failed an I can only reboot. Thanks again for your suggestions.

alchemist76 said:
2x4 thanks for your help, I not have any problem to keep my phone unlocked, but I don't able to update not even in manual way, maybe I wrong something.
I have enabled usb debug on op3, have connected the phone to my laptop and opened minimal ADB, then have downloaded the oxygenOS 3.2.4 put the phone in sideload mode, cecked the connection with adb devices command and the phone is connected. Then writed adb sideload and have dragged the oxigenOs .3.2.4 . but nothing happen in adb minimal and on the phone. After a bit the phone give me the same message that appears when I try to uptade through ota, installation failed an I can only reboot. Thanks again for your suggestions.
Click to expand...
Click to collapse
sorry, im not really sure what you mean, but if you're following the instructions on that post step by step and verifying what you get it should work.
You need to successfully flash the full zip to get the stock rom+recovery on there

ok sorry for my confusion. Please can you explain to me the right way to update a bootloader unlocked phone?

alchemist76 said:
ok sorry for my confusion. Please can you explain to me the right way to update a bootloader unlocked phone?
Click to expand...
Click to collapse
the bootloader being locked or unlocked is irrelevant - your issue is your non-stock recovery.
the full Oxygen OS zip includes the stock recovery from OnePlus, which OTA updates are programmed to use to automatically update your phone.
since you have TWRP recovery instead, you'll need to download and manually flash OxygenOS
download the full ZIP for 3.2.4 from this thread and flash it via TWRP recovery:
http://forum.xda-developers.com/oneplus-3/how-to/oxygen-os-3-2-4-released-t3437911

Couldn't install system update

I am unlocked and was rooted with Magisk and the OTA OPM1.171019.013 tried to install and failed. I uninstalled Magisk thinking it might resolve the problem. It didn't. I have OPM1.171019.011 and would really like the update and reinstall Magisk to be rooted. Is there a way to get this update to install?

ranlil said:
I am unlocked and was rooted with Magisk and the OTA OPM1.171019.013 tried to install and failed. I uninstalled Magisk thinking it might resolve the problem. It didn't. I have OPM1.171019.011 and would really like the update and reinstall Magisk to be rooted. Is there a way to get this update to install?
Click to expand...
Click to collapse
Look over this thread for problems with OTA's and rooting :good:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

I've got the same issue. it said failed a few days ago, now it just stays on step 1 of 2. read duce's thread but it's about his script, is there any way to get the ota to take?

kellybrf said:
I've got the same issue. it said failed a few days ago, now it just stays on step 1 of 2. read duce's thread but it's about his script, is there any way to get the ota to take?
Click to expand...
Click to collapse
Were your rooted or had custom recovery before you started?

Badger50 said:
Were your rooted or had custom recovery before you started?
Click to expand...
Click to collapse
rooted, twrp, magisk

kellybrf said:
rooted, twrp, magisk
Click to expand...
Click to collapse
Then that's why you can't take the ota. Need to be unrooted and on stock recovery for OTA's.

Badger50 said:
Look over this thread for problems with OTA's and rooting :good:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
Thanks!! Worked as described.

Badger50 said:
Look over this thread for problems with OTA's and rooting :good:
Click to expand...
Click to collapse
I had a look over there, and it looked a bit scary. I don't want to do the critical unlock. (I still have the stock bootloader) Instead I found another way that involved patching a factory image.
My steps where:
Download the latest factory image
Checked the SHA256, then unpacked the zip
Extracted the boot.img file from the image-taimen-<version>.zip
Copied the boot.img onto my device (adb push or drag and drop)
Used Magisk to patch it. (Install button, then "patch boot image file") (NB: The patched boot image is about half the size of the original. This is normal)
Copied the patched_boot.img back to my PC, and renamed it back to boot.img
Put the patched boot.img back into the image-taimen-<version>.zip replacing the original
Once I had modified system image, I then flashed my device in the usual way using flash-all.sh (NB: You need to remove the -w switch from the last fastboot command so that it does not wipe the user data).
The end result is that my phone is updated to the latest November firmware, and I still have root with Magisk.
Next month, I will try again with an OTA, but if that does not work, then the above process should be easy and reliable.

Ota update for pixel 2 xl with magisk and twrp already installed

I am sure this has been asked and answered 100 times but for the life of me I can't find a definite answer. I have a Pixel 2 XL and it is rooted and I have Magisk and TWRP installed on it. I want to be able to install the OTA for this month, but I do not want to lose anything on the phone. I also would rather not lose Magisk or TWRP. Normally on my android phones I use ROMs and can just update through TWRP, but I want to stay on stock because I don't want to lose Active Edge. So can someone please help me by giving me step by step instructions or point me to instructions that are simple to follow so I can take the OTA?
I really appreciate the help.

I was having the same problem and was helped by some of the members here.. Best way is to flash the firmware after removing the -w from the flash all file. Then flash twrp and magisk.
Ota

Thanks for your help. I will try that.

magicmaker said:
Thanks for your help. I will try that.
Click to expand...
Click to collapse
Here's a quick little guide I made for updating monthly factory images. Hopefully it'll help you out :good:

Sorta related...
Are there any ROMS that come rooted so I don't have to go through the monthly process of backup/unroot/update/root/restore?
Would love to just flash a ROM update and be done.

rank78 said:
Sorta related...
Are there any ROMS that come rooted so I don't have to go through the monthly process of backup/unroot/update/root/restore?
Would love to just flash a ROM update and be done.
Click to expand...
Click to collapse
Not that I'm aware of, but maybe some on the horizon...

Badger50 said:
Here's a quick little guide I made for updating monthly factory images. Hopefully it'll help you out :good:
Click to expand...
Click to collapse
Hi, quick question
I am only able to do them steps above if I have done 'fastboot unlock_critical'? I have only done 'fastboot unlock'
Also I would need to boot into TWRP and flash a kernel + magisk to retain root?

You have to issue the "fastboot unlock_critical" command in order for the bootloader to update, since the bootloader is included in both factory images and full OTAs. Speaking of full OTA's, one of our recognized developers, @elliwigy, revealed (thread here) that it is possible to flash a full OTA image through TWRP, which eliminates the need to open the factory image and remove the -w flag from the last line. Flashing the OTA works because TWRP doesn't check signatures like the stock recovery. You will lose both root and TWRP upon reboot however, so you will still need to connect to a PC in order to reinstall TWRP so you can subsequently replace the stock Kernel with the Flash Kernel and then root.
I can verify this works, as I tried it with the May update.

Root pie Dec update (v10.0.2)

I got update from oero to pie via OTA today,
I tried many patched boot.img and root maunally by patching stock img but its stuck on boot screen.. Any idea??

Download the OTA, extract the images from the payload, flash the stock boot.img in both slots. After your phone boots you can download the latest magisk manager, use it to patch the stock boot.img that you already downloaded and use it to root your device.

Hakkinan said:
Download the OTA, extract the images from the payload, flash the stock boot.img in both slots. After your phone boots you can download the latest magisk manager, use it to patch the stock boot.img that you already downloaded and use it to root your device.
Click to expand...
Click to collapse
What's mean " in both slots " ?
I tried to patch boot.img maunally but my device stuck on boot animations, So I flashed back stock boot.img into fastboot without root agian..

This is an A/B device which means that it has two slots for every partition (A and B). You need to flash the stock boot in the same partirion that it currently being used, flashing It in both is just to be safe in future updates.

Oh hey try this one: https://drive.google.com/file/d/1dBX2dZV_wWgSip8d9lk0lrO_JHfxGdKU/view?usp=sharing

Sorry if this has been asked before, but I didn't find it anywhere on this forum. I am also stuck on a bootloop after installing Pie update. I had Magisk installed and I've uninstalled it - didn't reboot. After, I've applied the Pie update. Didn't reboot. Went back to Magisk app and then did install - install to inactive slot. After that have a "nice" bootloop. How can I get the unpatched boot.img? Thanks in advance.

FRibeiro1400 said:
Sorry if this has been asked before, but I didn't find it anywhere on this forum. I am also stuck on a bootloop after installing Pie update. I had Magisk installed and I've uninstalled it - didn't reboot. After, I've applied the Pie update. Didn't reboot. Went back to Magisk app and then did install - install to inactive slot. After that have a "nice" bootloop. How can I get the unpatched boot.img? Thanks in advance.
Click to expand...
Click to collapse
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).

Hakkinan said:
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).
Click to expand...
Click to collapse
Thank you so much! I am going to try it later, hopefully I can get my phone back fully working. If it's not asking too much, what are the commands I have to type to install it on both slots?

FRibeiro1400 said:
Thank you so much! I am going to try it later, hopefully I can get my phone back fully working. If it's not asking too much, what are the commands I have to type to install it on both slots?
Click to expand...
Click to collapse
"fastboot flash boot_a boot.img" and "fastboot flash boot_b boot.img"

Hakkinan said:
"fastboot flash boot_a boot.img" and "fastboot flash boot_b boot.img"
Click to expand...
Click to collapse
Stuck on boot agian..
I tried flash OTA manual by fastboot & flash patched stuck too!
I think I need reset to root?
*NOTICE: I installed Xposed framwork on oreo, May that's problem?

HaN5aR said:
Stuck on boot agian..
I tried flash OTA manual by fastboot & flash patched stuck too!
I think I need reset to root?
*NOTICE: I installed Xposed framwork on oreo, May that's problem?
Click to expand...
Click to collapse
Wait, did you try to flash the whole OTA?

Hakkinan said:
Wait, did you try to flash the whole OTA?
Click to expand...
Click to collapse
At first I updated from oreo to pie via OTA without any VPN
I failed to root it so, I tried flash it again from HERE but facing the same problem with root it stuck on bootanimations

Hakkinan said:
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).
Click to expand...
Click to collapse
Unfortunatelly, it seems the link for the OTA zip was removed, so, phone will stay bricked thanks to the lack of instructions of how to update to Pie when Magisk is installed. Why do they remove the links?

HaN5aR said:
At first I updated from oreo to pie via OTA without any VPN
I failed to root it so, I tried flash it again from HERE but facing the same problem with root it stuck on bootanimations
Click to expand...
Click to collapse
Ok, now i understand what is happening. It bootloops as soon as you reboot after installing magisk right? If so, then i need to know what you are doing to install magisk.
FRibeiro1400 said:
Unfortunatelly, it seems the link for the OTA zip was removed, so, phone will stay bricked thanks to the lack of instructions of how to update to Pie when Magisk is installed. Why do they remove the links?
Click to expand...
Click to collapse
First the server is down, nobody removed the file, you just need to wait for it to go up again. Second, you can easily revert your phone back to 10.0.1.0 and stay there, your phone isn't bricked and it doesn't have to stay in this current state.

Hakkinan said:
Ok, now i understand what is happening. It bootloops as soon as you reboot after installing magisk right? If so, then i need to know what you are doing to install magisk.
First the server is down, nobody removed the file, you just need to wait for it to go up again. Second, you can easily revert your phone back to 10.0.1.0 and stay there, your phone isn't bricked and it doesn't have to stay in this current state.
Click to expand...
Click to collapse
I never had 10.01.0 installed. I was on Oreo and got the update this morning. I've followed the rule for OTA with Magisk and it was the wrong thing to do. If, at least, there was a warning to NOT follow the instructions, all would be sorted. Maybe I can find a link somewhere with this update, as I don't want to lose my data. On Xiaomi official site, the last rom available is version V9.6.11.0.ODLMIFF. Unless I install this one back.

FRibeiro1400 said:
I never had 10.01.0 installed. I was on Oreo and got the update this morning. I've followed the rule for OTA with Magisk and it was the wrong thing to do. If, at least, there was a warning to NOT follow the instructions, all would be sorted. Maybe I can find a link somewhere with this update, as I don't want to lose my data. On Xiaomi official site, the last rom available is version V9.6.11.0.ODLMIFF. Unless I install this one back.
Click to expand...
Click to collapse
Doesn't matter if you had 10.0.1.0 previously or not. You can download it and install it without losing data.