Database Develop

Magisk v15.2 not installing

Hello
Okay i flashed my mobile with new OTA
after i try to install magisk but getting error that "Magisk manager stopped" after zip downloaded
i dont know why that happening
after zip downloaded getting black window then pop up shown about error
i think it cant patch boot img properly
in my old rom it works properly, but after flashing it did not work
thank you....

Try installing it in recovery

I sometimes get that majisk stopped toast on just about any ROM and just about any majisk release. I just ignore it. I have no idea of the what or why. Haven't noticed it affecting anything.

Yes. It's happening to me too. Does it work if I flash this update with twrp?

rabin69x said:
Yes. It's happening to me too. Does it work if I flash this update with twrp?
Click to expand...
Click to collapse
Did you read the responses above? It was already suggested to try that.

After installing magisk 15.2, magisk manager 5.5.3 stuck at the splash screen for me. What's wrong ?

rabin69x said:
Yes. It's happening to me too. Does it work if I flash this update with twrp?
Click to expand...
Click to collapse
I always flash builds from TWRP.

Eng.Raman said:
After installing magisk 15.2, magisk manager 5.5.3 stuck at the splash screen for me. What's wrong ?
Click to expand...
Click to collapse
Having the exact same issue on a pixel xl. Tried on 7.1 and 8.1, both with the same result.

I never use manager. Always TWRP, and can people start searching and using the support thread for questions, logs, and bugs instead of keep making a hundred useless threads of the same thing, can't install, can't install modules, etc. That's what support thread for. Thanks.

I am using MIUI 7.12.28 (latest) on Redmid 3S and I can flash magisk 15.2 using TWRP normally but when the phone restart, i go to magisk manager and it shows that magisk is not installed
I tried flash many time but the same problem happen
When i tried to flash magisk 14.0, it works. what is the problem here o_o

hungragezone said:
I am using MIUI 7.12.28 (latest) on Redmid 3S and I can flash magisk 15.2 using TWRP normally but when the phone restart, i go to magisk manager and it shows that magisk is not installed
I tried flash many time but the same problem happen
When i tried to flash magisk 14.0, it works. what is the problem here o_o
Click to expand...
Click to collapse
If updating, why not use direct method?

madbat99 said:
If updating, why not use directethod?
Click to expand...
Click to collapse
No, i am flashing from start
I just flash new miui (full wipe, factory reset)
and i also try to update from Magisk manager but when the flash screen appear, magisk manager force close (I already tried to clear data of Magisk manager and tried to update again but no success)
Now i can have root with Magisk 14.0 but when i tried to update to 15.2 using TWRP, it just disappear lol
(Flashing normally, no error, restart phone, go to magisk manager -> magisk is not installed )

Error 1 after reflashing ROM, can't (un)install Magisk

Hello, so I decided to reflash my ROM because I kept running into issues, and I didn't uninstall Magisk before doing so.
Then when I tried flashing Magisk it showed me error 1. Flashing the uninstaller gives the same error. Magisk Manager shows that it is not installed, Root Checker states that the device is unrooted, and so far the only app that mentioned my phone being rooted is LastPass.
What can I possibly do to reinstall Magisk so it's back on my device in its full grace?
I checked other posts and either they are not related to my problem or didn't help
Phone: Xiaomi Redmi Note 4 Snapdragon, Recovery: official TWRP non-treble, ROM: latest build of official AOSP Extended

Maybe try dirty flashing and flashing Magisk again?
Not Sally when Magisk is already installed, I can flash it again with no problem. Weird that you're having these issues. ?

LennyTheCat said:
Hello, so I decided to reflash my ROM because I kept running into issues, and I didn't uninstall Magisk before doing so.
Then when I tried flashing Magisk it showed me error 1. Flashing the uninstaller gives the same error. Magisk Manager shows that it is not installed, Root Checker states that the device is unrooted, and so far the only app that mentioned my phone being rooted is LastPass.
What can I possibly do to reinstall Magisk so it's back on my device in its full grace?
I checked other posts and either they are not related to my problem or didn't help
Phone: Xiaomi Redmi Note 4 Snapdragon, Recovery: official TWRP non-treble, ROM: latest build of official AOSP Extended
Click to expand...
Click to collapse
Did you wipe everything? Wipe system and data before re flashing your rom.

