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...
Related
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 )
Systemless Root & SafetyNet working [GUIDE][Magisk][StockROM-6.0.1][SkyMelon][TWRP]
Hi XDA friends,
After quite investigation I finally have found the way to have our devices Systemless Rooted.
The main advantage? SafetyNet working on our rooted device. That means Google does not notice our device is rooted ...yes, you can play Nintendo games or use Android Pay as well!
View attachment 4371569 View attachment 4371476
Here is the step by step guide:
You Must Have: Unlocked bootloader, ADB Fastboot drivers and Flashtool installed.
- Flash Stock Android 6.0.1 ROM with Flashtool (Wipes checked). I recommend 26.3.A.1.33 for the E2303 model. You can find Stock ROMs in this post.
- Flash TWRP from ADB: "fastboot flash recovery recovery.img" (I tried with v3.0.2.0 and also the new v3.2.1-0 recently published here!)
- Flash custom kernel (SkyMelon 8.1 or 9 without-root) from TWRP. Download v8.1 from this post or v9 directly here: View attachment 9-20171210-no-root.zip. Wipe Dalvik/Cache after install it.
- Flash the latest version of Magisk with TWRP. Wipe Dalvik/Cache after install it. GitHub repo: https://github.com/topjohnwu/Magisk/releases
- Install the latest version of Magisk Manager.apk. GitHub repo: https://github.com/topjohnwu/MagiskManager/releases
- [Optional] In order to avoid flashing errors with TWRP it is recommended to update directly through Magisk Manager. If you want to install previous versions of Magisk (between v14.6 and v15.2), could be neccesary to check the box "Preserve AVB 2.0/dm-verity" before "Direct Install" it.
Note: Magisk v16.4 and Magisk Manager v5.7.0 was the last version working tested by me. From this version I will discontinue testing new Magisk releases on this device. Feel free to post your experience with the new ones
- This method is compatible with E2303, E2306 (reported by @zputnyq) and E2333 (reported by @Yester_Ko) models.
- Compatibility with Apps2SD reported by @tim_pear
Please if this works for you, thanks are very welcome to my first post! Also ideas or improvements to the post are welcome.
Credits:
- Special thanks to @osmank3 who built SkyMelon v9 without-root and help me with Magisk updates.
thanks for sharing your experience , I have A question what about DRM fix , did restore you TA backup ?
Hi! Thanks for your guide. Can you share your safety net check screen on magisk? I try that kernel and some other kernels with different magisk versions, but I don't understand safety net checking status.
Hi othmane.os,
I cannot provide information about restoring the TA. My warranty expired some time ago and I don´t have a TA backup.
Thanks for comment.
othmane.os said:
thanks for sharing your experience , I have A question what about DRM fix , did restore you TA backup ?
Click to expand...
Click to collapse
Hi osmank3,
I have modified the post with the screenshot request and also with some links to the material used in the guide.
If you have any problem, I will be glad to help you. Thanks for comment.
osmank3 said:
Hi! Thanks for your guide. Can you share your safety net check screen on magisk? I try that kernel and some other kernels with different magisk versions, but I don't understand safety net checking status.
Click to expand...
Click to collapse
I want to use your guide but I'm busy to do current configuration of my phone. I delete some files on my system partition for gaining storage (I copied some new versions of upgraded apps to system partition) This take my time but I haven't got enough.
I use skymelon 9 kernel, with supersu. I guess because of supersu changed system partition and safetynet fails. I dislike supersu app but skymelon 9 comes with it. So I built skymelon 9 myself without supersu, but I didn't flash stock rom before installing skymelon 9 without-root and magisk. Now on my phone Magisk15 and skymelon9(compiled by me) installed. Magisk's hide function hiding itself from google apps and choosen apps but safetynet check fails.
Can you or anybody try this guide with skymelon 9 without-root which built by me?
View attachment 9-20171210-no-root.zip
Thanks
Hi osmank3,
I have tested the kernel that you built and it is working perfect. Thank you! This version has been added to the post and of course is menctioned your contribution.
I'm afraid you'll have to install a stock ROM...
BTW: I cannot get working Magisk v15. If I install it direclty from Magisk Manager the installation fails. If I install it through TWRP (and do wipes), the process is correct but when I check it, Magisk Manager not shows it as installed. So for the moment, it is only working for v14.5.
osmank3 said:
I want to use your guide but I'm busy to do current configuration of my phone. I delete some files on my system partition for gaining storage (I copied some new versions of upgraded apps to system partition) This take my time but I haven't got enough.
I use skymelon 9 kernel, with supersu. I guess because of supersu changed system partition and safetynet fails. I dislike supersu app but skymelon 9 comes with it. So I built skymelon 9 myself without supersu, but I didn't flash stock rom before installing skymelon 9 without-root and magisk. Now on my phone Magisk15 and skymelon9(compiled by me) installed. Magisk's hide function hiding itself from google apps and choosen apps but safetynet check fails.
Can you or anybody try this guide with skymelon 9 without-root which built by me?
View attachment 4371416
Thanks
Click to expand...
Click to collapse
GameBoy1989 said:
BTW: I cannot get working Magisk v15. If I install it direclty from Magisk Manager the installation fails. If I install it through TWRP (and do wipes), the process is correct but when I check it, Magisk Manager not shows it as installed. So for the moment, it is only working for v14.5.
Click to expand...
Click to collapse
I'm using magisk manager to patch boot.img with v15. I flash patched_boot.img with TWRP. It is working.
When I update it from v14.5 /data/magisk link crashing. I delete /data/magisk and upgrade on magisk manager as recommended type and reboot system, it is starting to work.
Ups! I forget to say. Check AVB 2.0/dm-verity
It works
Thank you very much. Post updated!
osmank3 said:
I'm using magisk manager to patch boot.img with v15. I flash patched_boot.img with TWRP. It is working.
When I update it from v14.5 /data/magisk link crashing. I delete /data/magisk and upgrade on magisk manager as recommended type and reboot system, it is starting to work.
Ups! I forget to say. Check AVB 2.0/dm-verity
Click to expand...
Click to collapse
Hey, i downloaded Magisk v14.5 and tried to flash it with twrp but i got error "invalid zip file format" What should i do now or what did i do wrong?
Yay i got this work but little bit different way.
1. Flashed stock rom with flashtool. I downloaded my stock rom from XperiFirm.
2. Flashed TWRP with this guide.
3. Flashed Skymelon 8.1 with TWRP and wiped Dalvik/Cache after install.
4. Flashed Magisk v14.0 with TWRP from this post and wiped Dalvik/Cache after install.
When that was done i rebooted and Magisk and Magick manager was installed. They aren't latest versions so i updated them.
1. Downloaded latest Magisk manager from here and installed it.
2. From Magisk manager i checked "Preserve AVB 2.0/dm-verity" and installed it with choosing the recommended option "Direct Install"
Everything seems to working fine and i did this to my E2303 with 26.3.A.1.33
Great! Thanks for sharing :good:
Which is the difference between methods? I see that it also works for you by flashing Magisk v14.0.
Artsii said:
Yay i got this work but little bit different way.
1. Flashed stock rom with flashtool. I downloaded my stock rom from XperiFirm.
2. Flashed TWRP with this guide.
3. Flashed Skymelon 8.1 with TWRP and wiped Dalvik/Cache after install.
4. Flashed Magisk v14.0 with TWRP from this post and wiped Dalvik/Cache after install.
When that was done i rebooted and Magisk and Magick manager was installed. They aren't latest versions so i updated them.
1. Downloaded latest Magisk manager from here and installed it.
2. From Magisk manager i checked "Preserve AVB 2.0/dm-verity" and installed it with choosing the recommended option "Direct Install"
Everything seems to working fine and i did this to my E2303 with 26.3.A.1.33
Click to expand...
Click to collapse
GameBoy1989 said:
- Flash Magisk v14.5 from TWRP. Wipe Dalvik/Cache after install it. GitHub repo: https://github.com/topjohnwu/Magisk/releases
Click to expand...
Click to collapse
This was only thing i made differently. I didn't find right magisk there what would work when flashing because i had problem with "invalid zip file format" so i downloaded that magisk zip file from another place.
This worked fine for me but I directly tried flashing/installing latest version (15.1) from TWRP and later after booting via adb the .apk of the Manager.
Didn't show the Magisk as installed.
With making a backup in TWRP of the boot (just renaming it to .img it has a different extension in the name) and then modifying it (as Manager tells you when you want to install) I could make it work (flashing the modified boot image with fastboot).
(Other steps like flashing the stock ROM and the recovery worked as usual. Also no problems with installing the kernel in TWRP.)
If you try to flash directly the last Magisk version (v15.1 in this case) I don´t know why yet but it doesn´t work. For that reason it is neccesary to first flash Magisk v14.5 (last version working with TWRP).
The way that you do it is also a very good one! Thanks for sharing @lordmd.
lordmd said:
This worked fine for me but I directly tried flashing/installing latest version (15.1) from TWRP and later after booting via adb the .apk of the Manager.
Didn't show the Magisk as installed.
With making a backup in TWRP of the boot (just renaming it to .img it has a different extension in the name) and then modifying it (as Manager tells you when you want to install) I could make it work (flashing the modified boot image with fastboot).
(Other steps like flashing the stock ROM and the recovery worked as usual. Also no problems with installing the kernel in TWRP.)
Click to expand...
Click to collapse
After magisk 14.6+ there is a problem about dm-verity. Magisk can't patch it, so we must preserve the original dm-verity. When you are applying magisk 14.6+ from twrp, you can't preserve and magisk can't patch it. The true way is using magisk manager and patch with preserve dm-verity.
Magisk 15.2 version notes says that problem solved but I try it, it is not solved yet.
My first applying procedure is:
First, patch skymelon 9 boot.img file with new magisk version also with preserve dm-verity on Magisk Manager,
Flash recovery and open with twrp
Apply skymelon 9 wipe dalvik and cache
Apply new magisk
Flash patched img
Let´s see if the next v15.3 beta finally works. Thanks @osmank3
BTW: Did you finally install the stock ROM or could you unroot your CFW for installing Magisk?
osmank3 said:
After magisk 14.6+ there is a problem about dm-verity. Magisk can't patch it, so we must preserve the original dm-verity. When you are applying magisk 14.6+ from twrp, you can't preserve and magisk can't patch it. The true way is using magisk manager and patch with preserve dm-verity.
Magisk 15.2 version notes says that problem solved but I try it, it is not solved yet.
My first applying procedure is:
First, patch skymelon 9 boot.img file with new magisk version also with preserve dm-verity on Magisk Manager,
Flash recovery and open with twrp
Apply skymelon 9 wipe dalvik and cache
Apply new magisk
Flash patched img
Click to expand...
Click to collapse
GameBoy1989 said:
Let´s see if the next v15.3 beta finally works. Thanks @osmank3
BTW: Did you finally install the stock ROM or could you unroot your CFW for installing Magisk?
Click to expand...
Click to collapse
I must flash system partition from stock Rom, after that safetynet passed.
Ty
Is pexorom better than stock. Is this going to work on pexorom.
Please reply
I´ve tried with Pexo Rom v3 and systemless root works with Magisk but it does not passed Safety Net check.
Sayan Qadri said:
Is pexorom better than stock. Is this going to work on pexorom.
Please reply
Click to expand...
Click to collapse
System Configuration:
ROM: MIUI Global 8.1.25 | Beta
Kernel: 3.10.84-perf-g1cb6922
RAM: 2.00 GB
Device: Redmi note 3 (kenzo) with officially unlocked bootloader.
There are a number of tutorials and posts on XDA and YouTube with varying content. Some of them do not flash the boot.img, some of them do.
I will be using Ubuntu to flash using adb and fastboot. Any suggestions regarding that would be great.
Here are the steps I think I should follow ( from the posts I read):
1. Boot into fastboot.
2. Flash twrp-**.img
3. Boot into TWRP recovery.
4. Flash SuperSU
5. Flash Lazyflasher
Would that sequence cause any problem?
No problem, just flash twrp without prior boot.img flashing.
NealSchwartz said:
System Configuration:
ROM: MIUI Global 8.1.25 | Beta
Kernel: 3.10.84-perf-g1cb6922
RAM: 2.00 GB
Device: Redmi note 3 (kenzo) with officially unlocked bootloader.
There are a number of tutorials and posts on XDA and YouTube with varying content. Some of them do not flash the boot.img, some of them do.
I will be using Ubuntu to flash using adb and fastboot. Any suggestions regarding that would be great.
Here are the steps I think I should follow ( from the posts I read):
1. Boot into fastboot.
2. Flash twrp-**.img
3. Boot into TWRP recovery.
4. Flash SuperSU
5. Flash Lazyflasher
Would that sequence cause any problem?
Click to expand...
Click to collapse
yes the steps you're mentioned above is correct, you don't have to flash boot.img. just do the steps above.
Zasnizas said:
yes the steps you're mentioned above is correct, you don't have to flash boot.img. just do the steps above.
Click to expand...
Click to collapse
Thank you, bud! I have successfully install TWRP and also installed RR Rom on my Redmi Note 3. However, I have now lost root access.
I tried flashing the SuperSU.zip again, but to no avail. Where did I go wrong? How can I get root access back?
mistake37 said:
No problem, just flash twrp without prior boot.img flashing.
Click to expand...
Click to collapse
Thanks! Worked like charm. But I now lost root after installing RR custom Rom.
hey
I'm glad it worked, would you be so kind to post the links for those files you mentioned?
Also I'm on the latest stable Miui 9(snapdragon), will it work for me?
NealSchwartz said:
Thank you, bud! I have successfully install TWRP and also installed RR Rom on my Redmi Note 3. However, I have now lost root access.
I tried flashing the SuperSU.zip again, but to no avail. Where did I go wrong? How can I get root access back?
Click to expand...
Click to collapse
I recommend you to use magisk as a root access. To be safe you need to make clean flash your rom again , who's know maybe superSu already exists in your system but not appear on apps drawer by doing this your device will be cleaned from anything that can cause you into bootloop. First download magisk and magisk manager and place it in phone memory or SD card it's up to you and then reboot to TWRP ,wipe everything cache , dalvik cache , system and data then flash rom , gapps and magisk.. reboot. Search for magisk at XDA and download it.
Karanfil said:
I'm glad it worked, would you be so kind to post the links for those files you mentioned?
Also I'm on the latest stable Miui 9(snapdragon), will it work for me?
Click to expand...
Click to collapse
TWRP: Go to official website and download latest version
SuperSU: https://androidfilehost.com/?fid=385035244224394155
lazy-flasher: https://androidfilehost.com/?fid=457095661767111293
I am not sure if it would work, but I was also on MIUI 9 and it worked for me. Hopefully, someone else here will be able to let you know. AFAIK, it should work.
Zasnizas said:
I recommend you to use magisk as a root access. To be safe you need to make clean flash your rom again , who's know maybe superSu already exists in your system but not appear on apps drawer by doing this your device will be cleaned from anything that can cause you into bootloop. First download magisk and magisk manager and place it in phone memory or SD card it's up to you and then reboot to TWRP ,wipe everything cache , dalvik cache , system and data then flash rom , gapps and magisk.. reboot. Search for magisk at XDA and download it.
Click to expand...
Click to collapse
Thank you so much! It worked. I followed the steps, did a clean install and this time opted for Magisk. Awesome!
NealSchwartz said:
Thank you so much! It worked. I followed the steps, did a clean install and this time opted for Magisk. Awesome!
Click to expand...
Click to collapse
awesome.. glad it worked for you :good:
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
In next 2 weeks my mi pad 4 LTE will come to me.
Could you tell me, how to root it by magisk?
1) unlock it by xiaomi (360 hours waiting)
2) flash twrp
3) flash magisk
4) reboot
That is all I need to do to get a root ?)
Tysovwik said:
In next 2 weeks my mi pad 4 LTE will come to me.
Could you tell me, how to root it by magisk?
1) unlock it by xiaomi (360 hours waiting)
2) flash twrp
3) flash magisk
4) reboot
That is all I need to do to get a root ?)
Click to expand...
Click to collapse
yes
Usually you don't even have to flash TWRP recovery if you want to keep original recovery, you can just boot it with "fastboot boot twrp.img".
Just a FYI, the latest magisk 17 has not been working for me. Magisk 16 works just fine.
I am on the xiaomi.eu rom
I'm on latest xiaomi.eu and Magisk 17.1 is working fine
bartekm01 said:
I'm on latest xiaomi.eu and Magisk 17.1 is working fine
Click to expand...
Click to collapse
After I flash magisk 17.1 , my mipad 4 can't use LTE
簡_OvO said:
After I flash magisk 17.1 , my mipad 4 can't use LTE
Click to expand...
Click to collapse
That's strange... I've using magisk on 6 device's and never had this sort of problems. Uninstall magisk and check if it's working again
@簡_OvO
On what Rom you have this problem with Magisk ?
I use Mi Pad 4 LTE and Magisk 17.1 on AOSP 8.1_v25 and everything works as it should.
Magisk it has nothing to do with Modem/Baseband he patching Kernel.
After using Magisk uninstaller or restore stock Kernel works for you LTE ?
bartekm01 said:
That's strange... I've using magisk on 6 device's and never had this sort of problems. Uninstall magisk and check if it's working again
Click to expand...
Click to collapse
After I flash again, it can work well
---------- Post added at 11:25 AM ---------- Previous post was at 11:22 AM ----------
Andro_Nicus said:
@簡_OvO
On what Rom you have this problem with Magisk ?
I use Mi Pad 4 LTE and Magisk 17.1 on AOSP 8.1_v25 and everything works as it should.
Magisk it has nothing to do with Modem/Baseband he patching Kernel.
After using Magisk uninstaller or restore stock Kernel works for you LTE ?
Click to expand...
Click to collapse
I use MIUI10.I cannot understand why.But after I flash magisk again,LTE works well.
Could you please explain where I find the mipad 4 boot image when using this method to patch it?
When choosing the option in magisk manager to patch boot image I have to search for the original boot image to patch as the app doesn't point staight to it...
Many thanks
@Tysovwik, I see you want keep miui. You have to block overwriting recovery by original one. I have seen option for it in twrp, but i have not tested it. The same you can have if you use special zip package.
Twrp has second option for auto install magisk 17.1, but i installed it from zip file (twrp labeled 20.12.2018 can have 18.0)
is this the best way to Root a Mi Pad 4 LTE ?
A long time ago someone said:
Tysovwik said:
In next 2 weeks my mi pad 4 LTE will come to me.
Could you tell me, how to root it by magisk?
1) unlock it by xiaomi (360 hours waiting)
2) flash twrp
3) flash magisk
4) reboot
That is all I need to do to get a root ?)
Click to expand...
Click to collapse
My plan is to follow this process.
Does anyone know if I still have to do step (1) ? or how that is done ?
Some noobie questions.
I already have TWRP installed in my Mi pad 4, and want to keep my original MIUI rom
To install Magisk what should I do next?
Just flash magisk from twrp?
Do I need to flash no-verify-opt-encrypt.zip?
Select any option of wipe in twrp before flashing Magisk?
If I get a bootloop can I just use Magisk unistaller?
soulgazer said:
Some noobie questions.
I already have TWRP installed in my Mi pad 4, and want to keep my original MIUI rom
To install Magisk what should I do next?
Just flash magisk from twrp?
Do I need to flash no-verify-opt-encrypt.zip?
Select any option of wipe in twrp before flashing Magisk?
If I get a bootloop can I just use Magisk unistaller?
Click to expand...
Click to collapse
I would wipe cache /dalvik cache before and wipe cache again after flashing. But yeah, just flash the magisk zip. You check in the settings under security if your device is encrypted, which I'm guessing it probably is already. In which case there's no need to flash no verify encrypt zip. Unless you want to have no encryption. In which case you'll have to start all over, complete format in twrp then flash magisk and no encrypt zip before first boot.
If you want to stay encrypted (assuming you are already), just flash magisk. I haven't done it in a while! So not sure if magisk manager will be installed with zip flash, if it's not there when you boot to system, just download and install latest magisk manager. You can always then download a root checker app from playstore to be sure all went well.
Good luck dude