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
WIll Magisk 22.5 will work to root tq1a.221205.012 image on Pixel 6 Pro? It didn't work on my 7 Pro thus asking...
Do you mean 25.2? If so, it will work on the Pixel 6 Pro (also works on my Pixel 7 Pro).
If you actually mean 22.5, I don't think there is a version with that version number (maybe Canary?). Also, Magisk 22 is very old and likely won't work on either phone.
73sydney
Account currently disabled
Watch/bookmark this page - this is where up to date Magisk is discussed.
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Links to magisk (and other related tools) are on it
Example...Magisk repos:
Stable:
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Shows the current version info in release name and will be xx.x
(Canary):
GitHub - topjohnwu/magisk-files at canary
Magisk File Host. Contribute to topjohnwu/magisk-files development by creating an account on GitHub.
github.com
go to notes.md and you can see the version info (xx.xxx - currently 25205 or 25.205)
BostonDan
Senior Member
So just a note: when unrooting/updating/re-rooting I typically
uninstall root through Magisk
Take the update
Download the new image and extract boot.img
Patch the new boot.img
Reboot to fastboot
fastboot boot <magisk patched image> (not flash)
And then let magisk apply the patch to the boot images through magisk (ensures I have the files to uninstall the patch for the next system update).
However, this time when I tried fastboot boot <magisk patched boot images> I got an error that the command was not found. I ended up flashing the magisk patched boot images, but it seems Google does not want people booting from fastboot.
Anyone else notice this?
Cheers,
B.D.
uninstall root through Magisk
Take the update
Download the new image and extract boot.img
Patch the new boot.img
Reboot to fastboot
fastboot boot <magisk patched image> (not flash)
And then let magisk apply the patch to the boot images through magisk (ensures I have the files to uninstall the patch for the next system update).
However, this time when I tried fastboot boot <magisk patched boot images> I got an error that the command was not found. I ended up flashing the magisk patched boot images, but it seems Google does not want people booting from fastboot.
Anyone else notice this?
Cheers,
B.D.
73sydney
Account currently disabled
interesting, i normally (on my previous Pixel 2XL, before i sadly departed, wrongly back to Samsung - glad im back) always fastboot booted the magisk patched image just as a test, before rebooting and flashing it
i havent yet done the update but will try as you did when i get time...
but the previous and current A13 build im on lets me fastboot boot my current magisk patched boot image at least...there is a delay after the image is sent and before it reboots, and i didnt think it was going to do it
also its just nice to see you B.D. and not talk about, well, you know
I just downloaded the Dec 5 update for my P6P
Every time I attempt to copy the boot.img file to my phone for magisk, defender pops up with this message:
WARNING Trojan:Script/Wacatac.H!ml
and then it deletes it.
It didn't matter if I took the download from the OP page 1 or went directly to https://developers.google.com/android/images#raven
always the same warning.
thoughts?
ƒ
Every time I attempt to copy the boot.img file to my phone for magisk, defender pops up with this message:
WARNING Trojan:Script/Wacatac.H!ml
and then it deletes it.
It didn't matter if I took the download from the OP page 1 or went directly to https://developers.google.com/android/images#raven
always the same warning.
thoughts?
ƒ
False positive. Just disable Defender temporarily.
Yes defender thinks boot.img from December as a 2019 Trojan. Rstore it from defender's quarantine and copy it to your phone. As far as i can tell it's a false positive but there is no way in defender, that i found, to report it as such.
Curious.
Can I go to settings and do a factory reset without losing root, or would I have to have the original boot.img?
Can I go to settings and do a factory reset without losing root, or would I have to have the original boot.img?
Factory reset just resets the data partition, if you are currently rooted, you will retain root.
I believe Magisk Manager will automatically get installed, but if it does not, you should install it so that you can manage root.
Hey guys hope someone can give me some pointer to get my phone going again.
I was doing the December factory update and got this message:
After rebooting the phone goes directly into fastboot.
How can I get going again?
Thanks.
I was doing the December factory update and got this message:
After rebooting the phone goes directly into fastboot.
How can I get going again?
Thanks.
It looks like something happened to the connection should flashing.
Make sure the connection is solid, cable is good, the port preferably usb 2 and don't touch until it completes.
Flash again, if it completes, your phone should boot ok.
Thanks for responding.
I tried another cable.. same problem.
Tried a few other things with no luck.
Used android flash tool to load the december patch and flashed patched boot to get root back.
All good now. Hopefully I won't have to go through this process again in january.
Is it always at the same point that you got the error?
basically product_b 2/11 ?
If yes, the it could be that the image you downloaded is corrupted.
Always check the CRC to be certain.
If you still have the image, you can check the crc
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 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
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
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.