@LennyTheCat To be absolutely sure what's going on you're going to have to provide the recovery log, saved after you've attempted you flash Magisk.

madbat99 said:
Did you wipe everything? Wipe system and data before re flashing your rom.
Click to expand...
Click to collapse
Yes I did

Didgeridoohan said:
@LennyTheCat To be absolutely sure what's going on you're going to have to provide the recovery log, saved after you've attempted you flash Magisk.
Click to expand...
Click to collapse
Will provide later now I have stuff to do

@Didgeridoohan here's the log file

LennyTheCat said:
@Didgeridoohan here's the log file
Click to expand...
Click to collapse
Try updating your TWRP. That has solved "cannot mount vendor" for other Mido users.
https://forum.xda-developers.com/search/forum/5903?query=mido cannot mount vendor

Didgeridoohan said:
Try updating your TWRP. That has solved "cannot mount vendor" for other Mido users.
https://forum.xda-developers.com/search/forum/5903?query=mido cannot mount vendor
Click to expand...
Click to collapse
well, it has installed no problem, but then my phone got stuck in a bootloop after rebooting. I have to reflash everything now, will tell if it worked later

@Didgeridoohan when I install Magisk, the phone keeps running into bootloops. Clean install of the ROM and Gapps seems to work fine. Tried 16.0 and 16.4 packages

LennyTheCat said:
@Didgeridoohan when I install Magisk, the phone keeps running into bootloops. Clean install of the ROM and Gapps seems to work fine. Tried 16.0 and 16.4 packages
Click to expand...
Click to collapse
Well... You're using a Treble ROM, right? So I'm assuming you're using a Treble modified Magisk version (since there's no official Treble support in Magisk yet)... If not, I'm sure you can find the relevant information in your ROM's thread.
Always go to the source...

Didgeridoohan said:
Well... You're using a Treble ROM, right? So I'm assuming you're using a Treble modified Magisk version (since there's no official Treble support in Magisk yet)... If not, I'm sure you can find the relevant information in your ROM's thread.
Always go to the source...
Click to expand...
Click to collapse
I decided to flash Lineage OS and then I flashed the Magisk package included in the post. Now it's working all squeaky and shiny. Thanks for help anyway

Startup Hang after Installing Magisk v18.0

Hey, all!
Had a notification this morning for the new Magisk Manager (6.1) and Magisk (18.0) release. I downloaded both and rebooted the phone (OnePlus 2), updating from 17.3 to 18.0 directly, which had no errors during the install. Now upon startup it hangs on the splash screen. I can get into recovery (TWRP) and I have tried to flash the latest Magisk Uninstaller but I'm greeted with an ERROR 1: Error Installing zip file '/sdcard/...' - Unable to unpack boot.img
Any help here? Thanks in advance!

SpikyAndroid3 said:
Hey, all!
Had a notification this morning for the new Magisk Manager (6.1) and Magisk (18.0) release. I downloaded both and rebooted the phone (OnePlus 2), updating from 17.3 to 18.0 directly, which had no errors during the install. Now upon startup it hangs on the splash screen. I can get into recovery (TWRP) and I have tried to flash the latest Magisk Uninstaller but I'm greeted with an ERROR 1: Error Installing zip file '/sdcard/...' - Unable to unpack boot.img
Any help here? Thanks in advance!
Click to expand...
Click to collapse
You can do dirty flash of your current ROM. That would simply replace the boot.img back to normal and then you can try flashing Magisk v18.0 again (if you want to)
Sent from my #FlagshipKiller3T using Tapatalk

DarkSJ1998 said:
You can do dirty flash of your current ROM. That would simply replace the boot.img back to normal and then you can try flashing Magisk v18.0 again (if you want to)
Sent from my #FlagshipKiller3T using Tapatalk
Click to expand...
Click to collapse
Thanks for the response, just about to do a dirty flash of the stock ROM. My memory doesn't serve me well, is it best to wipe Cache as well as Dalvik Cache, or just Dalvik Cache?
The recovery also stays as is, right?

