www.droidwin.com Open in urlscan Pro
2606:4700:20::681a:de8 Public Scan

Back to summary

URL:
https://www.droidwin.com/patch-stock-boot-image-flash-magisk/
Submission: On February 23 via manual (February 23rd 2023, 11:58:32 am UTC) from AE — Scanned from DE

Form analysis
3 forms found in the DOM

GET https://www.droidwin.com/

<form role="search" method="get" class="search-form" action="https://www.droidwin.com/"> <label> <span class="screen-reader-text">Search for:</span> <input type="search" class="search-field" placeholder="Search …" value="" name="s" tabindex="-1">
  </label></form>

POST https://www.droidwin.com/wp-comments-post.php

<form action="https://www.droidwin.com/wp-comments-post.php" method="post" id="ast-commentform" class="comment-form">
  <p class="comment-notes"><span id="email-notes">Your email address will not be published.</span> <span class="required-field-message">Required fields are marked <span class="required">*</span></span></p>
  <div class="ast-row comment-textarea">
    <fieldset class="comment-form-comment">
      <legend class="comment-form-legend"></legend>
      <div class="comment-form-textarea ast-col-lg-12"><label for="comment" class="screen-reader-text">Type here..</label><textarea id="comment" name="comment" placeholder="Type here.." cols="45" rows="8" aria-required="true"></textarea></div>
    </fieldset>
  </div>
  <div class="ast-comment-formwrap ast-row">
    <p class="comment-form-author ast-col-xs-12 ast-col-sm-12 ast-col-md-4 ast-col-lg-4"><label for="author" class="screen-reader-text">Name*</label><input id="author" name="author" type="text" value="" placeholder="Name*" size="30"
        aria-required="true"></p>
    <p class="comment-form-email ast-col-xs-12 ast-col-sm-12 ast-col-md-4 ast-col-lg-4"><label for="email" class="screen-reader-text">Email*</label><input id="email" name="email" type="text" value="" placeholder="Email*" size="30"
        aria-required="true"></p>
    <p class="comment-form-url ast-col-xs-12 ast-col-sm-12 ast-col-md-4 ast-col-lg-4"><label for="url"><label for="url" class="screen-reader-text">Website</label><input id="url" name="url" type="text" value="" placeholder="Website" size="30"></label>
    </p>
  </div>
  <p class="form-submit"><input name="submit" type="submit" id="submit" class="submit" value="Post Comment »"> <input type="hidden" name="comment_post_ID" value="242" id="comment_post_ID"> <input type="hidden" name="comment_parent"
      id="comment_parent" value="0"></p>
  <p style="display: none;"><input type="hidden" id="akismet_comment_nonce" name="akismet_comment_nonce" value="3dfeaf8f9e"></p>
  <p style="display: none !important;"><label>Δ<textarea name="ak_hp_textarea" cols="45" rows="8" maxlength="100"></textarea></label><input type="hidden" id="ak_js_1" name="ak_js" value="1677153504035">
    <script>
      document.getElementById("ak_js_1").setAttribute("value", (new Date()).getTime());
    </script>
  </p>
</form>

GET https://www.droidwin.com

