I am assuming the command you are telling me to run is
Code:
fastboot flash boot <imagname>.img
How To Guide [GUIDE] Pixel 6 "oriole": Unlock Bootloader, Update, Root, Pass SafetyNet
- Thread starter V0latyle
- Start date
I have tried multiple version of Magisk now. 25.1 and 25.2
Here is the error I get when trying to flash
I downloaded the factory image of my Android release matching the build numbers from Nov 22.
Thanks
Are you sure you are flashing a correct boot.img file?
Did Magisk patching work?
file size of 98304 does not sound right
It does at least for the Pixel 5, I'm not sure what the boot image size for the P6 is
Oh yep.
@msaiko239 You're using the wrong firmware. The firmware zip should have "oriole" in the filename.
Yes, I should have caught that. What happened was I searched the build number and it matched on the wrong version...Thank you for the catch...
Man, I've literally never struggled this much to root a phone before. Out the box, I was having issues with not being able to switch the device that was in control to my pc to allow me to transfer files (which im praying is the case cause i have a new USB-C 3.0 Cable coming just in case) I've done all the steps up to getting the bootloader unlocked and flashing then renaming the boot image but now no matter what I do in deleting, installing, or updating drivers. it wont detect my device while in fastboot mode to flash boot the img file.
I know this is a bit old but any help please?
Android 13.0.0 Slider-1.2-8895132
I know this is a bit old but any help please?
Android 13.0.0 Slider-1.2-8895132
Attachments
Last edited:
Imgur makes it hard to see the images, you can just upload them directly to your post.
Make sure you're using an USB A to C cable. Don't use USB C to C.
You may be missing the fastboot driver. Get it here
Updated the image,
I did try a USB C to C cable to see but i've mainly been using the one that came with it in the box as well as one i already had and on all the USB ports i have. I have a 3.0 Cable coming in to see if that fixes anything
Unfortunately, I do have those drivers already installed prior to the process
No, after it enters fastboot mode i get no connection to it through my PC whatsoever
Sounds like a driver issue honestly. Check device manager when in bootloader mode and see if your computer recognizes an unknown device
Oddly enough.. I didn't do anything different today. I quite literally did the exact same steps as i was doing yesterday just to open the device manager to see what was showing to take a screenshot to post here and the process just... worked. flashed, Magisk shows installed and Root Checker confirms. Also, I did end up using a C to C cable and it worked.
arvylas
Senior Member
Anyone having problem with device integrity and gpay/wallet after updating to February image? Everything was working flawlessly and stopped after the Feb update. I tried updating to usnf 2.4.0 but still no luck.
Use 2.3.1 Displax mod 3.0. Make sure you aren't using other props/fingerprint mods at the same time.
arvylas
Senior Member
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
2
You don't need to mess with the slots, unless the device is on Android 12, in which case you'll want to flash the new bootloader to both slots.
Again, the instructions on updating and rooting your device are in the first post of this thread. Go back and read it, please. If you have questions about something specific, I'll be happy to help, but I took the time to write an exhaustive guide, and I would appreciate it if you used it instead of asking me to give you answers that are already readily available.1
Steps are correct, if you are already on May release, then correct, no need to flash full factory, otherwise you need to as you're using May boot.img.
As for
I don't believe that is true, where did you read that?1
In addition to what @badabing2003 said, also make sure both slots have the A13 bootloader on them before modifying your device. See this for more information. Wasn't clear how many updates you took since updating to A13 and if both slots indeed have the A13 bootloader on them already.1Re: Magisk version:
All official Magisk builds have a build number. 26.1 is 26100. Canary/debug builds are between the official releases. Refer to the Magisk releases page for the main releases.
25.2: 25200
Canary/debug: 25201 to 25999
26.0: 26000
Canary/debug: 26001 to 26099
26.1: 26100
If you have no reason to use a previous version of Magisk, just use 25.2 or 26.1; 26.0 is known to have problems.
If for whatever reason you use older Magisk releases, be aware that the fixes necessary for the Pixel 6 series were incorporated at 23016, meaning any version prior to those won't work properly. -
51
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 Pro
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!7Magisk Canary was updated to 23016 last night. This includes a fix for the vbmeta header issue, meaning that disabling verity/verification should no longer be required, and we should be able to root as we did before. This needs testing, make sure you back up your data and photos before you do this!
Additionally, for the Pixel 6 and 6 Pro, fstab will now load from /system/etc which should fix the root issue many of you were having.
Q: "If verity/verification are disabled, do I need to enable them now?"
A: No. The only thing you have to do is update to Magisk 23016.
Q: "Will enabling verity/verification wipe my data?"
A: No.
I will be updating the OP to reflect this.5Magisk 24306 (release notes) is now available on the canary channel, and I can confirm that the installation to the inactive slot OTA method is working for the April update.5
I always follow these steps once I know the OTA is available:
1. Open Magisk and select 'Uninstall Magisk -> Restore Images'
2. Open Settings and Download/Install OTA *DO NOT REBOOT*
3. Go back to Magisk and select 'Install -> Install to Inactive Slot (After OTA)' *DO NOT REBOOT*
4. Go back to Settings and 'Reboot' to finalize the OTA5
No, the tool does nothing to maintain root. It simply allows you to take the OTA. You will still need to reboot intofastbootand flash or boot from a patchedbootimage.
The steps would be:
- Restore
bootin the Magisk app - Restore
vbmetain Vbmeta Patcher - Take the OTA in System Updater
- Patch
vbmetain Vbmeta Patcher - Patch the new
bootimage in the Magisk app and copy it to your computer - Reboot into
fastboot - Boot from the new patched
bootimage - Direct Install Magisk in the Magisk App
I'm working on another tool to make it a bit easier to acquire the newbootimage in step 5, but that will likely be a few days. Hopefully we'll be able to install Magisk to the inactive slot on Pixel devices again in the future, which would consolidate steps 5-8.
New posts
-
-
General [Magisk] Magisk Zygote64_32: Enabling 32-bit Support For Apps
- Latest: badabing2003
-