Hello,
The same for me from 17.3 to 18.
I'm on Nexus 6 with stock ROM.

SpikyAndroid3 said:
Thanks for the response, just about to do a dirty flash of the stock ROM. My memory doesn't serve me well, is it best to wipe Cache as well as Dalvik Cache, or just Dalvik Cache?
The recovery also stays as is, right?
Click to expand...
Click to collapse
Yep the recovery should stay as it is. I would recommend wiping both Dalvik Cache & Cache. Also, do keep fastboot handy. TWRP survival really depends on the device. For my device (OnePlus 3T), the OOS overrides TWRP if no root solution is used or patched boot.img isn't used.
Sent from my #FlagshipKiller3T using Tapatalk
---------- Post added at 01:08 AM ---------- Previous post was at 12:55 AM ----------
StreamingMT said:
Hello,
The same for me from 17.3 to 18.
I'm on Nexus 6 with stock ROM.
Click to expand...
Click to collapse
Weird :/
Did you check the Magisk release thread for people facing similar issues? I'm still on v17.3.
I'm really reluctant to move to v18.0 after reading such things... Moreover, I always wait for feedbacks before trying out things that play with the boot.img's & stuff, because I already got /data partition of my last device corrupted [emoji52]
Sent from my #FlagshipKiller3T using Tapatalk

DarkSJ1998 said:
Yep the recovery should stay as it is. I would recommend wiping both Dalvik Cache & Cache. Also, do keep fastboot handy. TWRP survival really depends on the device. For my device (OnePlus 3T), the OOS overrides TWRP if no root solution is used or patched boot.img isn't used.
Click to expand...
Click to collapse
Alrighty! Just went ahead and did the flash and it successfully reboots! Tried to reboot into recovery to flash Magisk 17.3 and lo and behold TWRP is still there
Guess I'll wait until there has been an update or patch of some sorts if @StreamingMT is also getting this issue, maybe there are others too. Thanks for the help @DarkSJ1998

I will try to remember that @DarkSJ1998.
I was excited to have a new update, just got reckless...
Anyways, I replied to the official thread about the details, just search through it. I just restored my phone to the way it used to...
All my saves... Gone to trash.

SpikyAndroid3 said:
Hey, all!
Had a notification this morning for the new Magisk Manager (6.1) and Magisk (18.0) release. I downloaded both and rebooted the phone (OnePlus 2), updating from 17.3 to 18.0 directly, which had no errors during the install. Now upon startup it hangs on the splash screen. I can get into recovery (TWRP) and I have tried to flash the latest Magisk Uninstaller but I'm greeted with an ERROR 1: Error Installing zip file '/sdcard/...' - Unable to unpack boot.img
Any help here? Thanks in advance!
Click to expand...
Click to collapse
I had the same bootloop issue when I was reinstalling H2OS beta 21 in my OnePlus 5 today. I got it to boot again with Magisk 18.0 after:
1. Dirty flashing ROM. Now this is important Did not flash Magisk (yet).
2. Rebooting to Bootloader (fastboot) in TWRP (since no root, now stock recovery will reinstall).
3. Fastboot flashed TWRP. Booted to Recovery mode from Fastboot menu.
4. Flashed Magisk 18.0 in TWRP. Now this is important Only flashed Magisk, nothing else.
5. Rebooted to Recovery again instead of System to flash other stuff.
6. Rebooted system.
If course YMMV. The important thing was to not try to flash Magisk while flashing ROM.

Same here on a mi max 2, updated manager and magisk directly from app, now stuck in bootloop. im downloading my rom as im typing to restore stock boot image. will flash v17.1 instead.

I have 1 plus 5 with official H2OS and Magisk 17.1.
Today when after installed Magick 18 and reboot, it stuck at startup.
I try to flash TWRP using adb, but it give me error:
E:\Program Files\Android\platform-tools>adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
E:\Program Files\Android\platform-tools>adb kill-server
E:\Program Files\Android\platform-tools>
Click to expand...
Click to collapse

