How to get Magic Eraser on any Pixel with Android 12 - Android Police

Google's camera magic always comes to the latest Pixel devices in the form of software. This year, we got the new Magic Eraser tool to help remove unwanted objects from the background of pictures. This was pitched as an exclusive feature for the Pixel 6 and 6 Pro, but only a day after the first customers are holding the new phone in their hands, Magic Eraser is already available on other Pixel devices running Android 12.

Getting Magic Eraser on your Pixel phone is simple and only requires sideloading the latest version of the Google Photos app from a Pixel 6. I can confirm this using the Google Photos APK from my Pixel 6 and installing it on my Pixel 5, 5a, 4 XL, and 4a. Magic Eraser works flawlessly on all of them! Do note each device is running Android 12, which is required to get this working.

Here's what you need to do:

Download Split APKs Installer (SAI) from the Google Play Store.
Download the Google Photos APKs file. (The regular APK over at APK Mirror most likely won't work for you — you need this APK, as it's coming straight from the Pixel 6, which is what enables Magic Eraser.)
Open SAI, tap "Install APKs" and select "System file picker." You'll need to grant it the permission to access your files on your device.
Image Gallery (3 Images)
Find and select the Google Photos .apks file you've just downloaded. It should show up under Recent files, but it will also be in your Downloads folder.
Hit "Install" and allow SAI to install unknown apps. A pop-up will take you to the right settings screen.
Image Gallery (3 Images)
Click "Update" in the system install prompt.
Open Google Photos and enjoy Magic Eraser! You can access it by hitting the Edit button when viewing an image and navigating to the Tools section. A tutorial will then tell you how Magic Eraser works.

Image Gallery (3 Images)

While Magic Eraser is easy to install right now, we aren't sure how long it will stay this way. There is a chance a future Google Photos update could remove this functionality or Google could disable it server-side, but for now, it works.