<form action="https://www.droidwin.com" method="get"><label class="screen-reader-text" for="cat">Downloads</label><select name="cat" id="cat" class="postform">
    <option value="-1">Select Category</option>
    <option class="level-0" value="125">Android</option>
    <option class="level-0" value="17">Android</option>
    <option class="level-0" value="607">Android Tools</option>
    <option class="level-0" value="780">Apple</option>
    <option class="level-0" value="19">Custom ROMs</option>
    <option class="level-0" value="1">Default</option>
    <option class="level-0" value="11">Downloads</option>
    <option class="level-0" value="115">Facebook</option>
    <option class="level-0" value="890">Games</option>
    <option class="level-0" value="121">Google</option>
    <option class="level-0" value="284">Google</option>
    <option class="level-0" value="110">Google Apps</option>
    <option class="level-0" value="85">Google Camera</option>
    <option class="level-0" value="128">Google Chrome</option>
    <option class="level-0" value="107">Instagram</option>
    <option class="level-0" value="782">iPad</option>
    <option class="level-0" value="781">iPhone</option>
    <option class="level-0" value="507">LG</option>
    <option class="level-0" value="783">Mac</option>
    <option class="level-0" value="48">Magisk Manager</option>
    <option class="level-0" value="173">Magisk Modules</option>
    <option class="level-0" value="181">Motorola</option>
    <option class="level-0" value="8">News</option>
    <option class="level-0" value="182">Nokia</option>
    <option class="level-0" value="1114">Nothing Phone</option>
    <option class="level-0" value="183">OnePlus</option>
    <option class="level-0" value="549">Oppo</option>
    <option class="level-0" value="406">Pixel Series</option>
    <option class="level-0" value="352">Realme</option>
    <option class="level-0" value="185">Redmi</option>
    <option class="level-0" value="9">ROMs</option>
    <option class="level-0" value="22">Root</option>
    <option class="level-0" value="213">Samsung</option>
    <option class="level-0" value="21">Stock Firmware</option>
    <option class="level-0" value="14">Tips and Tricks</option>
    <option class="level-0" value="317">TWRP</option>
    <option class="level-0" value="89">TWRP Recovery</option>
    <option class="level-0" value="550">Unbrick</option>
    <option class="level-0" value="13">Unlock Bootloader</option>
    <option class="level-0" value="240">Vivo</option>
    <option class="level-0" value="118">WhatsApp</option>
    <option class="level-0" value="100">WhatsApp</option>
    <option class="level-0" value="18">Windows</option>
    <option class="level-0" value="20">Windows</option>
    <option class="level-0" value="184">Xiaomi</option>
  </select></form>

Text Content

Skip to content
MENU MENU
* TIPS AND TRICKS
* ROOT
* UNBRICK ANDROID
* APPLE
* STOCK FIRMWARES

Search for:
Search

PATCH STOCK BOOT IMAGE VIA MAGISK AND FLASH IT USING FASTBOOT

July 26, 2019 May 21, 2021 / Magisk Manager, Stock Firmware, Tips and Tricks /
By Sadique Hassan

In this guide, we will be providing detailed steps to patch a stock boot image
file using Magisk and then to subsequently flash it via Fastboot commands.
Thanks to the open-source nature of Android, there are a plethora of tweaks that
you could try out. Once you have unlocked the device’s bootloader, the
possibilities stand endless. From flashing custom ROMs such as Pixel Experience
and AOSPs to replacing the stock recovery via TWRP, there is a lot to be
achieved. Along the same lines, you could also root your device via Magisk.

Once rooted, you could then gain access to the system partition and carry out a
plethora of tweaks. For example, you could install Substratum Themes, Xposed
Frameworks, Magisk Modules. However, as far as rooting is concerned, it could be
achieved via two different methods: via TWRP or without TWRP via the patched
boot.img file. So before going on any further, let’s focus on the latter once it
is going to be the crux of this article. [Update 1: Added a Fix for Android 11
Boot.img patch issues].

--------------------------------------------------------------------------------

* How to Root Pixel 4, 4A, 4A XL running Android 11 without TWRP
* Update Magisk ZIP and Magisk Manager (without TWRP)
* How to Install OxygenOS OTA on Rooted OnePlus devices
* How to Root All Vivo Devices via Magisk without TWRP

Table of Contents

* Why Root using Patched Boot.Img file
* Patch Stock Boot Image via Magisk | Flash it via Fastboot
* Prerequisites
* Downloads
* Check for Ramdisk
* STEP 1: Get Stock Boot.img File from Stock ROM
* STEP 2A- Patch the Stock Boot Image File using Older Magisk
* STEP 2B: Patch Stock Boot Image File using Newer Magisk
* STEP 3- Install the Patched Boot Image using Fastboot

WHY ROOT USING PATCHED BOOT.IMG FILE

There exist two different methods to root any Android device. In the first one,
you just have to flash the Magisk Installer ZIP file via TWRP and your device
stands rooted. However, the next method calls for extracting the stock boot.img
file from the stock firmware. Nowadays these stock ROMs themselves come in
payload.bin or OZIP format. As a result, you will first have to decrypt this
firmware packaged and then get hold of the stock boot.img. After this, you will
have to patch this boot.img via Magisk.

