I have installed the rom again with erasing all data then it was very simple to root the device with flashing the patched boot.img
[HowTo] Magisk install without TWRP
- Thread starter katerpanne
- Start date
Since I have erased all data and setup anything new some older apps warn that they were designed for an older version of Android. How can I stop this very annoying message? On previous Android versions these message only appeared one time but now it appers evry time I open the old apps.
- Apr 19, 2014
- 3,506
- 332
read the guides to understand how to do it and why.
then I will be happy to read your guide
Why nobody reads the official guide on Magisk Github how to patch and flash the patched boot img
It's available by few clicks, starting from Magisk app (Magisk app can be installed to the not-rooted phone, it's just the app)
atreju (kris)
Members
- Aug 13, 2019
- 52
- 20
Thank you katerpanne, I could root my poco f3 following your thread (flashing both a and b partition) you're the king!
Hello,
I rooted my Poco F2 Pro with success. But I have one question.
Do I have to patch boot.img and flash it each time that I want to install the last release of the xiaomi.eu rom?
Will I lose my deny list?
Thx
I rooted my Poco F2 Pro with success. But I have one question.
Do I have to patch boot.img and flash it each time that I want to install the last release of the xiaomi.eu rom?
Will I lose my deny list?
Thx
emap85
Members
- Jan 23, 2011
- 40
- 20
In my Poco F2Pro i have installed the 22.3.16, magisk 24.3 with modules for safetynetfix and configured the denylist. Everything works perfectly, but what if you want to upgrade to the latest weekly beta? Can I directly flash rom fastboot and patch boot.img for magisk, or do I have to remove magisk? to disable modules? Do I lose my magisk configuration?
Thank you
Thank you
david3
Members
- Mar 29, 2022
- 12
- 15
One thing to note, that wasn't immediately obvious to me. When you copy the original boot.img to the phone/sd card, and patch it, that original file isn't changed. A new patched version is written elsewhere, on the internal storage. That's the new version you need to use.
I use XM12 13.0.30 to 13.0.32
After updating the system and re-modifying the boot.img and flash it, it entered the boot loop, but flash in the original boot.img before it could boot normally.
I tried to return the previous version I was using and repeat the same thing, but still the same boot loop, how do I fix it?
I apologize for my translator's English.
After updating the system and re-modifying the boot.img and flash it, it entered the boot loop, but flash in the original boot.img before it could boot normally.
I tried to return the previous version I was using and repeat the same thing, but still the same boot loop, how do I fix it?
I apologize for my translator's English.
- Apr 19, 2014
- 3,506
- 332
flash the original boot.img to get out of bootloop. did you disabled all magisk modules before and used the correct boot.img?
Yes, I don't have disabled magisk modules, maybe that's why, is there any way to force them to be disabled or removed?
Thanks!
Ricardo Silva
Members
- Jul 19, 2011
- 37
- 20
Hi,
I've used the fastboot method to root my Poco F4 GT when I've installed xiaomi.eu 13.0.8.
Unfortunately after upgrading to 13.0.9 version I can't root my phone again, because after flashing the patched boot, the phone starts to be unstable with several app FCs.
Do I have any solution to solve this? Or my only alternative is to perform a clean flash?
I was thinking that maybe those issues were related to my magisk modules previously installed, but I don't know if it's due to that or not.
Sent from my 21121210G using Tapatalk
I've used the fastboot method to root my Poco F4 GT when I've installed xiaomi.eu 13.0.8.
Unfortunately after upgrading to 13.0.9 version I can't root my phone again, because after flashing the patched boot, the phone starts to be unstable with several app FCs.
Do I have any solution to solve this? Or my only alternative is to perform a clean flash?
I was thinking that maybe those issues were related to my magisk modules previously installed, but I don't know if it's due to that or not.
Sent from my 21121210G using Tapatalk
- Apr 19, 2014
- 3,506
- 332
try to do this and delete the magisk app/module
Safe Mode (This is not the "Recovery mode" or the "Fastboot mode" )
In case your phone shows a lot of errors and you cant handle them because there are a lot of pop up windows or you want to deinstall something from magisk as example ... try the "safe mode" only some important standard apps will be loaded:
- Power off your Android device and then power it on. You can also use the Reboot or Restart option.
- You will see the Powered by Android logo and MI logo on the boot screen, If they disappear and the Screen ist black, press and hold the Volume Down key down so long till system ist loaded
- The System will load and you will see a watermark... Safe mode
- Deinstall the app with the error / analyze the root cause of the issue and so on ...
- Reboot the phone to get off the "safe mode"
- Perhaps after loading you have to disable AirPlane Mode
Hai,
I am using mi 11 ultra with miui 13 stable eu latest. Can you help me to install magisk in my device.
There is no proper instructions in the internet for the andorid 12 miui 13 version of mi 11 ultra for installing magisk.
please help
MeiGuddet
Members
- Apr 29, 2016
- 1,380
- 222
I want to root my phone Mi 11 Pro without - TWRP.
But by doing this with Magisk 25.1 and patching the boot.img after installing a tweak Magisk Hide props config
The phone boots continuously to the MIUI Recovery 5.0, instead of starting the phone normally... After a couple reboots into to MIUI Recovery, the phone boots normally again.
So Im wondering what I am doing wrong? How to fix this? That the phone directs boots into to the phone instead of the recovery stock.
Even remove any module/tweak in Magisk, the phone boots automaticcly to the recovery MIUI Recovery 5.0.
- Apr 19, 2014
- 3,506
- 332
extract original boot.img and flash it
# fastboot flash boot boot.img
please no double posts
Im going to flash the phone
Yeah I created the other post in the wrong section.. Can't delete it unfor.
What im going to do is flash a new firmware EEA build. and start over.
Installing Magisk 25.2 and not to hide this app. Is there some settings I need to do? Or miss pre-steps?
The phone support "Ramdisk" So indeed I need to patch it with the boot.img of the current build.
Thanks for helping me out.
I tried but still bootloops.
Yeah I created the other post in the wrong section.. Can't delete it unfor.
What im going to do is flash a new firmware EEA build. and start over.
Installing Magisk 25.2 and not to hide this app. Is there some settings I need to do? Or miss pre-steps?
The phone support "Ramdisk" So indeed I need to patch it with the boot.img of the current build.
Thanks for helping me out.
Fresh flashed with a stock EEA firmware.
Extract the boot.img and flash it with magisk. That gives a modified boot.img.
This one flashed in Fastboot.
" fastboot flash boot magisk_patched-25200_ECKSt.img "
If I now reboot the phone it DOESN'T automatically boots in to MIUI Recovery 5.0, it boots straight to the phone OS. And I have root now.
Enabled: Zygisk
Can I now install the module Magisk Hide props config module from github? Or are there some precauson?
Last edited:
- Apr 19, 2014
- 3,506
- 332
of course you can try to install the module... if you are back in bootloop / recovery than I think the module is not compatible any longer
I am excited
Stock flashed.of course you can try to install the module... if you are back in bootloop / recovery than I think the module is not compatible any longer
I am excited
Im rooted right now, but also in a bootloop/recovery.
This happend after installing a different kind of module, After a restart it keeps in the MIUI Recovery 5.0, after a serveral reboots it boots into the phone.
How can I fix this? Can I flash the normall boot.img? or the applied Magisk_boot.img?
- Apr 19, 2014
- 3,506
- 332
as I mentioned before if you flash original boot.img magisk will be history. I dont know about anything about your modules if they perhaps changed system config.
on the other side you can try safemode and deinstall the modules
Last edited:
I tried different Module's and on every module its gets a bootloop into the recovery of "MIUI Recovery 5.0" After a few reboots in to this recovery the phone boots finnaly up in the normale mode...
Similar threads
- Sticky
