is there anyway to Sideload Android P Preview on a lock Verizon Pixel 2 Xl ? I can get it to work getting errors like E:footer is wrong e:error 21 E:signatire verification failed
Thanks
https://developer.android.com/preview/download.html
Go to your recovery and flash it through adb sideload
I tried to flash it the ADB Sideload update.zip and it get to 0% and fails
You may have to enroll in Beta first in order for P to work.
There is no Beta Yet For Android P
Badwished said:
There is no Beta Yet For Android P
Click to expand...
Click to collapse
After doing some research, you have to be bootloader unlocked to flash the Android P firmware.
This is a developer preview. Next version will be Beta and then there will be an ota method.
update your adb and fastboot.
and get the OTA from here: https://developer.android.com/preview/download-ota.html
Remember if you go P on Verizon you can't go back because of the locked bootloader.
Is this still accurate? To sideload the OTA preview , any downside other than the locked bootloader?
bond32 said:
Is this still accurate? To sideload the OTA preview , any downside other than the locked bootloader?
Click to expand...
Click to collapse
You can flash the factory images through adb to go back to 8.1. I was on P and went back
franchise said:
You can flash the factory images through adb to go back to 8.1. I was on P and went back
Click to expand...
Click to collapse
Thanks! You got the OTA from here right?
https://developer.android.com/preview/download-ota
Why did you go back to O?
bond32 said:
Thanks! You got the OTA from here right?
https://developer.android.com/preview/download-ota
Click to expand...
Click to collapse
I bought my device from someone locally and it already had Android P on it. I just flashed the 8.1 images to go back. But that is the site to get the Image
franchise said:
I bought my device from someone locally and it already had Android P on it. I just flashed the 8.1 images to go back. But that is the site to get the Image
Click to expand...
Click to collapse
Followed the correct procedure I think, no go. I think maybe it's because my pixel XL 2 is already on the latest Verizon OTA which is April security patch...
bond32 said:
Followed the correct procedure I think, no go. I think maybe it's because my pixel XL 2 is already on the latest Verizon OTA which is April security patch...
Click to expand...
Click to collapse
Sorry to hear that. I may try it tomorrow to see if it works for me.
bond32 said:
Followed the correct procedure I think, no go. I think maybe it's because my pixel XL 2 is already on the latest Verizon OTA which is April security patch...
Click to expand...
Click to collapse
Yep, P is technically older than what you have so it won't OTA. A new P is due any day now.
//
Related
I've got the OTA update waiting for me to select to get the November update but I don't want to risk losing the ability to unlock to bootloader if I ever want to in the future because I'm not sure of the bootloader unlockability for Bell bought devices. So if I unlock the bootloader do I lose anything, can I still get and take OTA updates from Google in the future?
You're phone will do a factory reset when unlocking the bootloader, so you'd want to back everything up. You can also still update with an unlocked bootloader.
Sent from my Pixel XL using Tapatalk
gonzo237 said:
You're phone will do a factory reset when unlocking the bootloader, so you'd want to back everything up. You can also still update with an unlocked bootloader.
Click to expand...
Click to collapse
But will you still be able to re root after the update is installed....Verizon?
canemaxx said:
But will you still be able to re root after the update is installed....Verizon?
Click to expand...
Click to collapse
Yes
cwalker0906 said:
Yes
Click to expand...
Click to collapse
I do have to unroot to update though correct? Sorry I been out of the game for a while. If I do a full unroot via SuperSU I will have to push SuperSU back to my phone after right?
canemaxx said:
I do have to unroot to update though correct? Sorry I been out of the game for a while. If I do a full unroot via SuperSU I will have to push SuperSU back to my phone after right?
Click to expand...
Click to collapse
No you can go to stock recovery and from your computer sideload the factory ota image of the updated software, its on the google dev site at the link below just go to the pixel xl section and the updates ota images are there.
https://developers.google.com/android/ota
M9guy said:
No you can go to stock recovery and from your computer sideload the factory ota image of the updated software, its on the google dev site at the link below just go to the pixel xl section and the updates ota images are there.
https://developers.google.com/android/ota
Click to expand...
Click to collapse
First time side loading. Does side loading the newest stock image wipe everything? Or upgrade over it.
tommyntpham said:
First time side loading. Does side loading the newest stock image wipe everything? Or upgrade over it.
Click to expand...
Click to collapse
Sideloaded last night. Didn't wipe anything. Will lose root but rooted phone right after update completed with no issues.
Should I install the image for Verizon or would it be more safe to use one of the other images?
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
I am on 8.1 DP2 which is OPP6.171019.012, tried to install the official 8.1 OTA which is OPM1.171019.011 : obviously the latter is older that DP2, so now I am still on DP2.
Maybe I need to wait for the OTA for those that are on beta program?
Yes, you'll either have to wait for the official OTA for beta users or use the factory images to my knowledge. You can use the factory images and just remove the wipe command ( -w ) from the flashall.bat file to keep your data
skw5115 said:
Yes, you'll either have to wait for the official OTA for beta users or use the factory images to my knowledge. You can use the factory images and just remove the wipe command ( -w ) from the flashall.bat file to keep your data
Click to expand...
Click to collapse
I can confirm this, I have updated this way.
anyone has the OTA for those on DP2?
Curiosity, how can the final version be older than a beta? I've seen this posted a few times now, how can/does this happen?
But after flashing the final, we're still enrolled to the beta. How to cancel the enroll without erase data ?
Mikulec said:
I can confirm this, I have updated this way.
Click to expand...
Click to collapse
I'm assuming you already had an unlocked bootloader?
Mr Patchy Patch said:
Curiosity, how can the final version be older than a beta? I've seen this posted a few times now, how can/does this happen?
Click to expand...
Click to collapse
It isn't, but they probably put an unreasonable date stamp in on purpose to avoid any potential issues in the flashing process.
Sent from my Pixel 2 XL using Tapatalk
oxman said:
But after flashing the final, we're still enrolled to the beta. How to cancel the enroll without erase data ?
Click to expand...
Click to collapse
go to the website and unenroll.
imnuts said:
It isn't, but they probably put an unreasonable date stamp in on purpose to avoid any potential issues in the flashing process.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
So those on DP2 with unlocked bootloader when/how will be able to update to official/final 8.1?
Usually an OTA is made to go from one specific build to another. Which would make sense on why you can't do it that way. If you have the unlocked bootloader flashing the factory image for 8.1 can be done.
thegios said:
So those on DP2 with unlocked bootloader when/how will be able to update to official/final 8.1?
Click to expand...
Click to collapse
If you have an unlocked bootloader, you can update now with the factory image. Otherwise wait until the OTA rolls or for beta users.
Sent from my Pixel 2 XL using Tapatalk
I just got the small ota to bump me from DP2 to final. So it's in the wild now. You can probably force the update at this point.
Like he said, I just got the official OTA bump yesterday to final. If you can't force it, it should come soon regardless.. This shows the December 5th patch.
hrkahn said:
I'm assuming you already had an unlocked bootloader?
Click to expand...
Click to collapse
yes
I have same problem with Nexus 5X.
Adb sideload breaks at 47%.
Now i can only wait, because i have the no-rpmb-bug.
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
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.