This will in turn give you a patched boot.img file. Finally, you will have to
flash this patched boot.img file Fastboot to gain root access. So all this begs
for an important question- why choose this longer root method? Well, the thing
there do exists many Android devices that don’t have a working TWRP build. And
for them, this is the sole method to root their device. So with that said,
let’s now get on with the guide to Patch Stock Boot Image via Magisk and Flash
it using Fastboot.

--------------------------------------------------------------------------------

* How to Fix TWRP Error 70 [With Screenshots]
* How to Fix TWRP Error 20 GApps after flashing LineageOS
* Fix TWRP Error 7 (While Flashing Custom ROM via TWRP)
* How to Boot into Recovery (TWRP/Stock) from Fastboot Mode

--------------------------------------------------------------------------------

PATCH STOCK BOOT IMAGE VIA MAGISK | FLASH IT VIA FASTBOOT

Before we list out the instructions, there are a few requirements and downloads
that you need to check-mark. Make sure to go through them and then only proceed
with the instructions. Droidwin and its members wouldn’t be held responsible in
case of a thermonuclear war, your alarm doesn’t wake you up, or if anything
happens to your device and data by performing the below steps.

PREREQUISITES

* Make a complete backup of all your data. While creating a patched boot.img
file or flashing it via Fastboot doesn’t wipe the data partition, but it is
still advisable to be on the safer side and take a backup beforehand.
* Next up, it goes without saying that you need to unlock the bootloader on
your device. You may also refer to our guide on how to Unlock the Bootloader
of Android Devices.
* Also, download and install Android SDK Platform Tools on your PC. This will
provide you with the necessary ADB and Fastboot binaries.
* Finally, enable USB Debugging on your device. This will be needed so that
your device gets recognized by the PC in ADB Mode. This ADB Mode will be used
later on to boot your device to Fastboot Mode. Hence go to ‘Settings’ >
‘About Phone’ > Tap on the ‘Build Number’ 7 times > Go back to ‘Settings’ >
‘Developer Options’ > Toggle on the ‘USB Debugging’. [Don’t Miss: How to
Enable USB Debugging on a Broken Android Device’s Screen? ]

DOWNLOADS

* Download the latest Magisk Manager APK File. Since version 22, it is known as
the Magisk App and comes bundled in with both the Magisk ZIP and Magisk APK.
* Then download the stock ROM for your device. You could get it from the
respective OEMs website support or download section. We will explain in the
next section how to get hold of the stock boot.img file from the stock ROM.
* NOTE: You could also get the stock boot.img file directly from your device,
without even downloading the entire firmware. The only major prerequisite is
that your device needs to have the TWRP Recovery installed (or ready for
one-time boot). If you have it, then do check out our guide: Extract Boot.img
Directly from Device Without Downloading Firmware.

CHECK FOR RAMDISK

You would only be able to proceed with the below steps if your device has
Ramdisk. To check for the same, launch the Magisk App, and refer to the section
under Magisk. if it says, YES (see below image), you are good to proceed ahead
with the below steps. However, if it says NO under Ramdisk, then the below steps
wouldn’t work. In that case, you will have to refer to our other guide: Install
Magisk in Recovery and Root Android [No Ramdisk].

That’s it. You may now proceed with the steps to Patch the Stock Boot Image via
Magisk and Flash it using Fastboot.

STEP 1: GET STOCK BOOT.IMG FILE FROM STOCK ROM

To begin with, you will have to extract the stock boot.img file. And as opposed
to earlier times, the process is a little bit more complicated nowadays. You
cannot simply extract the firmware and get the required partition files (such as
vbmeta.img, system.img, boot.img, etc). The reason is that many OEMs packs the
ROM’s IMG files inside an encrypted package. For example, OnePlus has these
files inside payload.bin, Realme, and Oppo have their files inside the OZIP
format, and so on. In that case, you may refer to our below guides to get the
stock boot.img file:

* Extract payload.bin and get the stock boot image file
* How to Extract OZIP Realme/Oppo Stock ROM (Firmware)
* Extract Stock Boot.img from OnePlus OxygenOS Stock ROM
* How to Extract Sony Boot.sin and get the Stock Boot.img File
* How to Extract Boot.img from LG KDZ or DZ Firmware.