I too am having with latest magisk 18.0 my device is redimi 4x, on trying to update via magisk manager crashes with an error report, installed update using twrp now i get a error popup at start and magisk manger still shows am on 17.1 and tells to update, which crashes the app on trying

tmicrd68 said:
I had the same bootloop issue when I was reinstalling H2OS beta 21 in my OnePlus 5 today. I got it to boot again with Magisk 18.0 after:
1. Dirty flashing ROM. Now this is important Did not flash Magisk (yet).
2. Rebooting to Bootloader (fastboot) in TWRP (since no root, now stock recovery will reinstall).
3. Fastboot flashed TWRP. Booted to Recovery mode from Fastboot menu.
4. Flashed Magisk 18.0 in TWRP. Now this is important Only flashed Magisk, nothing else.
5. Rebooted to Recovery again instead of System to flash other stuff.
6. Rebooted system.
If course YMMV. The important thing was to not try to flash Magisk while flashing ROM.
Click to expand...
Click to collapse
Using Xiaomi Mi Max
Using your method and it work just took afew for it to boot back up :good:

netsonic said:
I have 1 plus 5 with official H2OS and Magisk 17.1.
Today when after installed Magick 18 and reboot, it stuck at startup.
I try to flash TWRP using adb, but it give me error:
Code:
E:\Program Files\Android\platform-tools>adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
E:\Program Files\Android\platform-tools>adb kill-server
Click to expand...
Click to collapse
Try 'Revoking USB Debugging' and restart the adb server. Then reinstate its authorization by plugging it back in with USB Debugging enabled. And just to check, make sure you run cmd as administrator, and ensure MTP is on.
huzeifa88 said:
I too am having with latest magisk 18.0 my device is redimi 4x, on trying to update via magisk manager crashes with an error report, installed update using twrp now i get a error popup at start and magisk manger still shows am on 17.1 and tells to update, which crashes the app on trying
Click to expand...
Click to collapse
Try flashing the uninstaller which you can get here. Then reinstall/reflash Magisk with a previous version that worked for you.

DarkSJ1998 said:
You can do dirty flash of your current ROM. That would simply replace the boot.img back to normal and then you can try flashing Magisk v18.0 again (if you want to)
Sent from my #FlagshipKiller3T using Tapatalk
Click to expand...
Click to collapse
It's possible only flash the stock boot.img (extracted from fastboot stock rom) with the TWRP?

otraver said:
It's possible only flash the stock boot.img (extracted from fastboot stock rom) with the TWRP?
Click to expand...
Click to collapse
I guess it's possible, but I'm not sure about that.... You can backup/restore boot.img from TWRP but I don't know if you can do this also... Do check it on the Internet.
Sent from my #FlagshipKiller3T using Tapatalk

DarkSJ1998 said:
You can do dirty flash of your current ROM. That would simply replace the boot.img back to normal and then you can try flashing Magisk v18.0 again (if you want to)
Sent from my #FlagshipKiller3T using Tapatalk
Click to expand...
Click to collapse
DarkSJ1998 said:
I guess it's possible, but I'm not sure about that.... You can backup/restore boot.img from TWRP but I don't know if you can do this also... Do check it on the Internet.
Sent from my #FlagshipKiller3T using Tapatalk
Click to expand...
Click to collapse
Don't work.
The cellular boot but stops in the Miui Screen with the unlocked symbol
I tried a dirty install of the rom but don't work
I need to install a clean global stock rom to boot correctly.

otraver said:
It's possible only flash the stock boot.img (extracted from fastboot stock rom) with the TWRP?
Click to expand...
Click to collapse
Actually, Magisk does a backup of stock boot.img before patching it, which lies stored in /data as ".img.gz.zip". Haven't looked for how to restore it yet; however, assuming it's a flashable zip, it can be restored via TWRP. Should check Magisk release OP to be sure...
Sent from my Moto Z2 Play using XDA Labs

