So I plan on updating my phone by uninstalling Magisk, not rebooting, install OTA and then reinstall Magisk to inactive drive. In the past, this had failed to work. May someone recommend a Magisk version that will work with the June update, so that I can install without losing my data through this method?
Thanks in advance!
Related
Hello
I've rooted my Nexus 5X and i left the recovery to stock recovery because i wanted to have the OTA updates normally without using a PC.
With ytsemless root I was hoping that this is no problem. But the febuary security OTA fails when I try to install.
Can someone explain to me why this could fail?
I have not much root apps installed. Just adaway, busybox, sd maid and supersu. No costum kernel.
So from my point of view I touched nothing that should have an impact to OTA.
So my question is: Why is there always an error when I try to update with OTA?
ChenZ86 said:
Hello
I've rooted my Nexus 5X and i left the recovery to stock recovery because i wanted to have the OTA updates normally without using a PC.
With ytsemless root I was hoping that this is no problem. But the febuary security OTA fails when I try to install.
Can someone explain to me why this could fail?
I have not much root apps installed. Just adaway, busybox, sd maid and supersu. No costum kernel.
So from my point of view I touched nothing that should have an impact to OTA.
So my question is: Why is there always an error when I try to update with OTA?
Click to expand...
Click to collapse
Because you have applied systemless root. Anything, ANYTHING different from completely stock will cause the normal OTA process to fail. These posts keep asking the same question and the answer never changes. It is what it is. There are a ton of posts here which will explain alternate flashing processes to update, then re-root your device.
Try using flashfire from Chainfire. It detects downloaded ota and ask you if you want to try and flash it. Also there is an option to re-root after updating. If the ota doesn't install then download the factory image for February and flash the whole thing. Make sure data is uncheked so that it doesn't wipe your data. It's a bigger download than ota but it will definitely work.
I had stock + root + xposed + layers. Managed to update to latest build with automatic re-root. Then I just flashed twrp-recovery using flashify and installed xposed through twrp. Took me 5 mins to flash everything (excluding time to download the factory image). All without using a PC!
Skickat från min Nexus 5X via Tapatalk
this all seems like a hassle compared to using a near-stock custom rom and updating it yourself.
2x4 said:
this all seems like a hassle compared to using a near-stock custom rom and updating it yourself.
Click to expand...
Click to collapse
[emoji106] Or even stock rom.
Sent from my Nexus 9 using Tapatalk
I've seen the guides for rooting the Developer Previews--but has any of that changed?
I'm on Marshmallow, decrypted using Xceed and TWRP.
I want to flash the Factory images and then root afterwards. Best advice?
wait until the kernels are done and/or supersu has been updated to reflect new build
I had the update notice when I got home Monday. It downloaded the update, and then I used FlashFire to apply the OTA since I had twrp installed. FF updated the tablet and then re-rooted it. Still have twrp and root.
Sent from my Nexus 5X using Tapatalk
Hi,
Do you mean that with flashfire you can root your pixel c and get Ota update without loosing data or root???
Thanks for your help
n1ck0 said:
Hi,
Do you mean that with flashfire you can root your pixel c and get Ota update without loosing data or root???
Thanks for your help
Click to expand...
Click to collapse
I used FlashFire to install the OTA and kept data and root.
Hello, my pixel 2 xl only has Magisk installed with Root and is on stock December 5th 8.1 update. I was wondering if the instructions of the official 'seamless OTA' installation would work with this January update (instructions here https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md). Basically, the instruction allows users to install OTA by disabling Magisk and re-installing it while the OTA is being applied.
I'm quite afraid to try it and was wondering if anyone can confirm.
Thanks
freemandjango said:
Hello, my pixel 2 xl only has Magisk installed with Root and is on stock December 5th 8.1 update. I was wondering if the instructions of the official 'seamless OTA' installation would work with this January update (instructions here https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md). Basically, the instruction allows users to install OTA by disabling Magisk and re-installing it while the OTA is being applied.
I'm quite afraid to try it and was wondering if anyone can confirm.
Thanks
Click to expand...
Click to collapse
Worst things that could happen are: OTA fails to install or you have to reinstall Magisk through fastbooting/T
WRP, so just try it.
I just flash full factory image and flash TWRP, Flash Kernel, and Magisk again, instead of waiting for OTA to be available through the phone.
freemandjango said:
Hello, my pixel 2 xl only has Magisk installed with Root and is on stock December 5th 8.1 update. I was wondering if the instructions of the official 'seamless OTA' installation would work with this January update (instructions here https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md). Basically, the instruction allows users to install OTA by disabling Magisk and re-installing it while the OTA is being applied.
I'm quite afraid to try it and was wondering if anyone can confirm.
Thanks
Click to expand...
Click to collapse
To be safe i would use the flash-all for December update. It will take to back to stock kernel and remove magisk. Then take the January ota. I think that is a sure way and doesn't take to many step.
Better to do flash all bat of January Factory Image, and reflashing magisk after that,
You can edit the flashing script, removing -w to prevent it wiping your data
I've tried it twice to no avail. I was able to go back to magisk and reinstall. I haven't lost anything. Ymmv...
Just unlocked, rooted (w/Magisk), and installed TWRP about a week ago. I'm on the stock ROM with the Feb security update. The March security update is pushing to my phone but fails install due to the previous mentioned items. I'm reading that a few problems are popping up that are contributed to the update so I'm holding off on installing it for now. How can I get it to quit trying to install it and showing the notification in the status bar? You can't dismiss the notification and if you reboot it tries to install the update again..
How did you install TWRP and keep it across updates?
Thanks for the response! I'm not 100% sure what you're asking, but I installed TWRP and magisk while on 8.1.0 and the Feb 2018 security update. A week or two later the March security update was released and pushed to my phone as an OTA but it fails install due to (and I'm guessing) the unlocked bootloader and root. Now I constantly have a failed install message in my notification bar and it won't go away. How can I keep the phone from attempting to install the OTA Update knowing it will fail?
the ota update is failing to install because your phone is rooted. the bootloader can be unlocked, but otas will fail to install if the os is not completely stock.
if you manually flash the march update, whether it's the ota or the full factory image, the notifications about an update being available or the failed install will go away.
altwu said:
the ota update is failing to install because your phone is rooted. the bootloader can be unlocked, but otas will fail to install if the os is not completely stock.
if you manually flash the march update, whether it's the ota or the full factory image, the notifications about an update being available or the failed install will go away.
Click to expand...
Click to collapse
I understand the reason it's failing. I don't really want to install the the OTA as I'm reading it has created additional problems. Is there anyway to keep the phone from checking for an update and subsequently failing and showing the notification?
Gulfstream 650 said:
I understand the reason it's failing. I don't really want to install the the OTA as I'm reading it has created additional problems. Is there anyway to keep the phone from checking for an update and subsequently failing and showing the notification?
Click to expand...
Click to collapse
When I got the notification to update, I just long pressed on it and hit the toggle to turn off notifications from whatever it was that it said it was coming from...Google play services I think?
Sent from my Pixel XL using XDA Labs
I flashed the full March Factory Image using the bat.all script (-w removed to keep data), then fastbooted into twrp 3.2.0.0 and flashed magisk. No additional problems or any issues at all.
kboya said:
I flashed the full March Factory Image using the flash-all.bat script (-w removed to keep data), then fastbooted into twrp 3.2.0.0 and flashed magisk. No additional problems or any issues at all.
Click to expand...
Click to collapse
Did you try turning off automatic update in Developer mode.
No, to me that is a no no especially if you have Flashfire installed
Gulfstream 650 said:
I understand the reason it's failing. I don't really want to install the the OTA as I'm reading it has created additional problems. Is there anyway to keep the phone from checking for an update and subsequently failing and showing the notification?
Click to expand...
Click to collapse
kboya said:
I flashed the full March Factory Image using the bat.all script (-w removed to keep data), then fastbooted into twrp 3.2.0.0 and flashed magisk. No additional problems or any issues at all.
Click to expand...
Click to collapse
same here. no problems with the march update + magisk. i've never updated using an ota. i always flash the full factory image.
Gulfstream 650 said:
Thanks for the response! I'm not 100% sure what you're asking, but I installed TWRP and magisk while on 8.1.0 and the Feb 2018 security update.
Click to expand...
Click to collapse
Let me elaborate:
Right now, if you install TWRP permanently, you don't get any OTAs. So you must install a full image. When you install the full image, TWRP get's wiped. So you always have to install TWRP using your computer. That's a real hassle for me.
Or is there any easy way how you can install a full image, while keeping TWRP or reinstalling TWRP on top without using a computer?
fiverings said:
Did you try turning off automatic update in Developer mode.
Click to expand...
Click to collapse
I'm not sure if this is a question to me or the OP!
Me? No, there's no need as once flashed any OTA notification is redundant and no longer displayed. Anyway, I usually dl and flash the new factory image when it's posted online. The whole process takes maybe 20 mins including the dl time. Also, if there are any "new issues" with a release, as the OP is suggesting, it's just as easy to go back a month with the previous factory image (easier as it's already dl'd)
kboya said:
I'm not sure if this is a question to me or the OP!
Me? No, there's no need as once flashed any OTA notification is redundant and no longer displayed. Anyway, I usually dl and flash the new factory image when it's posted online. The whole process takes maybe 20 mins including the dl time. Also, if there are any "new issues" with a release, as the OP is suggesting, it's just as easy to go back a month with the previous factory image (easier as it's already dl'd)
Click to expand...
Click to collapse
Good point, it's fairly easy to revert to the previous version if problems crop up. I'm going to go ahead and make the plunge. **edit** installed the March image and reinstalled TWRP and Magisk, so far so good.
Cool. Hope it stays that way.
Hi there,
Sorry, I'm finding contradictive answers to it. Is it ok to apply Android 11 OTA update to a rooted A10? Will it keep root after update? Should we do something special?
Thanks,
Mambobuzzz
Yes you can do the update and keep root.
Follow the instructions for doing a normal ota update.
Disable or remove any problem Magisk modules
Download the full update (currently 11.0.0.2)
Install the update as a “local upgrade” DO NOT REBOOT
Go to app and install Magisk to inactive slot
Reboot now
You should be on OOS 11
Reinstall/enable modules
Okay. Pretty much as usual actually then...
Thanks for your answer.
Did it. And succeded! Thank you!