How To Repair Boot Windows With No Root Android Phone To Sd Card

How to Root your Android smartphone: Google, OnePlus, Samsung, Xiaomi, and others as well!

Welcome to the XDA-Developers Root Directory. Here, y'all tin can find root tutorials for virtually devices that are on the XDA Forums. Learn how to root any Android device, fifty-fifty the all-time Android phones! If you don't see your device listed or you see a misplaced link, send a message to Skanda Hazarika (SkandaH on the forums) with the device details.

Table of Contents:

What is Root?
How to root a popular Android smartphone
- ASUS
- Google
- Motorola
- OnePlus
- Samsung
- Sony
- Xiaomi
How to root any Android device
- Identifying the type of the boot image
- Locating the kicking image
- Patching the boot image
- Verification
One Click Root Methods in 2022

What is Root?

For those new to the world of rooting, acquiring root access essentially grants you elevated permissions. With root access, you are able to alter or supplant system applications and settings, run specialized apps that require administrator-level permissions or perform other operations that are otherwise inaccessible to a normal Android user. And by proxy, y'all may likewise exist able to access certain "hidden" device features or apply existing features in new ways.

DISCLAIMER: Rooting a device may void the warranty on the device. It may likewise brand the device unstable or if not washed properly, may completely brick the device. XDA-Developers or the author does not have any responsibility for your device. Root at your own take a chance and only if you understand what y'all are doing!

How to root a popular Android smartphone

We tin go along about the virtues of root access advertizement infinitum, just we'll stop for now because we can sense you're salivating at the prospect of root access and what you lot tin do with your device once root is achieved. Head to the post-obit section to begin the journey. You should detect device-specific root guides for latest flagship models from every major OEM beneath.

ASUS

For other ASUS devices, kindly check out the ASUS department of our forums. You should be able to find like fine-tuned guides for your device under the device sub-forums. Y'all can also follow the generic rooting guide from this tutorial.

Google

For other Google devices, kindly check out the Google section of our forums. You should be able to find similar fine-tuned guides for your device nether the device sub-forums. You can as well follow the generic rooting guide from this tutorial.

Motorola

For other Motorola devices, kindly check out the Motorola section of our forums. You should be able to find like fine-tuned guides for your device under the device sub-forums. You can as well follow the generic rooting guide from this tutorial.

OnePlus

For other OnePlus devices, kindly bank check out the OnePlus section of our forums. You lot should be able to discover similar fine-tuned guides for your device under the device sub-forums. You can likewise follow the generic rooting guide from this tutorial.

Samsung

For other Samsung devices, kindly bank check out the Samsung section of our forums. You should be able to find similar fine-tuned guides for your device nether the device sub-forums. You can also follow the generic rooting guide from this tutorial.

Sony

For other Sony Xperia devices, kindly check out the Sony department of our forums. You lot should be able to find similar fine-tuned guides for your device under the device sub-forums. You tin can also follow the generic rooting guide from this tutorial.

Xiaomi

For other Mi, Redmi, and POCO branded devices, kindly check out the Xiaomi department of our forums. You should be able to find similar fine-tuned guides for your device nether the device sub-forums. You can also follow the generic rooting guide from this tutorial.

How to root whatever Android device

Present, Magisk is the de-facto rooting solution that lets y'all have root admission by leaving the system partition untouched and modifying the boot partition. This is why it's referred to as a "systemless" root method.

Before getting started with Magisk, make sure that:

You have access to a PC/Mac with adb and fastboot installed.
The bootloader of the target Android device is unlocked.
- For Samsung devices, unlocking the bootloader will trip KNOX.

Footstep 1: Identifying the type of the kick epitome

Download the latest version of the Magisk app from the projection'south GitHub repository. Since the APK of Magisk is hosted outside of the Google Play Shop, you may need to let sideloading apps from unknown sources commencement and then manually install the downloaded parcel.

Later installing, open the Magisk app. Yous should encounter a screen similar this:

Now, we need to note down the values of the following parameters:

Ramdisk
A/B
SAR

Pace 2: Locating the kick image

In order to patch the boot epitome for your device, you lot demand to extract it from the official firmware packages. In example you lot're using a custom ROM like LineageOS, then the flashable Zip file contains the boot image.

Case I: Y'all have access to the recovery-flashable ZIP file

If you have a device that still uses the A-only partition scheme, and then you can find the boot.img right within the recovery-flashable Zippo file. But excerpt it using a suitable archiver plan.

Find the boot.img file inside POCO M3's recovery Cipher

However, if your device utilizes the A/B segmentation scheme, then the boot image and other division images are farther packed inside a file named payload.bin as shown beneath.

The recovery ZIP of the Google Pixel 5 contains a payload.bin file

In that case, you take to extract the payload.bin file first, then apply one of the community-adult payload.bin unpackers to get the boot.img out of information technology. We strongly suggest y'all opt for the extractor written in Go as information technology is cross-platform and has been actively developed.

Known as "payload-dumper-become", this fork even allows end-users to extract a unmarried segmentation image without unpacking the whole payload.bin, which is particularly useful for this usage scenario.

First, utilize the -l parameter to list the partition images inside the payload.bin.

              payload-dumper-go -l payload.bin

Then use the -p parameter with the proper name of the boot image (usually stored as "kicking") to excerpt it.
```
              payload-dumper-go -p boot payload.bin            
```

Extracting the boot.img of the ASUS ROG Phone 5 from its payload.bin

