Related
I try and install directly from magisk but when I go and flash the zip through app it says installation failed. Am I doing something wrong?
Me too
I try unistall magisk in recovery but non success
I'm blocked
Edit: i'm return at v16.6 and work
I don't update for Now Walt for more info
Ty for now I'll wait
same here
Edit:- can't go back to v16.0 either,i'm getting "updater process ended with ERROR: 1
Any suggestions?
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Karls0 said:
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Click to expand...
Click to collapse
If I don't have TWRP I just install it? Sorry for noob question but i'm new here
Karls0 said:
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Click to expand...
Click to collapse
Thanks mate,worked for me.
Hi,
I'm running a HTC 10 with Lineage OS 15.1 (8.1.0). I came from Magisk 16 and an update message appeard. I downloaded Magisk 17 and tried to install it via TWRP as usual. The installation stopped with an Error 2. After that I had a boot loop and had to reinstall the Lineage OS. After that it booted again. But I still get this error message when trying to install Magisk 17.
Very odd. Besides of that, GREAT WORK!
Cheers
lmrcarneiro said:
If I don't have TWRP I just install it? Sorry for noob question but i'm new here
Click to expand...
Click to collapse
Magisk uninstaller will not works without custom recovery so i think my instruction is not applicable in this situation.
chaos_since_78 said:
Hi,
I'm running a HTC 10 with Lineage OS 15.1 (8.1.0). I came from Magisk 16 and an update message appeard. I downloaded Magisk 17 and tried to install it via TWRP as usual. The installation stopped with an Error 2. After that I had a boot loop and had to reinstall the Lineage OS. After that it booted again. But I still get this error message when trying to install Magisk 17.
Very odd. Besides of that, GREAT WORK!
Cheers
Click to expand...
Click to collapse
Double check if the package is not corrupted, MD5 should be: 6237bfaf7dcf516b60922b5b26f2dca8.
Karls0 said:
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Click to expand...
Click to collapse
Thanks for this
but now i can't install universal fix for safetynet check
I'm not sure if Magisk v.17.0 is fully backward compatible. Maybe this is preventing the module from installing?
Karls0 said:
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Click to expand...
Click to collapse
thank you very much i installed twrp and followed your steps worked great
Karls0 said:
I'm not sure if Magisk v.17.0 is fully backward compatible. Maybe this is preventing the module from installing?
Click to expand...
Click to collapse
ok so wait for new fix thanks
On my pixel 1 it claims to install, but causes a bootloop. AND updating to the most recent manager breaks using v16. So I'm stuck with an old manager and v16
Yes, the new manager seems to not fit to Magisk v16. In my case it also broke something so I updated to v17.
Karls0 said:
Magisk uninstaller will not works without custom recovery so i think my instruction is not applicable in this situation.
Double check if the package is not corrupted, MD5 should be: 6237bfaf7dcf516b60922b5b26f2dca8.
Click to expand...
Click to collapse
I got it solved by uninstallion the former Magisk package with the uninstaller. After reboot I could reinstall version 17 and until now it works fine. Thanks.
uninstaller for me does not flash for me. error 255 v16 same error and 17.1 wont flash either error 2
Thanks.
I'm able to do the steps without error. But then it is in bootloop. Using redmi note 4g (dior) Dot os
adz63 said:
uninstaller for me does not flash for me. error 255 v16 same error and 17.1 wont flash either error 2
Click to expand...
Click to collapse
Have you tried rebooting TWRP when the errors appear, and where are the logs?
barathrr96 said:
Thanks.
I'm able to do the steps without error. But then it is in bootloop. Using redmi note 4g (dior) Dot os
Click to expand...
Click to collapse
Is this on a clean install of Magisk v17.1? Also, logs...
Didgeridoohan said:
Have you tried rebooting TWRP when the errors appear, and where are the logs?
Is this on a clean install of Magisk v17.1? Also, logs...
Click to expand...
Click to collapse
Thanks.. the device does not belong to me..
for the time being I have installed magisk v16.7 and did installed viper and removed it ..
so when I get the device next time in my hand I will try to flash and take logs..
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.
So I've used TWRP r16 and it throws an "Image not signed or corrupt" error as suggested by other users I ignored it, but everytime I reboot to system and try to get to recovery "no command" show's up meaning TWRP was replaced by stock recovery all help will be appreciated.
Thanks
Akash731 said:
So I've used TWRP r16 and it throws an "Image not signed or corrupt" error as suggested by other users I ignored it, but everytime I reboot to system and try to get to recovery "no command" show's up meaning TWRP was replaced by stock recovery all help will be appreciated.
Thanks
Click to expand...
Click to collapse
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
Hey thanks that worked.
But everytime I boot to system and boot to twrp the data gets encrypted and I can't access the files do you happen to know any solution for this?
Akash731 said:
Hey thanks that worked.
But everytime I boot to system and boot to twrp the data gets encrypted and I can't access the files do you happen to know any solution for this?
Click to expand...
Click to collapse
If you are on stock Rom, according to my knoweldge it is not possible to remove encryption, if you format your date in twrp for removing encryption then reboot to system you can see that the phone is again encrypted.
But in custom roms this doesnt happen.
pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
pradeeppk said:
If you are on stock Rom, according to my knoweldge it is not possible to remove encryption, if you format your date in twrp for removing encryption then reboot to system you can see that the phone is again encrypted.
But in custom roms this doesnt happen.
Click to expand...
Click to collapse
I don't want to try custom rom's as this is my main device guess I'm stuck with the encryption then thanks for your help. :good:
Edit:-
Tried TWRP r20 it decrypts fine thanks
pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
You don't have to flash Magisk after flashing TWRP. The two are unrelated.
After flashing TWRP you have to boot into recovery, not system. Once TWRP was started, you can reboot into system. No need for Magisk (unless you want Magisk anyway).
gewe said:
You don't have to flash Magisk after flashing TWRP. The two are unrelated.
After flashing TWRP you have to boot into recovery, not system. Once TWRP was started, you can reboot into system. No need for Magisk (unless you want Magisk anyway).
Click to expand...
Click to collapse
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
pradeeppk said:
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
Click to expand...
Click to collapse
I am using stock ROM, and yes, also Magisk (installed later). IIRC Magisk is not needed for TWRP to work. When I receive the next OTA notification, I will test this.
The thread you are referring to is for a OnePlus 3T. For our device this is the thread: https://forum.xda-developers.com/moto-g5s-plus/development/recovery-twrp-3-1-1-r7-t3694910.
Since there is no official TWRP for the Moto G5S Plus, I took the following text from the TWRP page for the Moto G5S.
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
Instead of that you can also use fastboot reboot-bootloader, and then from the bootloader start recovery.
pradeeppk said:
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
Click to expand...
Click to collapse
Two days ago I received a notification for an OTA update, containing the August 2019 security patches.
After going back to stock ROM, installing all the updates up to the latest, I installed TWRP. After booting into recovery, and then into system, and recovery again, TWRP was gone. Strange, I don't remember this happening before. Maybe I always installed Magisk before booting into system.
Bottom line: you were right, I was wrong. Thanks for pointing it out.
gewe said:
Two days ago I received a notification for an OTA update, containing the August 2019 security patches.
After going back to stock ROM, installing all the updates up to the latest, I installed TWRP. After booting into recovery, and then into system, and recovery again, TWRP was gone. Strange, I don't remember this happening before. Maybe I always installed Magisk before booting into system.
Bottom line: you were right, I was wrong. Thanks for pointing it out.
Click to expand...
Click to collapse
As like you said this is the first time in my life i need to flash magisk to stick twrp.
I usualy doesn't use root or custom roms, install twrp, remove unnecessary apps from stock system, replace host files with adaway hosts, replace or edit gps config files. and continue using stock.
This is the main routine from Android 1.5
(Samsung spica (i think it was the first Android phone from Samsung)).
It may be due to security reason stock kernel or system delete twrp.
When installing magisk it patch stock boot image, that may be the reason of twrp remains after flashing magisk.
Hi all, as the title implies, I'm a newbie to all this. I tried to root my phone using an online guide on how to root xiaomi mi 9 using TWRP and Magisk. I faced some problems but eventually everything was done as the tutorial said.
Here are the exact steps I've done...
- unlocked the phone via Mi unlocking tool
- started fastboot and installed TWRP 3.3.1-0 ( I installed a version first that didn't start when I pressed both power and volume up, then installed the 331-0 version that worked)
- inside TWRP i installed Magisk 20.4
- The phone restarted but never reach the system. It hangs for sometime on android screen then restarts again and then brings me again to TWRP
I spent quiet sometimes reading online solutions but nothing worked for me...
I tried installing Magisk uninstaller.zip nothing changed. tried wiping cache. Tried installing magisk 20 and 20.3
some solutions recommended installing Magisk 19 0r 17 but they both ended up with error for me.
Please help. I'm on Android 10 with MIUI 11
Never had any problems with magisk What TWRP version have you used?
The steps are the same:
-Unlocked phone.
-TWRP.
-Flash magisk zip (you can install magisk manager, then download latest official magisk zip from it and then flash downloaded zip from TWRP).
-reboot.
Anyway you can fix your system by:
-wipe cache/dalvik.
-FORMAT data (with yes).
I don't think you need this 2 first steps for flashing fastboot ROM but it won't hurt.
-Flash official fastboot ROM in fastboot mod, using mi flash tool or included batch/bash scripts (don't lock your device if you don't want to, choose the right option when you flash, with or without "lock").
Mi 9 Fastboot V11.0.5.0.QFAMIXM Global
Mi 9 Fastboot V11.0.8.0.QFAEUXM EEA
You will loose all your data, apps and settings.
Thanks for your help mate...
I'm using this TWRP version..
----//dl.twrp.me/cepheus/
Strangely enough, my phone started after flashing Magisk-uninstaller-20191011.zip I'm sure i tried this before and it doesn't work.
Anyway, all my app and data are gone. I still want to root though, can you help me? what version of TWRP and Magisk i should use?
F.Ashour said:
Thanks for your help mate...
I'm using this TWRP version..
----//dl.twrp.me/cepheus/
Strangely enough, my phone started after flashing Magisk-uninstaller-20191011.zip I'm sure i tried this before and it doesn't work.
Anyway, all my app and data are gone. I still want to root though, can you help me? what version of TWRP and Magisk i should use?
Click to expand...
Click to collapse
Use twrp-3.3.1-62-cepheus-mauronofrio.img.
Magisk-v20.4.zip
antonio52 said:
Use twrp-3.3.1-62-cepheus-mauronofrio.img.
Magisk-v20.4.zip
Click to expand...
Click to collapse
Thanks for your time mate...
I tried this twrp and magisk your mentioned. same issue. boots back to twrp never to system. Any solutions?
F.Ashour said:
Thanks for your time mate...
I tried this twrp and magisk your mentioned. same issue. boots back to twrp never to system. Any solutions?
Click to expand...
Click to collapse
I would try flash latest fastboot ROM as i said before it will reflash almost everything And then flash magisk by installing magisk manager and download latest magisk zip through it and flash it with twrp-3.3.1-62-cepheus-mauronofrio TWRP
Sometimes first flash of TWRP don't work, just flash it ones more by fastboot flash twrp twrp-3.3.1-62-cepheus-mauronofrio.img from your pc.
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