The Analog Kid said:
Actually, Magisk does a backup of stock boot.img before patching it, which lies stored in /data as ".img.gz.zip". Haven't looked for how to restore it yet; however, assuming it's a flashable zip, it can be restored via TWRP. Should check Magisk release OP to be sure...
Sent from my Moto Z2 Play using XDA Labs
Click to expand...
Click to collapse
Doesn't look like a flashable zip too me. It stores a *.img file in it, which I think is flashable as an image from TWRP. But, I'm not 100% sure about it.
Great discovery though dude there
Sent from my #FlagshipKiller3T using Tapatalk

otraver said:
It's possible only flash the stock boot.img (extracted from fastboot stock rom) with the TWRP?
Click to expand...
Click to collapse
Hello, I do this with my Nexus 6, it's OK. Flash again Magisk (v17 not 18 for me) and all is OK for me.

Boot loop for me too after upgrading from v17 to v18 . I'm on Nexus 6. Any official information about this bug?
Fixed by installing TWRP then restored backup through TWRP and selected only boot image. I guess TWRP or me saved backup at some point, don't remember exactly. Will have to use v17 for now.

Error while installing Magisk through Magisk manager

I'm trying to instal Magisk 19.3 through Magisk Manager Version: v7.3.4
and getting this error:
Device platform: arm64-v8a
Coping image to cache
unpacking boot image
!unsupported/unknown image format
!installation failed
Any ideas how to solve it?
I have used Stable Magisk Version: v19.3 (also tried Beta Magisk Version: v19.4)

Maybe something's wrong with the boot image? Try to re-download magisk stable zip and reintall it via TWRP.

@LogicalMaverick, tried to download it again from this thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 but still the same error message
I did try to install in TWRP mode and also from the Magisk Manager and still not working.
When I install in TWRP mode the result is the phone is getting into loop mode and the only way out if it is to uninstall it

try to wipe data after flashing magisk before booting to system

Kzak25 said:
try to wipe data after flashing magisk before booting to system
Click to expand...
Click to collapse
Yeah, for me there are 2 ways:
1. Wipe data after flashing magisk before booting system
2. Complete phone setup first after installing new ROM, and then boot into recovery, then you're good to install magisk

Kzak25 said:
try to wipe data after flashing magisk before booting to system
Click to expand...
Click to collapse
Didn't work. Still getting to the same issue where the phone is stuck in bootloop and the only way out of it is to uninstall Magisk

What phone are you using?

cohenelad said:
Didn't work. Still getting to the same issue where the phone is stuck in bootloop and the only way out of it is to uninstall Magisk
Click to expand...
Click to collapse
are you on stock or custom ROM (if stock what MIUI Ver)

Kzak25 said:
are you on stock or custom ROM (if stock what MIUI Ver)
Click to expand...
Click to collapse
I'm on stock ROM.
Was on MIUI 10.3.2 Now I'm on 10.4.8.
Tried to install Magisk on bot ROM through TWRP and didn't work.
Tried also through Magisk manager and didn't work
When I installed TWRP on my phone it asked if I want to give it permission to modify the system or to leave it read only mode.
I choose read only mode as I thought it will be easier to get OTA updates.
Maybe that's the reason Magisk cannot be installed correctly ?
TIA for your help

cohenelad said:
I'm on stock ROM.
Was on MIUI 10.3.2 Now I'm on 10.4.8.
Tried to install Magisk on bot ROM through TWRP and didn't work.
Tried also through Magisk manager and didn't work
When I installed TWRP on my phone it asked if I want to give it permission to modify the system or to leave it read only mode.
I choose read only mode as I thought it will be easier to get OTA updates.
Maybe that's the reason Magisk cannot be installed correctly ?
TIA for your help
Click to expand...
Click to collapse
Yeah i think you should give TWRP all permission when you boot into it the first time
you can re-flash TWRP and try again

reboots to fastboot
Kzak25 said:
Yeah i think you should give TWRP all permission when you boot into it the first time
you can re-flash TWRP and try again
Click to expand...
Click to collapse
I can flash over twrp. then it says no rom installed so flash over magisk-error unknown image. this is a fresh download tried 3 new downloads same error. use adb sideload to flash rom. successful do the reboot and it reboots to fastboot. what do i do

