Hello xda,
Is it possible to downgrade from Android P DP5 to DP3 by just flashing the DP3 OTA image or is a full factory image required wiping all data?
Sent from my Pixel 2 XL using Tapatalk
Bromsoket said:
Hello xda,
Is it possible to downgrade from Android P DP5 to DP3 by just flashing the DP3 OTA image or is a full factory image required wiping all data?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Flash the factory image, but you shouldn't need to wipe data.
Use a text editor (I use Notepad++) to open the flash-all.bat file and remove the "-w " near the end of the script. Then it won't wipe your phone.
But to do that I need to unlock bootloader?
Then the phone will be wiped?
xunholyx said:
Flash the factory image, but you shouldn't need to wipe data.
Use a text editor (I use Notepad++) to open the flash-all.bat file and remove the "-w " near the end of the script. Then it won't wipe your phone.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
Bromsoket said:
But to do that I need to unlock bootloader?
Then the phone will be wiped?
Click to expand...
Click to collapse
Yep
Ok.
Not possible to just sideload DP3 OTA image I guess?
TonikJDK said:
Yep
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
Yeah, think I will go back to DP4 from DP5 myself, since I can't get TWRP to load temp recovery.
Bromsoket said:
Ok.
Not possible to just sideload DP3 OTA image I guess?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
You can always just relock your bootloader. It's not hard to do.
Bromsoket said:
Hello xda,
Is it possible to downgrade from Android P DP5 to DP3 by just flashing the DP3 OTA image or is a full factory image required wiping all data?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
May I ask why are you down grading?
If it's because TWRP not allowing you to boot into recovery, I found a work around for that issue.
Yes I know, done this before, I just want to avoid getting the phone wiped (Backup/restore takes ages..)
xunholyx said:
You can always just relock your bootloader. It's not hard to do.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
Sure
DP4 and 5 don't save exif data in photos taken using portrait mode and during summer I am taking loads of pictures and since the exif data is missing I can't organize them in a efficient way..
I didn't have any problem with my phone since DP3 so going back to is not really a "downgrade" for me and I don't root my phone, just stock.
3rd party camera might be a workaround but I find the stock cam better.
dallas90733 said:
May I ask why are you down grading?
If it's because TWRP not allowing you to boot into recovery, I found a work around for that issue.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
Need some help here...
Tried to downgrade from Android P DP5 to DP3 but it fails with this message:
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'vendor.sig'
archive does not contain 'system.sig'
Bootloader is unlocked and i tried many times but always fails with the same message...
(It worked before when i upgraded from 8.1 to DP2)
Any ideas?
Thanks.
Bromsoket said:
Need some help here...
Tried to downgrade from Android P DP5 to DP3 but it fails with this message:
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'vendor.sig'
archive does not contain 'system.sig'
Bootloader is unlocked and i tried many times but always fails with the same message...
(It worked before when i upgraded from 8.1 to DP2)
Any ideas?
Thanks.
Click to expand...
Click to collapse
Have you tried using Android SDK "platform tool?"
I download it, went into the platform tool folder and added the file I wanted to flash, and it ran super fast and easy without any error. I was getting multiple errors as well, when I try to use ADB.
Thanks,
Will try that, hopefully it works better.
dallas90733 said:
Have you tried using Android SDK "platform tool?"
I download it, went into the platform tool folder and added the file I wanted to flash, and it ran super fast and easy without any error. I was getting multiple errors as well, when I try to use ADB.
Click to expand...
Click to collapse
Bromsoket said:
DP4 and 5 don't save exif data in photos taken using portrait mode
Click to expand...
Click to collapse
Really? I'm not seeing that problem. All the pics I've taken since getting DP5 are still tagged with info like GPS coords, etc.
drwtsn32x said:
Really? I'm not seeing that problem. All the pics I've taken since getting DP5 are still tagged with info like GPS coords, etc.
Click to expand...
Click to collapse
Photos taken using portrait mode?
Normal mode is working, the problem is in
portrait mode.
Sent from my Pixel 2 XL using Tapatalk
Bromsoket said:
Photos taken using portrait mode?
Normal mode is working, the problem is in
portrait mode
Click to expand...
Click to collapse
Yep. Works in either orientation for me.
Ok.
Did you update to DP5 OTA or clean flash?
Thinking about trying a clean DP5 install.
Sent from my Pixel 2 XL using Tapatalk
It's not the orientation that's the issue. It's the Portrait Mode (Bokeh Effect). For me, sometimes EXIF information is there and sometimes it's not.
drwtsn32x said:
Yep. Works in either orientation for me.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
drwtsn32x said:
Yep. Works in either orientation for me.
Click to expand...
Click to collapse
Portrait mode as in the camera portrait mode (bokeh effect), not as in portrait orientation.
uicnren said:
Portrait mode as in the camera portrait mode (bokeh effect), not as in portrait orientation.
Click to expand...
Click to collapse
Oh, I see what you mean now. Yes confirmed - that mode doesn't store GPS coords.
Related
Mods please close.
Thank you soooooo much! The lack of a custom recovery and root has been killing me. This will definitely help tide me over until then. Inversion ui is the best, too.
Absolutely ^, thanks for throwing this together
any updates to this or will this vendor img work for the newest ota?
ZiggSVO said:
any updates to this or will this vendor img work for the newest ota?
Click to expand...
Click to collapse
Didn't really expect people to be using this at this point.
But when I get a chance I'll happily update this for the latest OTA
Sent from my iPhone using Tapatalk
ZiggSVO said:
any updates to this or will this vendor img work for the newest ota?
Click to expand...
Click to collapse
You can root your Pixel C now. There is no need to use this anymore. Just root and then install Layers Manager + Inversion UI.
oRAirwolf said:
You can root your Pixel C now. There is no need to use this anymore. Just root and then install Layers Manager + Inversion UI.
Click to expand...
Click to collapse
Layers no longer working, even with Root. I like this vendor.img.
Sent from my Pixel C using Tapatalk
---------- Post added at 07:21 PM ---------- Previous post was at 07:18 PM ----------
superchilpil said:
Didn't really expect people to be using this at this point.
But when I get a chance I'll happily update this for the latest OTA
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
For some reason I can't get layers working on Android N Preview 5. They did work on previews 2-4.
I therefore dl and flashed the Vendor.img file. Looks real nice, even on Preview 5. If you can update it or customize the Vendor.img so that other layers can be used, it would be nice. Thanks in advance.
Sent from my Pixel C using Tapatalk
Well the point of this was since root was a bit wonky at first I threw this together because I had root working on mine.
All I did was installed layers and pulled the vendor image.
Probably not what you want to hear but if you roll back to preview 4 then install layers and update everything but your vendor image you can keep layers.
I just don't have the time anymore.
Sent from my Nexus 6P using Tapatalk
superchilpil said:
Well the point of this was since root was a bit wonky at first I threw this together because I had root working on mine.
All I did was installed layers and pulled the vendor image.
Probably not what you want to hear but if you roll back to preview 4 then install layers and update everything but your vendor image you can keep layers.
I just don't have the time anymore.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No, that's good advice, but instead I can flash the vendor image from my Preview 4 Nandroid. Do you have any idea why layers is not working on DP5? I couldn't restore my layers backup and could not even create a file called "Overlays" in the System/Vendor even though I had root explorer set to R/W.
I did what you suggested, but got the exact same Google System error message when booting up that I got with your Vendor.img file. Google was not fooled by the Vendor.img from DP4. The vendor image works fine and I can flash whatever layers that work with N. Only thing I had an issue with was that in the Settings/About tablet a small window opens up and then when I press Check for Updates it crashes. I think that it is because of Inversions.UI or because I have a DP4 System Image and I'm checking for updates to DP5.
Got rid of the error message by copying the Build.prop from the Vendor.image file in DP5 and pasting it back into the DP4 Build.prop. No more Google warning! However, Settings/About tablet/Check System Updates still crashes.
Haven't' figured that one out yet.
Thanks,
Sent from my Pixel C using Tapatalk
Alxoom33 said:
No, that's good advice, but instead I can flash the vendor image from my Preview 4 Nandroid. Do you have any idea why layers is not working on DP5? I couldn't restore my layers backup and could not even create a file called "Overlays" in the System/Vendor even though I had root explorer set to R/W.
I did what you suggested, but got the exact same Google System error message when booting up that I got with your Vendor.img file. Google was not fooled by the Vendor.img from DP4. The vendor image works fine and I can flash whatever layers that work with N. Only thing I had an issue with was that in the Settings/About tablet a small window opens up and then when I press Check for Updates it crashes. I think that it is because of Inversions.UI or because I have a DP4 System Image and I'm checking for updates to DP5.
Got rid of the error message by copying the Build.prop from the Vendor.image file in DP5 and pasting it back into the DP4 Build.prop. No more Google warning! However, Settings/About tablet/Check System Updates still crashes.
Haven't' figured that one out yet.
Thanks,
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
Found out it seems to be a problem with the Inversion UI layers themselves. At some point I may have to use another dark theme like Timberwolve.
Sent from my Pixel C using Tapatalk
Hey guys, I wiped my device and re-rooted/re-flashed TWRP 2.8.7.0 and everything works fine except for the camera. Everytime I flash TWRP or root, I'll press on the camera icon and it'll open, but it just leaves me with the view finder and the little camera icon in the middle of a black screen. Does anyone have any idea what this is? I flashed SuperSU 2.52. I did not use systemless root, just the traditional.
That typically happens when the vendor image doesn't match the rest of the other images. There are flashable vendor images around. I'm too lazy to search for you though. Good luck.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
That typically happens when the vendor image doesn't match the rest of the other images. There are flashable vendor images around. I'm too lazy to search for you though. Good luck.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Yeah I figured it out a few hours ago actually, I downloaded 2 different nexus factory images for the 5x and accidentally mixed them up. Camera works fine now, thanks sir!
PiousInquisitor said:
That typically happens when the vendor image doesn't match the rest of the other images. There are flashable vendor images around. I'm too lazy to search for you though. Good luck.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
donsent work for me.
trying with the 6.0.1 (MMB29P).
camera not working. with supersu v2.46 and v2.52.
and with or without xposed-v79-sdk23-arm64.
gamerstar said:
donsent work for me.
trying with the 6.0.1 (MMB29P).
camera not working. with supersu v2.46 and v2.52.
and with or without xposed-v79-sdk23-arm64.
Click to expand...
Click to collapse
What doesnt work? Does the camera not open? Does it open but show the camera icon in the viewfinder area?
Did you flash any stock images at all? Are you sure you flashed the correct vendor image? Where did you get the vendor image?
Why are you using those ancient supersu zips? The latest is 2.67 I think.
Moar info pls.
So I bought my Google Pixel XL few days ago from eBay. The phone was used by the seller only for few days. Everything works fine except for the system update.
I'm actually able to download the 2017-03 security patch, but once the installation starts it fails in step 1 and I get the error message in the screenshot.
Did anybody experience a similar problem? Do you think I must return the phone?
Only reason I can think of that will bork an update is if one or more of the core apps are deleted or frozen. You verified you're all stock correct?
Sent from my Pixel XL using Tapatalk
tatootie67 said:
Only reason I can think of that will bork an update is if one or more of the core apps are deleted or frozen. You verified you're all stock correct?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
How can I do that ?
I checked that the phone is not rooted and I did a hard reset.
Elixir_ said:
How can I do that ?
I checked that the phone is not rooted and I did a hard reset.
Click to expand...
Click to collapse
The seller may have had it rooted. And he didn't install factory firmware, before he sold it to u. Maybe he did an unroot root in SuperSU and that is not a sure thing. Just a guess. I would go to Google site and fastboot newest factory image.
Edit. Is the bootloader unlocked?
Check in your about phone section and see what version, kernel, and baseband your on. Or screenshot it and post it here
Sent from my Pixel XL using Tapatalk
mac796 said:
The seller may have had it rooted. And he didn't install factory firmware, before he sold it to u. Maybe he did an unroot root in SuperSU and that is not a sure thing. Just a guess. I would go to Google site and fastboot newest factory image.
Edit. Is the bootloader unlocked?
Click to expand...
Click to collapse
This is what I get when I boot into bootloader
tatootie67 said:
Check in your about phone section and see what version, kernel, and baseband your on. Or screenshot it and post it here
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Here is a screenshot
Elixir_ said:
This is what I get when I boot into bootloader
Click to expand...
Click to collapse
Is it a Google version if it is I would unlock it and flash the new factory image. If it's not I would prob try to get money back. I'm not sure if you can flash factory image with locked bootloader. I think you can go ahead but not backwards. You will have to make sure.
You can use adb to sideload the signed ota zip in stock recovery with a locked bl.
You shouldn't have to do any of that if it's stock unrooted. But unfortunately, you don't know what the previous owner may have done.
Adb sideload might be your only choice to truly get back to stock.
Sent from my Pixel XL using Tapatalk
toknitup420 said:
You can use adb to sideload the signed ota zip in stock recovery with a locked bl.
Click to expand...
Click to collapse
I think this is the best place to start. Here are some directions for the OP.
Get the fastboot adb tools from google. Unzip them onto your computer's desktop.
https://developer.android.com/studio/releases/platform-tools.html
Then get the full ota zip and follow the directions on this page.
https://developers.google.com/android/ota
Keep us posted, we will help you.
TonikJDK said:
I think this is the best place to start. Here are some directions for the OP.
Get the fastboot adb tools from google. Unzip them onto your computer's desktop.
https://developer.android.com/studio/releases/platform-tools.html
Then get the full ota zip and follow the directions on this page.
https://developers.google.com/android/ota
Keep us posted, we will help you.
Click to expand...
Click to collapse
Which OTA should I download ? Sorry for my ignorance, it's my first Google/stock android phone...
Elixir_ said:
Which OTA should I download ? Sorry for my ignorance, it's my first Google/stock android phone...
Click to expand...
Click to collapse
XL right? Under the Marlin for XLsection the last one if your carrier is Rogers. Second to the last for anything else.
Elixir_ said:
Which OTA should I download ? Sorry for my ignorance, it's my first Google/stock android phone...
Click to expand...
Click to collapse
You should use the full flashable image and not the OTA to return to stock from this page:
https://developers.google.com/android/images
Using the specific image 7.1.1, second from bottom of Pixel XL seection.
Ok thanks a lot guys, I'll flash it once I get home.
Just to be sure, this won't void the warranty right ? because I checked with Google and the phone is still under warranty.
Elixir_ said:
Ok thanks a lot guys, I'll flash it once I get home.
Just to be sure, this won't void the warranty right ? because I checked with Google and the phone is still under warranty.
Click to expand...
Click to collapse
No it won't void the warranty.
IIIIkoolaidIIII said:
You should use the full flashable image and not the OTA to return to stock from this page:
https://developers.google.com/android/images
Using the specific image 7.1.1, second from bottom of Pixel XL seection.
Click to expand...
Click to collapse
He can't his bootloader is locked. No flashing images
toknitup420 said:
He can't his bootloader is locked. No flashing images
Click to expand...
Click to collapse
you can flash official signed images with locked bootloader, you just can't flash anything non official.
I did ti on my own only 2 weeks ago when messed up sometyhing with beta builds.
IIIIkoolaidIIII said:
you can flash official signed images with locked bootloader, you just can't flash anything non official.
I did ti on my own only 2 weeks ago when messed up sometyhing with beta builds.
Click to expand...
Click to collapse
So you ran the flash all on a locked bootloader?
toknitup420 said:
So you ran the flash all on a locked bootloader?
Click to expand...
Click to collapse
yes as i have many times before
Sent from my Pixel XL using XDA Labs
As title says you can now get the latest 7.1.2 images and OTA updates from the android developer site:
https://developers.google.com/android/ota
https://developers.google.com/android/images
update:
There is a bug with latest version of adb, so need to roll back to version 25.0.3, see here:
https://code.google.com/p/android/i... Priority Owner Summary Stars Reporter Opened
Won't let me install, am on 7.1.2 beta..
Sent from my Pixel XL using XDA-Developers Legacy app
Anyone know which OTA build is for the Verizon Pixel XL OTA? There are two different builds listed. Thanks.
tinpaul said:
Won't let me install, am on 7.1.2 beta..
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
Any luck?
Sent from my Pixel XL using Tapatalk
tinpaul said:
Won't let me install, am on 7.1.2 beta..
Click to expand...
Click to collapse
Are you unlocked? If so flash the whole image, but remove the -w from the flashall bat file to save your data.
TonikJDK said:
Are you unlocked? If so flash the whole image, but remove the -w from the flashall bat file to save your data.
Click to expand...
Click to collapse
You don't need to be unlocked for the OTA
Sent from my Pixel XL using Tapatalk
smallsmx301 said:
You don't need to be unlocked for the OTA
Click to expand...
Click to collapse
The OTA is failing for him, unless i read it wrong.
TonikJDK said:
The OTA is failing for him, unless i read it wrong.
Click to expand...
Click to collapse
Nope your reading right. I just didn't put it all together. I'm a little slow today
Sent from my Pixel XL using Tapatalk
Only thing I can do is unroll from the beta and wait for the 7.1.1 it's and install 7.1.2
Sent from my Pixel XL using XDA-Developers Legacy app
There is a bug with the latest adb (version 25.0.4) that means it can't deal with larger files (link bellow), you need to roll back to 25.0.3 version of adb. Once you do you can sideload it no problems, command:
adb sideload (name of your file)
https://code.google.com/p/android/i... Priority Owner Summary Stars Reporter Opened
Trooper27 said:
Anyone know which OTA build is for the Verizon Pixel XL OTA? There are two different builds listed. Thanks.
Click to expand...
Click to collapse
Flash E
Seems that ADB is broken. If you install the previous version it will sideload
Sent from my Pixel XL using Tapatalk
tinpaul said:
Only thing I can do is unroll from the beta and wait for the 7.1.1 it's and install 7.1.2
Click to expand...
Click to collapse
I would hold tight for a day or two. If you are on a different version there will be an OTA just for beta.
What version are you on now? Maybe the last beta update got you to where the rest of us are today.
Ok so i just tried to install the official OTA update on my pixel xl, the one google rolled out on my phone, and after downloading the file when it gets to step 1 of 2 it says
Coudn't Install
Installation failed
Im worried because my phone is rooted but i have done a systemless root so i could still get OTA updates. Does anybody know if this is an issue or will it be ok if i wait a couple days and then install it??
Sarim26 said:
Ok so i just tried to install the official OTA update on my pixel xl, the one google rolled out on my phone, and after downloading the file when it gets to step 1 of 2 it says
Coudn't Install
Installation failed
Im worried because my phone is rooted but i have done a systemless root so i could still get OTA updates. Does anybody know if this is an issue or will it be ok if i wait a couple days and then install it??
Click to expand...
Click to collapse
If it failed today it will fail in two days too. Something you did is making it fail. No big deal.
CZEddie has a guide here on how to sideload it with ADB. Below is how i do it each month.
Third post in the thread below. Just get the 7.1.2 full image instead of the 7.1.1 I mention in that post.
Pay attention to removing the -w from the flashall bat file. That is the key to saving your data.
And second to the last post in the thread are the instructions for getting root back.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
Is anyone having trouble flashing Supersu and getting it to work after installing the OTA? I've flashed and it won't stick. App shows but says it can't install binaries.
john7760 said:
Is anyone having trouble flashing Supersu and getting it to work after installing the OTA? I've flashed and it won't stick. App shows but says it can't install binaries.
Click to expand...
Click to collapse
What version of SU did you flash?
TonikJDK said:
What version of SU did you flash?
Click to expand...
Click to collapse
2.79 sr3
john7760 said:
2.79 sr3
Click to expand...
Click to collapse
Odd, I got nothing.
TonikJDK said:
Odd, I got nothing.
Click to expand...
Click to collapse
Redownloaded and works fine. Bad DL I suppose
I have fallen victim to the ram dump and have seen many other people encounter this issue when going from O to 7.1.2
Is it because we are flashing the new bootloader? Is it better to just unenroll and take the OTA. Or is it better to flash an older firmware(Pre May) ?
Sent from my Pixel XL using XDA-Developers Legacy app
yankeesfan714 said:
I have fallen victim to the ram dump and have seen many other people encounter this issue when going from O to 7.1.2
Is it because we are flashing the new bootloader? Is it better to just unenroll and take the OTA. Or is it better to flash an older firmware(Pre May) ?
Click to expand...
Click to collapse
You have to completely remove O from both slots. You have to flash 7.12 factory images to both slots with the - w left in the update. You will loose all data
After I flash the first slot how do I switch to the 2nd?
Sent from my Pixel XL using XDA-Developers Legacy app
Golf c said:
You have to completely remove O from both slots. You have to flash 7.12 factory images to both slots with the - w left in the update. You will loose all data
Click to expand...
Click to collapse
I have flashed both slots and can boot 7.1.2 and way back, but cannot flash TWRP and keep it. Device boot loops every time. I have to boot TWRP each time I want to do anything recovery wise.
yankeesfan714 said:
After I flash the first slot how do I switch to the 2nd?
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
Run the flash-all.bat on whichever slot you're on first then boot back into bootloader and enter in adb:
Code:
fastboot --set-active=a
but change active to either a or b for whichever you haven't flashed to.
TheBobMiller said:
Run the flash-all.bat on whichever slot you're on first then boot back into bootloader and enter in adb:
Code:
fastboot --set-active=a
but change active to either a or b for whichever you haven't flashed to.
Click to expand...
Click to collapse
Now, is this all post May bootloader? Do I have to do this if flashing say April? Or is it purely a Beta back to 7.1.2 issue?
Sent from my Pixel XL using XDA-Developers Legacy app
yankeesfan714 said:
Now, is this all post May bootloader? Do I have to do this if flashing say April? Or is it purely a Beta back to 7.1.2 issue?
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
If i'm not mistaken its Beta back to any version. I'm currently on the May bootloader but I flashed April before I went to May.
TheBobMiller said:
If i'm not mistaken its Beta back to any version. I'm currently on the May bootloader but I flashed April before I went to May.
Click to expand...
Click to collapse
I made Google aware of my last go round from O to May that resulted in a ram dump and my PC not recognizing my device in fastboot. They said to un enroll and take the OTA with no fear. If I see the ram dump which I shouldn't, but if I see it to let it complete. Do not abort. Maybe I just stay on O until the official is released in the fall.
Sent from my Pixel XL using XDA-Developers Legacy app
yankeesfan714 said:
I made Google aware of my last go round from O to May that resulted in a ram dump and my PC not recognizing my device in fastboot. They said to un enroll and take the OTA with no fear. If I see the ram dump which I shouldn't, but if I see it to let it complete. Do not abort. Maybe I just stay on O until the official is released in the fall.
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
Whatever you prefer! I'm too much of a flashaholic to stay on the Beta, plus it was too glitchy for my daily driver. Hope all works well for you!