Ok, i know it is advised to do a fresh wipe for android version updates but is it absolutely necessary?
How To Guide April 2, 2024 AP1A.240405.002 Global - Root Pixel 6 Pro [Raven]
- Thread starter roirraW "edor" ehT
- Start date
PSA:
"Android 13 is rolling out to Pixel devices starting today.
If you’re currently enrolled in the Android Beta program, you’ll get the Android 13 final release and remain enrolled to receive ongoing Beta updates for Android 13 feature drops, starting later this year. If you’d like to opt out of ongoing Beta updates without needing to wipe your device, just visit the Android Beta site and opt out after you get the Android 13 final release and before taking the first beta for Android 13 feature drops."
In other words, you won't be unenrolled automatically.
ADDENDUM: A13 QPR1 Beta due out in September.
android-developers.googleblog.com
"Android 13 is rolling out to Pixel devices starting today.
If you’re currently enrolled in the Android Beta program, you’ll get the Android 13 final release and remain enrolled to receive ongoing Beta updates for Android 13 feature drops, starting later this year. If you’d like to opt out of ongoing Beta updates without needing to wipe your device, just visit the Android Beta site and opt out after you get the Android 13 final release and before taking the first beta for Android 13 feature drops."
In other words, you won't be unenrolled automatically.
ADDENDUM: A13 QPR1 Beta due out in September.
Android 13 is in AOSP!
News and insights on the Android platform, developer tools, and events.
Last edited:
I rarely wipe my phone for any update at all. OTAs don't wipe the phone. Sure, it's possible that it'll run better if you wipe your phone, but not necessarily, and you can always wipe later if you must.
FYI:
Android 13 QPR1 Beta in September
9to5google.com
Android 13 QPR1 Beta in September
You can unenroll from Android 13 Beta without wiping after stable update, QPR1 preview in Sept.
The stable version of Android 13 is rolling out to Pixel today, and those on the Android Beta Program can unenroll their phones after...
9to5google.com
You are correct.
I did:
Code:
adb reboot bootloader
fastboot flash bootloader bootloader-raven-slider-1.2-8739948.img
fastboot rebootAnd I'm booted into Android 12 still just fine. Below is the command prompt output:
Note to anyone, if after upgrading to 13 you want to downgrade to 12 using a full factory image's flash-all.bat, you'll at minimum have to either remove Android 12's bootloader flash line from the file, or replace it with
fastboot flash bootloader bootloader-raven-slider-1.2-8739948.img (and have the right bootloader file in the same folder). Either should work fine.
p51d007
Senior Member
I've NEVER done a wipe, for an update from one version to the other. I guess it's "better", but I don't want to spend the time setting it all back up again.
Update 2: Different USB cable and port worked 100%
Hmmmm. Now, after having tested flashing only the bootloader and just now doing the flash-all.bat, I got this (TL;DR
Going to try again.
Update: Thought it was getting farther the second time, but got the same thing. Time to try a different USB cable/port.
fastboot: error: Command failed):Going to try again.
Update: Thought it was getting farther the second time, but got the same thing. Time to try a different USB cable/port.
Last edited:
Depends on how you update it, but for the more conventional update methods, yes, you'll have to re-root.
Just as @Lughnasadh said, and to add: only just as much as you have to re-root every month's update when you flash it, depending on your method.
^
Last edited:
The real trick will be if you can still flash the old factory image. Try to re-flash the July image (just the system image) and see if the bootloader rejects it.
For those of you that updated to A13 - Has Google removed the ability in A13 to sideload non GP apps?
No, but they've restricted a few permissions for sideloaded apps (e.g. Notification Listener and Accessibility permissions). But those restrictions can be disabled by going to the app info page and clicking on the 3 dot menu on top right.
Last edited:
There's no way I'll test that. Downgrading without wiping (because of updated app data, especially for system apps) is too much risk for me. I don't have the time to recover from.
Anyone else?
Last edited:
Leaving the past in the rear view mirror, sir...There's no way I'll test that. Downgrading without wiping (because of updated app data, especially for system apps) is to much risk for me. I don't have the time to recover from.
Anyone else?
Haven't seen anyone get V4A working on A13 on the Pixel 6 series. JamesDSP, however, does work.
MicroMod777
Recognized Contributor
Top Liked Posts
-
There are no posts matching your filters.
-
32
I gather you're all good now?
In the future please create post PF issues in PF thread to keep this thread tidy and focused, and always provide a support file.22
I did go through and successfully flashed my PX6 pro to AP1A.240405.002 with KSU using PixelFlasher 6.8.3.0 -
66Pixel 6 Pro [Raven]
April 2, 2024:
Android Security Bulletins | Android Open Source Project
source.android.com
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):
16The 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.16
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.1513Just 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
