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
Related
It's the second time that this problem confronts me.
The OTA update process keeps complaining '/system/bin/debuggerd' with unexpected contents. Last time I have no idea so I flash the whole stock image. This time I found out that it's stickmount who modified the file: http://forum.xda-developers.com/showthread.php?t=2062768
So, I managed to get three versions of debuggerd (JSS15R, KRT16O, KRT16S) for whose who need it.
See the attachment
p.s. added the new debuggerd from KOT49H after the OTA update.
felix021 said:
It's the second time that this problem confronts me.
The OTA update process keeps complaining '/system/bin/debuggerd' with unexpected contents. Last time I have no idea so I flash the whole stock image. This time I found out that it's stickmount who modified the file: http://forum.xda-developers.com/showthread.php?t=2062768
So, I managed to get three versions of debuggerd (JSS15R, KRT16O, KRT16S) for whose who need it.
See the attachment
p.s. added the new debuggerd from KOT49H after the OTA update.
Click to expand...
Click to collapse
So do you just flash this zip then?
goody2shoes said:
So do you just flash this zip then?
Click to expand...
Click to collapse
no, you get it wrong. I just packed different versions of debuggerd for update (this forum won't allow updated files with no extension). Just unpack the zip, choose the desired version and copy it to /system/bin.
thanks very useful i always seem to get this issue with stickmount....time to stop using it...
Can someone please post original debuggerd for KTU84L
Thanks
Stickmount makes a backup of debuggerd, it renames it debuggerd.backup, it's in the same directory as the one it replaced it with.
mdamaged said:
Stickmount makes a backup of debuggerd, it renames it debuggerd.backup, it's in the same directory as the one it replaced it with.
Click to expand...
Click to collapse
I tried that one and it didn't work. Same error message. If anyone has the 4.4.3 debuggerd, that'd be great. I tried using one from my Moto x on 4.4.3 and that didn't work either.
biggiestuff said:
I tried that one and it didn't work. Same error message. If anyone has the 4.4.3 debuggerd, that'd be great. I tried using one from my Moto x on 4.4.3 and that didn't work either.
Click to expand...
Click to collapse
Flash stock 4.4.3 system.img.
ahwebd said:
Can someone please post original debuggerd for KTU84L
Thanks
Click to expand...
Click to collapse
I need that file too please. I tried the backup file created by stickmount but somehow it doesn't work also, so please could someone upload that original debuggerd from 4.4.3
Thanks a lot
Sent from my Nexus 7 using Tapatalk 2
mdamaged said:
Flash stock 4.4.3 system.img.
Click to expand...
Click to collapse
Thanks! That definitely got me to the next step.
I fastboot flashed the system.img from 4.4.3 download from the google android site.
biggiestuff said:
Thanks! That definitely got me to the next step.
I fastboot flashed the system.img from 4.4.3 download from the google android site.
Click to expand...
Click to collapse
Could you please post the original debuggerd from the system.img here? I don't have access to a computer at the moment.
Thank you very much
Sent from my Nexus 7 using Tapatalk 2
itenos said:
Could you please post the original debuggerd from the system.img here? I don't have access to a computer at the moment.
Thank you very much
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
here it is
eli_1234 said:
here it is
Click to expand...
Click to collapse
Thank you so much but this file doesn't work either. Did you have by chance stickmount installed during the update? In that case the file gets modified during the first boot and therefore doesn't work anymore
Sent from my Nexus 7 using Tapatalk 2
felix021 said:
It's the second time that this problem confronts me.
The OTA update process keeps complaining '/system/bin/debuggerd' with unexpected contents. Last time I have no idea so I flash the whole stock image. This time I found out that it's stickmount who modified the file: http://forum.xda-developers.com/showthread.php?t=2062768
So, I managed to get three versions of debuggerd (JSS15R, KRT16O, KRT16S) for whose who need it.
See the attachment
p.s. added the new debuggerd from KOT49H after the OTA update.
Click to expand...
Click to collapse
:good: Thx - same problem -> Nexus 7 (2012) -> great help to fix my OTA problem (found system/bin/debuggerd_bak -> rename -> OK)
now I have to fix the next one -> Franco Kernel rename system file to -> /system/vendor/lib/hw/power.grouper.so.fkbak
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.
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
as per the title... I've flashed roms on the may bootloader plenty of times, but I have yet to find a method where I am able to do it without plugging a computer at some point during the flashing process ... what I usually do is as follows:
boot to recovery > wipe data/cache > flash rom > flash twrp (attempting to flash verified bootsigner at this point, it usually tells me that the boot image is already signed and whether I abort or sign anyway then rebooting to recovery seems to fail and I get a ram dump, so instead...) > ...reboot to bootloader > fastboot boot twrp > flash verified bootsigner > reboot to recovery > flash gapps, etc. > reboot system > profit
dirty flashing is easier because verified bootsigner works the first time. so the issue remains , has anyone found a way to Clean flash a rom explicitly through recovery?
Everytime you install a room you have to install the TWRP zip after and bootsigner ETC
Sent from my LG-LS997 using Tapatalk
bennyboy2120 said:
Everytime you install a room you have to install the TWRP zip after and bootsigner ETC
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
maybe you missed it
diabl0w said:
... what I usually do is as follows:
boot to recovery > wipe data/cache > flash rom > flash twrp (attempting to flash verified bootsigner at this point, it usually tells me that the boot image is already signed and whether I abort or sign anyway then rebooting to recovery seems to fail and I get a ram dump, so instead...)
Click to expand...
Click to collapse
diabl0w said:
maybe you missed it
Click to expand...
Click to collapse
My bad I missed that. Hmm. RC1 or RC2 zip for twrp?
Also. Some ROMs come with Gapps
Might be a flash over gapps issue
Sent from my Pixel XL using Tapatalk
bennyboy2120 said:
My bad I missed that. Hmm. RC1 or RC2 zip for twrp?
Also. Some ROMs come with Gapps
Might be a flash over gapps issue
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
twrp RC2 since its required for verified bootsignerv8 and magisk... I get the issue without even trying to boot into system so its not a gapps issue. beansgapps removes any preexisting gapps btw if your running into that issue
diabl0w said:
twrp RC2 since its required for verified bootsignerv8 and magisk... I get the issue without even trying to boot into system so its not a gapps issue. beansgapps removes any preexisting gapps btw if your running into that issue
Click to expand...
Click to collapse
Weird. I'm on RR rom may boot loader.
Sent from my Pixel XL using Tapatalk
---------- Post added at 07:43 PM ---------- Previous post was at 07:42 PM ----------
bennyboy2120 said:
Weird. I'm on RR rom may boot loader.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Did you go to the O beta and come back?
Sent from my Pixel XL using Tapatalk
bennyboy2120 said:
Weird. I'm on RR rom may boot loader.
Sent from my Pixel XL using Tapatalk
---------- Post added at 07:43 PM ---------- Previous post was at 07:42 PM ----------
Did you go to the O beta and come back?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
nope never had O... as I said I don't have a problem running a custom rom on may boot loader... I'm running pixel dust right now. the issue is being able to clean flash and have verfified bootsigner work. I'm questioning my methodology bcuz no one else seems to be having this issue
diabl0w said:
nope never had O... as I said I don't have a problem running a custom rom on may boot loader... I'm running pixel dust right now. the issue is being able to clean flash and have verfified bootsigner work. I'm questioning my methodology bcuz no one else seems to be having this issue
Click to expand...
Click to collapse
Hm. Weird I never had that but I root su not magisk but I doubt there is an issue with that
Sent from my Pixel XL using Tapatalk
diabl0w said:
nope never had O... as I said I don't have a problem running a custom rom on may boot loader... I'm running pixel dust right now. the issue is being able to clean flash and have verfified bootsigner work. I'm questioning my methodology bcuz no one else seems to be having this issue
Click to expand...
Click to collapse
It seems to be rom dependent. Works every time on DU and PN. Pixel dust is one that I also have trouble with. I can make it work a couple of different ways but I still need a computer to do it. Haven't tried it lately with Pixel Dust though.
Golf c said:
It seems to be rom dependent. Works every time on DU and PN. Pixel dust is one that I also have trouble with. I can make it work a couple of different ways but I still need a computer to do it. Haven't tried it lately with Pixel Dust though.
Click to expand...
Click to collapse
Aha this is probably it, I think it has to do with whether or not the system image is signed despite only rebooting into recovery it probably checks boot and system since recovery is located in boot anyway. I think an update to chainfires signer could fix this , maybe I'll post over there.
How do you like DU? Also have you tried Paranoid Android? these are the two roms I've been considering trying but don't feel like changing my stable set up just yet without a good reason
diabl0w said:
Aha this is probably it, I think it has to do with whether or not the system image is signed despite only rebooting into recovery it probably checks boot and system since recovery is located in boot anyway. I think an update to chainfires signer could fix this , maybe I'll post over there.
How do you like DU? Also have you tried Paranoid Android? these are the two roms I've been considering trying but don't feel like changing my stable set up just yet without a good reason
Click to expand...
Click to collapse
PA needs some work. Not many features. Love Pixel Dust. PN is always top notch. DU is the BEST, most stable rom for our device you can run. It's flawless. That's not something you can say for most roms out for our device. Especially LOS based roms.
Golf c said:
PA needs some work. Not many features. Love Pixel Dust. PN is always top notch. DU is the BEST, most stable rom for our device you can run. It's flawless. That's not something you can say for most roms out for our device. Especially LOS based roms.
Click to expand...
Click to collapse
Thank you, you have me pretty convinced to try out DU because you seem to be on the same thought process as me. I like to stay close to stock, despite loving custom roms, bcuz nothing has ever beat stock when it comes to reliability and set-it and forget-it, especially because I'm starting to get a little too busy to entertain any of my tech hobbies...
diabl0w said:
Thank you, you have me pretty convinced to try out DU because you seem to be on the same thought process as me. I like to stay close to stock, despite loving custom roms, bcuz nothing has ever beat stock when it comes to reliability and set-it and forget-it, especially because I'm starting to get a little too busy to entertain any of my tech hobbies...
Click to expand...
Click to collapse
My phone is also my work phone, so I need stability. My preference is
1. Stability
2. Performance
3. Battery life
4. Features I would actually use.
Gotta have Viper4a
Exclusively use LMT pie.
Don't know what Nav bars our? Lol
Love Sdcardfs kernels.
Other nice thing about DU is weeklie updates. I start to get the shakes after seven days if I don't flash something. Not a big crack flasher. Every week satisfies my addiction. Hope you like DU?
Golf c said:
My phone is also my work phone, so I need stability. My preference is
1. Stability
2. Performance
3. Battery life
4. Features I would actually use.
Gotta have Viper4a
Exclusively use LMT pie.
Don't know what Nav bars our? Lol
Love Sdcardfs kernels.
Other nice thing about DU is weeklie updates. I start to get the shakes after seven days if I don't flash something. Not a big crack flasher. Every week satisfies my addiction. Hope you like DU?
Click to expand...
Click to collapse
well that's pretty much dead on with my priorities except maybe i would add EAS/schedutil in addition to sdcardfs. does DU have its own pie implementation?
diabl0w said:
well that's pretty much dead on with my priorities except maybe i would add EAS/schedutil in addition to sdcardfs. does DU have its own pie implementation?
Click to expand...
Click to collapse
No, it does not. PA has a basic pie. I think a couple of other roms do. I recommend 2.8 LMT pie. Outstanding, been using it for years.
https://forum.xda-developers.com/showthread.php?t=1330150&p=18993800
Golf c said:
No, it does not. PA has a basic pie. I think a couple of other roms do. I recommend 2.8 LMT pie. Outstanding, been using it for years.
https://forum.xda-developers.com/showthread.php?t=1330150&p=18993800
Click to expand...
Click to collapse
thanks for your help... one last question, do you notice any impact on performance with LMT from it not being part of the system framework? it looks like an awesome app, I'm a sucker for shortcuts I use all vim keybinding programs on my desktop
diabl0w said:
thanks for your help... one last question, do you notice any impact on performance with LMT from it not being part of the system framework? it looks like an awesome app, I'm a sucker for shortcuts I use all vim keybinding programs on my desktop
Click to expand...
Click to collapse
No performance hit whatsoever. Fast as lightning. Also works on stock without root.
Golf c said:
PA needs some work. Not many features. Love Pixel Dust. PN is always top notch. DU is the BEST, most stable rom for our device you can run. It's flawless. That's not something you can say for most roms out for our device. Especially LOS based roms.
Click to expand...
Click to collapse
This may be a stupid question, but which ROM is DU?
TheBobMiller said:
This may be a stupid question, but which ROM is DU?
Click to expand...
Click to collapse
Dirty Unicorns
Golf c said:
Dirty Unicorns
Click to expand...
Click to collapse
Thanks! Now I know it was a stupid question.
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.