Themes / Apps / Mods PixelFlasher for Google Pixel 6 Support Thread.

Search This thread

badabing2003

Recognized Contributor
Sep 17, 2012
1,348
1,538
Is the "Automatic system updates" in developer options? Sorry I'm italian so things may have different names.
Yes
1668704718871.png
 
  • Like
Reactions: guniens
Hi @badabing2003
Sorry to bother you again but I have a question.

I ****ed up my phone installing Pixelify module (my bad, great module btw!) and I would like to format my phone and root again doing a clean setup.
First time I rooted I chosed: flash to inactive slot, wipe data so rooted image become active slot and non-rooted image the inactive one.

Is it possible to flash to the active slot? So I still have the non-rooted image in the inactive slot and I overwrite the image (****ed up) in the active one?

Thanks!
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,348
1,538
Hi @badabing2003
Sorry to bother you again but I have a question.

I ****ed up my phone installing Pixelify module (my bad, great module btw!) and I would like to format my phone and root again doing a clean setup.
First time I rooted I chosed: flash to inactive slot, wipe data so rooted image become active slot and non-rooted image the inactive one.

Is it possible to flash to the active slot? So I still have the non-rooted image in the inactive slot and I overwrite the image (****ed up) in the active one?

Thanks!
Yes,
I suggest, the following
Flash to both slots with wipe , but don't choose a patched boot image, just select the stock boot. (the first entry in the boot list)
You will have stock on both slots.
After that, select the patched boot change flash options to custom
paste it and flash it.
1669303347079.png
 
  • Like
Reactions: guniens
Yes,
I suggest, the following
Flash to both slots with wipe , but don't choose a patched boot image, just select the stock boot. (the first entry in the boot list)
You will have stock on both slots.
After that, select the patched boot change flash options to custom
paste it and flash it.
View attachment 5769211
Got it!
But why not wiping again when flashing the patched boot.img? I won't have any data as I wiped earlier

EDIT:
paste it and flash it.
Not sure about this
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,348
1,538
Got it!
But why not wiping again when flashing the patched boot.img? I won't have any data as I wiped earlier

EDIT:

Not sure about this
Wipe twice does not achieve anything, besides to get a patched image you would install Magisk, and that would be removed if you wipe again.

See the image I pasted, follow those steps, it would be self explanatory, let me know if it is still not clear.
 
  • Like
Reactions: guniens
Wipe twice does not achieve anything, besides to get a patched image you would install Magisk, and that would be removed if you wipe again.

See the image I pasted, follow those steps, it would be self explanatory, let me know if it is still not clear.
Will do like you said then!
Will do tomorrow and get back to you if I need help. Thank you so much for your help!
 
  • Like