Now that you have got hold of the stock boot image file, it’s time to patch it
via Magisk and flash it via Fastboot Commands. We have listed the steps for both
the older as well as the newer build of Magisk Manager. As far as the difference
between them goes, it’s just some UI tweaks here and there, the underlying
functionality remains the same.

--------------------------------------------------------------------------------

UPDATE 1: Quite a few Android 11 users are facing issues while patching the
stock boot.img file via Magisk manager. Well, I have found the fix to this
issue, please refer to our detailed guide on the same: Fix Magisk patched
boot.img issue while Rooting Android 11. If you wish to save a click, then
here’s the explanation in short:

You have to install the Magisk Canary build instead of the stable and then
change the update channel to Canary from within the app itself. Once you have
done the said change, you may then proceed with the below steps to patch the
stock boot image file using Magisk and flash it via Fastboot commands.

--------------------------------------------------------------------------------

STEP 2A- PATCH THE STOCK BOOT IMAGE FILE USING OLDER MAGISK

1. Download the stock firmware for your device.
2. Extract the boot.img file from it.
3. Transfer it to the device’s internal storage.
4. Install the Magisk Manager App on your device.
5. Open it. Tap on the first ‘Install‘ button, next to Magisk status.
6. In the next menu, again chose ‘Install‘.

7. Now select ‘Select and Patch a File‘.
8. Navigate to internal storage and select the stock boot.img file that you
extracted earlier.
9. Let Magisk do the patching process. When it’s done, copy this patched
boot.img file, named as magisk_patched.img, from your device (will be
present under Internal Storage > Downloads) to PC where you have installed
the ADB and Fastboot Tools (inside the platform-tools folder).

--------------------------------------------------------------------------------

* How to Update Magisk ZIP and Magisk Manager (without TWRP)
* Disable DM-Verity or Android Verified Boot without TWRP
* Fix Magisk Module Bootloop without TWRP Recovery
* How to Root Android Devices Without TWRP Recovery

--------------------------------------------------------------------------------

STEP 2B: PATCH STOCK BOOT IMAGE FILE USING NEWER MAGISK

1. Launch the Magisk Manager app on your device.
2. Then tap on the Install button situated next to Magisk.
3. From the Method section, choose Select and Patch a file.

4. Browse to the extracted boot.img file and select it.
5. Then tap on the Let’s Go option situated at the top right.
6. Magisk will now load the boot.img file and will patch it accordingly. Once
that is done, you would get the Download Complete message.

7. The patched boot image file will be saved in Internal Storage > Downloads.
The name of the file will be magisk_patched.img

STEP 3- INSTALL THE PATCHED BOOT IMAGE USING FASTBOOT

Now that you have created the patched boot image file via Magisk, it’s time to
flash it via Fastboot Commands. Follow along

1. Connect the device to the PC via USB Cable.
2. Now transfer the patched boot file from your device to the platform-tools
folder on your PC.
3. Inside the same folder, right-click on an empty area while pressing the
‘Shift’ key.
4. Select the option ‘Open PowerShell window here’.

5. Or you could also head over to the platform-tools folder on your PC, type
in CMD in the address bar, and hit Enter. This will launch the Command
Prompt.

6. Type in the below code to make sure the device is successfully connected
(an alpha-numeric code suggests successful connection):

adb devices

7. Now type in the below code to boot your device to fastboot/bootloader mode:

adb reboot bootloader

8. Next, type the below code to flash the patched boot image file:

fastboot flash boot magisk_patched.img

9. For devices with A/B partition, you need to flash the patched boot file to
both partitions. Type the below code for the same:

fastboot flash boot_a magisk_patched.img

fastboot flash boot_b magisk_patched.img

10. Now you may Reboot the device by typing the below code:

fastboot reboot

That’s it. You have successfully rooted your device. When the device reboots,
you could open the Magisk Manager app and confirm that the installation is
successful. With the device now rooted, try tweaking your device by editing the
build.prop file, optimize the device’s battery by the Greenify app or manage
your kernel via the Kernel Aduitor. There are countless other things you could
do. Explore the endless possibilities. So this was the detailed guide on how to
Patch Stock Boot Image and Flash it on Android Devices. If you face any error,
do mention it in the comments section below. We will get back to you with a
solution at the earliest.

--------------------------------------------------------------------------------

