I tried it w/o reboot between also no luck
I'll just wait until MArch, but keep checking here just for fun
I'll just wait until MArch, but keep checking here just for fun
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
why not do it my way then re-flash the Feb update so root and custom kernel gets replaced with stock? assuming it also disappears for you after applying the custom kernel
Code:
adb fastboot flash boot customKernel.imgOK I just looked at the Kirisakura page. it looks pretty simple.
I guess I am curious as the the pluses and minuses of using this (or any other ) kernel.
Last edited:
If you didn't already have Verity and Verification disabled, you need to in order to flash a custom kernel. And disabling those will wipe your data, and there's no way around that.
I was doing that a long time ago, when we had to on this phone, but once that was "fixed" i haven't done it since.
I assume that doesn't hold-over from back in the early A12 days with this phone.
Would I have to wipe every time I i did the monthly update if I flashed a kernel?
To my understanding and limited experience with disabling them - since I only disabled them for a few months on the Pixel 6 Pro before the kernels obtained the capability to not need them disabled:
If you had them disabled at one time, but you've since flashed without disabling them, re-disabling them still requires a wipe. That's the problem - you have to remember to disable them from then on each time you flash something that flashes vbmeta.img, like the factory image/flash-all.bat does, or the next time you disable them you'd have to wipe again.
You wouldn't have to wipe each month as long as you disabled them each and every time you flash anything that flashes vbmeta.img.
Note that just performing a factory reset (at least, if you return to fully stock, unrooted) would likely fix your corruption issue. It's been the assumption all along that you'd rather not wipe if you don't absolutely have to.
If I'm not mistaken, you only need to disable verity and verification to flash a custom kernel on a Pixel 7 series device. While in the early days of the Pixel 6 series this was required (disabling verity alone was good enough), it is no longer required to the best of my knowledge.
EDIT: Probably a mix up in threads/device again?
EDIT: Probably a mix up in threads/device again?
Last edited:
Oh, whoops (me)! Indeed. Argh. I should probably stop replying in the Pixel 6 Pro sections. LOL! @biTToe forget all that I said - you don't need to disable Verity and Verification on the Pixel 6 Pro to flash a custom kernel. Apologies for my confusion about which device section I was posting in.If I'm not mistaken, you only need to disable verity and verification to flash a custom kernel on a Pixel 7 series device. While in the early days of the Pixel 6 series this was required (disabling verity alone was good enough), it is no longer required to the best of my knowledge.
EDIT: Probably a mix up in threads/device
No Worries.
I greatly appreciate all the help here.
I'm just an even-Pixel guy I guess: P4, P6. probably P8...
I've only had the P1 (used it for 3 1/2 years, was waiting on a 512 GB Pixel), the P6P, and P7P. I'm wondering if the P8's CPU will be ARM v9 to have the greater security features?
Arm introduces second-generation Armv9 processors, plus a ray-tracing GPU
Arm has introduced its second-generation Armv9 processors plus new GPUs, including the new Immortalis-G715, which supports ray tracing.
Or for the uber-technical:
Arm Memory Tagging Extension | Android Open Source Project
source.android.com
interesting stuff.I've only had the P1 (used it for 3 1/2 years, was waiting on a 512 GB Pixel), the P6P, and P7P. I'm wondering if the P8's CPU will be ARM v9 to have the greater security features?
Arm introduces second-generation Armv9 processors, plus a ray-tracing GPU
Arm has introduced its second-generation Armv9 processors plus new GPUs, including the new Immortalis-G715, which supports ray tracing.www.xda-developers.com
Or for the uber-technical:
Arm Memory Tagging Extension | Android Open Source Project
Sadly, more "security" generally comes at the exxpense of "fun"
Here's a somewhat related article about A14, ARMv9 and MTE. Hopefully the Pixel 8 will have it like most other Snapdragon 8 Gen 1 & 2 Android flagships currently do.I've only had the P1 (used it for 3 1/2 years, was waiting on a 512 GB Pixel), the P6P, and P7P. I'm wondering if the P8's CPU will be ARM v9 to have the greater security features?
Arm introduces second-generation Armv9 processors, plus a ray-tracing GPU
Arm has introduced its second-generation Armv9 processors plus new GPUs, including the new Immortalis-G715, which supports ray tracing.
Android 14 may add an advanced memory protection feature to protect your device from memory safety bugs
Android 14 may add a new beta feature called "advanced memory protection" that can protect against memory safety bugs on compatible devices.
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Anyone know if it's ok to upgrade with this release?
Changelog doesn't mention the fastbootd issue (268872725), so it may not be ok to use the new release for flashing factory images.SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
Anyone know if it's ok to upgrade with this release?
Also, the download links are downloading SDK Platform-tools rev. 34.0.0 not rev. 34.0.1.
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
Anyone know if it's ok to upgrade with this release?
I confirm that link still only gives the v34.0.0 zip. Besides the same version number in the filename, I've checked the hash of the zip file, and it's the same as the 34.0.0 that was released on February 10th.
I have Aignes Website-Watcher set to let me know when the direct link below leads to an updated file:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
(https://dl.google.com/android/repository/platform-tools_r34.0.1-windows.zip also gives a 404 error)
Thanks for the heads-up about the possible impending release, though. Hopefully it actually fixes all the issues everyone had with using 34.0.0 once it is made available.
Google Pixel 6/6a/6 Pro | Updates
#Updates #Android SDK Platform Tools r34.0.1 has been released! Release date: March 2023 Changelog (adb): • macOS: Reverted "unstable connectivity (MacBook high speed cable)" resolution due to adb install hang. Changelog (fastboot): • Windows: Fixed "mke2fs: Illegal or malformed device name...
My mistake. I just checked the link.
The download links there are still to the 34.0.0 version as well. Confirmed it's the same zip file, still today.Google Pixel 6/6a/6 Pro | Updates
#Updates #Android SDK Platform Tools r34.0.1 has been released! Release date: March 2023 Changelog (adb): • macOS: Reverted "unstable connectivity (MacBook high speed cable)" resolution due to adb install hang. Changelog (fastboot): • Windows: Fixed "mke2fs: Illegal or malformed device name...t.me
My mistake. I just checked the link.
Oddly, even though:
source.android.com
doesn't show the March 2023 Pixel Update Bulletin, websites have revealed that it is available here:
source.android.com
Still no hint of the actual firmware, however.
Pixel Update Bulletins | Android Open Source Project
source.android.com
Android Security Bulletin—March 2023 | Android Open Source Project
source.android.com
Still no hint of the actual firmware, however.
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
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
3
I have added fastbootd testing into PF's Dry Run Mode which is part of the PF's next release.
I just tested this on a Pixel 5 device, and the device was able to get into fastbootd, which was the issue with the previous v34.x versions.
I don't know if this is conclusive enough to prove that this version is good, as I didn't flash anything just switched to bootloader, then fastbootd then bootloader and then system, which is what happens during dirty flashing.
I would expect it to work, as it is able to get the device into fastbootd and detect it.3
They changed the time stamp of the zip again, but it's the same file as earlier today. -
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.
