Magisk Installation - Xiaomi Mi Note 10 Lite Questions & Answers

I'm looking for help getting Magisk installed on MIUI 12.1.1. If I use the boot.img and pass it to Magisk manager and flash it, the system just reboots to recovery after a few minutes.
Does anyone have it working or a recovery that works with 12.1.1 global?

moffa~ said:
I'm looking for help getting Magisk installed on MIUI 12.1.1. If I use the boot.img and pass it to Magisk manager and flash it, the system just reboots to recovery after a few minutes.
Does anyone have it working or a recovery that works with 12.1.1 global?
Click to expand...
Click to collapse
By "passing it to magisk", do you mean patching the boot.img and getting a magisk_patched.img? Do you have the latest magisk app? It's no longer called magisk manager (v22).
Edit: You probably just hot the patched boot from the wrong boot.img

Tulsadiver said:
By "passing it to magisk", do you mean patching the boot.img and getting a magisk_patched.img? Do you have the latest magisk app? It's no longer called magisk manager (v22).
Edit: You probably just hot the patched boot from the wrong boot.img
Click to expand...
Click to collapse
Hi, thanks for responding.
Yes, I mean I take the boot.img from the MIUI fastboot package and select it in Magisk (no longer manager). I then reboot to bootloader mode, then run "fastboot flash boot magisk_patched_sLsab.img " but after running fastboot reboot it just ends up in recovery mode.
The only way to recover is to use fastboot to flash the original boot.img back over

I finally figured out that I had magisk modules left over before the upgrade which broke everything. A factory reset wiping all data has fixed it.

Related

Pixel 3 root issue

Hi,
i have a problem rooting my Pixel 3.
it already worked, then i installed another rom which i did not like, so i re-installed the stock image from google (9.0.0 PQ1A.181205.006, Dec 2018).
But, here comes the problem, i can not install Magisk. When i do, my Pixel does not boot to system, but boots back to recovery or says can´t load android system.
this is how i do it:
1. flash factory image
2. boot to system
3. boot twrp
4. flash Magisk v18.0
also tried:
1. flash factory image
2. boot twrp directly
3. flash Magisk v18.0
this does not work. what i also tried is patch the stock boot.img with magisk and flash it to boot_a and boot_b. also did not work.
what am i doing wrong?
thnaks in advance for your help!
Spocki990 said:
Hi,
i have a problem rooting my Pixel 3.
it already worked, then i installed another rom which i did not like, so i re-installed the stock image from google (9.0.0 PQ1A.181205.006, Dec 2018).
But, here comes the problem, i can not install Magisk. When i do, my Pixel does not boot to system, but boots back to recovery or says can´t load android system.
this is how i do it:
1. flash factory image
2. boot to system
3. boot twrp
4. flash Magisk v18.0
also tried:
1. flash factory image
2. boot twrp directly
3. flash Magisk v18.0
this does not work. what i also tried is patch the stock boot.img with magisk and flash it to boot_a and boot_b. also did not work.
what am i doing wrong?
thnaks in advance for your help!
Click to expand...
Click to collapse
You've got the kernel and recovery messed up on your device from the failed flash of twrp and magisk. I would start over by flashing the factory image using the flash all batch file with the -w edited out of it. Then try again booting twrp, not flashing it. Once you try to flash the twrp image file you pretty much have to start over with the stock boot image. When you boot into twrp you'll want to allow modifications. You also need to setup a pin or pattern security for your system so twrp will decrypt your device.
Sent from my [device_name] using XDA-Developers Legacy app
Thanks for the hint. It works now. But had to use the patched boot image from this link.
https://www.google.de/amp/s/forum.x...o-root-pixel-3-xl-magisk-t3856712/amp/?espv=1
Spocki990 said:
Thanks for the hint. It works now. But had to use the patched boot image from this link.
https://www.google.de/amp/s/forum.x...o-root-pixel-3-xl-magisk-t3856712/amp/?espv=1
Click to expand...
Click to collapse
you are my hero. My phone was stuck in the situation you describe after installing active edge. I was thinking about wipe my pixel 3 until I saw your post. Thank you !:good:

Ota updates with magisk