* Detailed Steps to Fix adb is not recognized Error
* How to Fix Unauthorized Device with ADB Commands [3 methods]
* Fix Android stuck in Recovery Mode: No Command screen
* How to Install Split APKs (APKM) on any Android Device

ABOUT CHIEF EDITOR

SADIQUE HASSAN

administrator

A technical geek by birth, he always has a keen interest in the Android platform
right since the birth of the HTC Dream. The open-source environment always seems
to intrigue him with the plethora of options available at his fingertips. “MBA
by profession, blogger by choice!”

See author's posts

Post navigation
← Previous Post
Next Post →

52 THOUGHTS ON “PATCH STOCK BOOT IMAGE VIA MAGISK AND FLASH IT USING FASTBOOT”

1.
2. C.Phurmy
October 31, 2020 at 5:47 am

I have a error boot prepare – stuck in fastboot. I have a Pixel3a XL with
LIneageOS 17 based on Android 10. What happened?

Reply
1. Sadique Hassan
November 1, 2020 at 12:42 am

Hi C.Phurmy, this usually happens when you flash the incorrect boot.img
file. I guess you might have patched and flashed the stock boot.img file
(from Pixel 3a XL stock ROM) rather the one from LineageOS. Since you
are currently using LineageOS, you need to extract and flash the
boot.img of that custom ROM only (you should extract the boot.img from
the same software version of LineageOS that is currently installed on
your device). Try it and do let me if it helped you or not.

3. Dave
November 6, 2020 at 7:59 am

Is it normal for the patched image to be significantly smaller than the
original boot img – 14mb vs 65 mb?

Reply
1. Sadique Hassan
November 7, 2020 at 10:23 pm

Yes, it is completely normal. Even I had recently patched a 101MB stock
boot.img file and its patched version came out to be of just 38MB.

4. Steve
November 17, 2020 at 11:23 am

I, too, have the same problem. I had an original boot.img at size of 66M,
then after the process, the patched_boot.img was about 13M, then odin
failed to flash the patched boot.img, but worked with the original
boot.img. I guess something is messed up during the patching. is there a
way to patch the boot.img without the GUI, I mean, completely from command
line so we know what is going on?

5. sophie
November 21, 2020 at 9:21 pm

the device appears when I do adb device, but when I do flashboot fast boot
command, it gets stuck in waiting for device. and the device is also stuck
on fastboot. how to fix this? I’m using redmi 9c.

Reply
1. Sadique Hassan
November 21, 2020 at 9:58 pm

Could you double-check a few things:
1. That you are opening the CMD window inside the platform-tools folder
only?
2. In your comment ‘ flashboot fast boot’ is a typo, right? Because if
you would execute this command then it will not work. The correct
command is fastboot flash boot file.img
3. Also verify that magisk patched boot.img file has been transferred to
the platform-tools folder

Reply
1. Jay
December 9, 2020 at 8:22 pm

Great work bro, even noob can learn everything from this guide

Reply
1. Sadique Hassan
December 11, 2020 at 1:21 pm

Thank you so much Jay for these encouraging words.

2. Rob
March 12, 2021 at 12:02 pm

Thanks for yours tutorials, I have the same problem off Sophie, adb
stuks in “waiting whatever device” in Samsung S3 T825 10″, regarding the
site, is great, arrive in time, awesome, congratulations e Thanks so
much !

Reply
1. dursch69
June 15, 2021 at 2:14 am

Android Device drivers are missing. Install Samsung Android USB
Drivers for Windows. You might even need to set the driver manually
within device manager if it still doesn’t work.

6. Dilshan
December 27, 2020 at 5:20 pm

very clear explanation.
why vivo devices hard to unlock bootloader compare to other devices?

Reply
1. Sadique Hassan
December 29, 2020 at 9:57 pm

Hi Dilshan, thanks for the appreciation. Yes, I have received quite a
few complaints regarding issues related to rooting Vivo devices. Could
you let me know your deivce name and whether or not you were able to
root your Vivo device using this method?

7. Filipe Nobre Mosse
January 11, 2021 at 7:00 pm

Hi, I’m getting a hard time to root Inifinx S5 Lite (X652C), can’t get to
unlock bootloader… Any HELP PLESASE?

