As long as it is unlikely that adb reboot "dm-verity enforcing" won't force a wipe, I'll try that. But if you're pretty sure it will. I will hold off until March.
Thanks for the insight
How To Guide Platform-Tools v34.0.3 has a different bug - May 17, 2023 TQ2A.230505.002.G Verizon/MVNOs - May 1 TQ2A.230505.002 Global - Root Pixel 6 Pro [Raven]
- Thread starter roirraW "edor" ehT
- Start date
Thanks for the insight
I will run this tonight and post.
I have read a little about this issue and some takl about sideloading, but I am not really sure how that is done.
Yeah, from my observation sideloading the full OTA doesn't always work for getting rid of the corruption message, but that person can certainly try.
Code:
(bootloader) slot-count:2
(bootloader) current-slot:b
(bootloader) slot-retry-count:b:2
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:2
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yesHere's a good tutorial...
here it is, and then some
(bootloader) secure:yes
(bootloader) secure-boot
RODUCTION(bootloader) slot-count:2
(bootloader) slot-fastboot-ok:a:yes
(bootloader) slot-fastboot-ok:b:yes
(bootloader) slot-retry-count:a:2
(bootloader) slot-retry-count:b:2
(bootloader) slot-successful:a:yes
(bootloader) slot-successful:b:yes
(bootloader) slot-suffixes:_a,_b
(bootloader) slot-unbootable:a:no
(bootloader) slot-unbootable:b:no
(bootloader) snapshot-update-status:none
hahahaha.... I like that it turned the : & P into the smiley
Thanks, looks normal.here it is, and then some
(bootloader) secure:yes
(bootloader) secure-boot
(bootloader) slot-count:2
(bootloader) slot-fastboot-ok:a:yes
(bootloader) slot-fastboot-ok:b:yes
(bootloader) slot-retry-count:a:2
(bootloader) slot-retry-count:b:2
(bootloader) slot-successful:a:yes
(bootloader) slot-successful:b:yes
(bootloader) slot-suffixes:_a,_b
(bootloader) slot-unbootable:a:no
(bootloader) slot-unbootable:b:no
(bootloader) snapshot-update-status:none
hahahaha.... I like that it turned the : & P into the smiley
Nothing is out of place.
I appreciate the look.
THere is a lot of info there. Nothing looks out of place. No "corrupt" or "error"
I'm going to try and d/l the firmware from google again and extract the boot.img. maybe there was in issue there. I did not run a checksum
THere is a lot of info there. Nothing looks out of place. No "corrupt" or "error"
I'm going to try and d/l the firmware from google again and extract the boot.img. maybe there was in issue there. I did not run a checksum
at the bottom of the fastboot mode screen it does say UART: Disabled
i too have the corruption message (didn't see the v34 warning in time) but i'll wait for your findings as i am not confident/experienced enough to be tinkering this much with my own main driver phone.
edit: i got it to patch and boot but would like to have the corrupt message removed without wiping. at least not till the weekend
edit: i got it to patch and boot but would like to have the corrupt message removed without wiping. at least not till the weekend
Last edited:
nvm , i just flashed my magisk patched boot, then flashed the latest Kirisakura kernel (4.4.2) and the message disappeared. Restarted just now to confirm and it's not there anymore
Hmmm.... that begs the question: is there a stock android kernel I can patch?
Apologies, I'm not understanding the question. The stock Android kernel is in the inner zip of the full firmware zip.
Yeah, so @djo_5296 Flashed the Kirisakura kernel and "fixed" his corruption issue.
Is there a separate kernel file I might try flashing, and if so, which file is it (I don't see a kernel.img file)
android-info.txt
boot.img
dtbo.img
product.img
pvmfw.img
super_empty.img
system.img
system_ext.img
system_other.img
vbmeta.img
vbmeta_system.img
vbmeta_vendor.img
vendor.img
vendor_boot.img
vendor_dlkm.img
I think I see. boot.img is the stock kernel. Specifically, flash an old kernel (boot.img), such as from January or February, then flash the Stable February boot.img.
Edit: If you were rooted, you'll want to finally flash the Magisk'd Stable February boot.img before you boot into Android.
Ahh.
I tried that and it didn't work: Flash December | reboot | Flash February | Reboot | No luck
So: Flash Dec | Flash Feb | Flash Magisk | Reboot?
this is new: "unauthorized"
C:\p6p\reco>adb devices
List of devices attached
1A041FDEE0023Q unauthorized
I thought that was you (the same person), but I was too lazy to double-check.
Correct. You can try
fastboot reboot fastboot between each flash as well, but I thought that's what you did. Not necessary to flash the Magisk'd boot.img if you don't want to be rooted - it won't be a part of the fix, I don't think, although who knows.At this point, I would be tempted to leave it as is until next month's firmware comes out. I know it's a slight PITA when you reboot.
Just need to authorize it on the phone. If necessary, you could rescind all authorizations, and then get a fresh prompt to authorize after you plug it back in and run adb from the computer to it.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
4
Android’s May 2023 security patch prevents downgrades to infinitely old system app versions
May’s security patch fixes a potential...www.androidpolice.com
3
They changed the time stamp of the zip again, but it's the same file as earlier today.3
I understand! And you're welcome!
Next up: A new survey by Google.
How many times would you like to reflash your device per month?
- 1
- 2
- 10
3Google will soon let Pixel phones double as dashcams
Rather than needing to buy a (sometimes...
9to5google.com
-
62Pixel 6 Pro [Raven]
Updated May 13, 2023
Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes)
Someone reported it to Google (added a comment about 34.0.1 to the existing 34.0.0 report).
Factory Images for Nexus and Pixel Devices | Google Play services | Google Developers
developers.google.com
Google Pixel Update
Android Security Bulletins | Android Open Source Project
source.android.com
Regarding Developer Support Android 12 images, see @Lughnasadh's post here.
I am not linking directly to the Developer Support Android 12 images because I don't want them to be confused with Stable Android 12, and since the Developer Support images won't receive any OTAs...ever. They likely also will never be manually updated on the Developer Support images site, so they will forever be stuck with the security patch level they're currently on, which will become further out of date every month. You can Google searchDeveloper Support Android imagesif you want to find them.
TL;DR regarding the PSA. If you update one slot to Android 13, you canfastboot reboot bootloaderafter and thenfastboot --set-active=otherto change slots in order to flash Android 13 to the new slot, but IF you have Android 13 on one slot and still have Android 12 (including Android 12 bootloader) on the other slot and you try to fully boot into Android 12, you will be permanently bricked and have to seek repair from Google. No one has yet found a way to repair this on our own. I will update if there is any progress. At least a small handful, and probably more, people have done this already.
At a minimum, do this first:fastboot flash bootloader --slot all bootloader-devicename-slider-1.2-3456789.img(change the name of the bootloader file to the one for your device), then you *should* be much safer than without doing that first. Also note that the bootloader is NOT the same as boot.img (kernel). The bootloader image file has "bootloader" in the filename.
IF you have already bricked your phone and the screen is blank - there is likely nothing we can do to help. You should seek to get a repair from Google, possibly under warranty.
You CANNOT go back to Android 12 Stable. It *seems* as if you can, but Android 12 will not work 100% correctly after updating to the Android 13 bootloader.
My tiny, early, very mini-review of Android 13 is here.
Here there be dragons.
I am not responsible for anything at all. 
Check warranty status - *may* reveal if a phone is refurbished, only if the phone was refurbished through Google - thanks to @Alekos for making me aware of the site.
Official Google Pixel Update and Software Repair(reported as of January 23, 2022 to still not be updated for the Pixel 6/Pro yet)
Google's Help Page for Find problem apps by rebooting to safe mode - this can be a lifesaver and keep you from having to do a restore to 100% complete stock or even from having to do a factory reset. This will deactivate all Magisk modules, and they'll remain deactivated even after you boot normally after briefly booting to safe mode. You can reenable the Magisk modules as you wish to try to narrow down the problem if it was caused by a Magisk module. This can even get things working again after a Magisk Module wasn't finished installing and potentially causing a bootloop.
Official Google Pixel Install fingerprint calibration software (also available at the bottom of the Update and Software Repair page above) - I believe this is only helpful if you've replaced the screen
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
ADB/Fastboot, Windows Drivers, and unlocking the bootloader (thanks @sidhaarthm for confirming unlocking the bootloader works as intended, be sure to thank him in his post)
Rooting-related
No longer applies -Things that make rooting more complicated on Android 12
A list of the other important guides - be sure to thank the respective OPs
For all relevant guide threads just click the yellow "How To Guide" quick filter above the list of threads in the Pixel 6 Pro section.
- Here's the Magisk section of XDA's forums, for rooting. Magisk on GitHub. The most recent Magisk Stable is what's recommended these days.
- @sean222's thread Restore WiFi and Cellular Data in Quick Settings (Root Required)
- @rickysidhu_'s thread HBM (High Brightness Mode)
- @gururoop's thread Probable method to upgrade every month, without wiping data and retaining root
- @rickysidhu_'s thread Limit Charge
- @Typhus_' thread [MOD][MAGISK][ANDROID 12] Addon Features for Pixel Devices - Pixel 6 Pro Thread
- @siavash79's thread [MOD][Xposed+Magisk][Pre-Release] AOSP Mods - System modifications for AOSP-based Android 12+ - a mod that compliments @Typhus_' mod above, and may eventually completely replace it.
- @TotallyAnxious' thread [MOD] Collection of "Anxious" Modules for Pixel 6/Pro Series
- Every single one of @foobar66's posts.
TWRP (not made for the Pixel 6 Pro yet - will update when it has)
Custom kernels for stock ROM(s)
Factory Images (requires an unlocked bootloader)
Full OTA Images (doesn't require an unlocked bootloader)
The usefulness of having Verity and Verification enabled (now that it's not needed for root) - post #2 below.
Regarding P6P 5G model numbers and capabilities - post #3 below.
List of all Pixel monthly security bulletins and Play System Updates - post #4 below.
How I root and update (which is identical whether rooting the first time or updating):
1515The unlock process works like this;
1) Take brand new fresh phone out of box. Do NOT put sim card in it, just power it on.
2) When it starts harassing you to join google, hit "skip" and "remind me tomorrow" as applicable until you reach home screen. YOU DO NOT need to plug in a google account.
3) Settings --> About --> Build number. Tap it until it says you're a developer.
4) Back --> Network --> Wifi and connect it.
5) Back --> System --> Developer --> OEM unlocking (check), USB debugging (check), plug in USB, authorize when requested.
6) # adb reboot-bootloader
7) # fastboot flashing unlock
Now that you've unlocked it, it has been wiped, so repeat 1-4, then disable all the google spyware, and go ahead and start using it while waiting for aosp and root.13Just to let everyone know, updating to .037 and re-rooting (without wiping anything) worked with no problems. My method is to just replace -w with --disable-verity --disable-verification in the flash-all.bat file and run the flash-all command. I then let it reboot, patch the boot image, return to bootloader and flash the patched boot image.
Canary 23014
EDIT: Thank you @ipdev for confirming my inquiry that this method would work back on Nov. 4
12
Used a factory image and booted into Android 13. Auto OTA and a sideload of the full OTA will end in the same result as both useupdate_engine. I did boot into Android 13 so the ARB counter did get incremented.
Downgraded by just forcing Android 12 system image with a wipe, switched slots, and did it again. It might be able to be done with a full OTA, but I didn't test it because of the following issue:
Android 12 doesn't work properly on the Android 13 bootloader.
It boots up just fine, appears to work just fine, made and received calls and texts, however the issue @bush911 had with WebView crashing is true. It's more than just WebView, the media DRM APEX immediately crashes. WebView crashes sometime after launch when it tries to find out if ClearPlay or WideVine are functional, and DRM Info crashes immediately when I try to launch it. Without DRM working that means you won't be able to play some music or movies and won't be able to use Netflix or any other streaming app.
There might be more systems or modules nonfunctional, but without working browsers your smartphone isn't going to be more useful than a dumbphone.
@roirraW "edor" ehT
So I guess it's time to retract that you can revert to Android 12, because until a modder comes along to cook up a custom Android 12 ROM with Android 13 APEXs or patched ones it won't work.