How Can I Flash the December security update in my magisk rooted device? If I tray the "normal" way it gives me an error.
Hi. I had the same problem. Tried with restoring stock rom without wipe, but no go. Still error.
I ended up backing up my stuff and flashed stock with wipe, and then everything went well.
After your procedure what boot.img you use to reinstall magisk?
Usually when the bootloader is unlock is impossible to install any official update.
In that case I have the same problem, and I think the solution is to lock the bootloader, try to apply the update and to see if root still works. ( I am sure not).
In other case is, unlock the bootloader again, to wait the official ROM with December patch, extract boot.img, rebuild it with magisk and install it with fastboot and wait the final result.
Is crazy but while there is not another solution is a good way to have root on this Moto One.
skia16 said:
After your procedure what boot.img you use to reinstall magisk?
Click to expand...
Click to collapse
I booted up twrp and made a backup of boot.img, then patched it and flashed with fastboot.
tys0n said:
I booted up twrp and made a backup of boot.img, then patched it and flashed with fastboot.
Click to expand...
Click to collapse
I follow this way but magisk manager tells me that magisk Is not installed
skia16 said:
I follow this way but magisk manager tells me that magisk Is not installed
Click to expand...
Click to collapse
skia16 said:
I follow this way but magisk manager tells me that magisk Is not installed
Click to expand...
Click to collapse
Make a backup of boot in twrp.
Go to backup folder and make a copy of it somewhere. Rename the copy from "boot.emmc.win" to "boot.img".
Open Magisk manager, select install, choose "patch boot image file" and select the boot.img-file to patch.
It will unpack, patch and repack the boot.img for magisk functionality.
Move the patched_boot.img to pc and flash it with fastboot. "fastboot flash boot patched_boot.img".
Reboot, open Magisk manager. It should now ask to continue with environmental setup.
Or if you have the firmware package, you could just extract boot.img from it, put it on phone and patch it instead of using boot from twrp back up.

Can somebody help me please!

So hey! I successfully booted into the TWRP and used it to flash the DISABLEFORCEENCRYPTION file, right after. I decided to reboot to recovery (Cause I think that would be great just after you flash something in TWRP) but then after it finishes showing the pocophone booting screen rather than showing TWRP recovery. It showed the stock MIUI recovery! someone please help! I just finished flashing magisk and a custom rom by using the method of: Everytime I need to flash something using TWRP I would just open adb and fastboot boot recovery it again so that I could use the TWRP!
Thank you in advance!
GGerniWhite said:
So hey! I successfully booted into the TWRP and used it to flash the DISABLEFORCEENCRYPTION file, right after. I decided to reboot to recovery (Cause I think that would be great just after you flash something in TWRP) but then after it finishes showing the pocophone booting screen rather than showing TWRP recovery. It showed the stock MIUI recovery! someone please help! I just finished flashing magisk and a custom rom by using the method of: Everytime I need to flash something using TWRP I would just open adb and fastboot boot recovery it again so that I could use the TWRP!
Thank you in advance!
Click to expand...
Click to collapse
I decided to fix this problem after I flashed a rom cause I think I would run into future problems involving magisk and it's use of the TWRP recovery.
GGerniWhite said:
I decided to fix this problem after I flashed a rom cause I think I would run into future problems involving magisk and it's use of the TWRP recovery.
Click to expand...
Click to collapse
If you already have the ROM installed, use adb to flash TWRP and without booting flash Magisk and then boot to system. If you are on stock ROM, follow THIS.
For entering into TWRP, use the key combination of volume up + power buttons.
You can use the encryption compatible TWRP (search for it) instead of the official one.

Unofficial TWRP now available

