when i type in adb sideload and then the package name it keeps saying cannot read
what am i doing wrong?
what am i doing wrong?
Did you properly open the command prompt in the ADB folder? (shift rightclick)it says now send the package you want to apply, so i do that and still says cannot read on powershell
adb folder? i dont have a specific adb folder?Did you properly open the command prompt in the ADB folder? (shift rightclick)
how do i get the folder? do i paste the ota file to a folder?
It should see the OTA eventually - there are others who already received the OTA while using an unlocked P6P on Verizon. Not bootloader unlocked or rooted, correct? If so, you'll have to sideload the Verizon OTA.I'm using an unlocked/international 6 pro running SD1A.210817.036 on Verizon. Do I need to sideload the verizon OTA of this newest version or will my phone magically see an update eventually?
It should see the OTA eventually - there are others who already received the OTA while using an unlocked P6P on Verizon. Not bootloader unlocked or rooted, correct? If so, you'll have to sideload the Verizon OTA.
Either way, you can sideload the Verizon (or regular) OTA whenever you want if you don't feel like waiting.
Can you clarify; others received the update using an unlocked p6p on verizon and they were running SD1A.210817.036 or they were running SD1A.210817.036.A8 (VZW variant)?
If I'll get the update automagically, then i'm not going to bother with ADB.
Had you set up your FP again after the november patch? (the .036 one). My guess: You have not set up your FP correctly. For me, it's a night and day difference, easily double the speed. Hard to believe that you don't "noticed a difference".I haven't noticed a difference, but some have said battery life has also improved? I'll be monitoring that very closely...
No, I haven't done anything with my FP after the patch.Had you set up your FP again after the november patch? (the .036 one). My guess: You have not set up your FP correctly. For me, it's a night and day difference, easily double the speed. Hard to believe that you don't "noticed a difference".
I think you've posted in the completely wrong place and regarding the wrong subject.For everyone having problem and the "Cannot read" error message, I had the same thing and fixed it using CMD instead of PowerShell/Win11 Terminal. You can also try applying the patch to read large adresses: https://www.techpowerup.com/forums/threads/large-address-aware.112556/
Yes my badI think you've posted in the completely wrong place and regarding the wrong subject.
finally, it's not the wrong thread lol.when i type in adb sideload and then the package name it keeps saying cannot read
what am i doing wrong?
Applying a patch to read large addresses has nothing to do with the Pixel 6 Pro, applying updates, or anyone's issue in this thread. If it does have something to do with it, you're going to have to explain as there's no obvious tie-in.
"An update with the November security patch arrived for the majority of Pixel 6 and 6 Pro owners at the end of October. Google is now releasing updated builds for both phones, with global and Verizon variants.
Update 11/17: According to Verizon, this mid-cycle update “improves the performance of your device’s fingerprint sensor.” Early anecdotes of the 14.56MB OTA are bearing that out. However, “Check for update” does not currently trigger the download for all users."
- Pixel 6 Pro – SD1A.210817.037 – all – Factory Image – OTA
- Pixel 6 Pro – SD1A.210817.037.A1 – Verizon – Factory Image – OTA
So your phone isn't on the global software version now? I'm on Verizon too but don't want their software version. Right now I'm on the global software. Still haven't received the update so I was curious about your situation. Thanks