[GUIDE] [TOOL] TWRP Installer + Root Redmi 8 (Olive)

TWRP INSTALLER FOR REDMI 8
​
I want to share my tool for installing TWRP for Redmi 8.Tested on MIUI 11 Global 11.0.10.0 (PCNMIXM). Always take a backup of your data before doing this modifications. I'm not responsible if something went wrong and do it at your own risk!!!
About this tool:
Includes Official TWRP for Redmi 8
Includes ADB and Fastboot
Easy to Use
Files:
TWRP Installer for Redmi 8 - https://androidfilehost.com/?fid=8889791610682873743
Magisk Zip - https://magisk.me/zip/
How to Install TWRP & Root:
Unlock the Bootloader.
Connect your phone with USB cable and put the Magisk zip file to your internal or SD Card
Turn off your device and reboot into fastboot by pressing Vol down and Power button
Extract the TWRP installer zip file
Open TWRP_Installer.bat
Press Enter to proceed
Then press any key to install the TWRP and wait to finish
Press any key again , it will automatically boot into TWRP
Go to Install
Find the Magisk Zip File then flash
Reboot and your done
Congratss!!! You successfully install TWRP and Root your Redmi 8
Notes:
You need to Flash the Magisk after you install the TWRP. So that it will not back to stock recovery and the TWRP is now your permanent recovery.
You can also change the TWRP that I use on this tool. Go to the installer folder and delete the recovery.img then paste the recovery that you want and rename it to "recovery.img"
Credits:
XDA
Xiaomi Redmi 8 Developers
TWRP
Google
THANK YOU FOR USING MY TOOL!!! HAVE A NICE DAY AND GODBLESS ​

I've followed every step im this guide with no errors but after reboot after flashing magisk phone boots to normal mode, nothing different other than magisk manager installed and root checker says phone not rooted. Any idea?

GreenGremlim said:
I've followed every step im this guide with no errors but after reboot after flashing magisk phone boots to normal mode, nothing different other than magisk manager installed and root checker says phone not rooted. Any idea?
Click to expand...
Click to collapse
Did you try to flash it again on TWRP? Or try to open the Magisk Manager App and go to Superuser and allow the root access on the root checker app

MattPRZ said:
Did you try to flash it again on TWRP? Or try to open the Magisk Manager App and go to Superuser and allow the root access on the root checker app
Click to expand...
Click to collapse
Yes tried flash again even did a factory reset and restarted all over and after flashing on twrp I dont have the magisk manager app
Edit: I downloaded and installed magisk manager app but says magisk is not installed.

GreenGremlim said:
Yes tried flash again even did a factory reset and restarted all over and after flashing on twrp I dont have the magisk manager app
Edit: I downloaded and installed magisk manager app but says magisk is not installed.
Click to expand...
Click to collapse
Maybe the root was gone after reset... Flash again the Magisk zip file or install it via the magisk manager
When I first install the magisk , I wait couple minutes and then the magisk manager appears

MattPRZ said:
Maybe the root was gone after reset... Flash again the Magisk zip file or install it via the magisk manager
Click to expand...
Click to collapse
I am trying to install via the magisk manager but I can't seem to see the right option I have tried download only zip file (dont know waht to do next) and also select and patch a file, where i select the downloaded zip file but I get an unssuported/unknown image format and then installation failed

GreenGremlim said:
I am trying to install via the magisk manager but I can't seem to see the right option I have tried download only zip file (dont know waht to do next) and also select and patch a file, where i select the downloaded zip file but I get an unssuported/unknown image format and then installation failed
Click to expand...
Click to collapse
Uninstall that magisk manager , reboot to twrp and flash again the magisk zip file , in my case I wait couple minutes then magisk manager appear

MattPRZ said:
Uninstall that magisk manager , reboot to twrp and flash again the magisk zip file , in my case I wait couple minutes then magisk manager appear
Click to expand...
Click to collapse
Uninstalled, rebooted and flashed again but magisk manager still doesnt appear, I am gonna restart phone and give leave it alone a couple of hours, will let you know how it goes.

