Which ota are you guys using for non-vzw models that are on the vzw network? Anyone know what the difference is exactly? I assume it has some carrier-related apps. I also assumed the vzw ota's were specifically for vzw models but I guess not.
General New report of actual Verizon OTA SD1A.210817.037.A1 on Pixel 6/Pro
- Thread starter roirraW "edor" ehT
- Start date
I'm on Ting (verizon towers) on an unlocked p6 - I just manually upgraded to the .036 firmware. Everything is working fine, but not sure what the difference would be.
I wonder if this will help with monthly auto updates for unlocked vzw customers. It's insane how big this issue is. Most unlocked phones on vzw can't auto update? This is so bad.
So it has been years time since I've played with adb and side loading.
I was curious to what I'm doing wrong here. I followed all the steps.
-I am able to boot into recovery from the adb command line.
-I check adb devices and it says sideload next to it.
But when I try to sideload the ota zip file, it just says "cannot read 'oriole-ota-sd1a.210817.036.a8-41f0de82.zip' "
Won't let me sideload the zip. Am I doing something dumb here lol?
I was curious to what I'm doing wrong here. I followed all the steps.
-I am able to boot into recovery from the adb command line.
-I check adb devices and it says sideload next to it.
But when I try to sideload the ota zip file, it just says "cannot read 'oriole-ota-sd1a.210817.036.a8-41f0de82.zip' "
Won't let me sideload the zip. Am I doing something dumb here lol?
I have had my p6p 256 unlocked on VZ network for almost 2 weeks. Still no update and I have installed a new sim card, restored to factory, and basically done all I can to get update to load with no luck. I don't want to load it manually as this could be a forever problem and it should do it itself. Sigh...
Hi. You'll likely have to give more details.
Using the newest Platform Tools from Google?
Using the newest drivers from Google?
Give an example of a command you've tried (the whole command line) including the location for where you tell it to sideload the file from.
If you are on the Pro you need 'Raven' not 'Oriole'. Looks like you downloaded the wrong OTA file.
Sure.
-I am using the latest platform tools available.
-I think I'm using the newest drivers. Not quite sure. I uninstalled and reinstalled drivers
in device manager.
-I placed the Oriole(I realize that is not for the Pro, I am on the regular 6)zip ota file in the platform tools directory.
-Debugging enabled.
-First command "adb reboot recovery"
-Power and volume up, then scroll down to "Apply update from adb"
-Ran "adb devices" to make sure it said sideload next to device name.
-Finallay "adb sideload oriole-ota-sd1a.210817.036.a8-41f0de82.zip"
Not sure if I'm doing something wrong with the file name or directory, but everything else seemed to be in order.
- The latest drivers are available here. Make sure and install/update them if necessary when you're in sideload mode.
- You have oriole-ota-sd1a.210817.036.a8-41f0de82.zip in the same folder as adb?
- You could try moving the folder that has Platform Tools and the zip file closer to the root of your file system, such as in C:\T\, to avoid having been in too long a filepath.
- Check the SHA-256 hash of your zip file compared to what's shown on Google's site? My Windows program of choice to check the hash of a single file is HashTab. If you install it, then right-click the OTA zip file, choose Properties, then click the HashTab tab, choose Settings to enable SHA-256, then you can paste in the SHA-256 hash that Google shows for the OTA you downloaded, and it'll tell you if that pasted hash matches the actual files' hash.
- You could try the non-Verizon variant of the OTA "oriole-ota-sd1a.210817.036-fac7e678.zip" with SHA-256 of fac7e67859e10838950af963d5e196e94ae3bf72317e505e71a87ea6160cca38.
Last edited:
Make sure you are in terminal (Command prompt) and not power shell. You are unlocked Verizon? The 36.a8 is for Verizon only not sure if it will work if you are using a different carrier. All other carriers are on .36 Other than that IDK hopefully Warrior can help you out. Maybe try downloading file again in case it got corrupted somehow.
Last edited:
Good advice.
I've tried mostly everything, and the drivers and adb interface appear to be working how they should. I think this may be user error in that I am putting the wrong filename in the "adb sideload" command.
in the terminal it shows: C:\WINDOWS\system32>adb sideload oriole-ota-sd1a.210817.036.a8-41f0de82.zip
"* cannot read 'oriole-ota-sd1a.210817.036.a8-41f0de82.zip' *"
Is this wrong or am I missing something about the file I'm pasting or which directory I'm placing it in?!
Do you have ADB and the OTA zip in the "C:\WINDOWS\system32\" folder? If not, do you have them in the same folder together? If so, "CD" (Change Directory) to the path where you have both ADB and the OTA zip. Like:
Code:
CD "C:\Users\Me\Downloads\Platform Tools\"
adb sideload oriole-ota-sd1a.210817.036.a8-41f0de82.zipIt is definitely the correct filename for one of the two SD1A.210817.036 OTAs - specifically the SD1A.210817.036.A8 (Verizon) one. Whether you should be flashing the SD1A.210817.036.A8 OTA or the regular SD1A.210817.036, we have no way of telling without more information, like @znel52's question about if you're on Verizon (and which model P6P you're using on Verizon if so - Unlocked or Verizon edition).
There's still a chance that the zip file is just corrupt. Checking the hash to see if it matches what's on Google's site would tell you. If it's not a match, the file you have is corrupt and you should re-download it and re-check the hash. I check hashes on all important files that I flash to my phone, when the hash is available.
Looks like you need to navigate to your ADB folder in terminal. It appears you are not running the commands from within the folder if I am reading your post right.
for instance when I pull up terminal it says C:\Windows\blah blah
My ADB folder is on the root of the C: drive so in command prompt I do 'cd/adb' which changes to my adb directory.
Command prompt then shows 'C:\ADB' which is where I need to be.
I'm sure I'm not explaining this well but you need to navigate to your ADB directory in command prompt before running the adb sideload command.
Or if you navigate to where your ADB folder is on your hard drive in explorer and Hold Shift + right click on the folder you should have an option to open a command prompt window from that location. Then you can just run your commands as you should be in the right spot.
Last edited:
Yourself and znel52 are completely right. My directory is for sure wrong with the command line. Figured I was messing up here.
I have the Pixel 6 unlocked, with a new verizon sim in it. After what I have been reading, it seems like there is still uncertainty with which ota to flash--the .036 or .036.A8. Figured since I am on Verizon that it would safe to flash the .A8, still not sure if I should flash the global one instead though?
Either way, I'm sure you'd be fine. The worst that would happen is you'd find that you should flash the other one to work better with Verizon. I'd stick to the assumption that you should flash the Verizon (.036.A8) OTA.
Hope it works well for you now.
I'm unlocked Verizon and I sideloaded A8 on my Pro. I really don't think it will make much difference either way but I'd probably go with A8.
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
4@pntballer505 reports getting the .037.A1 OTA on Verizon at post #138.
Old Verizon OTAs:
https://support.google.com/pixelpho...t-software-to-get-all-the-features?hl=en&s=09
4
It will come if they build it. I setup and popped the sim in. Be patient. It takes an hour to download. Damn. It's still updating. Best phone I ever had. I don't understand these complainers3
My accubattery says that my P6 Pro is capable of delivering 9h54minutes of SoT (discharge rate of roughly 10%/1hour), not sure if you are trolling, if you have a rogue app, a broken phone or if the P30 Pro indeed only loses 5% battery every hour of SoT, which would be a monstrous achievement.
What is known however, and not everyone is aware of that, is that Google phones are constantly calling home - meaning they offer 100% app functions - and because of that, "idle" battery life (like 1% lost every hour, depending on the amount of apps, more) is relatively bad. You can easily fix this with apps like Naptime or Servicely, even though those might only function in a limited way without root.
As a reference: https://dontkillmyapp.com/
What should also be mentioned, is that Google Pixels are not multi-day. They are designed by Google to run for one day, and for one day safely (anticipated battery saving functions, whatnot) - it's their decision to guarantee all app functions and therefore limit their phones battery life somewhat (some also call it: "muh spying, no good" - even though that only leaves me with a chuckle, Google already knows almost everything there is to know about most people, they don't need more information to know when you take a sh*t or watch porn), if you are looking for a mutli-day battery phone, Pixels can't help you (except if you root and use something like LKT like I usually do, that way you can get the awesome Pixel experience + awesome battery life) - but that requires work and of course you don't have to or should, if you don't like that.
--
Concerning the phone getting warm, I am still not able to replicate this (except shooting videofootage, which is normal for the phone to get warmer, even though I certainly wouldn't call it hot, it doesn't get uncomfortable, it's just noticeable that it gets warmer) - are you, by chance, active in 5G networks? There is no 5G connectivity near my home, so I never used that, I am 4G or Wifi only. Maybe this is the rootcause for those people here that talked about heat issues.
What might also cause a heat issue is a big ass case that might trap heat between the phone and the case - do you use a case? which one do you use? Maybe we can further narrow it down, if people with the same set of problems all use 5G and/or have similar cases.3
Just for the hell of it, I just tried to flash the regular global .036 over the vzw .036.A8 version and it failed citing the image was older than what I currently have now and downgrade isn't an option. Oh well, like I said, the toggle is still there and working for me. We'll see what Google does next month. I am still feeling these are mostly modem optimizations built in to the image for the specific carrier mentioned. If you look at previous builds for all the other phones, there are several that are carrier specific, especially when a new OS is released. Then eventually, as someone else mentioned, they merge them all together after a few months. Probably settings and coding that needs to be worked out to have the images compatible with all carriers.
3
You are correct, Google just likes to release firmware updates that do nothing.
/s
