How To Guide April 2, 2024 AP1A.240405.002 Global - Root Pixel 6 Pro [Raven]
- Thread starter roirraW "edor" ehT
- Start date
I typed the other post before finishing it or double checking it so yolo. Or maybe I should say (you only post once), I tried to fix a few stuff but I'm not going to rewrite the whole thing now haha... Sorry for the confusion
Never mind, I mixed up partitions and slots.
Last edited:
I just flashed over to 13 with android flash tool and it was really smooth. Now that flashes both slots right?
No. The Android Flash Tool site has an option to force flash all partitions (this also wipes your phone because your internal storage is a partition). That's unrelated to the two separate slots.
I believe so, that's my impression.
Ah my bad, I mixed up partitions and slots. Thanks for clearing that up for me!
Spookymyo
Senior Member
I've tried the flash tool. It won't recognize the phone.
Spookymyo
Senior Member
I did mention how long I held the buttons down in post #1219. I held all the different combos for over 2 minutes. When I had the cable plugged in the computer did the disconnect reconnect sound but never recognized it as a phone.
Yeah, I didn't go back to see you edited it. Running out of ideas.
I'm so embarrassed to post this, but I have to ask because I feel like I'm missing something... @roirraW "edor" ehT If you happen to read this, you might remember; I have a boring Verizon Pixel 6 Pro with the locked bootloader, so my first question is: is the OTA on the developers.google.com site also for my Verizon locked phone?
If so, I'm completely stumped as to why I can't sideload this OTA zip file with ADB. I tried two different new Windows 10 computers, four different new cables that all say they're data cables right on them, the latest drivers installed on the computer, etc.
So when I begin to side load, it begins verifying the zip file, but stops at around ~3 or ~4 and then... Nothing... absolutely nothing. No matter how long I wait or what I do. I've downloaded the OTA three separate times, I've checked to make sure the sha256 hash matches what's on the downloads page and all three of them did. So I'm hoping that someone with stronger brain cells than I, can tell me what I'm doing wrong and why this isn't installing for me. Thank you all so much!
If so, I'm completely stumped as to why I can't sideload this OTA zip file with ADB. I tried two different new Windows 10 computers, four different new cables that all say they're data cables right on them, the latest drivers installed on the computer, etc.
So when I begin to side load, it begins verifying the zip file, but stops at around ~3 or ~4 and then... Nothing... absolutely nothing. No matter how long I wait or what I do. I've downloaded the OTA three separate times, I've checked to make sure the sha256 hash matches what's on the downloads page and all three of them did. So I'm hoping that someone with stronger brain cells than I, can tell me what I'm doing wrong and why this isn't installing for me. Thank you all so much!
I crossed my fingers, Knocked on wood, rubbed my lucky rabbits foot and fired up my computer
- Booted the bootloader
- Connected the computer and phone
- Opened a command prompt
-
fastboot flash boot magisk_patched...img- Pressed the enter key
- Took a deep breath, wiped the sweat from my forehead and pressed the pwr button on my phone.
- After, a few seconds had passed, I noticed there was no smoke coming from it, I looked at the screen.
- It had booted up and was rooted.
- I put the Flash Tool on hold untill the next crisis.
To all the XDA members and Staff that helped
get my problem resolved.
Thank you!
Last edited:
I actually have the OTA update (I hadn't installed it since people were saying on the forum that it "wasn't released" which confused me, since I've been sitting on it this entire time.) I wasn't sure to mention it because I have been waiting DAYS for the file to be released. It's been nagging me for 3 weeks so far (I got the prompt on like the 3rd of Aug) for this OTA.
After reading some of these posts though.. I'm not sure if I should update to 13 or not.
There ya go!!!I crossed my fingers, Knocked on wood, and rubbed my lucky rabbits foot and fired up my computer
- Booted the bootloader
- Connected the computer and phone
- Opened a command prompt
-fastboot flash boot magisk_patched...img
- Pressed the enter key
- Took a deep breath, wiped the sweat from my forehead and pressed the pwr button on my phone.
- After, a few seconds had passed, I noticed there was no smoke coming from it, I looked at the screen.
- It had booted up and was rooted.
- I put the Flash Tool on hold untill the next crisis.
To all the XDA members and Staff that helped
get my problem resolved.
Thank you!
Hi, I think lots of people have been having trouble sideloading 13, so it's not just you. I really don't fool with sideloading, use the full factory image so I don't have the experience to attempt to help.
I would expect the same OTA to work for you normally, so I'm guessing it's just the general trouble a lot, although not necessarily all, people are having sideloading the OTA, from all the posts I've read since 13 came out Monday.
You may just want to hang in there and wait for an actual over the air update, or more news or yet another update from Google.
Sorry I don't have better advice.
I'm confused. Android 13 Stable didn't come out until August 15th. The OTA from the beginning of the month was the second July update that no one was expecting.
I'm not saying you don't have the 13 OTA ready and waiting for you to install, I just don't understand how you would've received it two weeks ago.
Absolutely, that's fine. I can wait for it. I'd rather not do the full image because I really like the way I've got my apps right now, and it's a real pain in the you know what to load them all back. Maybe one day when I get a wild hair, I'll just do it for the heck of it. But you're right; I'm not in a rush for it, but I am very curious about it. But it's nothing that can't wait until Google gets around to us. Thanks so much RW! Hope all is well!
I know i've had it since at least the 3rd because (I have the option to disable automatic updates enabled) and every other day I have a popup (that uses kind of strong language) that I should update, but I postpone it.
I know it was the 3rd because I made a twitter post about it (nobody replied
)If it helps, mine is the USCellular variant.
I'm terrified of messing this up. I've read all the relevant threads, I know how to use pixelflasher, and yet I still don't trust myself to NOT brick my device.
Last edited:
What has worked for a lot of people who haven't gotten the OTA update yet is to join the A13 Beta program. You should then receive an OTA update to Stable A13. Once installed, unenroll from the Beta program.
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
