Today I am going to teach you how to root Google Pixel 4 via Magisk patched boot.img. Even though the device from this OEM is usually not supported in custom development, they got a niche segment of their own. Nowadays their popularity is increasing gradually. Mostly among the tech experts. Read More – Does Rooting or Unlocking void your Android Phone Warranty
However, there is a prerequisite you need to complete before rooting. That is an unlocked bootloader. Once you have that you can try various types of mods, which can flash custom recoveries like TWRP or custom ROMs such as LineageOS. Moreover, you can gain administrator privileges even! Read More – 30 Amazing Things You Can Do After Rooting Your Android
Why are we waiting? Let’s get into business.
How to Root Google Pixel 4 using Magisk Patched Boot.img
To simplify the instructions I have listed them under separate sections. The only thing you have to do is to follow the exact steps without skipping a single one. And please keep in mind that won’t take responsibility if anything happens to your phone and its data. Read More – The First 10 Things to Do After Rooting your Device
Step 1 : Install Android SDK
Firstly you need to install the Android SDK Platform Tools on your PC. As some of you are already aware this is the recommended official ADB and Fastboot binary given by Google. Just download it and extract it to any convenient location on your PC. Then you will have the platform-tools folder, which is essential for the process.
Step 2 : Enable USB Debugging and OEM Unlocking on Google Pixel 4
Then you should enable USB Debugging and OEM Unlocking on your Google Pixel 4. By unlocking OEM, you will be able to make your phone discoverable by the PC in ADB mode. And then allowing you to boot your device to Fastboot Mode.
Here’s how you gonna do that. : Enable USB Debugging and OEM Unlocking
Step 3 : Unlock Google Pixel 4 Bootloader
As the third step, you need to unlock the bootloader of the phone. Don’t ever forget that unlocking will wipe all the device data. So, perform a complete backup beforehand and then refer to our guide on How to Unlock the Bootloader on Google Pixel 4.
Step 4 : Extract Boot.img from Google Pixel 4 Firmware
Then you have to download the firmware for your Google Pixel 4. You have to download the same version that is currently installed onto your device. After downloading, extract the file to a suitable location on your PC.
Now go to the extracted Firmware folder and see whether you can see the boot.img file. Just transfer this file to your phone and follow me.
Still Can’t found boot.img or Don’t know how to find?
Step 5 : Patch Stock Boot.img via Magisk
- Firstly install the Magisk app to your phone. Read More: Everything about Magisk
- And confirm whether the boot.img has been transferred to the device.
- Now tap on Install button. (see below image)
- In the Options menu, enable both the Preserve Force Encryption and Recovery Mode options.
- Then tap Next.
- You will be navigated to the Method selection screen. Now choose Select and Patch a file.
- As the next step, browse to the extracted boot.img file and select it.
- And tap in the Let’s Go button and Magisk will now load the boot.img file and start patching.
- You will see a message saying Download Complete once the patching is done.
- Then the patched patched boot image file will be saved as magisk_patched.img in Internal Storage > Downloads.
- You can rename the file by deleting the random numbers at the end of the name. So the file will be named as magisk_patched.img.
- Finally transfer the file to the internal storage of your device for future use.
Step 6 : Boot to Fastboot Mode on Google Pixel 4
- Enable USB Debugging and connect your device to the PC using a USB cable.
- Now go to the platform-tools folder, type CMD in the address bar and press Enter. or Search CMD and open it. after that, navigate to the platform-tools folder
- That will launch the Command Prompt.
- Then type the following command in the CMD window to boot your device to Fast boot mode.
adb reboot bootloader
To verify the connection, type in the below command. You should get the device ID followed by the Fastboot keyword. if you get a reply from the command prompt, its means, the connection has been successfully established.
Disable DM Verity: Only if you have a problem with performing step 7.
Flash Magisk Patched Boot.img and Root Google Pixel 4
- First transfer the magisk_patched.img file to the platform-tools folder.
- Then type the following command in the CMD window to flash the Magisk Patched file.
fastboot flash boot magisk_patched.img
- Finally enter the following command to reboot your device to the OEM.
Now, you have successfully rooted your device.
Frequently Asked Questions (FAQ)
I unroot Google Pixel 4 but still the apps say my mobile is rooted.
Q: I completely unrooted my mobile a few days back. But still, many apps say that the device is rooted. Thereafter I rooted my device using Magisk HIDE. Please help me!
A: If your bootloader is unlocked, they will report your device as a rooted device. According to your description, Magisk Hide alone has failed to do the job. I suggest you try the “Repackage Magisk Manager” option in the Magisk Manager settings. It worked for me.
Google Pixel 4 got stuck at boot after uninstalling Magisk from app
Q: I installed Magisk via TWRP(Temp version) and installed some modules. Thereafter, I decided to uninstall Magisk using the Magisk Manager APK. Then the phone rebooted and stuck into the phone logo with the red danger logo. I tried flashing Magisk again via Temp TWRP, but now a few apps keep crashing. I tried uninstalling and reinstalling them. But couldn’t fix it. Can you help me?
A: If your phone is stuck in the boot loop or apps still crashing, then you have to wipe the Dalvik cache again. If you still need to unroot for whatever reason you can try this:
- update magisk first and then clicking uninstall from Magisk manager.
- manually flash uninstaller.zip from TWRP.
- flash the uninstaller as a module as stated in this post.
- Finally if it’s still no use, then you can factory reset the device to remove the root.
Magisk keeps uninstalling
Q: During the past 4 days I had to re-install Magisk 16.3 at least 4 times a day. Because it keeps uninstalling itself. I have previously experienced this issue with Magisk, but it has gotten worse instead of being solved.
A: After uninstalling, you can try flashing the stock boot image from your ROM/firmware package/factory image.
Unable to repack boot image
Q : I tried to install MAGISK v16.O using MAGISK installer. But there is a message saying, Installation failed with (! Unable to repack boot image! Failed! ! Installation failed). What can I do to get rid of this?
A: Just try uninstalling v15.3 first and then install v16.0 clean.
Magisk ERROR when installing
Q: I got this error when installing Magisk using TWRP. What am I supposed to do now?
Updater process ended with ERROR:1 Error installing zip file '/sdcard/MagiskManager/Magisk-v13.3.zip'
A: I advise you to use the magisk_uninstaller.zip first. From what I saw in your log, your boot. img is already patched by something else. Therefore, you need to install Magisk on your stock boot.img.
OTA Update fails after using Magisk Root [Install fail
- To start you need to fully restore to stock and erase user data. (basically, the same as starting with a brand new phone).
- Then, flash Magisk (I used the image provided on the thread about Magisk) fastboot flash boot magisk_patched.img.
- Boot to Android.
- Next, install magisk manager.
- Verify root works.
- Now, reboot to bootloader, flash default boot.img: fastboot flash boot boot.img.
- Next, reboot to android.
- Finally, apply OTA update.
MagiskHide or SafetyNet fails after an update
Magisk isn’t working
If you can boot up, but Magisk isn’t working as expected (not detecting the Magisk installation, loss of root, etc), there are a few troubleshooting steps you can try.
- First, Reboot. Sometimes this helps Magisk to mount everything as it should.
- Try removing any installed modules. So that you can see if it’s a faulty module causing issues.
- If that seems to fix it, just install the modules one at a time to find which one causes issues.
- If nothing else works, try starting from the very beginning with a new installation.
- check here: “Asking for help/reporting bugs”.
Invalid image: not signed
If you see a message in the install log, indicating “Invalid image: not signed”, that means your boot image is not signed. Don’t panic! It’s perfectly normal and nothing to worry about.
A “process error” when installing Magisk is usually caused when the app doesn’t have storage permission. So you can fix it by clearing app data.
Can’t install from the Magisk app
When attempting to install/update either the app or Magisk in the Magisk app v8+, some users experience that nothing happens. Usually, this is caused by having a custom hosts file, or similar, that is blocking the CDN used by the Magisk app (JSDelivr). The solution is to whitelist that particular URL.
I can’t root Google Pixel 4 with Magisk
If you are naive to rooting, you are at the right place. How about the people who are experienced in rooting? We are here to provide you a root solution to every feature you were wishing for. Please go to the top of the website and try the step-by-step guide again. Read More: Everything about Magisk
Do you think this guide on How to Root Google Pixel 4 Device using Magisk Patched Boot.img is helpful? If so, please share this article on Facebook, LinkedIn, etc. And we warmly welcome your queries, comments, and suggestions. Feel free to contact us.
You can join our community and open help Topic under Android.
It’s totally free! And, please don’t forget to like our Facebook page. Thank you very much! Have a nice day! 😊