Need proper guide to install Magisk.
From sratch. Need halp
Poacmy said:
Need proper guide to install Magisk.
From sratch. Need halp
Click to expand...
Click to collapse
>Go to your ROM thread
>flash firmware
>flash ROM
>flash GAPPS
>flash Magisk
>reboot
>enable Magisk Hide
That wasn't hard at all.
AutumQueen92 said:
>Go to your ROM thread
>flash firmware
>flash ROM
>flash GAPPS
>flash Magisk
>reboot
>enable Magisk Hide
That wasn't hard at all.
Click to expand...
Click to collapse
LineageOS comes with pre root. When I install magisk(the zip one), it doesnt show Supersu inside magisk manager and my SafetyNwt fails because of pre installed supersu
Poacmy said:
LineageOS comes with pre root. When I install magisk(the zip one), it doesnt show Supersu inside magisk manager and my SafetyNwt fails because of pre installed supersu
Click to expand...
Click to collapse
Flash this before flashing Magisk: https://forum.xda-developers.com/showpost.php?p=63615067
AutumQueen92 said:
Flash this before flashing Magisk: https://forum.xda-developers.com/showpost.php?p=63615067
Click to expand...
Click to collapse
Thanks for the help. Did all the process again.
One question, do I need to reinstall another root or Magisk is ok?
Poacmy said:
Thanks for the help. Did all the process again.
One question, do I need to reinstall another root or Magisk is ok?
Click to expand...
Click to collapse
Nah, Magisk's in-built root is good enough. No need to complicate thigs by adding other stuff
AutumQueen92 said:
Nah, Magisk's in-built root is good enough. No need to complicate thigs by adding other stuff
Click to expand...
Click to collapse
If the OS I'm using will get an update, what to do?
Using LineageOS.
Poacmy said:
LineageOS comes with pre root. When I install magisk(the zip one), it doesnt show Supersu inside magisk manager and my SafetyNwt fails because of pre installed supersu
Click to expand...
Click to collapse
LOS isn't pre rooted. If you are using some unofficial version then it might be pre rooted but official version isn't pre rooted
Kapiljhajhria said:
LOS isn't pre rooted. If you are using some unofficial version then it might be pre rooted but official version is pre rooted
Click to expand...
Click to collapse
LineageOS for Redmi Note 4x isnt official yet…
Prerequisites:
Unlocked bootloader (via http://en.miui.com/unlock/)
Working fastboot and adb
Custom recovery, e.g. twrp: https://dl.twrp.me/mido/
Installing twrp recovery on mido
* download the recovery file to your computer, e.g. twrp-3.1.1-0-mido.img
* enter fastboot mode
a) shut down phone
b) press volume down + power button, release power in ~4 after the phone vibrates
c) from terminal type
Code:
fastboot boot twrp-3.1.1-0-mido.img
Magisk Installation:
From the phone download the latest versions of the following files:
http://tiny.cc/latestmagisk
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/ (get latest zip)
As an alternative download the files to your computer and then push them to the phone with:
Code:
adb push /sdcard/Magisk-v14.0.zip
adb push /sdcard/no-verity-opt-encrypt-5.1.zip
Reboot into twrp recovery (`adb reboot recovery` from the computer) and:
1. Flash no-verity-opt-encrypt-5.1.zip
2. Flash Magisk-v14.0.zip
3. Reboot.
If the phone still boots into the Mi Recovery and not into TWRP, then enter fastboot mode and do `fastboot boot twrp-3.1.1-0-mido.img` (with the correct path to the IMG file).
---HELP NEEDED ---
I am not able update magisk to 16.0 , i tried every different way the phone Goes to BOOTLOOP. But MAGISK 14.0 WORKS FINE. PLEASE HELP .
(Redmi Note 4 Snapdragon, 8.1 custom Rom )
Related
This guide provides all the steps and patches required to root the Stock system and having Xposed installed while maintaining SafetyNet (Android Pay, Pokemon Go, etc) compatibility. There are some problems of this method that Magisk is supposed to fix, however the latest Magisk v10 is not supporting our stock ROM yet.
The prerequisites of this guide is to have the bootloader unlocked and TWRP recovery.
DOWNLOADS
The recipe require the following ingredients to be downloaded to your internal or external storage:
1. TWRP 3.0.3 (This is the last release at this moment). more info in the Official Thread. Thanks to @jcadduono . TWRP 3.0.2 can't succesfully flash SuperSU 2.79
2. Default Stock ROM for your phone (Required only if you have modified your system or boot partition). You can download them from this thread. Thanks to @DrakenFX . You can alsouse any other custom ROM based on stock such as ZADMix or HelsAx7 SubMix (both tested).
3. SuperSU v2.79. more info in its official thread.
4. SUhide 0.55. More info in its official thread. Thanks to Chainfire.
5. SafetyNet-KCAL Kernel patch, thanks to @jcadduono also for this one!
6. Xposed v86.2 So far only this version is compatible with SUhide.
7. Material Design Xposed Manager app by DVDandroid. More info about this release in its official thread.
8. Root Switch 1.3.3.2 app. Thanks to shakalaca. More info in its official thread.
INSTALLATION
1. Do a backup of your system, I recommend Boot+System+Data partitions. The next steps will modify at least your boot and data partitions, and some Xposed modules will modify also your system partition.
2. If you already have TWRP 3.0.3 then just boot to recovery and proceed to step 3. If you are still using TWRP 3.0.2 please upgrade to the latest TWRP 3.0.3 and reboot to recovery again.
3. I recommend to flash the default Boot and System Partitions and reboot directly to recovery. You can also use any other custom ROM based on the stock ROM such as ZADMix or HelsAx7.
4. All this step must be done without leaving TWRP. Flash SuperSU 2.79 adding also the zips for SUhide 0.55, Xposed v86.2 and the SafetyNet Kernel patch in that order. They must be flashed together. Without leaving TWRP, navigate from the main menu to Advanced > Terminal, introduce the command reboot disemmcwp and the system will reboot by itself once or twice while configuring the settings for SuperSU. Do not be alarmed.
5. Install Xposed Manager and Root Switch apps.
6. Now you have your system fully rooted and you can now install Xposed modules. However you will see the test app SafetyNet Helper reporting a validation failure. Do not worry about it anymore! When you want to initiate a SafetyNet sensitive application (Android Pay or Pokemon Go among others), just open Root Switch and disable root, no need to reboot. SafetyNet will pass and all your apps will work. You can see that Xposed continue working even after disabling root since it was started before. Do not forget to enable root again otherwise new apps requiring root won't load.
Magisk v10+ promises auto root hide per app, but sadly our stock ROM is not yet supported and the method psoposed here requires the user to disable root before loading any SafetyNet protected app.
Enjoy
Reserved for future Magisk guide.
Has anyone managed to get this working on A2017G/B09? I've had a few attempts, forcing systemless SuperSU, but it hangs at the "AXON" boot screen
H0lmEd said:
Has anyone managed to get this working on A2017G/B09? I've had a few attempts, forcing systemless SuperSU, but it hangs at the "AXON" boot screen
Click to expand...
Click to collapse
At what point of the guide is it hanging at the Axon boot screen? after step 4? Have you ensured that the SafetyNet patch is the last thing you flashed before boot?
I just did this on my B29 A2017U phone and it worked perfectly, can switch root on and off with the root switcher and Safetynet passes fully with root set to off.
My previous attempts were all thwarted by the bootloader being unlocked, so that patch to the kernel works great. I'll be backing this up with twrp and getting a little more adventurous (really want to try the BeastMode kernel) soon.
Much thanks for making it nice and simple, Oki !
Oki said:
At what point of the guide is it hanging at the Axon boot screen? after step 4? Have you ensured that the SafetyNet patch is the last thing you flashed before boot?
Click to expand...
Click to collapse
I'm on the same configuration (A2017G B09). I did a step by step installation/reboot/installation/reboot. The Problem is with suhide. After installing suhide the boot process will stick in the Axon screen.
tron1 said:
I'm on the same configuration (A2017G B09). I did a step by step installation/reboot/installation/reboot. The Problem is with suhide. After installing suhide the boot process will stick in the Axon screen.
Click to expand...
Click to collapse
You do not have to reboot after SUhide. The files at step 4 have to be flashed together without leaving TWRP otherwise it won't work.
Oki said:
You do not have to reboot after SUhide. The files at step 4 have to be flashed together without leaving TWRP otherwise it won't work.
Click to expand...
Click to collapse
In theory you're right. But how do like a bugfix to be done if you don't know at which point you're failing?!?
tron1 said:
In theory you're right. But how do like a bugfix to be done if you don't know at which point you're failing?!?
Click to expand...
Click to collapse
The last patch fixes some problems created by SuperSU, SUhide and Xposed. This is why all the patches in step 4 have to be flashed together without leaving TWRP and in the specified order, otherwise it wont work on stock ROMs.
That looks way complicated. What's wrong with the easy way of flashing Magisk V10 + Phh Superuser r266? This has worked on all my devices since the November security patch broke suhide. Magisk now takes care of the flag to hide bootloader unlock status so no need for a kernel patch too. Then flash systemless Xposed by topjohnwu if you want that and you can turn it on and off in Magisk Manager if you want to use Android Pay, play Pokemon Go, etc.
Hi,
I have a A2017G running B08, already unlocked and witch SuperSU 2.79. Just the older version of TWRP.
Can I just upgrade the TWRP and proceed with step 4 and so on? Hate to go back to stock...
Tia,
Cheers,
/Cacti
Tikerz said:
That looks way complicated. What's wrong with the easy way of flashing Magisk V10 + Phh Superuser r266? This has worked on all my devices since the November security patch broke suhide. Magisk now takes care of the flag to hide bootloader unlock status so no need for a kernel patch too. Then flash systemless Xposed by topjohnwu if you want that and you can turn it on and off in Magisk Manager if you want to use Android Pay, play Pokemon Go, etc.
Click to expand...
Click to collapse
For some reason Magisk is not compatible with the Axon 7 kernel. Not yet. This is why it is so complicated and requires a guide. Last time I tested this was yesterday using Magisk v10.2 and phh Superuser r2, and they still failed to root the system.
le_cactus said:
Hi,
I have a A2017G running B08, already unlocked and witch SuperSU 2.79. Just the older version of TWRP.
Can I just upgrade the TWRP and proceed with step 4 and so on? Hate to go back to stock...
Tia,
Cheers,
/Cacti
Click to expand...
Click to collapse
Yes you can try to begin with step 4 with SUhide on. It should work. However I recommend you to upgrade to TWRP 3.0.3 and do the whole step 4.
Gr8. Thanks.
Cheers,
/Cacti
Oki said:
The last patch fixes some problems created by SuperSU, SUhide and Xposed. This is why all the patches in step 4 have to be flashed together without leaving TWRP and in the specified order, otherwise it wont work on stock ROMs.
Click to expand...
Click to collapse
Not quite sure I understand you.
I've tried doing this on A2017g, b09;
0) wipe data/system/boot
1) flash stock Boot stack + System stack zips in twrp 3.0.3 unlocked bl
2) rebooted straight to recovery
3) flashing SuperSU wrote to system so I had to start again but forcing systemless (in terminal; echo "SYSTEMLESS">/data/.SuperSU
4) flash supersu, suhide
5) flash xposed
6) flash the safety net/kcal patch
7) reboot
And I still get stuck on "AXON" boot screen
H0lmEd said:
Not quite sure I understand you.
I've tried doing this on A2017g, b09;
0) wipe data/system/boot
1) flash stock Boot stack + System stack zips in twrp 3.0.3 unlocked bl
2) rebooted straight to recovery
3) flashing SuperSU wrote to system so I had to start again but forcing systemless (in terminal; echo "SYSTEMLESS">/data/.SuperSU
4) flash supersu, suhide
5) flash xposed
6) flash the safety net/kcal patch
7) reboot
And I still get stuck on "AXON" boot screen
Click to expand...
Click to collapse
SuperSU 2.79 installs in systemless mode, no need to set systemless.
Regarding your problem, please try this. Instead of rebooting using the button, open the terminal in TWRP and type "reboot disemmcwp". I hope this was your problem.
This doesn't work for me. Steps:
1. complete wipe
2. install b29 boot stack
2. install b29 system
3. install super su 2.79
4. install su hide 0.55
su hide comes back with an error that says it can't find super su and I should make sure I've installed 2.79 or greater.
edit:
I missed the part in step 3 where you say "reboot directly to recovery". I tried that, but it rebooted to system instead and now I lost TWRP entirely.
edit2:
fastboot flashed twrp again and once in recovery I was able to get through step 4
edit3:
Now it's just stuck on the axon logo. Tried force reboot and the same thing.
Are you sure you tested this from scratch? I have the US version of the axon 7.
Oki said:
SuperSU 2.79 installs in systemless mode, no need to set systemless.
Regarding your problem, please try this. Instead of rebooting using the button, open the terminal in TWRP and type "reboot disemmcwp". I hope this was your problem.
Click to expand...
Click to collapse
I have tried it and am stuck on the same stage also even after using "reboot disemmcwp".
I followed all of your steps and am using an A2017G B08.
corpdecker said:
I just did this on my B29 A2017U phone and it worked perfectly, can switch root on and off with the root switcher and Safetynet passes fully with root set to off.
My previous attempts were all thwarted by the bootloader being unlocked, so that patch to the kernel works great. I'll be backing this up with twrp and getting a little more adventurous (really want to try the BeastMode kernel) soon.
Much thanks for making it nice and simple, Oki !
Click to expand...
Click to collapse
Don't install beast mode yet, from my experience all the steps from op worked fine until I flashed beast mode and it broke safetynet.
lexman098 said:
This doesn't work for me. Steps:
1. complete wipe
2. install b29 boot stack
2. install b29 system
3. install super su 2.79
4. install su hide 0.55
su hide comes back with an error that says it can't find super su and I should make sure I've installed 2.79 or greater.
edit:
I missed the part in step 3 where you say "reboot directly to recovery". I tried that, but it rebooted to system instead and now I lost TWRP entirely.
edit2:
fastboot flashed twrp again and once in recovery I was able to get through step 4
edit3:
Now it's just stuck on the axon logo. Tried force reboot and the same thing.
Are you sure you tested this from scratch? I have the US version of the axon 7.
Click to expand...
Click to collapse
Are you using TWRP 3.0.3? SuperSU 2.79 installs fine and in systemless mode when flashed with the latest TWRP. TWRP 3.0.2 can't flash it properly.
Yes this method has been tested, not only with stock Roms, but also with ZADmix.
If you are doing a complete cleanup before flashing the ROM, boot into system at least once after installing the ROM so the data tree structure is setup. You actually don't need a full cleanup.
Kingo64 said:
I have tried it and am stuck on the same stage also even after using "reboot disemmcwp".
I followed all of your steps and am using an A2017G B08.
Click to expand...
Click to collapse
H0lmEd said:
And I still get stuck on "AXON" boot screen
Click to expand...
Click to collapse
Please ensure you have flashed the right stock ROM for your unit. I have modified Ingredient 2 in the OP since it was highly misleading. Ensure you have unlocked bootloader, TWRP 3.0.3 and flash the right ROM for your system: ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip and ZTE_A2017GV1.0.0B09_StockSystem_by_tron1.zip. And boot to the system at least once before continue to the rest of the procedure.
Can anyone help me install ashyx's TWRP with magisk instead of super su? I've seen that it's been done on the TWRP thread.
I've installed TWRP, then flashed magisk but its not working, seems like I need to patch the boot.img but from my basic understanding that negates the point of magisk right?
Thanks in advance.
sp4r3h said:
Can anyone help me install ashyx's TWRP with magisk instead of super su? I've seen that it's been done on the TWRP thread.
I've installed TWRP, then flashed magisk but its not working, seems like I need to patch the boot.img but from my basic understanding that negates the point of magisk right?
Thanks in advance.
Click to expand...
Click to collapse
You have to install the Magisk zip with TWRP then the Magisk manager apk.
@sp4r3h did you manage to get it working?
@ashyx can you give me some more details?
This is what I tried.
1. Restore stock firmware
2. Flash TWRP
3. Choose Read Only
4. Install zip - Magisk
5. Reboot
Then I get the verification failed error. But from my understanding.. if I use your dm-verify patch then I can't pass SafetyNet?
Which kind of negates the point of magisk?
Thanks for your time.
Follow instructions in first post and flash magisk.zip instead of supersu.
Install magisk manager after system reboot.
napx said:
Follow instructions in first post and flash magisk.zip instead of supersu.
Install magisk manager after system reboot.
Click to expand...
Click to collapse
The manager was removed from the appstore. I'll try manually installing an APK.
napx said:
Follow instructions in first post and flash magisk.zip instead of supersu.
Install magisk manager after system reboot.
Click to expand...
Click to collapse
If I try patching the Magisk then I get the verification failed. If I patch the dm-verify then I can't pass SafetyNet.
Any ideas?
Magisk 12 can't pass SafetyNet anymore.
I also tried the beta Magisk 13.0 but I ran into the same error, so I can't even check if it can pass ...
Follow instructions in first post (in TWRP thread) and flash magisk.zip instead of supersu.
Install magisk manager after system reboot.
That works for me.
napx said:
Magisk 12 can't pass SafetyNet anymore.
Click to expand...
Click to collapse
Google Tweaked Some S**ta again
So What you Gotta do is -
1. Goto Magsisk Manager Settings
2. Enable Core Only and Magisk Hide and select the app (Also Disable the other two adblocker and BusyBox)
3. Reboot
Worked for me (Verified Snapchat and Then Undo all got root back)
But I did one my S4mini
I was just surfing and saw the post and Share it with you guys
Magisk
sp4r3h said:
Can anyone help me install ashyx's TWRP with magisk instead of super su? I've seen that it's been done on the TWRP thread.
I've installed TWRP, then flashed magisk but its not working, seems like I need to patch the boot.img but from my basic understanding that negates the point of magisk right?
Thanks in advance.
Click to expand...
Click to collapse
Well, I also like to try magisk because SU does not work proper. Is there a way to uninstall SU
without a wipe in TWRP ??
Hi. This might be interesting for ALL.. After me Tab hangs, I downloaded the latest OFFICIAL ROM from Samsung,
in my case "DBT-T825XXU1AQF3-20170713092645.zip"...
Extract and place AP, BL, CP and CSC. I decided not to use CSC-home.
Now, reboot.
Activate the developer-option and activate USB Debug.
Restart phone in download-mode (you will need 3 hands Menu, vol-down, power keys at the same time..
Again use odin. This time flash TWRP "twrp_3.1.0-1_sm-t825_AQD6.tar" as AP.
In ODIN, you might select the auto-reboot option because after flashing, you will only need to press
menu + vol-up keys.. Easier with two hands
Now proceed as already described in this thread (format data, wipe etc...) for rooting your tab, BUT (!!!!) do not use supersu. Use magisk "Magisk-v14.0.zip".
After flashing magisk, flash "no-verity-no-encrypt_ashyx.zip".
Now reboot and enjoy a rooted tab. This does not modify the knox counter, warranty is not void. I still use the original samsung firmware..
Lets see if a suitable custom ROM will show up soon. Would be nice if Lineage was available, for tab S3 and phone S8..
ashyx said:
raymondbernard
Need some help with magisk I downloaded the magisk v14.0 and it still says that it's not install just magisk manager is installed I'm trying to root a samsung sm-j320w8
---------- Post added at 03:06 PM ---------- Previous post was at 03:04 PM ----------
ashyx said:
You have to install the Magisk zip with TWRP then the Magisk manager apk.
Click to expand...
Click to collapse
Hey it's raymondbernard trying to get help from you about magisk manager app to root a Samsung sm-j320w8
Click to expand...
Click to collapse
Click to expand...
Click to collapse
It seems it is impossible to get root with magisk on latest Oreo stock. Maybe someone found solution?
I asked and I answer =)
To get the root it is required to
- install latest TWRP (current version twrp-3.2.1-0)
- reboot to TWRP
- install 16.2 or higher magisk, link for 16.2
- install f2fs bug workaround
- reboot system
- install magisk Manager
- enjoy your root =)
dolar4ik said:
I asked and I answer =)
To get the root it is required to
- install latest TWRP (current version twrp-3.2.1-0)
- reboot to TWRP
- install 16.2 or higher magisk, link for 16.2
- install f2fs bug workaround
- reboot system
- install magisk Manager
- enjoy your root =)
Click to expand...
Click to collapse
its not work for me:crying:
Try to follow this guide then: https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
But use latest magisk beta instead of suggested 15.3.
And keep in mind that it is possible to easily restore working state with magisk uninstaller.
Do you have any errors during magisk or workaround installation in twrp console?
dolar4ik said:
Try to follow this guide then: https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
But use latest magisk beta instead of suggested 15.3.
And keep in mind that it is possible to easily restore working state with magisk uninstaller.
Do you have any errors during magisk or workaround installation in twrp console?
Click to expand...
Click to collapse
now its working for me.:highfive::highfive:
dolar4ik said:
I asked and I answer =)
To get the root it is required to
- install latest TWRP (current version twrp-3.2.1-0)
- reboot to TWRP
- install 16.2 or higher magisk, link for 16.2
- install f2fs bug workaround
- reboot system
- install magisk Manager
- enjoy your root =)
Click to expand...
Click to collapse
Hi, does not work for me, stuck at bootloader logo, tried Magisk, followed the steps many times but nothing, can you help please ?
evnimaster said:
Hi, does not work for me, stuck at bootloader logo, tried Magisk, followed the steps many times but nothing, can you help please ?
Click to expand...
Click to collapse
follow this: https://forum.xda-developers.com/mot...reo-8-t3743273
Code:
echo keepverity=true>>/data/.magisk
echo keepforceencrypt=true>>/data/.magisk
Is there a way to remove encryption already?
Remove root?
Is it possible to remove root and the TWRP without hard reset? Does anyone already have the original recovery of Oreo?
DavidKalil10 said:
Is it possible to remove root and the TWRP without hard reset? Does anyone already have the original recovery of Oreo?
Click to expand...
Click to collapse
There is magisk uninstaller provided in official thread.
To remove twrp you just need to flush original recovery via fastboot
Hello guys, can I have some advice on whether I should install this latest Oreo update on my moto z, how is the battery doing on this update? And overall experience?
@dolar4ik
i reflash the stock oreo ROM,then flash TWRP,flash magisk,flash f2fs bug workaround, stuck at bootloader logo,how can i do it??
Flash the Magisk uninstaller, reboot to recovery (you have this option in TWRP) and flash again only the Magisk 16.3 (without the f2fs bug workaround). This worked for me two days ago.
Today I updated to the latest Magisk 16.4 without any problems.
lesbianu said:
Flash the Magisk uninstaller, reboot to recovery (you have this option in TWRP) and flash again only the Magisk 16.3 (without the f2fs bug workaround). This worked for me two days ago.
Today I updated to the latest Magisk 16.4 without any problems.
Click to expand...
Click to collapse
still not work for me.:crying::crying:
---------- Post added at 03:12 AM ---------- Previous post was at 02:58 AM ----------
This is strange. It works on Oreo OTA but it does not work in full flash Oreo ROM.
have anyone help me??
rakee said:
It works on Oreo OTA but it does not work in full flash Oreo ROM.
Click to expand...
Click to collapse
This is right.
I re-flashed my phone using the OPL27.76-51 firmware. Now, no way to install Magisk (old, new, any version).
The solution, I restored a TWRP backup made at the first bootloader unlock (when the ROM was updated only using OTAs, not flashed). Immediately I was able to install Magisk 16.4 - without any F2FS workaround.
HERE is my TWRP backup containing the partitions: Boot, Data & System. Hope it helps!
rakee said:
@dolar4ik
i reflash the stock oreo ROM,then flash TWRP,flash magisk,flash f2fs bug workaround, stuck at bootloader logo,how can i do it??
Click to expand...
Click to collapse
Uninstall magisk with it's own uninstaller.
I installed Magisk on the full Oreo release and everything is working.
I did make a "less bloat, less bs" zip version but I doubt it would make a change.
If you guys want, I can upload it when I get home.
The Marionette said:
I installed Magisk on the full Oreo release and everything is working.
I did make a "less bloat, less bs" zip version but I doubt it would make a change.
If you guys want, I can upload it when I get home.
Click to expand...
Click to collapse
Could you provide your twrp ZIP Version? That would be great.
lesbianu said:
This is right.
I re-flashed my phone using the OPL27.76-51 firmware. Now, no way to install Magisk (old, new, any version).
The solution, I restored a TWRP backup made at the first bootloader unlock (when the ROM was updated only using OTAs, not flashed). Immediately I was able to install Magisk 16.4 - without any F2FS workaround.
HERE is my TWRP backup containing the partitions: Boot, Data & System. Hope it helps!
Click to expand...
Click to collapse
Just got myself a hand me down Moto z.
My friend who gave it to me hasn't touch the phone for a year.
So i started with 6.0 and after multiple updates, now i am on Oreo.
Since i have done ota from Marshmallow, would this method work?
Bootloader was never unlocked.
thanks for any input
Hello. I was going through this guide --> https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-root-unlock-bootloader-t3852520
I've got a problem. I've unlocked bootloader and next I'm booting correctly to TWRP, but when I try to flash any zip of magisk manager I receive an error: "invalid zip file format". I'm using TWRP 3.2.3-0 from first post in guide - I was trying to use both 20181012 and 20181211 versions and no result - still the same error. What can I do? I'm using POCOPHONE F1 with MIUI Global 10.2.3.0
fajniejest said:
Hello. I was going through this guide --> https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-root-unlock-bootloader-t3852520
I've got a problem. I've unlocked bootloader and next I'm booting correctly to TWRP, but when I try to flash any zip of magisk manager I receive an error: "invalid zip file format". I'm using TWRP 3.2.3-0 from first post in guide - I was trying to use both 20181012 and 20181211 versions and no result - still the same error. What can I do? I'm using POCOPHONE F1 with MIUI Global 10.2.3.0
Click to expand...
Click to collapse
You have an old version of TWRP... You need to install a newer version - 3.2.3.2 - which you will find by doing a search for it here on XDA...
Just load img file on INTERNAL storage of phone, choose install>install image file> and click on recovery partition. After install go to home menu and restart recovery...
If you still have issues then download magisk again, it may be corrupt...
Cheers....
ultramag69 said:
You have an old version of TWRP... You need to install a newer version - 3.2.3.2 - which you will find by doing a search for it here on XDA...
Just load img file on INTERNAL storage of phone, choose install>install image file> and click on recovery partition. After install go to home menu and restart recovery...
If you still have issues then download magisk again, it may be corrupt...
Cheers....
Click to expand...
Click to collapse
First of all, I'm not going to install TWRP - I want only to boot into TWRP once for flashing Magisk's ZIP.
Second - in this guide OP says that Unofficial TWRP should be used. I've tried v1 and v2 TWRP from the guide. So which other TWRP should I try to boot into? This? https://forum.xda-developers.com/poco-f1/development/recovery-twrp-3-2-3-x-t3836241
fajniejest said:
First of all, I'm not going to install TWRP - I want only to boot into TWRP once for flashing Magisk's ZIP.
Second - in this guide OP says that Unofficial TWRP should be used. I've tried v1 and v2 TWRP from the guide. So which other TWRP should I try to boot into? This? https://forum.xda-developers.com/poco-f1/development/recovery-twrp-3-2-3-x-t3836241
Click to expand...
Click to collapse
I am new on this forum (pocophone) and i seee how messed up it is. You should definitly use official twrp
You don't need official TWRP, but I think you need to install Disable Force Encryption, before installing the Magisk app
This thread will be more helpful.
fajniejest said:
Hello. I was going through this guide --> https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-root-unlock-bootloader-t3852520
I've got a problem. I've unlocked bootloader and next I'm booting correctly to TWRP, but when I try to flash any zip of magisk manager I receive an error: "invalid zip file format". I'm using TWRP 3.2.3-0 from first post in guide - I was trying to use both 20181012 and 20181211 versions and no result - still the same error. What can I do? I'm using POCOPHONE F1 with MIUI Global 10.2.3.0
Click to expand...
Click to collapse
what are you trying to flash? If it is Magisk Manager, it is in apk format and you just click it to install. No TWRP.
If it is Magisk, which version are you trying to flash? Try 18.1. And preferably download any file from its source.
EDIT: If Magisk v18.1 is also not flashing, try Magisk Canary version. Some phones need that.
tnsmani said:
what are you trying to flash? If it is Magisk Manager, it is in apk format and you just click it to install. No TWRP.
If it is Magisk, which version are you trying to flash? Try 18.1. And preferably download any file from its source.
EDIT: If Magisk v18.1 is also not flashing, try Magisk Canary version. Some phones need that.
Click to expand...
Click to collapse
I'm trying to flash zip with Magisk Manager, as it is said in guide. I know that I can have an apk, but is it enough to just install apk without having custom recovery (but having bootloader unlocked)?
GrecoNeoV said:
You don't need official TWRP, but I think you need to install Disable Force Encryption, before installing the Magisk app
This thread will be more helpful.
Click to expand...
Click to collapse
I will try it if nothing from "my" guide will work, because I really don't want to lose my storage (I see that in this guide installing Magisk needs it)
fajniejest said:
I'm trying to flash zip with Magisk Manager, as it is said in guide. I know that I can have an apk, but is it enough to just install apk without having custom recovery (but having bootloader unlocked)?
I will try it if nothing from "my" guide will work, because I really don't want to lose my storage (I see that in this guide installing Magisk needs it)
Click to expand...
Click to collapse
Well Here is how i managed it to work. After i unlocked my bootloader i launched twrp and flashed beta magisk 19.0 (not latest anymore because 19.1 just today showed up) then i reminded that i forgot about DisableForceEncryption_Treble_v18.0.zip so i flashed iit and after it flashed again magisk 19.0, after reboot it everything was fine
GrecoNeoV said:
You don't need official TWRP, but I think you need to install Disable Force Encryption, before installing the Magisk app
This thread will be more helpful.
Click to expand...
Click to collapse
There is no need to flash DFE. I've unlocked my bootloader, installed TWRP, flashed PE and Magisk 19.0 all without DFE which I don't need.
@OP, you need TWRP version 3.2.3-2 at a minimum, which you can boot using 'fastboot boot twrp-<version>.img' . Then flash Magisk. You'll
need at least version 18.1.
HTH
guhvanoh said:
There is no need to flash DFE. I've unlocked my bootloader, installed TWRP, flashed PE and Magisk 19.0 all without DFE which I don't need.
@OP, you need TWRP version 3.2.3-2 at a minimum, which you can boot using 'flashboot boot twrp-<version>.img' . Then flash Magisk. You'll
need at least version 18.1.
HTH
Click to expand...
Click to collapse
The command is 'fastboot boot twrp-<version>.img'
tnsmani said:
The command is 'fastboot boot twrp-<version>.img'
Click to expand...
Click to collapse
Thanks for the correction. I really don't know where I got flashboot from.
Cheers!
guhvanoh said:
There is no need to flash DFE. I've unlocked my bootloader, installed TWRP, flashed PE and Magisk 19.0 all without DFE which I don't need.
@OP, you need TWRP version 3.2.3-2 at a minimum, which you can boot using 'fastboot boot twrp-<version>.img' . Then flash Magisk. You'll
need at least version 18.1.
HTH
Click to expand...
Click to collapse
So, to make it clear (and to not brick my poco... ):
1. I should use TWRP image from this link --> https://twrp.me/xiaomi/xiaomipocophonef1.html...
2. ...and I don't need to replace my recovery - just booting it once (as You described) is enough.
3. I should flash Magisk's ZIP, not MagiskManager's ZIP or Magisk.apk
4. No more flashing, clearing data and other operations needed.
Am I right?
1 - Yes.
2 - That's down to you. I have TWRP recovery installed and I have the app as well.
3 - You need to flash Magisk and install the apk. See this link for instructions on installing Magisk.
4 - Yes, you need to clear data, wipe dalvik and cache when installing a new ROM. If updating a current rom, I just wipe dalvik & cache.
HTH
Hey I know its not a thread related but if u install magisk can u tell me if you have 60fps screen recoding option? Because I already Dirty flashed rom once and nothing changed still cant unlock it :/
guhvanoh said:
1 - Yes.
2 - That's down to you. I have TWRP recovery installed and I have the app as well.
3 - You need to flash Magisk and install the apk. See this link for instructions on installing Magisk.
4 - Yes, you need to clear data, wipe dalvik and cache when installing a new ROM. If updating a current rom, I just wipe dalvik & cache.
HTH
Click to expand...
Click to collapse
Big thanks! Finally dealt with it. So grateful for Your help. :victory:
Dearminder said:
Hey I know its not a thread related but if u install magisk can u tell me if you have 60fps screen recoding option? Because I already Dirty flashed rom once and nothing changed still cant unlock it :/
Click to expand...
Click to collapse
Yes, I do. I've not tried it though...
Hi there,
i'm rooted and i installed the latest OTA (oxygen os 10.3.7.hd01AA - india rom maybe because i used a patched boot.img in the first time months ago) right now and just like all the times before i made the usual steps:
1) Restored Original Image via Magisk Manager
2) Downloaded and installed OTA
3) Didn't reboot and tried to Install Magisk to inactive slot
Unfortunately 3 didn't work. More than that - Magisk Manager doesn't even recognized Magisk was uninstalled. So there is no Installation option.
Tried to Uninstall it again (Restore Original Image) but that didn't change anything.
a) Was the 2nd "Restore Original Image" after installing the OTA a bad idea?
b) How can i install Magisk now?
I don't reboot the phone as i think it could be bricked after that.
Dacoco said:
Hi there,
i'm rooted and i installed the latest OTA (oxygen os 10.3.7.hd01AA - india rom maybe because i used a patched boot.img in the first time months ago) right now and just like all the times before i made the usual steps:
1) Restored Original Image via Magisk Manager
2) Downloaded and installed OTA
3) Didn't reboot and tried to Install Magisk to inactive slot
Unfortunately 3 didn't work. More than that - Magisk Manager doesn't even recognized Magisk was uninstalled. So there is no Installation option.
Tried to Uninstall it again (Restore Original Image) but that didn't change anything.
a) Was the 2nd "Restore Original Image" after installing the OTA a bad idea?
b) How can i install Magisk now?
I don't reboot the phone as i think it could be bricked after that.
Click to expand...
Click to collapse
Well the procedure is disable all magisk modules. Reboot. Take the update don't reboot when the updater says to. Go to magisk select patch to inactive slot let it do it's thing then reboot
for now make a new patched one based on your current is to obtain root like you did initially
Ex pull your current non root boot img patch it in magisk then flash in fastboot
If you need I can grab the India ROM from Updater and make you a patched boot image?
I've already done it for HD01AA EU and HD01BA
Hey, i could manage to install Magisk into inactive slot after updating Magisk manager to the latest version. I would try to reboot now?
If I would like to patch my current boot.img - how can I do so?
digidude512 said:
If you need I can grab the India ROM from Updater and make you a patched boot image?
I've already done it for HD01AA EU and HD01BA
Click to expand...
Click to collapse
Thanks. I think I'll try to reboot and then - if it doesn't Boot - I will come back to you.
Dacoco said:
Thanks. I think I'll try to reboot and then - if it doesn't Boot - I will come back to you.
Click to expand...
Click to collapse
Any luck?
digidude512 said:
Any luck?
Click to expand...
Click to collapse
Booted up and root is working! Thanks a ton!
Dacoco said:
Booted up and root is working! Thanks a ton!
Click to expand...
Click to collapse
Well the ROM is already downloading, Might as well do the boot and recovery images anyway lol
When I'm done I'll update this thread to include HD01AA India
https://forum.xda-developers.com/7t-pro/how-to/oos-10-0-13-hd01aa-t4195159