Reply
1. Sadique Hassan
January 12, 2021 at 11:27 am

I haven’t used an Infinix device as of now. But I guess the command to
unlock the bootloader should be fastboot OEM unlock. Or if that doesn’t
work out, then you may use fastboot flashing unlock. However, this
process will wipe off all the data on your device and might void the
deivce warranty as well. Do so at your own risk.

2. Von
March 10, 2021 at 12:15 pm

Hi. I want to root my vivo Y11 (2019) and I cant unlock the bootloader,
no matter what command I use. So, Can I still extract the boot.img from
the stock update firmware zip file? and then patch it with magisk and
flash it using fastboot?

will it boot? or not because bootloader is lock.. thanks

Reply
1. Sadique Hassan
March 14, 2021 at 10:23 pm

Hi Von, you need to unlock the bootloader, and then only you could
root your device.

8. Danilo
March 6, 2021 at 4:16 am

Hi
I’ve installed Magisk v.22 . When I push install , in the method I got only
one choice “Select and update file” I don’t find Select and patch file. I
need this to patched boot.img into magisk.boot.img and flash it to root.
Can you help ? Thanks Danilo

Reply
1. Sadique Hassan
March 14, 2021 at 10:40 pm

Hi Danilo, in that case, you may install the Magisk app on any
non-rooted device and then carry out the patching process. I know it’s a
kinda workaround but it definitely does its job.

9. Danilo
March 6, 2021 at 4:35 am

Hi , I found the solution. Sorry it was a translation mistake. Thanks again
Danilo

10. Sadique Hassan
March 23, 2021 at 7:30 pm

Hi Jatin, the patched image will permanently root your device. Do you have
the TWRP Recovery installed? If yes, then there exists a method through
which you could make changes to the build.prop file and enable Camera2 API
without Root.

11. Steve Fox
March 25, 2021 at 8:15 pm

phone won’t shut off, won’t boot into recovery, what happened? Can it be
fixed or have I bricked it?

Reply
1. Sadique Hassan
March 30, 2021 at 2:16 pm

Hi Steve, please let me know your device name. Also, are you able to
boot to Fastboot Mode via hardware keys combination? If yes, then you
may flash stock firmware via fastboot commands and unbrick it.

12. Steve Fox
March 25, 2021 at 8:19 pm

Weird, previous comment seems to have disappeared

On Pixel 3, I patched boot img with OTA modified boot img (
magisk_patched_OwbsU.img ), now phone won’t boot at all, responds with
error boot prepare in fastboot screen. Won’t shut off, no options work.
Phone appears to be bricked… Please advise.

Reply
1. Sadique Hassan
March 30, 2021 at 2:14 pm

Hi Steve, this guide should help you out: Fix error boot prepare- device
stuck in fastboot (Pixel devices)

13. Steve Fox
March 26, 2021 at 1:57 am

Does it matter if it’s the factory or OTA boot image?

Reply
1. Sadique Hassan
March 30, 2021 at 2:24 pm

Hi Steve, it is always recommended to extract the stock boot.img from
the stock firmware and not incremental OTAs

14. Yassin
April 19, 2021 at 8:13 am

Hi friend, thank you for the tutorial.

I’m currently trying a lot of things to root my 7T on 11OxyOs, most
tutorials adress the global version and I can’t find any european magisk
boot patched file. So I tried to patch it with my magisk manager, and once
I boot it I just freeze on fastboot mode.
I even tried your tip of booting A and B, it still doesn’t work.
Hopefully I everytime I fail I can still boot the stock boot.img but I
would love to root this phone.

Any idea ?
Thank you in advance

Reply
1. Sadique Hassan
April 19, 2021 at 5:47 pm

Hi Yassin, so did you tried patching and flashing global boot.img onto
your European one? If you did that, then unfortunately it wouldn’t give
you any success. But if you picked the European boot.img, then please
double-check and make sure that you are extracting the boot.img from the
same firmware that is currently installed onto your device (refer to the
device’s Build Number)

15. Peter Bergonzi
June 3, 2021 at 8:28 am

Thank you for your very clear and useful guides.

16. Ahmad
June 7, 2021 at 1:47 pm

