Related
Hi,
I thought that after rooting OTA won't be available but I just got a notification about an update.
Is it safe to click "restart and install"? will it keep the device rooted?
if not, what's the easiest way to update?
nirfun said:
Hi,
I thought that after rooting OTA won't be available but I just got a notification about an update.
Is it safe to click "restart and install"? will it keep the device rooted?
if not, what's the easiest way to update?
Click to expand...
Click to collapse
Last time I updated, I noticed that TWRP took over the updating process if you have it flashed.
While updating, TWRP wont let the updating script to replace the recovery partition, so TWRP remains after the update, after that you have the option to flash more zips if you wish to.
I'd recommend you reflash SuperSU after the update.
nirfun said:
Hi,
I thought that after rooting OTA won't be available but I just got a notification about an update.
Is it safe to click "restart and install"? will it keep the device rooted?
if not, what's the easiest way to update?
Click to expand...
Click to collapse
TWRP wont flash the update... You can use Flashfire, get the latest firmware from here https://developers.google.com/android/images and flash using flashfire....
mcerk02 said:
TWRP wont flash the update... You can use Flashfire, get the latest firmware from here https://developers.google.com/android/images and flash using flashfire....
Click to expand...
Click to collapse
Should I download the OTA or full firmware?
Does it make sense the OTA is 1.1 GB?
nirfun said:
Should I download the OTA or full firmware?
Does it make sense the OTA is 1.1 GB?
Click to expand...
Click to collapse
I dont know what makes the OTA so large... I could be wrong but it is probably an OTA you would get if you were to be updating from M-N or something.... I just went right for the full firmware package, if you never used flashfire here is all the instructions https://flashfire.chainfire.eu/ but its pretty simple, click the + button at bottom right, click flash firmware package, select the files to flash and it will start doing its thing, I chose not to flash recovery when you get to that point, I was concerned it was gonna flash the stock recovery so didnt want to do that....
I flashed the OTA but now my root is gone
mcerk02 said:
TWRP wont flash the update... You can use Flashfire, get the latest firmware from here https://developers.google.com/android/images and flash using flashfire....
Click to expand...
Click to collapse
Last time I ran the update OTA, TWRP ran the update script just fine...
Hey guys! I have enrolled to beta program to get 7.1.1 so now I am on 7.1.1 October 5 patch. But I got a security update patch and I thought that I've done nothing with my root to the /system so I tried to update my phone using restart & update function in "System Update" . It brought up TWRP with some failed script. Now I'm on October 5 patch and I don't have any notification about system update and it shows that my system is up to date. How can I get and flash the November 5 security update? Please help
tauio111 said:
Last time I ran the update OTA, TWRP ran the update script just fine...
Click to expand...
Click to collapse
I heard others say this as well, I have NEVER had TWRP flash an OTA for me....
---------- Post added at 10:01 PM ---------- Previous post was at 09:55 PM ----------
Suren Manukyan said:
Hey guys! I have enrolled to beta program to get 7.1.1 so now I am on 7.1.1 October 5 patch. But I got a security update patch and I thought that I've done nothing with my root to the /system so I tried to update my phone using restart & update function in "System Update" . It brought up TWRP with some failed script. Now I'm on October 5 patch and I don't have any notification about system update and it shows that my system is up to date. How can I get and flash the November 5 security update? Please help
Click to expand...
Click to collapse
Here s the page for the 7.1.1 download, I would imagine it has the latest security update.... https://developer.android.com/preview/download.html
mcerk02 said:
I heard others say this as well, I have NEVER had TWRP flash an OTA for me....
---------- Post added at 10:01 PM ---------- Previous post was at 09:55 PM ----------
Here s the page for the 7.1.1 download, I would imagine it has the latest security update.... https://developer.android.com/preview/download.html
Click to expand...
Click to collapse
It says that flashing factory image will prevent getting future OTAs. So should I check that webpage every month to get the security updates? Os there a way to get OTAs back?
http://nexus5.wonderhowto.com/how-t...thout-losing-root-no-computer-needed-0168428/
Suren Manukyan said:
It says that flashing factory image will prevent getting future OTAs. So should I check that webpage every month to get the security updates? Os there a way to get OTAs back?
Click to expand...
Click to collapse
Not getting OTA's while rooted is nothing new.... You can check that page every now and then if you wanted to....
mcerk02 said:
Not getting OTA's while rooted is nothing new.... You can check that page every now and then if you wanted to....
Click to expand...
Click to collapse
Well actually now I got the OTA. The problem is I don't know how to flash it. Because FlashFire is not working anymore.
If you can figure out where is downloaded to I am sure flashfire will flash it, When mine was downloaded I couldn't find the file in system/cache or anywhere else so I gave up and just flashed the whole firmware package.... If you find it, let me know how it goes...
nirfun said:
Should I download the OTA or full firmware?
Does it make sense the OTA is 1.1 GB?
Click to expand...
Click to collapse
Yes it makes sense. These are not incremental OTA zips that you may be used to from previous Nexus devices.
mcerk02 said:
I dont know what makes the OTA so large... I could be wrong but it is probably an OTA you would get if you were to be updating from M-N or something....
Click to expand...
Click to collapse
This is a full OTA patch. The quick explanation is that these OTA zips will update over whatever you have installed (custom rom, stock, rooted, etc) and will patch every partition to the zips OTA level. You could be on OTA #1, 2, 6, 11 or whatever, the zip will update over each previous update.
Sent from my Nexus 5X using Tapatalk
mcerk02 said:
If you can figure out where is downloaded to I am sure flashfire will flash it, When mine was downloaded I couldn't find the file in system/cache or anywhere else so I gave up and just flashed the whole firmware package.... If you find it, let me know how it goes...
Click to expand...
Click to collapse
I think it is in data/ota_package/update.zip. I can see it with root browser but FlashFire doesn't see it.
Guys? No one knows how to update a rooted phone through OTA and without FlashFire?
Suren Manukyan said:
Guys? No one knows how to update a rooted phone through OTA and without FlashFire?
Click to expand...
Click to collapse
adb sideload an OTA image (file does not exist for 7.1.1 developer preview 2, fyi):
https://developers.google.com/android/ota
or
follow section 11 of my guide to update via fastboot:
http://forum.xda-developers.com/showthread.php?t=3206930
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
adb sideload an OTA image (file does not exist for 7.1.1 developer preview 2, fyi):
https://developers.google.com/android/ota
or
follow section 11 of my guide to update via fastboot:
http://forum.xda-developers.com/showthread.php?t=3206930
Click to expand...
Click to collapse
As I said I've found a zip called update.zip in data/ota_package. Can it be the OTA , can I try to sideload it?
Suren Manukyan said:
As I said I've found a zip called update.zip in data/ota_package. Can it be the OTA , can I try to sideload it?
Click to expand...
Click to collapse
Supposing you have no other mods installed and no other changes to /system have been made, unroot, reboot, then see if you can adb sideload that update.zip. If it fails, you have two ways on how to do so successfully and without Flashfire like you asked.
Sent from my Nexus 5X using Tapatalk
I cannot update to Oreo on my Sprint variant. I was rooted with TWRP but did the flash all back to stock. I am unrooted, stock recovery, with unlocked bootloader. I have tried through update.zip, sideload, and the normal way through the settings and they all fail. I successfully updated the normal way with the last 2 updates that were released, but no luck with this one.
Comet1966 said:
I cannot update to Oreo on my Sprint variant. I was rooted with TWRP but did the flash all back to stock. I am unrooted, stock recovery, with unlocked bootloader. I have tried through update.zip, sideload, and the normal way through the settings and they all fail. I successfully updated the normal way with the last 2 updates that were released, but no luck with this one.
Click to expand...
Click to collapse
Very weird as I was in the same predicament as you with being rooted with twrp & having to use flash all to go back to stock, but I was able to take the Oreo ota with no problems afterwards.
Sent from my Moto Z (2) using Tapatalk
piscesjoey said:
Very weird as I was in the same predicament as you with being rooted with twrp & having to use flash all to go back to stock, but I was able to take the Oreo ota with no problems afterwards.
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
It's like the system and recovery don't have access to the storage at all.
Which flash all did you use? mine updated just fine with that file doing adb sideload file/name/here when selecting the option for update via adb. How long did it take before the error. It takes awhile for the update to go through. (roughly the same time or longer than updating in android. my time was about 12mins.
Uzephi said:
Which flash all did you use? mine updated just fine with that file doing adb sideload file/name/here when selecting the option for update via adb. How long did it take before the error. It takes awhile for the update to go through. (roughly the same time or longer than updating in android. my time was about 12mins.
Click to expand...
Click to collapse
It got to 47% then started to flash and then the error that's for the sideload. As for the update.zip and applying it, it fails instantly.
I think I did this one: https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859
Comet1966 said:
It got to 47% then started to flash and then the error that's for the sideload. As for the update.zip and applying it, it fails instantly.
I think I did this one: https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859
Click to expand...
Click to collapse
So, you flashall and then it doesn't take Oreo but all others? Sounds like something is really messed up on your device then. Did you flash a modified logo bin?
Uzephi said:
So, you flashall and then it doesn't take Oreo but all others? Sounds like something is really messed up on your device then. Did you flash a modified logo bin?
Click to expand...
Click to collapse
I did the flashall and that's it. I have no idea what's up with it
Comet1966 said:
I did the flashall and that's it. I have no idea what's up with it
Click to expand...
Click to collapse
What is your current version? -11/November patch?
Uzephi said:
What is your current version? -11/November patch?
Click to expand...
Click to collapse
This
Comet1966 said:
This
Click to expand...
Click to collapse
That isn't one of the flash all's in the thread. You need to run the bat file. Depending on the one you use you should go to the August or September security patch.
Uzephi said:
That isn't one of the flash all's in the thread. You need to run the bat file. Depending on the one you use you should go to the August or September security patch.
Click to expand...
Click to collapse
I am trying that one again. Factory reset didn't help either.
I did the flashall to 122-59-8. Now I am updating to 122-59-8-6
Comet1966 said:
I did the flashall to 122-59-8. Now I am updating to 122-59-8-6
Click to expand...
Click to collapse
Which version of the bootloader? If the Oreo bootloader then perhaps this will result in an error.
If you installed Oreo Global or TMO after that, the bootloader will be upgraded to Oreo, perhaps this will lead to an error.
So I did the flashall, updated all the way through and it worked. It was the same flash all I did before because I already had it downloaded. Thanks for helping, sucks I had to wipe, but it is what it is.
Comet1966 said:
So I did the flashall, updated all the way through and it worked. It was the same flash all I did before because I already had it downloaded. Thanks for helping, sucks I had to wipe, but it is what it is.
Click to expand...
Click to collapse
Wow, must've been some kind of bad flash previously? Either way glad that you've finally joined the rest of us!
Sent from my Moto Z (2) using Tapatalk
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.
Hey everyone, I have a pixel 2XL rooted with stock recovery (and stock firmware).
I was wondering if I can get OTA updates ? I thought I could receive them and install them (and then re-root of course), but I still haven't received the March OTA yet.
Thanks!
youssefkr said:
Hey everyone, I have a pixel 2XL rooted with stock recovery (and stock firmware).
I was wondering if I can get OTA updates ? I thought I could receive them and install them (and then re-root of course), but I still haven't received the March OTA yet.
Thanks!
Click to expand...
Click to collapse
You'll likely get the notification, and it might even download, however, it won't install. But no biggie, you can either fastboot the monthly updates, or flash the OTA zip in twrp. Either way, you'll still have root it again :good:
Badger50 said:
You'll likely get the notification, and it might even download, however, it won't install. But no biggie, you can either fastboot the monthly updates, or flash the OTA zip in twrp. Either way, you'll still have root it again :good:
Click to expand...
Click to collapse
Thanks, but I thought the whole point of keeping the stock recovery is that I could install OTA directly ?
In that case I should probably flash TWRP.
youssefkr said:
Thanks, but I thought the whole point of keeping the stock recovery is that I could install OTA directly ?
In that case I should probably flash TWRP.
Click to expand...
Click to collapse
Stock recovery yes, however, root is the ota killer as well :good:
There was a moment that flashing twrp would brick the phone and that they made it where you couldn't flash twrp anymore
Looks like they found a work around
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
Sent from my Pixel 2 XL using Tapatalk
Downloaded the October patches and now phone has been for 1h on spinning wheel with status "preparing system update"
I am new to stock ROM after years of custom ROMs that would update at least monthly. Now on Android 10 on my pixel 2 xl should I expect OTA updates automatically? I tried to update ROM in the settings menu and it still says I have the latest update but it is September not October. Do I have to reload the factory image? I'd much rather flash an update wIth TWRP or the phone to do it automatically. It is the only reason I chose to use the stock ROM rather than Lineage or something else that updates.
Anyone with the same problem or a solution?
Problem yes - Solution no. Worked the last few months without a problem but this month I cant update. Seems they screwed it up somehow.
Same here cannot update
You both mean that you don't find the update or that it downloads and then you get stuck on preparing system update?
My friend here managed to update...
thegios said:
Downloaded the October patches and now phone has been for 1h on spinning wheel with status "preparing system update"
Click to expand...
Click to collapse
almahix said:
I am new to stock ROM after years of custom ROMs that would update at least monthly. Now on Android 10 on my pixel 2 xl should I expect OTA updates automatically? I tried to update ROM in the settings menu and it still says I have the latest update but it is September not October. Do I have to reload the factory image? I'd much rather flash an update wIth TWRP or the phone to do it automatically. It is the only reason I chose to use the stock ROM rather than Lineage or something else that updates.
Click to expand...
Click to collapse
thegios said:
Anyone with the same problem or a solution?
Click to expand...
Click to collapse
D-m-x said:
Problem yes - Solution no. Worked the last few months without a problem but this month I cant update. Seems they screwed it up somehow.
Click to expand...
Click to collapse
humdrum2009 said:
Same here cannot update
Click to expand...
Click to collapse
Are all of you updating via OTA or factory image?
OTA
thegios said:
OTA
Click to expand...
Click to collapse
Then your full stock, bootloader locked I assume. Does side loading the OTA work?
Badger50 said:
Then your full stock, bootloader locked I assume. Does side loading the OTA work?
Click to expand...
Click to collapse
Full stock and locked bootloader.
How do I sideload an OTA?
I used to do it from Twrp but since I have a Pixel again I'm not unlocking or rooting any longer
thegios said:
Full stock and locked bootloader.
How do I sideload an OTA?
I used to do it from Twrp but since I have a Pixel again I'm not unlocking or rooting any longer
Click to expand...
Click to collapse
You can do it from stock recovery. Full instructions can be found here :good:
https://developers.google.com/android/ota
You mean "Apply update from Sd card"?
I have downloaded the OTA zip file, put in in the root of my phone, entered recovery mode and chosen "apply update from sd card" but then no file is found
rooted
is rooted sideload possible with twrp
thegios said:
I have downloaded the OTA zip file, put in in the root of my phone, entered recovery mode and chosen "apply update from sd card" but then no file is found
Click to expand...
Click to collapse
The OTA zip file should be in your platform-tools folder if I remember correctly.