Reactions: badabing2003

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Maybe I still have a chance because even though adb devices does not return any devices, I can fastboot reboot the device from terminal. So I can probably flash some image, but I don't want to try anything randomly right now so waiting to see if anybody has ideas. Now I wish I could cross-post this with the pixel 7 thread.
    Good news. I used Android Flash Tool to flash TD1A.221105.001 (9104446). Lost all my configurations, but phone is working again. Though I still get the "your device is corrupt" message, but now it works when you press continue and I can boot into the phone. So now I repeated all the manual command executions. And now it worked fine, and I have root.

    God I wish I wasn't so stupid yesterday and flashed the boot.img. Is there a way to get rid of the "your device is corrupt" message?!#@!
    1
    Hi all!

    I would like to root my Pixel 6 but I've been out from the modding scene since 2017 and everything is different now! My Pixel 6 is bootloader-locked, stock Android 13 manual installed when it came out via adb (didn't want to wait for the ota).

    I'm having difficult times understanding if I can root directly with this tool and also the slots thing, does it apply to my case too?

    Thanks in advance!
    I encourage everyone to read up on the guides, learn the what it takes to mod manually before jumping into using automated tools that do it for you.
    Granted the learning curve at first could be steep, but the benefits are enormous, if anything goes wrong or not according to the plans, you would know how to recover.

    If you still want to use PF without investing in learning the manual way,
    The Basic Usage steps on the Main page page or the Github page is what you need to follow.
    However considering that you're bootloader is locked, you need to unlock it first, PF has a button to do it, but it is not part of the automated process, as one would probably do this once.
    Furthermore to be able to unlock the bootloader, you need to enable developer mode, turn on OEM unlock and ADB Debugging ...
    Details of all of these are mentioned in the Guide threads, there are few great such guides links in the Help menu of PF, and you probably could find other good guides as well.

    Speaking of slots, it applies to your device, Pixel 6 has two slots, but you don't have to worry about it, the only recommendation I would make is flash to inactive slot, this way if anything goes wrong, you can still go back to the previous slot, and if everything goes well, the inactive becomes the current active and you're good,
    You repeat that on next month's release, this way you always have something to fallback to.

    Good luck and don't shy away to ask questions if anything is unclear.
    1
    I think I will follow the part about unlocking bootloader and then use your tool to root. Is this fine?
    Yes this is fine

    I still don't understand the part about slots, when should I enable "flash to inactive slot"? When I flash the boot.img or the patched_boot.img?
    Typically with PF, you don't flash the boot.img, you flash the patched_boot.img, PF automates the process for you so that with one flash you're updated and patched.

    The basic flow is as follows
    - you download a firmware, and select it in PF, no need to unpack the zip or extract files from it, just point to it, PF does the rest.
    - you process the firmware (just press the button) which extracts and shows the the boot.img
    - you select the boot and press the patch button
    - you select your flash options (this is when you choose flash to inactive slot, and keep data)
    - you flash
    1
    Did everything and all went like a charm! So easy and straightforward!

    I still have a question about monthly updates: Which updates I'm allowed to do directly on phone and which need to be done via PF to preserve root?

    Thanks again for your help!
    I wouldn't do anything on the phone,
    Much easier / quicker / reliable to do on PF,
    Repeat the process as you did now.
    1
    Yes I think the same but if I remember correctly there're play system updates, security updates and system updates (maybe also feature drops or they count as system update?). Which of then is mandatory doing in PF?
    Nothing is mandatory to do it in PF, it's a choice.
    Security update / System Updates / Feature drops are all part of the firmware updates / OTA updates.
    Play store updates are not part of it. I personally choose firmware updates through PF, I stay away from OTA (but that's my choice), if you choose to do OTA update and retain root, you have to follow the guides.
  • 15
    PF_promo-banner.png

    This is the support thread of PixelFlasher for Google Pixel 6
    PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/updating with extra features.


    Basic mode: Should suit most users. Some of the features in basic mode are:
    • Simple UI interface, click and go. No more command line, no more placing all files in one directory.
    • boot.img management UI, select the boot.img file to patch and click the patch button. Fully Automated patching with Magisk (without user interaction) and perform upgrades without losing root.
      No more manually extracting files transferring to the phone, patching / re-flashing and doing multiple reboots.
      No more setting airplane mode and clearing storage to retain Safetynet passing.
    • Display details of boot.img.
      • SHA1 checksum.
      • Origin (file it was extracted from).
      • Whether it is patched or not, and if it is patched.
        • What version of Magisk was used to patch it.
        • On what device it was patched.
        • Date of patching.
        • The SHA1 of the source boot.img file.
      • Option to Live boot from a choice of boot.img.
    • Choose to keep data or wipe data while flashing.
    • Ability to flash even if multiple devices are connected to the computer.
    • Display information about the phone.
      • ID
      • Hardware model.
      • Current installed firmware (build).
      • If it is rooted with Magisk.
      • Magisk version (Magisk Tools).
      • Magisk Manager version (the app).
      • List installed Magisk modules.
      • Connection mode (Adb | Fastboot | Sideload | Recovery).
      • Bootloader version.
      • Android OS API version.
      • Convenient quick links to download Android platform tools or device firmware.
    • Magisk Manager installation UI, screenshot. Supported versions:
      • stable
      • beta
      • canary
      • debug
    • Magisk modules management, enable / disable modules selectively, this comes in handy to disable suspect modules before an upgrade screenshot:
      • Name
      • Version
      • Description
      • Enabled / Disabled.
    • Display Android Platform Tools (SDK) version and warn / block if the version is old.
    • Install APK file from the computer onto the device.
    • Advanced features are hidden to keep the interface simple and easy to follow.
    • A lot of checks and validations for smooth operation.
    • Automatic check for program updates.
    Expert mode: (should only be turned on by experienced users). In addition to the basic features, you get:
    • The ability to flash custom ROM (with or without patching boot.img)
    • Option to flash to both slots.
    • Option to flash to inactive slot.
    • Options to disable verity and or verification.
    • Ability to change the active slot.
    • Ability to live boot to custom boot.img (temporary root).
    • Ability to boot to recovery.
    • Ability to flash custom image: boot, recovery, radio, kernel, ...
    • Ability to sideload an image.
    • Lock / Unlock bootloader.
    • Option to gain temporary root (good for testing or checking things out).
    • SOS Disable Magisk modules to get out of bootloop (experimental).

    For full details on where to download / usage and feature set of the tool, visit the main thread at XDA or the project's Github page.

    Troubleshooting:
    • See this post.
    • Generate Sanitized support.zip file (File Menu) and submit that with your report.
    Note: This thread is meant for issues and problems faced in Google Pixel 6 devices, generic issues that are device agnostic should be discussed in the main thread.
    5
    Thank you for the consideration.
    No donation, this is simply giving back to the community that has given me a lot over the years.
    5
    Update:
    Version 2.0.1 which includes a hotfix for issue reported here.
    5
    New Release:
    April 17, 2022 v2.3.0 release
    • Optional automatic check for updates feature.
    • Added help menu links to:
      - Report an issue
      - Feature Request
      - PixelFlasher Project Page
      - PixelFlasher Community (Forum)
      - Homeboy76's Guide
      - V0latyle's Guide
      - Open Configuration Folder
      - Check for New Version
    • Icons for menu items.
    • Link to download Pixel Firmware.
    • Link to download Android Platform Tools.
    • Unlock Bootloader.
    • Lock Bootloader.
    • SOS (experimental) - disable Magisk modules to get out of bootloop.
    • Additional flashing options:
      - product
      - system
      - system_ext
      - system_other
      - vbmeta_system
      - vbmeta_vendor
    • Added sideload flashing option.
    • Updated documentation.
    • Further improved console messages for troubleshooting.
    • Linux build using Github Actions.
    • Manual build for Kali Linux.
    5
    PixelFlasher 4.0.0 pre-release:
    Sep 25, 2022 v4.0.0 pre-release
    • New Feature: On supported devices, where device is not yet rooted (or adb shell su not allowed), an option to control the Magisk Manager GUI (drive UI) to programmatically control the app through UIAutomator and create a patched boot.img
      See Patching flow chart for details.
    • New Feature: Detect if Magisk Manager is at a higher version than installed Magisk, warn the user of a potential rare corner case and offer a choice of patching method.
    • New Feature: Temporary Root, when flashing if you choose this option, the phone will be flashed with unpatched boot.img, but Live boot to patched boot.img to provide a temporary root.
    • New Feature: Warn the user to flash both bootloader slots if their device is a Tensor device (Pixel 6, Pixel 6a, Pixel 6 Pro), if current version of OS is lower than Android 13.
    • New Feature: Flash to inactive slot. Unlike OTA flashing factory image flashing is always done on the current active slot, with this option selected, PixelFlasher will write to inactive slot. This allows one to revert to current working state in case anything goes wrong. This feature combined with Temporary Flash provides best method to test a new firmware without risking losing current working setup.
      Note: You should avoid this option if you are on a Tensor device and are upgrading from Android 12 to Android 13 (see the previous feature).
    • New Feature: Detect and operate on devices that are in Sideload or Recovery mode.
    • New spinner to indicate PixelFlasher activity.
    • Renamed Reload button to Scan, to better reflect the button's function. After a scan print the count of devices found.
    • PixelFlasher previously used MD5 to uniquely identify boot images (patched or otherwise), with version 4.0.0 PixelFlasher now uses SHA1 instead of MD5.
      This has no bearing on the functionality, it just better aligns with Magisk way of identifying and tagging boot images.
    • PixelFlasher now extracts the embedded SHA1 of a Magisk Patched images (only available in newer devices) and assures that it matches the source boot.img's SHA1.
      This is just an extra validation.
    • Code cleanup / refactoring, adding more validations and exception handling.
    • Print debug details when encountering non compliant Magisk modules.
    • Firmware link now takes you to the device's download page instead of just the general download page.
    • To better reflect the file details, transferred and stored boot.img files are now suffixed by their shortened SHA1, while magisk_patched.img files are now suffixed by shortened SHA1 of their source boot.img.
    • Allow sideload even if bootloader is locked.