hello .. i am working on infinix X655C device
flashed final software “Genuine Software”
ADB Enabled
OEM Unlocked
Magisk is installed
patched boot.img via magisk
patched boot.img copied to new folder on pc
flashed it with CMD via fastboot to the device
but now device went into neverending boot loop I believe the device is not
yet supported I would like to know if my device is supported that’s all and
if its not please reply … thank you

17. Bagiarta
June 21, 2021 at 6:08 pm

Hi friend,,,
every time i flash with command: fastboot flash boot magisk_patched.img i
get this massage “error: cannot load ‘magisk_patched.img’: No such file or
directory”
please help me (my phone is oneplus X)

Reply
1. Sadique Hassan
July 11, 2021 at 11:56 pm

Hi Bagiarta, you need to place the magisk_patched boot.img file inside
the platform tool folder and the CMD window should also be opened in the
same platform-tools folder. Then execute the desired command and it
should work.

Reply
1. Stefamo
July 25, 2021 at 11:15 pm

Hi , i have a redmi note 8 pro and After flashing i had a bootloop. I
flashed the original boot for fix but still no root. Did i have to do
something with vbmeta.img?

18. ZxRistos
July 28, 2021 at 5:59 am

When i type adb reboot bootloader it just restarts my device and also when
i type fastboot flash boot magisk_patched.img it says wating for device

Reply
1. Remo
May 6, 2022 at 1:31 pm

i have the same issue on Oppo A15.
would love some help.

19. ZxRistos
July 28, 2021 at 6:11 am

Hey, when i type adb reboot bootloader my device just restarts and when i
type fastboot flash boot magisk_patched.img it says waiting for any device

20. Peter
August 20, 2021 at 9:26 pm

Hi, how do i extract boot.img on tecno ke5 spark go 2020

21. Ioannis
September 15, 2021 at 12:46 am

I’d like to do the opposite but I can’t find a way. The device (tv box) has
preinstalled patched magisk boot image or something and it won’t let me use
newer versions of Magisk or completely unroot the device.

22. Daniel
October 30, 2021 at 6:42 pm

Hi,

I have a Sony Xperia XZ2 Compact mobile phone. I am using 22.1 version of
Magisk. I have unlocked the bootloader, extracted the boot image and putted
it into the phone. I have patched the boot file on my phone and tried to
flash it back with the command:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img

But I cannot see the options for the modules and superuser. It says that
Magisk is not installed on the phone.
Any idea why it does not work?
Thank you.

Reply
1. Sadique Hassan
November 2, 2021 at 6:04 pm

After executing the two commands that you had listed, did you get any
error messages in the CMD window? Furthermore, you could also try using
the fastboot flash boot magisk_patched.img command.

23. Pingback: Extract boot.img from boot.img.lz4 and Root Samsung

24. ethan allen allen
December 28, 2021 at 11:47 am

So far so good. Had a bad moment when i found out that at least on my gl g5
h83030c. you can not eve SEE img files in download from the PC. Weird…
Trying to do anyting with the magisk created boot image gives error of file
type not suported. But it was easy enough to just copy it to the ‘internal
data’ folder where the PC could see it and copy it.

25. ethan allen allen
December 28, 2021 at 12:00 pm

well i thought i had a winner but….
I got almost thru everything but the lg fastboot just can not write over
the boot partition.

i even tried the boot_a partition.
On my PC I have to preface all fastroot commands with ./ when i use power
shell., and i renamed the patched file mpatched.img.

So here is what i got on errors:
PS D:\androidsdk> ./fastboot flash boot mpatched.img
Sending ‘boot’ (32029 KB) OKAY [ 1.303s]
Writing ‘boot’ FAILED (remote: ‘unknown command’)
fastboot: error: Command failed
PS D:\androidsdk> ./fastboot flash boot_a mpatched.img
Sending ‘boot_a’ (32029 KB) OKAY [ 1.272s]
Writing ‘boot_a’ FAILED (remote: ‘unknown command’)
fastboot: error: Command failed
PS D:\androidsdk>

*** Any idea why LG hides the boot (or boot_a) partition, and where we nead
to flash the image so it works??? **

26. alan
January 25, 2022 at 5:00 pm

After installing the magisk_patched.img, do I have to continue using the
magisk manager canary or can I install the stable version?

27. NotImpressed
July 25, 2022 at 5:56 am

