It really does seem like there are more issues than normal this month. The changelog is posted around here somewhere but I can't remember where I seen it. I highly recommend using PixelFlasher to update your device, it's a very well put together program that Badabing2003 created. I can't say enough good things about it, really well done. It literally takes me 224 seconds every month to update, except this month do to an error on my part. Give it a go, if you have any questions or run into any issues PM me and I'll help you out.
How To Guide [GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet
- Thread starter V0latyle
- Start date
Excellent, I will check it out. I remember seeing a comment about the latest version (34.0.x?) having a bug, and to use 33.x.x instead - is this still the case? Many thanks!
There's no issues with PixelFlasher, it's Platform Tools that is having issues. I guess the latest version 34.0.0 has issues so they're telling everyone to revert back to 33.0.3 If you have 34.0.0 you'll have to find a place to download 33.0.3 from. Once you get that straightened out then you can use PixelFlasher if you want. Just don't use the latest Platform Tools or you'll end up in a bootloop (at least that's what I hear).
It could be worse as several users have reported their devices being bricked or unresponsive after using 34+.
You'd really think that with such a critical problem that can corrupt bootloaders and brick devices, they would at the very least pull the problem releases.
You would think, lol. But we know how slow Google sometimes reacts to major issues: re: ARB in the Pixel 6 series.
They're saying that they're bricked but from what I've read they're actually stuck in a bootloop. Not nearly as bad but still an issue. Yeah, they probably should at least include a warning with the download that warns of the potential to end up in a bootloop. At least until they get it straightened out no matter who's software is causing the problem. .
Type "Adb version" without quotes in command line (in the platform tools folder of course)
Ninja'd.
This works
Attachments
Android Debug Bridge version 1.0.41
Version 33.0.3-8952118
What I have installed. So guess I wont update.
Lol i know i just told you that ROFL
I was stating as an experiment i typed "fastboot version" it might have given a build number, but i didn't let it go through to a device
Yeah, in this case you're asking fastboot to return the version of a particular variable on the deviceLol i know i just told you that ROFL
I was stating as an experiment i typed "fastboot version" it might have given a build number, but i didn't let it go through to a device
Thanks. Got 33.0.3 downloaded. Will give PixelFlasher a look-see later this week, when I get enough time to do it. Much appreciated!
Well I glad I saw the posts about the issues with platform tools 34.0. Used 33.0.3 instead with magisk 2520, and just finishing updating through the factory image and fastboot, and patching and booting the patched boot.img, and it works perfectly. I was coming from the Feb. update.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1
Let me give you a little advice, when I rooted my Pixel 6 Pro, it was the first device I had rooted since my Nexus 6p. I came across the PixelFlasher program developed by Badabing2003 and haven't gone back to the old school way of doing things. once you learn how to use it, it's so easy! it literally takes me about 4 minutes to update my device every month when the update releases. The first thing you want to do is read the OP from the beginning and follow the instructions. If for some reason you can't figure something out and can't find what you're looking for, just ask your question in the thread and someone will get back to you pretty quick. if you need to you can always message me and I'll try to help you out.1
I would flash the regular world version as its a GSM Unlocked model from Google (the same one I have). The Verizon SIM will work just fine in it just like any other carrier. If it was the specific Verizon model, I would have said flash the Verizon update as it probably has something that works with their specific device because it has a different chip and also works on the millimeter wave band.1
Because it's verizon and mnvo carriers, i use the vz one on my unlocked google phone on Verizon's network. I imagine a signal tweak but don't know if i see an actual better signal.
I also use the global before the verizon comes out and it works just as well, so either. -
98
WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST!
If you are looking for my guide on a different Pixel, find it here:
- Pixel 3
- Pixel 3XL
- Pixel 3a
- Pixel 3aXL
- Pixel 4
- Pixel 4XL
- Pixel 4a
- Pixel 4a (5G)
- Pixel 5
- Pixel 5a
- Pixel 6
Discussion thread for migration to 24.0+.
Note: Magisk prior to Canary 23016 does not incorporate the necessary fixes for Android 12+.
WARNING: YOU AND YOU ALONE ARE RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. THIS GUIDE IS WRITTEN WITH THE EXPRESS ASSUMPTION THAT YOU ARE FAMILIAR WITH ADB, MAGISK, ANDROID, AND ROOT. IT IS YOUR RESPONSIBILITY TO ENSURE YOU KNOW WHAT YOU ARE DOING.
Prerequisites:
- Latest SDK Platform Tools - if Platform Tools is out of date, you WILL run into problems!
- USB Debugging enabled
- Google USB Driver installed
- I recommend using Command Prompt for these instructions; some users have difficulty with PowerShell.
Make sure the Command Prompt is running from your Platform Tools directory!
Android Source - Setting up a device for development
- Follow these instructions to enable Developer Options and USB Debugging.
- Enable OEM Unlocking. If this option is grayed out, unlocking the bootloader is not possible.
- Connect your device to your PC, and open a command window in your Platform Tools folder.
- Ensure ADB sees your device:
If you don't see a device, make sure USB Debugging is enabled, reconnect the USB cable, or try a different USB cable.Code:
adb devices
If you see "unauthorized", you need to authorize the connection on your device.
If you see the device without "unauthorized", you're good to go. - Reboot to bootloader:
Code:
adb reboot bootloader - Unlock bootloader: THIS WILL WIPE YOUR DEVICE!
Select Continue on the device screen.Code:
fastboot flashing unlock
- Install Magisk on your device.
- Download the factory zip for your build.
- Inside the factory zip is the update zip: "device-image-buildnumber.zip". Open this, and extract boot.img
- Copy boot.img to your device.
- Patch boot.img with Magisk: "Install" > "Select and Patch a File"
- Copy the patched image back to your PC. It will be named "magisk_patched-23xxx_xxxxx.img". Rename this to "master root.img" and retain it for future updates.
- Reboot your device to bootloader.
- Flash the patched image:
Code:
fastboot flash boot <drag and drop master root.img here> - Reboot to Android. Open Magisk to confirm root - under Magisk at the top, you should see "Installed: <Magisk build number>
- Before you download the OTA, open Magisk, tap Uninstall, then Restore Images. If you have any Magisk modules that modify system, uninstall them now.
- Take the OTA update when prompted. To check for updates manually, go to Settings > System > System Update > Check for Update
- Allow the update to download and install. DO NOT REBOOT WHEN PROMPTED. Open Magisk, tap Install at the top, then Install to inactive slot. Magisk will then reboot your device.
- You should now be updated with root.
- Download the OTA.
- Reboot to recovery and sideload the OTA:
Once in recovery:Code:
adb reboot sideload
Code:adb sideload ota.zip - When the OTA completes, you will be in recovery mode. Select "Reboot to system now".
- Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
- Reboot to bootloader.
- Boot the master root image (See note 1):
Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.Code:
fastboot boot <drag and drop master root.img here> - Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
- Reboot your device. You should now be updated with root.
Please note that the factory update process expects an updated bootloader and radio. If these are not up to date, the update will fail.
- Download the factory zip and extract the contents.
- Reboot to bootloader.
-
Compare bootloader versions between phone screen and bootloader.img build numberIf bootloader is updated, reboot to bootloader.Code:
fastboot flash bootloader <drag and drop new bootloader.img here> -
Compare baseband versions between phone screen and radio.img build numberIf radio is updated, reboot to bootloader.Code:
fastboot flash radio <drag and drop radio.img here> - Apply update:
When the update completes, the device will be in fastbootd. Reboot to bootloader.Code:fastboot update --skip-reboot image-codename-buildnumber.zip - Boot the master root image (See note 1):
Note: If you prefer, you can manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.Code:
fastboot boot <drag and drop master root.img here> - Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
- Reboot your device. You should now be updated with root.
flash-allscript included in the factory zip. You will have to copy the script, bootloader image, radio image, and update zip into the Platform Tools folder; you will then have to edit the script to remove the-woption so it doesn't wipe your device.
The scripted commands should look like this:
Once this completes, you can reboot to bootloader and either boot your master patched image, or if you patched the new image, flash it at this time.Code:fastboot flash bootloader <bootloader image name> fastboot reboot bootloader ping -n 5 127.0.0.1 > nul fastboot flash radio <radio image name> fastboot reboot bootloader ping -n 5 127.0.0.1 > nul fastboot update --skip-reboot <image-device-buildnumber.zip>
PixelFlasher by @badabing2003 is an excellent tool that streamlines the update process - it even patches the boot image for you.
The application essentially automates the ADB interface to make updating and rooting much easier. However, it is STRONGLY recommended that you still learn the "basics" of using ADB.
For instructions, downloads, and support, please refer to the PixelFlasher thread.
- Follow the instructions on the Android Flash Tool to update your device. Make sure Lock Bootloader and Wipe Device are UNCHECKED.
- When the update completes, the device will be in fastbootd. Reboot to bootloader.
- Boot the master root image (See note 1):
Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.Code:
fastboot boot <drag and drop master root.img here> - Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
- Reboot your device. You should now be updated with root.
SafetyNet has been deprecated for the new Play Integrity API. More information here.
In a nutshell, Play Integrity uses the same mechanisms as SafetyNet for the BASIC and DEVICE verdicts, but uses the Trusted Execution Environment to validate those verdicts. TEE does not function on an unlocked bootloader, so legacy SafetyNet solutions will fail.
However, @Displax has modified the original Universal SafetyNet Fix by kdrag0n; his mod is able to force basic attestation instead of hardware, meaning that the device will pass BASIC and DEVICE integrity.
Mod available here. Do not use MagiskHide Props Config with this mod.
This is my configuration that is passing Safety Net. I will not provide instructions on how to accomplish this. Attempt at your own risk.
Zygisk + DenyList enabled
All subcomponents of these apps hidden under DenyList:
- Google Play Store
- GPay
- Any banking/financial apps
- Any DRM media apps
- Universal SafetyNet Fix 2.3.1 Mod - XDA post
To check Play Integrity status:
- Play Integrity Checker - NOTE:
MEETS_STRONG_INTEGRITYwill ALWAYS fail on an unlocked bootloader.
Points of note:
- The boot image is NOT the bootloader image. Do not confuse the two - YOU are expected to know the difference. Flashing the wrong image to bootloader could brick your device.
- While the Magisk app is used for patching the boot image, the app and the patch are separate. This is what you should see in Magisk for functioning root:
- "Installed" shows the version of patch in the boot image. If this says N/A, you do not have root access - the boot image is not patched, or you have a problem with Magisk.
- "App" simply shows the version of the app itself.
- If you do not have a patched master boot image, you will need to download the factory zip if you haven't already, extract the system update inside it, then patch boot.img.
- If you prefer updating with the factory image, you can also extract and manually patch the boot image if desired.
- Some Magisk modules, especially those that modify read only partitions like /system, may cause a boot loop after updating. As a general rule, disable these modules before updating. You are responsible for knowing what you have installed, and what modules to disable.
Credits:
Thanks to @badabing2003 , @pndwal , @Displax , @Az Biker , @ipdev , @kdrag0n , @Didgeridoohan , and last but not least, @topjohnwu for all their hard work!9Magisk Stable is now at version 24.1, so I will no longer be providing any Magisk updates.
You can use any version of Magisk now - Stable, Beta, or Canary. as long as it is 23016 or newer.
Once again, if you want to switch versions of Maagisk, it is HIGHLY RECOMMENDED that you "Complete Uninstall" within Magisk before installing the new version. Multiple instances of Magisk can break root.
If you simply want to update Magisk, the best way to do so is from within the app.
Once the February update is out, I will perform some testing with installing to inactive slot, and if it works, I will update this guide.
Given the low activity on this thread, I will probably close it if everything goes well with the next update.
Thank you all for your testing and contributions.7Magisk Canary updated to 23019
Changes:
- [Zygisk] Skip loading modules into the Magisk app to prevent conflicts
- [MagiskBoot] Change `zopfli` to a more reasonable config so it doesn't take forever
- [General] Several `BusyBox` changes
Preferred method of update is from within Magisk app.
If installing for the first time, here is the APK Download