MattPRZ said:
Uninstall that magisk manager , reboot to twrp and flash again the magisk zip file , in my case I wait couple minutes then magisk manager appear
Click to expand...
Click to collapse
GreenGremlim said:
Uninstalled, rebooted and flashed again but magisk manager still doesnt appear, I am gonna restart phone and give leave it alone a couple of hours, will let you know how it goes.
Click to expand...
Click to collapse
Update, after restarting phone and not using it for a copuple hours magisk manager still doesnt appear. Question; how to install magisk from magisk manager? Might try install it with the apk I downloaded from magisk manamger website.

GreenGremlim said:
Update, after restarting phone and not using it for a copuple hours magisk manager still doesnt appear. Question; how to install magisk from magisk manager? Might try install it with the apk I downloaded from magisk manamger website.
Click to expand...
Click to collapse
Maybe the magisk is now Installed , but if the magisk manager still not appear , install the magisk manager with the latest version

MattPRZ said:
Maybe the magisk is now Installed , but if the magisk manager still not appear , install the magisk manager with the latest version
Click to expand...
Click to collapse
Installed latest magisk manager, it shows magisk not instaled.

GreenGremlim said:
Installed latest magisk manager, it shows magisk not instaled.
Click to expand...
Click to collapse
That's strange... I never face that problem
Maybe the only solution is download and flash the magisk uninstaller , so that it will remove all the magisk files , and repeat the flashing of magisk

MattPRZ said:
That's strange... I never face that problem
Maybe the only solution is download and flash the magisk uninstaller , so that it will remove all the magisk files , and repeat the flashing of magisk
Click to expand...
Click to collapse
Ok will try that, thanks.

MattPRZ said:
That's strange... I never face that problem
Maybe the only solution is download and flash the magisk uninstaller , so that it will remove all the magisk files , and repeat the flashing of magisk
Click to expand...
Click to collapse
GreenGremlim said:
Ok will try that, thanks.
Click to expand...
Click to collapse
Made another hard reset to phone and I am going to try this https://c.mi.com/thread-3159753-1-1.html will keep you posted.

MattPRZ said:
That's strange... I never face that problem
Maybe the only solution is download and flash the magisk uninstaller , so that it will remove all the magisk files , and repeat the flashing of magisk
Click to expand...
Click to collapse
GreenGremlim said:
Ok will try that, thanks.
Click to expand...
Click to collapse
GreenGremlim said:
Made another hard reset to phone and I am going to try this https://c.mi.com/thread-3159753-1-1.html will keep you posted.
Click to expand...
Click to collapse
So, after ahard reset tried again following yor guide, still not rooted, after that I flashed stock rom to have a clean install and tried the tutorial I posted using a stock boot image patched with magisk and still no root. Is it possible that I am having no luck and you managed to root yours because of different stock roms i.e. Global vs China or Russia roms?

GreenGremlim said:
So, after ahard reset tried again following yor guide, still not rooted, after that I flashed stock rom to have a clean install and tried the tutorial I posted using a stock boot image patched with magisk and still no root. Is it possible that I am having no luck and you managed to root yours because of different stock roms i.e. Global vs China or Russia roms?
Click to expand...
Click to collapse
You flash stock rom via Mi flash tool? Maybe because of the rom that you use... I only tested on Global

MattPRZ said:
You flash stock rom via Mi flash tool? Maybe because of the rom that you use... I only tested on Global
Click to expand...
Click to collapse
Yes I flash stock rom via MiFlash tool, and my rom is Global like yours so that is not the issue. Still haven't figured what's wrong.

GreenGremlim said:
Yes I flash stock rom via MiFlash tool, and my rom is Global like yours so that is not the issue. Still haven't figured what's wrong.
Click to expand...
Click to collapse
Try other magisk version

MattPRZ said:
Try other magisk version
Click to expand...
Click to collapse
Any particular version in mind?

GreenGremlim said:
Any particular version in mind?
Click to expand...
Click to collapse
Try the lower versions like 20.3 , 20.2 and others