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
Related
So I've stayed at 2.19.40.20 because I wanted to wait to see if a better way to unlock the bootloader would be found, but I've given up and unlocked my bootloader (the unoffical way).
I want to get up to speed and update to the latest OTA.
Can I just flash the latest one or do I need to download every one til the newest update and sideload them individually?
If I have to do each one can I just load them one after the other, or do I need to reboot the phone and let it fully load to the OS for every update?
I did side load the latest one when I was coming from the 18 something that came with my phone. Loading the full 1.1gig firmware did the trick.
So just for clarification, to take me from 2.19.40.20 to 2.20.40.139 I should just flash the latest Stock ROM from the ASUS site?
DiGecko said:
I did side load the latest one when I was coming from the 18 something that came with my phone. Loading the full 1.1gig firmware did the trick.
Click to expand...
Click to collapse
Azdinflash said:
So just for clarification, to take me from 2.19.40.20 to 2.20.40.139 I should just flash the latest Stock ROM from the ASUS site?
Click to expand...
Click to collapse
Yes that should do it.
I was seriously dreading having to update, but this shows that my worries were unfounded, thanks!
I don't need to unroot as I'm flashing the whole rom, right?
The_wolf88 said:
Yes that should do it.
Click to expand...
Click to collapse
Azdinflash said:
I was seriously dreading having to update, but this shows that my worries were unfounded, thanks!
I don't need to unroot as I'm flashing the whole rom, right?
Click to expand...
Click to collapse
You need to unroot and make sure you are sideloading the whole 1.1 gig one.
DiGecko said:
You need to unroot and make sure you are sideloading the whole 1.1 gig one.
Click to expand...
Click to collapse
Does unrooting include removing Xposed?
Yes, and don't try to install it after you get to 139 firmware, as far as I know it still causes bootloop.
Wait, if I flash the 1.1 gig stock ROM, do I lose everything in the internal memory?
DiGecko said:
Yes, and don't try to install it after you get to 139 firmware, as far as I know it still causes bootloop.
Click to expand...
Click to collapse
I did a little digging, and it seems that the bootloop was fixed a few days ago:
http://forum.xda-developers.com/zenfone2/general/guide-to-install-xposed-installer-t3116476/page26
J M L said:
There's a new Xposed out, v78, which claims to fix a bootloop on 5.0 roms due to a security fix. I haven't tried it yet because I'm running a backup. Here is the thread and changelog.
We want the sdk21-x86 version.
Installed with no problem in TWRP with the flash able zip. Took a few minutes to boot, but seems to be working.
Click to expand...
Click to collapse
Good to know. No, you would not loose anything, at least I did not. Everything migrated over without any issues.
So I've gotten through sideloading the current version with no hiccups. Booted into system fine, it's the right version in the About section, and my internal memory came through intact.
I've flashed TWRP, and booted into it to install SuperSU when I got this message: "TWRP may have detected an unmodified system partition"
It explains that I can keep it as read only and make it easier to take official updates, but then TWRP will not be able to stop the stock ROM from replacing it and will not offer to root my device.
Should I keep it "Read Only" or should I allow the modification?
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
Hi,
This guide is based in my first post about how to do it with the Moto G4: http://forum.xda-developers.com/moto-g4/how-to/guide-simple-ota-update-rooted-unlocked-t3510126
(Read it for full info).
Then, here the updated info for the Moto G5+:
1) If you are in NPN25.137-33 and like to apply the last OTA, but you have rooted and/or flashed a custom recovery (TWRP) + custom kernel, then you can.
2) Requirements: original SYSTEM and BOOT partitions. If you have flashed another version, then restore the originals. You can use any backups from you, or you can download from here: http://drive.google.com/open?id=0B6-Tz_7kDyxsZnVNa0pldnhndG8
(Thank you to GtrCraft: http://forum.xda-developers.com/showpost.php?p=72387571&postcount=15)
3) To apply the OTA download this ZIP and install it from the TWRP recovery (it's not required to have the TWRP flashed, you can start it from the fastboot util): http://www.sendspace.com/file/7w75rw
This file is the original OTA (shared by the user olive23) and patched by me to remove the check for the fingerprint of the running firmware. Then it can run over the TWRP.
Warning: Don't install this OTA if you don't have the exact version of the required firmware.
4) After install the OTA, reboot and check the new version. At that point the ROM isn't rooted. Then, you need to re-root.
That's all!
Tried flashing and it fails.
You need stock recovery to flash OTA's
GtrCraft said:
You need stock recovery to flash OTA's
Click to expand...
Click to collapse
Isn't that the point of this post? He said he patched the OTA update so it could be flashed with TWRP.
3) To apply the OTA download this ZIP and install it from the TWRP recovery (it's not required to have the TWRP flashed, you can start it from the fastboot util): http://www.sendspace.com/file/7w75rw
This file is the original OTA (shared by the user olive23) and patched by me to remove the check for the fingerprint of the running firmware. Then it can run over the TWRP.
Click to expand...
Click to collapse
bvsbutthd101 said:
Isn't that the point of this post? He said he patched the OTA update so it could be flashed with TWRP.
Click to expand...
Click to collapse
Well the OTA isn't meant for reteu firmware. So that will bring problems with it
bvsbutthd101 said:
Tried flashing and it fails.
Click to expand...
Click to collapse
Because isn't for your device OR you have modified SYSTEM or BOOT.
GtrCraft said:
You need stock recovery to flash OTA's
Click to expand...
Click to collapse
FALSE!
GtrCraft said:
Well the OTA isn't meant for reteu firmware. So that will bring problems with it
Click to expand...
Click to collapse
TRUE! :silly:
manos78 said:
Because isn't for your device OR you have modified SYSTEM or BOOT.
Click to expand...
Click to collapse
Installing TWRP and rooting doesn't change the SYSTEM or BOOT right? Must just not be for my device then. I have the US 4gb model (XT1687)
bvsbutthd101 said:
Must just not be for my device then. I have the US 4gb model (XT1687)
Click to expand...
Click to collapse
Probably. This OTA is from user "olive23".
I don't have (still) received any OTA in my XT1685 (EU 3/32).
manos78 said:
Probably. This OTA is from user "olive23".
I don't have (still) received any OTA in my XT1685 (EU 3/32).
Click to expand...
Click to collapse
Here's the OTA for the US 4gb model if you're interested. :good:
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA
bvsbutthd101 said:
Installing TWRP and rooting doesn't change the SYSTEM or BOOT right? Must just not be for my device then. I have the US 4gb model (XT1687)
Click to expand...
Click to collapse
I have the same US model and this is supposed to be for it but it didn't work for me either, got errors during flash of OTA zip in TWRP that various partitions weren't accessible &/or verifiable. Even tried it a second time after a full restore to stock and had similar errors. I restored SYSTEM too (not sure that our rooting process works for systemless yet, meaning it would change SYSTEM), so that wasn't the problem in my case. Restored stock again and will wait to see if I get OTA normally.
bvsbutthd101 said:
Here's the OTA for the US 4gb model if you're interested. :good:
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA
Click to expand...
Click to collapse
So did you get this OTA normally as a system update, indicating that we should be receiving it now?
Dahenjo said:
I have the same US model and this is supposed to be for it but it didn't work for me either, got errors during flash of OTA zip in TWRP that various partitions weren't accessible &/or verifiable. Even tried it a second time after a full restore to stock and had similar errors. I restored SYSTEM too (not sure that our rooting process works for systemless yet, meaning it would change SYSTEM), so that wasn't the problem in my case. Restored stock again and will wait to see if I get OTA normally.
So did you get this OTA normally as a system update, indicating that we should be receiving it now?
Click to expand...
Click to collapse
I got the update weeks ago. I've been postponing until someone makes it's flashable. I ripped it from my phone when I got it so yes, it's from my phone.
bvsbutthd101 said:
I got the update weeks ago. I've been postponing until someone makes it's flashable. I ripped it from my phone when I got it so yes, it's from my phone.
Click to expand...
Click to collapse
Thanks. I wonder why I haven't gotten anything and had phone since it came out on 3/31. I'm on NPN25.137-33 with a 4GB XT1687 from Amazon ($299 full-price without ads) on AT&T if carrier matters. Rooted or not we should still get the notifications as you have.
Dahenjo said:
Thanks. I wonder why I haven't gotten anything and had phone since it came out on 3/31. I'm on NPN25.137-33 with a 4GB XT1687 from Amazon ($299 full-price without ads) on AT&T if carrier matters. Rooted or not we should still get the notifications as you have.
Click to expand...
Click to collapse
Yeah I got mine the day it came out from amazon, using on Verizon.
Here is a flashable stock zip based on reteu firmware:
https://drive.google.com/open?id=0B6-Tz_7kDyxsU2NlTERsSzZsalk
U have*67 files??
Same Here
US variant XT1687 4/64GB on Sprint but no OTA notification. Maybe I should just wait another week before flashing this. Not sure if there is something in the SIM the server notices and stops updates on some carriers. But maybe the SIM is how they decide, not sure what else they could go by other than IP to detect the carrier.
bvsbutthd101 said:
Yeah I got mine the day it came out from amazon, using on Verizon.
Click to expand...
Click to collapse
I also have XT1687 4/64G US on 25.137-33 + root & TWRP, and no OTA notification.
So, is there a way to go to -67 (flash over TWRP, restore back to -15 stock)?
I could not understand the right answer from all the thread on the subject.
Sorry for this noob question: I have just rooted a brand new phone. After the first login the OTA warning popped out so I downloaded it. When finished I got a loop on the recovery; I fastbooted boot and got my phone working again ... what do I have to do? Thanks.
Hi,
My upgraded guide: http://forum.xda-developers.com/g5-plus/how-to/guide-complex-ota-update-magisk-rooted-t3688175
Hi has anyone received the Oreo ota on non rooted nexus 5x and without signing up for the beta program???
ttocs99 said:
Hi has anyone received the Oreo ota on non rooted nexus 5x and without signing up for the beta program???
Click to expand...
Click to collapse
Not yet. I'm on T-mobile.
mrpink10 said:
Not yet. I'm on T-mobile.
Click to expand...
Click to collapse
Same I spoke to Google support and they claim it's Al read available via ota
Haven't got it yet I bought my phone from Google.
Sent from my Nexus 5X using Tapatalk
Are you rooted? If so just get the ota from google and flash it with flashfire
jd1639 said:
Are you rooted? If so just get the ota from google and flash it with flashfire
Click to expand...
Click to collapse
Flashfire doesn't fully support Oreo yet so that's a no go, same with TWRP. ADB sideload might work.
I just flashed it this morning and had no problems.
I flashed a couple of hours ago official OTA package via ADB. No problems till now.
I took the plunge and flashed the 8.0 stock factory image the done a factory reset after to make sure and it been great ever since turned off animation and it's nippy just wish battery was about better but I'll give it a few days see if that goes
jd1639 said:
I just flashed it this morning and had no problems.
Click to expand...
Click to collapse
Did you use Flashfire?
Does anyone know why the battery drains so fast on Oreo even after fresh clean install
Yes, Pro v0.60. I also maintained root and twrp. I had supersu 2.82-sr3 installed at the time so make sure you have that.
jd1639 said:
Yes, Pro v0.60. I also maintained root and twrp. I had supersu 2.82-sr3 installed at the time so make sure you have that.
Click to expand...
Click to collapse
Well then, I guess it's just when coming from the beta that it doesn't work. Thanks for the heads up.
ttocs99 said:
Does anyone know why the battery drains so fast on Oreo even after fresh clean install
Click to expand...
Click to collapse
Enable dev options and disable always keep mobile data on.
I just noticed that for some reason that is checked in oreo and it shouldn't be unless you are never on WIFI.
ttocs99 said:
Same I spoke to Google support and they claim it's Al read available via ota
Click to expand...
Click to collapse
It is true that the OTA is out there. I confirm it because I signed-up to beta program to get the update and two days later I opted out to see if this is the latest official OTA ROM and I didn't get the update. So if you don't want to wait you can do the same it's safe. You can check the latest OTA here: https://developers.google.com/android/ota
The version is the same I have. 8.0.0 OPR6.170623.013.
I can confirm that jd1639's method works for people rooted with TWRP.
- download OTA (https://developers.google.com/android/ota)
- run Flashfire 60.0 (free version is OK)
- when asked "A system update has been detected", cancel
- Flash ZIP or OTA
- uncheck "restore boot and recovery images"
- press "EverRoot" and select "Inject SuperSU" and "Preserve recovery"
- Flash
- wait patiently
I tried flashing the modem FW using "Flash firmware package" on the OTA zip file. It rebooted and the screen went black for many minutes. I had to hard reset.
Can anyone confirm the 8.0 baseband? I have M8994F-2.6.39.3.03. I know that's the baseband for the 8.0 developer preview, but I wanted to make sure it was the final.
Billys20 said:
It is true that the OTA is out there. I confirm it because I signed-up to beta program to get the update and two days later I opted out to see if this is the latest official OTA ROM and I didn't get the update. So if you don't want to wait you can do the same it's safe. You can check the latest OTA here: https://developers.google.com/android/ota
The version is the same I have. 8.0.0 OPR6.170623.013.
Click to expand...
Click to collapse
Probably a stupid question, but this OTA file- since it's ~1gb-, does it wipe the device like the full image?
tallgrasshawk said:
Probably a stupid question, but this OTA file- since it's ~1gb-, does it wipe the device like the full image?
Click to expand...
Click to collapse
Nope
Sent from my Nexus 5X using Tapatalk
tallgrasshawk said:
Probably a stupid question, but this OTA file- since it's ~1gb-, does it wipe the device like the full image?
Click to expand...
Click to collapse
No. There is no such problem.You can do it with any of the two ways if you didnt get the OTA until now. 1) Sign-up for the beta program install the update and then opt-out of it. 2) Flash the OTA files from Google to your phone. Or 3) But these are rumors and I can't be sure: An update will come at 11 of September with new Version of Oreo 8.0.1 with better support for Carriers (it is 8.0.0).
Billys20 said:
No. There is no such problem.You can do it with any of the two ways if you didnt get the OTA until now. 1) Sign-up for the beta program install the update and then opt-out of it. 2) Flash the OTA files from Google to your phone. Or 3) But these are rumors and I can't be sure: An update will come at 11 of September with new Version of Oreo 8.0.1 with better support for Carriers (it is 8.0.0).
Click to expand...
Click to collapse
6p here, downloaded ota (NOT factory), ran Tibu, ran Flashfire 7.0 pro as described and after three reboots and a while of booted finishing, was cleanly updated to 8.0.0. took < 20 min. [emoji2]
Sent from my Nexus 6P using Tapatalk
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