Was searching in preparation of my K30 arriving, and found an unofficial version of TWRP is now available.
https://www.google.com/amp/s/unofficialtwrp.com/unofficial-twrp-3-3-1-xiaomi-redmi-k30/amp/
Note: I've not tried it myself, as I don't have the phone yet.
It's a none working TWRP ripped from a dev who was working on it. don't even test it guys. Devs at .eu made one that actually works.
https://xiaomi.eu/community/threads/twrp.53906/page-8
ddaggebi said:
It's a none working TWRP ripped from a dev who was working on it. don't even test it guys. Devs at .eu made one that actually works.
https://xiaomi.eu/community/threads/twrp.53906/page-8
Click to expand...
Click to collapse
please give instalation guide also
ddaggebi said:
It's a none working TWRP ripped from a dev who was working on it. don't even test it guys. Devs at .eu made one that actually works.
https://xiaomi.eu/community/threads/twrp.53906/page-8
Click to expand...
Click to collapse
Thanks for the info @ddaggebi
I used the K30 TWRP from https://xiaomi.eu/community/threads/twrp.53906/page-8#post-528914 to fastboot boot to TWRP and dump stock boot, recovery and misc (using e.g. `dd=/dev/block/bootdevice/by-name/boot of=/tmp/boot.img`). Then I patched the boot.img with Magisk Manager Canary. :good:
Any idea why that TWRP recovery installer .bat overwrites the misc partition? Temp booting the .img directly with fastboot boot seemed to work fine without their patched misc, so I'm sticking with that for now.
Again, be sure to fastboot boot recovery and then dump your ROM's misc first if you plan on flashing the recovery using that batch script, since you might need to flash it back along with the ROM's recovery for OTAs to succeed.
I can understand rooting here but is twrp installed permanently here? I mean to flash any rom do we always need fastboot command to boot twrp or its staying always and working normally??
Hard_Rock83 said:
I can understand rooting here but is twrp installed permanently here? I mean to flash any rom do we always need fastboot command to boot twrp or its staying always and working normally??
Click to expand...
Click to collapse
Yes. But some features are limited for now.
btw I installed eu rom in case stock rom replaces TWRP to stock recovery.
osm0sis said:
I used the K30 TWRP from https://xiaomi.eu/community/threads/twrp.53906/page-8#post-528914 to fastboot boot to TWRP and dump stock boot, recovery and misc. Then I patched the boot.img with Magisk Manager Canary. :good:
Any idea why that TWRP recovery installer .bat overwrites the misc partition? Temp booting the .img directly with fastboot boot seemed to work fine without their patched misc, so I'm sticking with that for now.
Also here is the latest Magisk Canary (20308) patched stock boot.img to simplify rooting for those just getting started on this device. Simply fastboot flash boot it..
Click to expand...
Click to collapse
Ok so the question is can we reboot to recovery normally or we need to manually type fastboot command to boot to recovery..
I am still searching for twrp , which can normally appears while rebooting to recovery
LR.Team twrp-3.4.0-0209 will be installed by default when you install Eu rom.
I can reboot into recovery as normal (by pressing "vol up" & "power" button). To install root, I can simply go to "Advanced" -> "Install Root" or by using boot.img method. One thing which I can't do is deleting (or changing file name) to system file to remove some of the unwanted app.
It works very well
https://xiaomi.eu/community/threads/twrp.53906/page-8#post-528914

Phone stuck on MI logo after re-rooting following forced update to Android 10

Hey guys, so I had the forced update to Android 10 about 1 month ago, and I lost root, which I didn't found about until I tried installing something today.
As this isn't my first time losing root I just followed the steps I always do on this guide (https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509) and I managed to successfully install TWRP, but the phone is now stuck on the orange MI logo when I reboot to system. Someone pls help!
Edit: For anyone curious, I just used the Fix Recovery Bootloop inside TWRP and it worked! I still don't have root tho...
Edit 2: After trying to flash Magisk installer for the second time I determined it to be the problem. Can anyone help me with that?
Use the magisk patched boot.img from here that corresponds with your firmware version and follow to guide to flash in fastboot https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509/page40
garylawwd said:
Use the magisk patched boot.img from here that corresponds with your firmware version and follow to guide to flash in fastboot https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509/page40
Click to expand...
Click to collapse
Just tried that, the phone is stuck again on the orange MI logo and now when I try to boot into TWRP it shows an android laying down with the message "No command" PLEASE HELP
garylawwd said:
Use the magisk patched boot.img from here that corresponds with your firmware version and follow to guide to flash in fastboot https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509/page40
Click to expand...
Click to collapse
Just tried that, the phone is stuck again on the orange MI logo and now when I try to boot into TWRP it shows an android laying down with the message "No command" PLEASE HELP.
Edit: I just flashed TWRP on flashboot and I was able to solve this. I can't still fond what's the issue with magisk tho.
SirAerion said:
Just tried that, the phone is stuck again on the orange MI logo and now when I try to boot into TWRP it shows an android laying down with the message "No command" PLEASE HELP.
Edit: I just flashed TWRP on flashboot and I was able to solve this. I can't still fond what's the issue with magisk tho.
Click to expand...
Click to collapse
What Magisk modules do you have installed? They might be preventing the phone to boot up.
_mysiak_ said:
What Magisk modules do you have installed? They might be preventing the phone to boot up.
Click to expand...
Click to collapse
Afaik the only module I HAD installed before the forced update was Smali patcher for POGO. But I can't check the modules now because the option isn't there in the manager.
SirAerion said:
Afaik the only module I HAD installed before the forced update was Smali patcher for POGO. But I can't check the modules now because the option isn't there in the manager.
Click to expand...
Click to collapse
Well, the module "only" patches framework from the phone, so you're trying to boot Android 10 system with Android 9 framework. It doesn't get uninstalled automatically even if you remove Magisk from boot image.
Either flash Magisk uninstaller from TWRP or flash correct patched boot file, connect phone to the PC, type in this command and reboot the phone.
adb wait-for-device shell magisk --remove-modules

Categories

Resources