Case II: You have access to the Fastboot-flashable epitome

A handful of OEMs like Google and Xiaomi provide Fastboot-flashable manufacturing plant images for their devices. If you managed to grab such a package, then the raw kicking.img tin can easily be extracted from the annal.

The location of the boot.img inside the Google Pixel 5'south Fastboot firmware

Special Case: Samsung

Samsung Galaxy devices don't a traditional Fastboot interface, hence their manufactory images are packed differently.

Utilize Samsung Firmware Downloader to download the mill image for your model.
Unzip the decrypted package and locate the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5.

Step 3: Patching the boot image

At present that we have the kicking image in hand, nosotros should proceed with the patching part.

Instance I: The value of the "Ramdisk" parameter is "Yes"

Re-create the kick paradigm to your device. In fact, you tin patch it on a different Android device than the target one, only y'all need to install the Magisk app on the secondary device also.
Press the Install button in the Magisk card.
Choose Select and Patch a File in Method, and select the stock boot image.

The Magisk app will patch the image to [Internal Storage]/Download/magisk_patched_[random_strings].img.

Copy the patched image to your PC with ADB:

              adb pull /sdcard/Download/magisk_patched_[random_strings].img

Flash the patched boot image to your device. For most devices, reboot into Fastboot mode and flash with the post-obit command:
```
              fastboot flash boot /path/to/magisk_patched.img            
```
Reboot and bask root access!

Continue in mind that it is possible to patch the boot paradigm on the wing on legacy devices having boot ramdisk through a custom recovery like TWRP, merely the method is no longer recommended on modern devices. Having said that, if yous have an old phone and want to stick with the custom recovery route, the steps are equally follows:

Download the Magisk APK.
Rename the .APK file extension to .Nix (eastward.1000. Magisk-v23.0.APK → Magisk-v23.0.Cypher).
Flash the ZIP file just like any other ordinary flashable ZIP.

Note that the sepolicy.rule file of modules may exist stored in the enshroud partition, so don't clear it.
Check whether the Magisk app is installed. If it isn't installed automatically, manually install the APK.

Case II: The value of the "Ramdisk" parameter is "No"

In this instance, y'all need to locate the recovery.img file from the factory image of your device instead of boot.img file. This is because Magisk needs to be installed in the recovery partition, which means you will accept to reboot to the recovery mode every time you desire root access.

Copy the recovery image to your device (or a secondary device with the Magisk app installed).
Printing the Install push on the Magisk card.
Choose "Select and Patch a File" in method, and select the stock recovery image.
The Magisk app will patch the epitome to [Internal Storage]/Download/magisk_patched_[random_strings].img.

Copy the patched image to your PC with ADB:

              adb pull /sdcard/Download/magisk_patched_[random_strings].img

Wink the patched recovery image to your device. For most devices, reboot into Fastboot mode and flash with the following command:
```
              fastboot wink recovery /path/to/magisk_patched.img            
```
Reboot.

At this stage, there are three possible scenarios:

Power up normally: Y'all'll end upwards with no Magisk, i.e. no root access.
Recovery Fundamental Combo → Splash screen → Release all buttons: The organization should kicking with Magisk and total root access.
Recovery Key Combo → Splash screen → Continue pressing volume up: To admission the stock recovery fashion.

Special Instance: Samsung

Re-create the extracted AP tar file to your device.
Press the Install button on the Magisk menu.
If your device doesn't have boot ramdisk, brand sure Recovery Mode is checked in options.
Cull Select and Patch a File in Method, and select the AP tar file.
The Magisk app volition patch the whole firmware file to [Internal Storage]/Download/magisk_patched_[random_strings].tar
Copy the patched tar file to your PC with ADB:
```
              adb pull /sdcard/Download/magisk_patched_[random_strings].tar            
```
- Don't attempt to copy over the MTP interface as it is known to decadent big files.
Reboot to download fashion. Open Odin on your PC, and flash magisk_patched.tar as AP, together with BL, CP, and CSC from the original firmware.
- Don't choose HOME_CSC because we want to wipe data.
Your device should reboot automatically in one case Odin finished flashing. Concur to do a factory reset if asked.
If your device doesn't have boot ramdisk, reboot to recovery now to enable Magisk.
Install the latest Magisk app and launch the app. It should testify a dialog asking for additional setup. Let information technology do its job and the app will automatically reboot your device.
Reboot and enjoy root access!

Pace 4: Verification

The concluding step is to verify that everything is working properly. Locate the newly installed Magisk app and open it. We desire to run across a version number abreast the "Installed" parameter. This ways y'all take successfully obtained root. Great job!

One-Click Root Methods in 2022: Kingroot, KingoRoot, and others

A few years back, several generic root methods like Kingroot, KingoRoot, and others gained popularity as "i-click root" methods, promising root and related benefits with minimal steps and knowledge needed by the user. Still, equally Android has matured, these one-click root methods are no longer valid for modern smartphones and Android devices in 2022.

We strongly dissuade against the use of these generic root methods as they are either ineffective or worse, pack in malware that can greatly compromise your device and crusade you losses. Practically all of these methods are no longer recommended. You should follow the steps listed above for an constructive root solution for most Android devices.

We hope this guide not only points you to the right threads for rooting your device simply likewise provides general rooting instructions that can exist applied for a large majority of Android devices generally. We'll be updating this guide with links to further guides for specific phones, and so bank check dorsum again in the futurity.