قالب وردپرس درنا توس
Home / Tips and Tricks / Pixel 4 Bootlooping after installing a Magisk module? To fix the problem without TWRP «Android :: Gadget Hacks

Pixel 4 Bootlooping after installing a Magisk module? To fix the problem without TWRP «Android :: Gadget Hacks



TWRP is only months after release for Pixel 4 and 4 XL ready. However, since you can already root with Magisk and tinker with the operating system, your phone may stop booting and you may not have a custom recovery installed to fix the problem. Luckily, there is still a way out.

This recovery method uses a core-only version of Magisk to disable all modules so you can boot back into Android. XDA Member Tulsadiver has provided a number of Pixel 4 and 4 XL image files to help you recover from this bootloop. You still need to do a few extra things to get it up and running, as the file itself is a temporary fix. However, follow the instructions below to get done.

Step 1
: Download the Magisk-only image.

You've won because you're trying to remove Pixel 4 from a bootloop. & # 39; I can not do anything with it on the phone side. However, with a modified boot image file and a computer, you can use fastboot commands to bring them back to life! Download the file to your computer using one of the links below.

After downloading move it to your desktop for easier access later.

Step 2: Download the Platform Tools Package

Your only lifesaver without TWRP will be Fastboot. However, you will need Google's SDK Platform Tools package to send fastboot commands to your phone. Therefore download the tool via one of the following links. When it's done, extract the ZIP file and place the extracted folder on your desktop .

Step 3: Booting in Fastboot Mode

You must set your phone to accept the commands required for the recovery process. Your phone is probably already off since it was started. Hold down the power key and the volume key at the same time until the fastboot menu is displayed. If the phone is still in active boot mode, press and hold the volume key during one of the reboots until the fastboot menu is displayed.

Now make sure that your phone is connected to your computer via USB cable .

Step 4: Open a Command Window in Platform Tools

Now open a command prompt on your computer. If you are using Windows, press the Windows key on your keyboard, type "cmd" and press Enter. If you are using Linux or Mac, open the Terminal App in your Applications folder.

Type in "cd" and add a single space, but do not press Enter . Instead, drag the folder platform-tools from your desktop and drop it in the Command window. This completes the full path of the folder. Once this happens, press Enter .

If you need more help, read our complete guide below.

Step 5: Flash the Magisk-only image

Finally! It's time to bring back your pixels 4 from the dead. If you are using Windows, type fastboot boot and add a space, but do not press Enter . If you are using Mac or Linux, enter ./ fastboot boot and add a space. However, do not press yet the Enter key .

Now drag the Magisk Core – Download only the image file downloaded in Step 1 from your desktop and place it directly above the command window. This completes the full path for the location, giving you a command that looks something like the one below. If so, go to and press Enter

  Quick Launch C:  Users  YourName  Desktop  image-newpixel4.img 

Your phone should automatically reboot to Android at this point, but this is temporary. If you reboot at this time, you will return to bootlooping, as the problem is not resolved yet. So let your phone be connected to the computer for the time being and do not close the terminal window yet.

Step 6: Enable Developer Options

Return to Android, go to Settings -> By Phone, and then tap the "Build number" entry seven times in quick succession to activate the developer options. If you've never done this before, you can visit our full tutorial below.

Step 7: Enable USB Debugging

Now open the Developer Options menu and enable "USB Debugging" at the top. If you have never used ADB with this phone, you will be asked if you want to allow "USB debugging". Select the check box next to "Always allow" and click "OK" in this popup. Read the complete guide below for more help on this part.

Step 8: Removing the Magisk modules

The last and final step in this entire recovery process – you have two options here. You can open the Magisk Manager app and look in the Module section for the module that caused the bootloop. Tapping on the trash icon and then restarting will fix the problem. If you can not open Magisk Manager because it's being forcibly closed, keep reading to get it up and running again.

It's time to run the ADB command to remove all installed Magisk modules from your system. Make sure your phone is connected to your computer with a USB cable. Now copy the following command into the terminal window you opened in step 4 and press Enter to confirm your selection.

Windows command:

  adb wait-for-device shell magic -remove-modules 

mac & linux command

  adb wait for device shell magisk --remove-modules 

The The above command deletes your Magisk modules and restarts the system automatically. If you're back after the reboot, go to the Magisk Manager app and you'll see that everything looks good, even with full root access. What kind of bootloop?

If you go to the "Modules" section, you will see that there is nothing at this time, which means you need to start over. You have protected your device from a complete data deletion, so installing some modules costs only a small price.

(1) Full root access, Magisk is up to date and SafetyNet checks are successful! (2) The modules have been deleted, so it's a reboot! At least you have not lost all your data this time.
Cover picture and screenshots of Stephen Perkins / Gadget Hacks [19659043]

Source link