Fail, adb/fastboot doesn’t work so Magisk is pointless. I can make the
patched file, but can’t flash it. Twrp is installed, this method is just
trash af. I have followed the directions as described to the letter
substituting the file names as required appropriately.

fastboot devices

That command sees nothing. Yes, the phone is in usb debug mode, bootloader
is unlocked, verification is turned off.

Samsung Grand Prime SM-G530W with Fido Android 5.1.1 stock rom.

There has to be a better way than this trash approach.

28. Labear
August 22, 2022 at 9:25 am

MotoG7 w/ LineageOS19.1, both TWRP & Magisk previously (before OS19.1
upgrade) flashed, though not sure when I began to experience issues with
TWRP opening the Sideload port and/or performing Backups….all since
upgrading from OS18.1 to 19.1
Anyhow, this patch I was hoping would resolve my initial issues w/ TWRP.
The boot.img file extraction turned into about 23mb img file. I was able to
load that into recently updated Magisk v24. Then upon flashing the same
file to both boot-a & boot-b, and even if I tried just the boot (only, not
a or b);
Everytime I get (bootloader) is-logical: boot_a: not found (or boot_b when
I attempted to flash boot-b)
So I figured my efforts failed. Though when I open Magisk on my device
(MotoG7) the “Magisk” section at the top of the app home display says
“Installed : 4737c511 (25202). This was not there before I flashed it and
this agrees with the “APP” section just below in same app home display.
So I guess the flashing worked???
I was also allowed this time to enable Zygisk, and after rebooting, even
that now says its active.
So whats up – did I fix the patching issue?

For the hell of it I did try opening the TWRP by rebooting device into
Recovery.
I did not get the TWRP application this timer.
Hmmm, now I’m confused.
Do I now need to re-flash TWRP and create a ramdisk again?

Crazy stuff – I feel like I’m going in circles, since all I wanted was a
reasonable backup system when I started this 50 hours of screwing around.

Anyone – HELP !
Thank you!

29. Abhishek Singh
September 20, 2022 at 10:07 pm

Sir Plzz help me after root video is not playing in my device because i
patch wrong boot img kya me firse stock rom ka jo boot img hota hai use
flash kar sakta hu plzz bataiye sir

30. Hamid
January 8, 2023 at 7:14 am

I’m getting the error:
FAILED (remote: Command not allowed)

31. Hitanshu Gaur
January 30, 2023 at 10:58 pm

Bro how can 2 patched files have the same name…. from the older magisk it
had a code in the end and from the updated magisk one also had a different
code in the end. In the instructions you’ve asked to ‘copy’ the old image
file to the folder; should we copy it or cut paste it? and then should we
rename the new magisk version patched file to magisk_patched.img?

The patched file from the older version would be in the platform tools
folder and from the new version the patched file will be in the internal
memory. Wouldn’t it clash while rooting due to the 2 patched files being
from 2 different versions?

If you could make the instructions a bit more specific it’d solve the
bootloop problem as well, coz that error is due to having too many files
named magisk_patched.img and the system is unable to figure out which one
is the appropriate one to use for rooting.

If you could amend the instructions to more specific one it’d help a long
way man

32. Hitanshu Gaur
January 31, 2023 at 8:22 am

C:\Program Files\Android\platform-tools>fastboot flash boot
magisk_patched.img
Sending ‘boot_b’ (40960 KB) OKAY [ 0.976s]
Writing ‘boot_b’ FAILED (remote: ‘not allowed in locked state’)
fastboot: error: Command failed

I am using ulefone power armour 18t

Reply
1. Hitanshu Gaur
January 31, 2023 at 9:14 am

This is the stock ROM of my phone:-

https://drive.google.com/file/d/1aq8f–ruq7Jf7rlKZGnd_eUeUGpSfJUD/view

Please help!

www.droidwin.com Open in urlscan Pro 2606:4700:20::681a:de8 Public Scan

Form analysis 3 forms found in the DOM

GET https://www.droidwin.com/

POST https://www.droidwin.com/wp-comments-post.php

GET https://www.droidwin.com

Text Content

www.droidwin.com Open in urlscan Pro
2606:4700:20::681a:de8 Public Scan

Form analysis
3 forms found in the DOM