Hi,
I'm a happy new owner of the redmi note 4 and I've already unlocked the bootloader.
I would like to use google camera, and eventually adblock.
I've seen there are various way to
- install bootloaders (and it seems there are also various boatloaders)
- root the phone
- enable camera2 api, with and without root
- ...
Actually I like to keep the stock rom and the phone as vanilla as possible, as I've read there are redundant issue with custom rom. I also do like the idea of being able to update the phone "normally", which seems to be what you call OTA update . Also, I've seen that some app may not work if some verification fails ?
So basically the question could you explain me a bit the broad picture and what would you recommend ?
Thank's
PS : sorry I'm not super acurate, I rooted my LG G2 years ago and things seems to have evolved a lot since then.
jbonlinea said:
Hi,
I'm a happy new owner of the redmi note 4 and I've already unlocked the bootloader.
I would like to use google camera, and eventually adblock.
I've seen there are various way to
- install bootloaders (and it seems there are also various boatloaders)
- root the phone
- enable camera2 api, with and without root
- ...
Actually I like to keep the stock rom and the phone as vanilla as possible, as I've read there are redundant issue with custom rom. I also do like the idea of being able to update the phone "normally", which seems to be what you call OTA update . Also, I've seen that some app may not work if some verification fails ?
So basically the question could you explain me a bit the broad picture and what would you recommend ?
Thank's
PS : sorry I'm not super acurate, I rooted my LG G2 years ago and things seems to have evolved a lot since then.
Click to expand...
Click to collapse
So, you want root and GCam working on your MIUI without breaking OTA updates, is that right?
• Unlock bootloader, flash RedWolf recovery then through Redwolf recovery flash LazyFlasher.
• In Redwolf enable OTA survival.
• Flash Magisk through recovery for root.
• For GCam to work, you need to enable Camera2API in your build.prop. This can be done through a simple Magisk module too. But I must warn you enabling Camera2API on MIUI might break some functionalities of your MIUI stock camera app.
I am using pixel experience 8.1 oreo rom in my redmi notr 4.and i have also install google canera mod.mgcmod5.i have done all the settings but ehen i am trying to take puctures its force closing and lagging..need solution..
ArK96 said:
So, you want root and GCam working on your MIUI without breaking OTA updates, is that right?
• Unlock bootloader, flash RedWolf recovery then through Redwolf recovery flash LazyFlasher.
• In Redwolf enable OTA survival.
• Flash Magisk through recovery for root.
• For GCam to work, you need to enable Camera2API in your build.prop. This can be done through a simple Magisk module too. But I must warn you enabling Camera2API on MIUI might break some functionalities of your MIUI stock camera app.
Click to expand...
Click to collapse
After every OTA update do I need to re-flash everything?
ÀnkanKoley said:
After every OTA update do I need to re-flash everything?
Click to expand...
Click to collapse
If RedWolf succeeds OTA survival, then there is no need. But after OTA if RedWolf is replaced by stock recovery, then yes you'll have to flash everything once again. Refer RedWolf thread for more details on OTA survival.
ArK96 said:
So, you want root and GCam working on your MIUI without breaking OTA updates, is that right?
• Unlock bootloader, flash RedWolf recovery then through Redwolf recovery flash LazyFlasher.
• In Redwolf enable OTA survival.
• Flash Magisk through recovery for root.
• For GCam to work, you need to enable Camera2API in your build.prop. This can be done through a simple Magisk module too. But I must warn you enabling Camera2API on MIUI might break some functionalities of your MIUI stock camera app.
Click to expand...
Click to collapse
Sounds right and great, thank's !
Two question.
- I've read somewhere that some custom recovery and/or root may cause some app to fail, notably banking app.
Well I used to use such app on my rooted G2 , but will it remain posible after folowing the process you suggest above ?
about redwolf, there is quite a lot of explainations in theses two links 1 and 2, however I can figure out how to install redwolf ?! what am I suppose to do with the .iso image available for download ? isn't there a step by step install guide somewhere ?
Thank's
jbonlinea said:
Sounds right and great, thank's !
Two question.
- I've read somewhere that some custom recovery and/or root may cause some app to fail, notably banking app.
Well I used to use such app on my rooted G2 , but will it remain posible after folowing the process you suggest above ?
about redwolf, there is quite a lot of explainations in theses two links 1 and 2, however I can figure out how to install redwolf ?! what am I suppose to do with the .iso image available for download ? isn't there a step by step install guide somewhere ?
Thank's
Click to expand...
Click to collapse
Use Magisk for root and once Magisk is installed enable Magisk hide for the banking app, this will hide root from that particular app.
Installing a custom recovery like redwolf :
1. Unlock your phone's bootloader.
2. Download the recovery image file, rename it to "recovery.img" and place in a folder on your computer. Make sure you have working ADB and fastboot drivers installed on this computer.
3. Connect your phone in fastboot mode (Volume Down + Power button)
4. Open command prompt in the folder containing the downloaded recovery. (Shift + Mouse right click)
5. Type the below command into the command prompt
fastboot flash recovery recovery.img
fastboot boot recovery.img
Once inside recovery flash ROM, Magisk, if ROM is MiUI flash lazyflasher too, or phone won't boot. If custom ROM ignore lazyflasher and flash GApps instead.
If recovery installation instructions confuse you there are infinite number of YouTube videos that will help you.
ArK96 said:
So, you want root and GCam working on your MIUI without breaking OTA updates, is that right?
• Unlock bootloader, flash RedWolf recovery then through Redwolf recovery flash LazyFlasher.
• In Redwolf enable OTA survival.
• Flash Magisk through recovery for root.
• For GCam to work, you need to enable Camera2API in your build.prop. This can be done through a simple Magisk module too. But I must warn you enabling Camera2API on MIUI might break some functionalities of your MIUI stock camera app.
Click to expand...
Click to collapse
What would broke on miui camera?
amnher said:
What would broke on miui camera?
Click to expand...
Click to collapse
The HDR mode.
ArK96 said:
Use Magisk for root and once Magisk is installed enable Magisk hide for the banking app, this will hide root from that particular app.
Installing a custom recovery like redwolf :
1. Unlock your phone's bootloader.
2. Download the recovery image file, rename it to "recovery.img" and place in a folder on your computer. Make sure you have working ADB and fastboot drivers installed on this computer.
3. Connect your phone in fastboot mode (Volume Down + Power button)
4. Open command prompt in the folder containing the downloaded recovery. (Shift + Mouse right click)
5. Type the below command into the command prompt
fastboot flash recovery recovery.img
fastboot boot recovery.img
Once inside recovery flash ROM, Magisk, if ROM is MiUI flash lazyflasher too, or phone won't boot. If custom ROM ignore lazyflasher and flash GApps instead.
If recovery installation instructions confuse you there are infinite number of YouTube videos that will help you.
Click to expand...
Click to collapse
Thank's again , that's awesome!
Maybe a few more question
FIRST
at step 2) how do I make sure I have a working ADB and Fastboot drivers ?
As far as I understand, fastboot drivers should already be installed ; however I suspect ADB not to be installed.
Indeed, I've already unlocked the bootloader with this tutorial, and I can confirm the phone is unlocked from settings > more settings > developper options > Mi locking status.
So basically I've already installed MiUSBDrivers and ran miflashunlock. There are fastboot.exe, fastboot_unlock.exe and AdbWinApi.dll files in the miflash_unlock folder I downloaded and used to unlock, but I haven't used any of these later 3 files.
I have found this post to install ADB
SECOND
at step 4), the best would be to place the recovery image downladed from here into the folder containing ADB downloaded just above right ?
Then, go on with step 5)
THIRD
If everything went well, my phone is supposed to reboot in redwolf recovery, ok.
but whart do you mean by "Once inside recovery flash ROM" ?
Why am I suposed to flash a rom ?
To my understanding, I already have a rom, miui, and do not want to change for the moment.
Should I download the "Full Rom" from here, or the "Redmi Note 4 Qualcomm Latest Global Stable Version Fastboot File" rom from here ? If so, what souhld I do with the rom; where sould I place it, on the computer, on the phone ?
Or do I need to flash ROM only if I want to change/upgrade my rom ?
FOURTH
To flash Magisk and Lazyflasher.
I understood that redwolf recovery comes with Magisk, so I assume I'll only have to go to "install" tab of redwolf, and I'll find the Magisk file to flash.
Ok what about Lazyflasher ? is it also provided with redwolf ?
Or should I download it ? and if so where should I place the file ?
FIFTH (and last)
I assume once installed from recovery, Magisk will show himself as an app/icon on the "desktop", and I'll be able to selectively enable Magisk hide for the banking app.
Thank's again for your help.
Sorry if I have too many questions, I'm a little rusted, and prefer having a comprehensive picture of the porcess before jumping into it, and avoid one more post entitled helpppp pleeeeeese I bricked my phone
jbonlinea said:
Thank's again , that's awesome!
Maybe a few more question
FIRST
at step 2) how do I make sure I have a working ADB and Fastboot drivers ?
As far as I understand, fastboot drivers should already be installed ; however I suspect ADB not to be installed.
Indeed, I've already unlocked the bootloader with this tutorial, and I can confirm the phone is unlocked from settings > more settings > developper options > Mi locking status.
So basically I've already installed MiUSBDrivers and ran miflashunlock. There are fastboot.exe, fastboot_unlock.exe and AdbWinApi.dll files in the miflash_unlock folder I downloaded and used to unlock, but I haven't used any of these later 3 files.
I have found this post to install ADB
SECOND
at step 4), the best would be to place the recovery image downladed from here into the folder containing ADB downloaded just above right ?
Then, go on with step 5)
THIRD
If everything went well, my phone is supposed to reboot in redwolf recovery, ok.
but whart do you mean by "Once inside recovery flash ROM" ?
Why am I suposed to flash a rom ?
To my understanding, I already have a rom, miui, and do not want to change for the moment.
Should I download the "Full Rom" from here, or the "Redmi Note 4 Qualcomm Latest Global Stable Version Fastboot File" rom from here ? If so, what souhld I do with the rom; where sould I place it, on the computer, on the phone ?
Or do I need to flash ROM only if I want to change/upgrade my rom ?
FOURTH
To flash Magisk and Lazyflasher.
I understood that redwolf recovery comes with Magisk, so I assume I'll only have to go to "install" tab of redwolf, and I'll find the Magisk file to flash.
Ok what about Lazyflasher ? is it also provided with redwolf ?
Or should I download it ? and if so where should I place the file ?
FIFTH (and last)
I assume once installed from recovery, Magisk will show himself as an app/icon on the "desktop", and I'll be able to selectively enable Magisk hide for the banking app.
Thank's again for your help.
Sorry if I have too many questions, I'm a little rusted, and prefer having a comprehensive picture of the porcess before jumping into it, and avoid one more post entitled helpppp pleeeeeese I bricked my phone pen
Click to expand...
Click to collapse
ADB/Fastboot Drivers
Looks like you don't have ADB/Fastboot installed system wide. Although it is completely fine to use adb/fastboot in a folder, installing it system wide is much more convenient because you can open a command window in any folder and execute ADB/Fastboot commands. [URL="https://forum.xda-developers.com/showthread.php?t=2588979”]Here's the link[/URL] to download the system wide installer. Install it and REBOOT your PC.
Flashing RedWolf
Once drivers are installed and PC rebooted, connect phone in Fastboot mode and follow my previous instructions. Also now you can open command prompt in any folder and execute the commands since ADB/Fastboot is installed system wide.
Flashing ROM
Sorry if I confused you there in the previous post. If you wish to stick with your current MIUI ROM then you don't need to flash any ROM file.
Flashing Lazyflasher
You MUST flash lazyflasher since you want to stay with MIUI. If you install a custom recovery on MIUI without flashing lazyflasher, the phone will not boot and will be stuck at the MI logo. I've attached the file.
Flashing Magisk
Flash Magisk after lazyflasher. You may download the latest package from Magisk thread or use RedWolf's built in Magisk package as you said and update it later through the Magisk manager app. And yes, you can select which apps can be Magisk hidden.
ArK96 said:
ADB/Fastboot Drivers
Looks like you don't have ADB/Fastboot installed system wide. Although it is completely fine to use adb/fastboot in a folder, installing it system wide is much more convenient because you can open a command window in any folder and execute ADB/Fastboot commands. [URL="https://forum.xda-developers.com/showthread.php?t=2588979”]Here's the link[/URL] to download the system wide installer. Install it and REBOOT your PC.
Flashing RedWolf
Once drivers are installed and PC rebooted, connect phone in Fastboot mode and follow my previous instructions. Also now you can open command prompt in any folder and execute the commands since ADB/Fastboot is installed system wide.
Flashing ROM
Sorry if I confused you there in the previous post. If you wish to stick with your current MIUI ROM then you don't need to flash any ROM file.
Flashing Lazyflasher
You MUST flash lazyflasher since you want to stay with MIUI. If you install a custom recovery on MIUI without flashing lazyflasher, the phone will not boot and will be stuck at the MI logo. I've attached the file.
Flashing Magisk
Flash Magisk after lazyflasher. You may download the latest package from Magisk thread or use RedWolf's built in Magisk package as you said and update it later through the Magisk manager app. And yes, you can select which apps can be Magisk hidden.
Click to expand...
Click to collapse
Awesome !
Great to know that I should fisrt flash lazyflasher and then magisk.
Stupid, probably last question
Should I do everything up to and incliding flashing lazyflsher, rebot normally, and then reboot again in redwolf and flash magisk ?
of is this extra zealous ?
Thanks
jbonlinea said:
Awesome !
Great to know that I should fisrt flash lazyflasher and then magisk.
Stupid, probably last question
Should I do everything up to and incliding flashing lazyflsher, rebot normally, and then reboot again in redwolf and flash magisk ?
of is this extra zealous ?
Thanks
Click to expand...
Click to collapse
While it can all be flashed at one go, I suggest you to flash LF and once boot your device successfully and reboot to redwolf and flash Magisk afterwards.
ArK96 said:
While it can all be flashed at one go, I suggest you to flash LF and once boot your device successfully and reboot to redwolf and flash Magisk afterwards.
Click to expand...
Click to collapse
Thank you very much !
jbonlinea said:
Thank you very much !
Click to expand...
Click to collapse
No problem.
ArK96 said:
No problem.
Click to expand...
Click to collapse
hum, :silly:
the link you sent for adb do not work
jbonlinea said:
hum, :silly:
the link you sent for adb do not work
Click to expand...
Click to collapse
Here,
https://www.dropbox.com/s/mcxw0yy3jvydupd/adb-setup-1.4.3.exe?dl=0
ArK96 said:
Here,
https://www.dropbox.com/s/mcxw0yy3jvydupd/adb-setup-1.4.3.exe?dl=0
Click to expand...
Click to collapse
Excellent !
so
- I did installed redwolf recovery - changed settings as advised here
- flashed lazyflasher
- reboot -> wokrs I'm back on miui
- reboot in redwolf and flashed magisk
- reboot into android, installed rootchek, I'm rooted
- hide magisk from magisk manager for my apps --> working
Everything works
Further questions :
- Am I suppose to clean cache at some stage ? I can still do it now ?
- Is there some recomended module for magisk ? (not sure what they are for)
- as for everything else, I've seen many options to enable camera2api. Which one would you recomend ? is "persist.camera.HAL3.enabled=1" the only needed change or this treat rises something this
- is there a recomended version/release of google camera to use with miui9 global, latest update (not developper) (I've seen various reported issues depending on version/release)
- any other must/nice/interesting hacks to fully enjoy this phone ?
- any security recomendation ? (re-locking the bootloader ? instally some utilities... ?)
thanks
after that, I'll be done
jbonlinea said:
Excellent !
so
- I did installed redwolf recovery - changed settings as advised here
- flashed lazyflasher
- reboot -> wokrs I'm back on miui
- reboot in redwolf and flashed magisk
- reboot into android, installed rootchek, I'm rooted
- hide magisk from magisk manager for my apps --> working
Everything works
Further questions :
- Am I suppose to clean cache at some stage ? I can still do it now ?
- Is there some recomended module for magisk ? (not sure what they are for)
- as for everything else, I've seen many options to enable camera2api. Which one would you recomend ? is "persist.camera.HAL3.enabled=1" the only needed change or this treat rises something this
- is there a recomended version/release of google camera to use with miui9 global, latest update (not developper) (I've seen various reported issues depending on version/release)
- any other must/nice/interesting hacks to fully enjoy this phone ?
- any security recomendation ? (re-locking the bootloader ? instally some utilities... ?)
thanks
after that, I'll be done
Click to expand...
Click to collapse
Clean cache not required.
Magisk modules are MODs for your system but they are done without tampering your system. (Systemless MODs).
Try Dolby atmos ZTE Axon 7 audio MOD module, YouTube vanced module (100% Adfree, background play)..etc
Use Arnova's GCam.
Never ever relock bootloader with a custom recovery or custom ROM. Else irreversible brick.
I've repeated too much stuff that has been posted in the forum already, if you have any further doubts search the forum or use Google.
Flash through redwolf the attached file to enable camera2api. If you want to uninstall it later go to magisk manager and delete it.
Cheers.
ArK96 said:
Clean cache not required.
Magisk modules are MODs for your system but they are done without tampering your system. (Systemless MODs).
Try Dolby atmos ZTE Axon 7 audio MOD module, YouTube vanced module (100% Adfree, background play)..etc
Use Arnova's GCam.
Never ever relock bootloader with a custom recovery or custom ROM. Else irreversible brick.
I've repeated too much stuff that has been posted in the forum already, if you have any further doubts search the forum or use Google.
Flash through redwolf the attached file to enable camera2api. If you want to uninstall it later go to magisk manager and delete it.
Cheers.
Click to expand...
Click to collapse
Hi dude
I'm almost done but back to square 0, with blinking black screen at boot !
No crisis, I can still go to redwolf recovery, as well as fastboot.
How it happend ?
In magisk manager (on miui) I checked what modules were available in the download panel, and tried "Google Pixel 2 Experience" or something similar.
On reboot, the mi logo is displayed, then I have a black screen blinking on and off, without mi logo, just black, on and off
I thus wanted to unistal the mod with magisk module uninstaller, but the install fails and return that "magisk is not installed" and "magisk is required for this mod"
So I obviously couldn't try to uninstall the supposed failing module
I thus rebooted in redwold and installed magisk from redwolf (the included release), things went well
However, I still cant install magisk module uninstaller, getting the same error as above.
I took my chance and try to re-install magisk from the zip filed I downloaded, the install process was successfull, but I still can't install magisk mod uninstaller, and the black screen issue persist.
Lastly, I took my chance and try to re-install lazy flasher, the install process was successfull, but the black-screen issue persist.
To be honest, I'm a bit sctuck now.
What may be the right procedure to solve this problem ?
Am I screwed and do I have to reflash a whole rom ?
If so Should I do it from redwolf, and how ?
Or should I do it from the pc with fastboot, and how ?
Thanks for your directions
ps: i was interested by pixel 2 experience module as at it was written that it was compatible with mido and provides camera2api, which might have been a nice combo.
ps 2 : I also did installed dolby as you suggested, it worked but the demo crashed to app
ps 3 : I also did installed youtube vaccant, but I couldn't see any new app and my original youtube still had add and couldn't play in the back... not sure it reveals something on the effectiveness of magisk...
Related
This guide shows how to install TWRP and Magisk even starting from firmwares after B19 A2017U firmware (starting B25, ZTE removed Fastboot). As always read the ENTIRE directions before beginning. If you'd like to try a faster method, see instead King1990's Alternate Method posted below steps A, B and C.
Step A involves downgrading your OS to B19. If you are on B25 or higher currently, you must not skip this step. If you are on B19, skip this step.
Step B is upgrading to B32 on an unlocked system, retaining Fastboot and the Recovery by using DrakenFX's method.
Step C is installing Magisk.
STEP A: FLASH TO B19 WITH TWRP USING EDL MODE
NOTE: This assumes you are unlocked. If you need to unlock starting from a firmware later than B19, please follow the EDL Unlock instructions at the EDL Thread, or use the Axon7Toolkit unlock, which is essentially the same but may be easier for some.
1. Install MiFlash using the EDL thread
2. Install the QUALCOMM drivers linked in the same thread.
3. Download "B19-NOUGAT_FULL (Nougat 7.1.1)" from the same thread.
4. Extract the ZIP file.
5. Open MiFlash, select the named sub-folder from the ZIP
6. Connect Axon 7 via a USB cable, and hold VOL-UP/VOL-DOWN/POWER until the screen goes black and the red notification LED blinks very intermittently (~1 time per 4 seconds) to get it in EDL mode.
7. Hit Refresh in MiFlash and confirm device is shown in list.
8. Hit Flash in MiFlash to flash it. (This rolls back your device to B19 stock)
9. Repeat Steps A.3-A.8 for "B19-NOUGAT_TWRP (Nougat 7.1.1)," found in the same EDL thread (to get TWRP).
10. After EDL flashing B19-NOUGAT_TWRP (Nougat 7.1.1), hold Power+VolUp when boot into TWRP. At the first warning screen, slide to allow modifications, but DO NOT BOOT INTO THE ROM until you complete the next step re: no-verity.
11. Tap Mount, and then Mount the phone via MTP in TWRP. Transfer over the latest (5.1 at time of writing) no-verity-opt-encrypt-5.1.zip file from this link (original thread) to your phone via MTP. Flash this file using the "Install" command in the TWRP main menu.
Troubleshooting Notes:
If bootup freezes at the very first screen after the ZTE logo ("Start - Continue to Boot..."), you probably have either (1) not properly flashed the B19 FULL before the TWRP folder, or (2) enabled changes in TWRP without flashing the zip in Step 11. If so, start over from the beginning, reinstall B19 FULL and TWRP via EDL. If you cannot boot into the system, this is likely your only option.
If you are stuck on a bootup screen that says "To start android, enter your password": You have probably mistakenly started a normal boot after flashing the B19 FULL but before flashing TWRP. Do not attempt to enter a password, simply get back into EDL mode to flash the TWRP folder for Step A.9. Do this by either holding VOL+/VOL-/POWER, or by using the ADB command if available, "adb reboot edl" . If you are in-between steps and having trouble finding a part of the boot sequence that ADB receives commands, try opening an ADB console on Windows and entering "adb devices -l" to see if your device is visible to ADB at either the bootloader itself (VOL+/POWER), or the main root TWRP screen. (Worst case, if TWRP is not installed, but if you can access Fastboot, put the TWRP .img file in the same directory on your PC as your ADB/Fastboot .exes, rename to "recover.img" and use the command "fastboot boot recovery.img" to temporarily boot into TWRP.)
If MiFlash cannot flash to your device even when it can see your device: If you can access ADB, try the command "adb reboot edl" . Some Axon 7 phones apparently do not correctly enter EDL mode when holding VOL+/VOL-/POWER, and although visible to MiFlash cannot be flashed unless a software command puts the phone into EDL. Alternatively, Axon 7 Toolkit can do this - select Option 10 when ADB is active.
If you follow this guide and receive a ctsProfile mismatch error when running a SafetyNet check in Magisk, you likely had some remnant of a prior SU installation that is triggering the error. Please follow the steps in this troubleshooting guide: https://android.gadgethacks.com/how-to/magisk-101-fix-safetynet-cts-profile-mismatch-errors-0178047/
STEP B: UPDATE TO B32
Important: You cannot use the update process in Mifavor to update, or you will lose fastboot. Instead, any updates must be flashed via TWRP.
1. Go to DrakenFX's thread and follow the instructions. Relevant portion added below for simplicity.
2. Download and move to your phone (Internal or SD):
- A2017UV1.1.0B32_bootstack_by_DrakenFX.zip
- A2017UV1.1.0B32_StockSystem_by_DrakenFX.zip
3. Boot into TWRP, and Wipe Cache, Dalvik, and Data
4. Flash ("Install" in TWRP) A2017UV1.1.0B32_bootstack_by_DrakenFX.zip, then install A2017UV1.1.0B32_StockSystem_by_DrakenFX.zip.
5. Flash the no-verity-opt-encrypt-5.1.zip file again from this link (you should already have this on your phone from Step 1 above)
STEP C: INSTALL MAGISK ZIP VIA TWRP
NOTE: If you have performed this with the 13.6 Beta per my earlier guide, simply download Magisk 14.0 within the Manager app and then flash 14.0 in TWRP to update. For new installations, flashing directly the 14.0 ZIP file should be fine. Any Magisk before 13.6 Beta will likely no longer work.
1. This guide assumes you have a clean image with NO SU. (If you have used SuperSU or another SU, you will need to either reset/reflash a clean image, or uninstall it sufficiently. If you have a prior Magisk, there is a Magisk Uninstall tool (here You can proceed without flashing a clean image using that tool, included in Step 3b below.)
2. Download the latest Beta Magisk ZIP file ("Magisk-v14.0.zip") in the main Magisk thread. I have also attached it to this thread for convenience. NOTE that this ZIP file also automatically installs Magisk Manager, so you do not need to download or install it separately in Android.
3. Go to TWRP, and install the Magisk-v14.0.zip. Clear Dalvik/Cache after install.
4. Reboot into stock, and open Magisk Manager which should be installed now automatically. Magisk Hide should be auto enabled, MagiskSU 14.0 should be installed, and all checks should pass including SafetyNet. Catch all the Poke-mans and Pay all the Androids.
Please make a TWRP backup before attempting, and be ready to roll back if needed.
Alternate Method (Thanks to King1990)
This method may be quicker, so you may prefer to try this method first, or as an alternate if the above method is too complex or doesn't work for you:
*these steps only if you are already unlocked your bootloader first UNLOCK *
*Note: it does not matter if your on stock B25 or B32 or any custom roms just follow the steps below*
*Backup first*
1- Download & install Axon7toolkit 1.2.1,install drivers & ADB from the tool (option 1).
2- using the tool, choose option 11 & follow the instructions to flash "A2017U_B19-NOUGAT_FULL_EDL" using Miflash (Axon7toolkit will start Miflash)
3- if the flashing was successful reboot your phone
4- now update using OTA to B25 then again update to B32 through OTA .
5- now you have completely stock B32 , you will also lose fastboot command
6- Reboot to EDL
7- Start Miflash directly it should be here "C:\Program Files\Xiaomi\MiPhone" & Click on refresh , a COM port should appear
8- in the target white bar, paste this destination "C:\Axon7Development\Axon7Toolkit\miflash\unlock\FASTBOOT_UNLOCK_EDL_N" & click flash, if succeed reboot & you should now have fastboot commands
9- again use Axon7toolkit & choose option 9 to flash TWRP , follow the instruction and you should have TWRP.
10- start the system then reboot to recovery and flash magisk 14.0 check for safety net if fails just reboot your phone & it will pass.
11- done.
Previous threads and guides
(Previous Thread)
-----------
(Previous Magisk and OTA process - DO NOT USE)
STEP 2: INSTALLING MAGISK 13.2 WITH ROOT AND SAFETYNET PASS
1. This guide assumes you have a clean image with NO SU. (If you have SuperSU or another SU, you will need to either reset/reflash a clean image, or uninstall it sufficiently. If you have a prior Magisk, there is a Magisk Uninstall tool. You can proceed without flashing a clean image using that tool, included in Step 3b below.)
2. Enable Settings->Security->Unknown Sources in stock.
3. Download Magisk Manager 5.0.6 and Magisk 13.2 (here, and attached for convenience), and copy them to your device. (Note that you can also just install Magisk Manager 5.0.6 and download the latest Magisk flashable ZIP from there.)
(3b. If you already have a prior Magisk & Manager installed, also download Magisk Uninstall (here, attached for convenience) and copy it to your device. Boot into TWRP, and "Install" (flash) Magisk Uninstall. Boot into system, and uninstall Magisk Manager. Clear Dalvik/Cache after each step.)
4. Install Magisk Manager v5.0.6 via File Manager direct as an APK.
5. Go to TWRP, and install the Magisk 13.2.
6. Reboot into stock, and open Magisk Manager. You should see both Magisk and Root installed (Root as "Magisksu"). If you try SafetyNet right now, it will fail.
7. Go into Settings in Magisk Manager and enable MagiskHide.
8. Reboot into TWRP, and flash the Magisk 13.2 SafetyNet Fix, attached. Reboot.
9. Now if you check SafetyNet, it should pass.
STEP 3: GET OTAS (EXPERIMENTAL)
There are still issues with B19 to B25 upgrades with Magisk using OTA packages, (such as those by DrakenFX).
Prior to the SafetyNet update (Magisk 13.0 beta), users reported partial success - if they installed Magisk successfully on B19, and gave root permission as needed, they could upgrade to B25 and retain old root permissions but NOT add new permissions for apps. I have not seen it tested whether this is still true after the SafetyNet update (Magisk 13.2).
----------
(Previous Original Guide - DO NOT USE)
If you are only here for Magisk: Despite all the horror trying to get it to work with 12.0 and earlier versions, it should flash fairly easily using versions later than the 20170520 beta and 13.0 beta Magisk Manager.. But since the 20170520 files are the only version I've tested, I can only vouch for those files and they are specifically mentioned in the guide.
NOTE: This assumes you are starting at B25, but the instructions should work for any B version number, since MiFlash is going to force us to B19.including how to install Magisk successfully - only new beta versions will install, and I've only tested the 20170520 build with Magisk 13.0 beta, but it worked entirely as intended. Below are the steps needed, and below that is my old post (hidden) for posterity in case it helps troubleshoot later if something breaks.
STEP 1: FLASHING FROM B25 TO B19 USING EDL MODE:
1. Install MiFlash using the EDL thread
2. Install the QUALCOMM drivers linked in the same thread.
3. Download "B19-NOUGAT_FULL (Nougat 7.1.1)" from the same thread.
4. Extract the ZIP file.
5. Open MiFlash, selected on the named sub-folder from the ZIP
6. Connect Axon 7 via a USB cable, and hold VOL-UP/VOL-DOWN/POWER until the screen goes black and the red notification LED blinks very intermittently (~1 time per 4 seconds) to get it in EDL mode.
7. Hit Refresh in MiFlash and confirm device is shown in list.
8. Hit Flash in MiFlash to flash it. (This rolled back my B25 device to B19 stock)
9. Then do the same process again with "B19-NOUGAT_TWRP (Nougat 7.1.1)," found in the same EDL thread (to get TWRP). ALTERNATIVELY, you can use the Toolkit to install TWRP, or via ADB, or any other method.
Note that first I just downloaded the TWRP version, and TWRP successfully installed and I could boot into TWRP, but it would totally freeze before loading the OS ROM every time. You MUST flash the B19 FULL first to avoid this.
Also, if any of these steps fail, install the Toolkit and use the same operations in the Toolkit. I used v. 1.2.0 for both the EDL flashing and to install TWRP as well, since on a later A2017U, the button restart method appeared to put me in a halfway-EDL mode which was visible from MiFlash, but did not allow flashing. In that case, a software EDL reset ("adb reboot edl" or "reboot edl" in the TWRP console) was the only way to get MiFlash to allow it to flash. The Toolkit does this nicely.
STEP 2: INSTALLING MAGISK 13.0 BETA WITH ROOT AND SAFETYNET PASS
1. Make sure you have a clean image with NO SU (PHH or MagiskSU or otherwise), and NO Magisk/Magisk Manager installed.
2. Enable Settings->Security->Unknown Sources in stock.
3. Download Magisk Manager 20170520 13.0 beta and Magisk 20170520 (here, and attached for convenience) (full beta thread here if needed), and copy them to your device.
4. Install Magisk Manager 20170520 13.0 beta via File Manager direct as an APK.
5. Go to TWRP, and install the Magisk 20170520 beta (here, and attached for convenience)
6. Reboot into stock, and open Magisk Manager 13.0. You should see both Magisk and Root installed (Root as "Magisksu"). If you try SafetyNet right now, it will fail.
7. Go into Settings in Magisk Manager and enable MagiskHide.
8. Now if you check SafetyNet, it should pass.
Note that the temporary beta builds appear to only be available for a short time, so either use the files attached, or go ahead and try the latest beta build. The first build I tried, 20170520, worked. Again, my guess is all beta builds or full builds after 20170520 will work with the instructions above, but feel free to test.
STEP 3: GET UPDATES / GO TO B25: I have not tested yet to ensure Magisk doesn't break, but I believe you should be able to download OTA packages, such as those by DrakenFX and flash them. However, users are reporting some bugs upgrading beyond B19, so OTAs are a work in progress. Please make a TWRP backup before attempting this and be ready to roll back if needed.
6bolt2g reports he had success moving from B19 (rooted) to B25, with the following steps: (a) flash "the DrakenFX B25 flashable zip's and the no-verity zip to keep TWRP"; and (b) follow STEP 2 above. However, 6bolt2g and StickMonster report that after upgrading to B25, you may experience problems with adding apps not previously whitelisted. Again, this is not verified by me but reporting it in the first thread for convenience.
For now, applying OTAs beyond B19 should be considered experimental - please be aware of the risk and have a backup before trying, and share your results here.
Changelog
Edit 5/21/2017: Added additional steps to Magisk to show process after flashing in TWRP.
Edit 5/23/2017: Added 6bolt2g report re: moving from B19 to B25.
Edit 5/24/2017: Added additional updates re: OTAs.
Edit 7/17/2017: Revised based on new ~7/12 Google SafetyNet changes, new Magisk from 5/15, and SafetyNet fix
Edit 9/3/2017: Added additional alternate solutions and troubleshooting advice.
Edit 9/4/2017: Revised process for B32, Magisk 13.6 Beta.
Edit 9/10/2017: Revised process for Magisk 14.0.
Edit 9/17/2017: Added King1990's alternate method.
Just wanted to thank you for the guide. Now I'll be able to get root on B25.
EDIT: I just wanted to know if flashing the B19_full will wipe userdata? I have a feeling it does, but I just want to double check.
Sent from my ZTE A2017U using XDA-Developers Legacy app
troy5890 said:
Just wanted to thank you for the guide. Now I'll be able to get root on B25.
EDIT: I just wanted to know if flashing the B19_full will wipe userdata? I have a feeling it does, but I just want to double check.
Click to expand...
Click to collapse
When I did it, it did NOT wipe userdata. Surprising to me that all my apps and things were still on the screen, but the version did indeed roll back. YMMV.
I've played with Magisk 13 too. I could get root, but not safety net. That's on b25. I can't remember if I tried it on b19.
To get safety net and Magisk 10 working on b25 I have to get it working on b29 and then upgrade to b25. So what you suggest for 13 sounds promising.
I'll have to play some more if you got it working on b19.
Curious, what makes you think OTAs will work? B25 removes fastboot for me and installed stock recovery. I had magisk working on B25 when not updating the bootsect and keeping that at B19.
Second question, with only B19 installed, after rolling back from B25 do you, or anyone for that matter have a problem where the signal constantly cycles on/off?
StickMonster said:
I've played with Magisk 13 too. I could get root, but not safety net. That's on b25. I can't remember if I tried it on b19.
To get safety net and Magisk 10 working on b25 I have to get it working on b29 and then upgrade to b25. So what you suggest for 13 sounds promising.
I'll have to play some more if you got it working on b19.
Click to expand...
Click to collapse
Magisk 10.3-beta2 worked after simply flashing the zip and the superuser and manager apks for me on b19
I was on rooted B19 (super su) and I used the DrakenFX B25 flashable zip's and the no-verity zip to keep TWRP. Then booted into the OS to put the Magisk manager on following 'STEP 2' in the OP then flashed the Magisk zip in TWRP and all seems to be working. I will do a full test drive today and report back if any issues. So far I have root and pass safety net checks and android pay let me open it up and set it up.
6bolt2g said:
I was on rooted B19 (super su) and I used the DrakenFX B25 flashable zip's and the no-verity zip to keep TWRP. Then booted into the OS to put the Magisk manager on following 'STEP 2' in the OP then flashed the Magisk zip in TWRP and all seems to be working. I will do a full test drive today and report back if any issues. So far I have root and pass safety net checks and android pay let me open it up and set it up.
Click to expand...
Click to collapse
Nice. Looking forward to hearing those results.
crashnova said:
Nice. Looking forward to hearing those results.
Click to expand...
Click to collapse
So far the masking function ie. Android Pay worked today when I went to use it. I went to use a few root apps, ES File Explorer and just an emoji switcher this afternoon and it was force closing the Magisk app. I tried to restart the phone to see if that was some of the issue, no difference. I also tried to uninstall and install the app from the Play Store, but it was an older version (v12). So I removed it and put the v13 back on and the force closes have stopped for now. I will have to continue using it to see how it goes. Anyone have any suggestions for root apps they would like me to try? With all the goodies baked into these stock roms there is less and less need for root access, at least for me.
6bolt2g said:
I was on rooted B19 (super su) and I used the DrakenFX B25 flashable zip's and the no-verity zip to keep TWRP. Then booted into the OS to put the Magisk manager on following 'STEP 2' in the OP then flashed the Magisk zip in TWRP and all seems to be working. I will do a full test drive today and report back if any issues. So far I have root and pass safety net checks and android pay let me open it up and set it up.
Click to expand...
Click to collapse
Thanks! I will update the original post with your results.
Edit: Can you confirm exactly which ZIP files you flashed, and where you specified "no-verity"?
Dodgexander said:
Curious, what makes you think OTAs will work? B25 removes fastboot for me and installed stock recovery. I had magisk working on B25 when not updating the bootsect and keeping that at B19.
Click to expand...
Click to collapse
I figure that as long as you can keep TWRP, the fact that Magisk was updated and confirmed to work with one version of Nougat suggested it should work with minor updates. (Nougat seems to be what broke Magisk initially.) I understand DrakenFX allows flashing in a way that preserves TWRP, so infer that it will likely work. I'm trying not to overstate what I know, but it appears to work for at least 6bolt2g. However, upgrading to B25 should be considered experimental at this point.
Dodgexander said:
Second question, with only B19 installed, after rolling back from B25 do you, or anyone for that matter have a problem where the signal constantly cycles on/off?
Click to expand...
Click to collapse
I haven't had that issue rolling back from B25. Maybe clear caches? Try reflashing with MiFlash?
ScaryBugThing said:
Thanks! I will update the original post with your results.
Edit: Can you confirm exactly which ZIP files you flashed, and where you specified "no-verity"?
Click to expand...
Click to collapse
I already was unlocked and had TWRP installed and I was on Stock B19 with root via Super SU, but the root part shouldn't matter.
I flashed the stock Bootstack and B25 Rom from this post: B25 TWRP Flashable
His directions mentioned using the vm-verity zip file if you want to keep TWRP and not flash super SU. He did not link the verity zip that I saw, so I searched XDA for them.
The link to the TWRP post with the download link: TWRP dm-verity Half way down the first post.
And the direct link to the download file list : no-verity download link I just picked the newest version.
Hope that helps.
*Edit*
To add to my issue earlier about the Magisk Manager crashing when approving root access. After re-installing it seems to work fine. I believe its after a reboot, it starts to have the crashing problem. It does seem to maintain previously approved root accesses though. For example, ES File manager is still able to explore system folders during the crash, because I approved it earlier when it was still working. I'm no programmer so I do not have a clue what is going on. I imagine, something is not persisting through the reboot. And to clarify, it is crashing when new programs are asking for root access and the pop-up shows.
Same for me using the 170523 build. Everything works at first, including root for apps already whitelisted from before the b25 upgrade, but once you try to add a new app to your root list you get FCs from then on any time su tries to run, including trying to start superuser from within Magisk manager. If you delete Magisk data, from twrp or Android app settings, the FCs stop but then you have no apps with root granted.
It looks like there is a version from nfound we should try.
Yep tried miflash running back to b19 and it's the same. I can't run b19 stock anymore, but it's off topic here so I'll shut up
Dodgexander said:
Yep tried miflash running back to b19 and it's the same. I can't run b19 stock anymore, but it's off topic here so I'll shut up
Click to expand...
Click to collapse
If you flash back to b19 try erasing Magisk data. I'm pretty sure that worked for me.
StickMonster said:
If you flash back to b19 try erasing Magisk data. I'm pretty sure that worked for me.
Click to expand...
Click to collapse
Magic is no problem on B19, signal is not. Flashing on and off like the phone is detecting a modem one sec and the next not.
Thanks for the updates about moving to B25. Updated first post - if you test anymore, please share.
ScaryBugThing said:
Hi all - this thread originated in the Q&A forum (old thread), but since I mapped out steps in a guide, I am posting it here since it is the more proper place for it.
This is a guide showing how to get TWRP installed, Magisk running, and I plan to update once I confirm OTAs can be flashed.
If you are only here for Magisk: Despite all the horror trying to get it to work with 12.0 and earlier versions, I believe you should be able to flash it fairly easily using versions later than the 20170520 beta and 13.0 beta Magisk Manager, see links below. But since the 20170520 files are the only version I've tested, I can only vouch for those files and they are specifically mentioned in the guide.
NOTE: This assumes you are starting at B25, but the instructions should work for any B version number, since MiFlash is going to force us to B19.including how to install Magisk successfully - only new beta versions will install, and I've only tested the 20170520 build with Magisk 13.0 beta, but it worked entirely as intended. Below are the steps needed, and below that is my old post (hidden) for posterity in case it helps troubleshoot later if something breaks.
STEP 1: FLASHING FROM B25 TO B19 USING EDL MODE:
1. Install MiFlash using the EDL thread
2. Install the QUALCOMM drivers linked in the same thread.
3. Download "B19-NOUGAT_FULL (Nougat 7.1.1)" from the same thread.
4. Extract the ZIP file.
5. Open MiFlash, selected on the named sub-folder from the ZIP
6. Connect Axon 7 via a USB cable, and hold VOL-UP/VOL-DOWN/POWER until the screen goes black and the red notification LED blinks very intermittently (~1 time per 4 seconds) to get it in EDL mode.
7. Hit Refresh in MiFlash and confirm device is shown in list.
8. Hit Flash in MiFlash to flash it. (This rolled back my B25 device to B19 stock)
9. Then do the same process again with "B19-NOUGAT_TWRP (Nougat 7.1.1)," found in the same EDL thread (to get TWRP).
Note that first I just downloaded the TWRP version, and TWRP successfully installed and I could boot into TWRP, but it would totally freeze before loading the OS ROM every time. You MUST flash the B19 FULL first to avoid this.
STEP 2: INSTALLING MAGISK 13.0 BETA WITH ROOT AND SAFETYNET PASS
1. Make sure you have a clean image with NO SU (PHH or MagiskSU or otherwise), and NO Magisk/Magisk Manager installed.
2. Enable Settings->Security->Unknown Sources in stock.
3. Download Magisk Manager 20170520 13.0 beta and Magisk 20170520 (here, and attached for convenience) (full beta thread here if needed), and copy them to your device.
4. Install Magisk Manager 20170520 13.0 beta via File Manager direct as an APK.
5. Go to TWRP, and install the Magisk 20170520 beta (here, and attached for convenience)
6. Reboot into stock, and open Magisk Manager 13.0. You should see both Magisk and Root installed (Root as "Magisksu"). If you try SafetyNet right now, it will fail.
7. Go into Settings in Magisk Manager and enable MagiskHide.
8. Now if you check SafetyNet, it should pass.
Note that the temporary beta builds appear to only be available for a short time, so either use the files attached, or go ahead and try the latest beta build. The first build I tried, 20170520, worked. Again, my guess is all beta builds or full builds after 20170520 will work with the instructions above, but feel free to test.
STEP 3: GET OTAS: I have not tested yet to ensure Magisk doesn't break, but I believe you should be able to download OTA packages, such as those by DrakenFX and flash them. However, users are reporting some bugs upgrading beyond B19, so OTAs are a work in progress. Please make a TWRP backup before attempting this and be ready to roll back if needed.
6bolt2g reports he had success moving from B19 (rooted) to B25, with the following steps: (a) flash "the DrakenFX B25 flashable zip's and the no-verity zip to keep TWRP"; and (b) follow STEP 2 above. However, 6bolt2g and StickMonster report that after upgrading to B25, you may experience problems with adding apps not previously whitelisted. Again, this is not verified by me but reporting it in the first thread for convenience.
For now, applying OTAs beyond B19 should be considered experimental - please be aware of the risk and have a backup before trying, and share your results here.
Edit 5/21/2017: Added additional steps to Magisk to show process after flashing in TWRP.
Edit 5/23/2017: Added 6bolt2g report re: moving from B19 to B25.
Edit 5/24/2017: Added additional updates re: OTAs.
Click to expand...
Click to collapse
I kept having error Object ref not set to an instance of an object. I already have TWRP, i wonder if i need stock recovery for this to work?
Question: On B25, once you have your root apps whitelisted and root access granted, does the Magisk Manager work alright? Other than FC on new apps, does it still do its thing and the phone work normal? My Axon 7 should be arriving today and I want to be on B25 for the wifi-calling fixes. I can probably live with white listing the apps on B19 and then updating to B25 once everything is ironed out.
genbu said:
I kept having error Object ref not set to an instance of an object. I already have TWRP, i wonder if i need stock recovery for this to work?
Click to expand...
Click to collapse
Can you give more details... whats your starting point? and what step are you getting this error?
---------- Post added at 08:35 AM ---------- Previous post was at 08:33 AM ----------
HallOfPromise said:
Question: On B25, once you have your root apps whitelisted and root access granted, does the Magisk Manager work alright? Other than FC on new apps, does it still do its thing and the phone work normal? My Axon 7 should be arriving today and I want to be on B25 for the wifi-calling fixes. I can probably live with white listing the apps on B19 and then updating to B25 once everything is ironed out.
Click to expand...
Click to collapse
I cant answer for stock AXON 7 OS... but im running LineageOs and everyththing is working very well... no Force closes with apps or anything like that.
MODS: Please move this question to the HELP section - incorrectly posted. Thanks.
Hello,
I am trying to root the Global MIUI _V10.2.1.0.PECMIXM ROM using Magisk. I want my phone to remain encrypted, and having spent all day today trying to achieve this, I am turning here for help.
I have tried flashing via Fastboot and TWRP, have tried flashing Disable DMVerity (without disabling the force encryption) before, and after flashing Magisk. I hava managed to get Magisk 18 flashed and able to boot to the ROM, but when I open Magisk Manager (Installed by the flash) it updates itself and says it needs to install Magisk, proposing to download it - or patch boot img.
Every time I try to flash the downloaded zip, or try fastboot flashing the modified boot.img, the phone won't boot - it just ends up in TWRP recovery.
I have wiped data 100s of times to try to fix this, to no avail.
I have tried to boot into TWRP without flashing it, but this just hands on the TWRP flash screen every time.
Any help / tips would be appreciated.
Were you following any tutorial post? Recent xiaomi phones come with more strict policy on bootload locks. I'm not familiar with it, but if I didn't misunderstand, without BL unlock it's kinda dangerous to flash anything on the phone.
msg7086 said:
Were you following any tutorial post? Recent xiaomi phones come with more strict policy on bootload locks. I'm not familiar with it, but if I didn't misunderstand, without BL unlock it's kinda dangerous to flash anything on the phone.
Click to expand...
Click to collapse
Thanks for replying. Yes, following tutorials, have unlocked my bootloader and can flash ROMs, just cannot get the latest MIUI 10 Global Stable rooted, without decrypting the phone. I have managed it on the Xiaomi.eu global stable, but not with the original Stock ROM.
Has anyone succeeded?
hello bro, u can try my way.
NEED:
unlock bootloader.
folder ADB / u can download all in my GG driver or internet from other source if u scare virus (^o^)
twrp / u can download all in my GG driver or internet from other source if u scare virus (^o^)
diver ADB / u can download all in my GG driver or internet from other source if u scare virus (^o^)
PREPARING:
download and copy to phone store and folder ADB
u should rename file TWRP with short name, any name u can remember. (ex: twrp.img or aaa.img, etc....)
install diver for PC/ LAP, u can try to plug mi phone in case FASTBOOT and check in DEVICE MANAFER of PC/ LAP.
remember ENABLE USB debugging on phone
OK, ACTION:
open CMD/ command window in folder ADB (u can put this folder at any diver on PC / LAP) with right click at this folder.
type all commands, follow with contrucs:
adb reboot bootloader (past this if u are in BL)
choose 1 in 2 ways:
1.
fastboot flash recovery twrp.img (do it to install recovery cook replace recovery stock)
fastboot flash misc misc.bin (do this line if u use stock folder china - TWRP-3.2.3-1202-XIAOMI8UD-CN-wzsx150-fastboot.7z)
fastboot boot twrp.img (do it for reboot to recover cook)
2.
fastboot boot twrp.img (do it, u use recovery temporary recovery cook and very easy, find file recovery, install it)
(test again by to use temporary reovery, reboot to recovery again)
note: i like second way, very easy and fast with pro person (^o^)
i tested in all miui stock (china, global)
HAVE FUN \(^o^)/
this link for all
https://drive.google.com/open?id=1uT8g1oOOkD27P2fylNzlAlXrT8PbCJEs
do note use it if u scare virus, malware, etc........ \(^o^)/
reply me if u can not apply all or do not dowload my GG driver.
u can read and do all with this stock link in miui en (http://en.miui.com/thread-3671565-1-1.html)
t4manh198E said:
hello bro, u can try my way.
NEED:
unlock bootloader.
folder ADB / u can download all in my GG driver or internet from other source if u scare virus (^o^)
twrp / u can download all in my GG driver or internet from other source if u scare virus (^o^)
diver ADB / u can download all in my GG driver or internet from other source if u scare virus (^o^)
PREPARING:
download and copy to phone store and folder ADB
u should rename file TWRP with short name, any name u can remember. (ex: twrp.img or aaa.img, etc....)
install diver for PC/ LAP, u can try to plug mi phone in case FASTBOOT and check in DEVICE MANAFER of PC/ LAP.
remember ENABLE USB debugging on phone
OK, ACTION:
open CMD/ command window in folder ADB (u can put this folder at any diver on PC / LAP) with right click at this folder.
type all commands, follow with contrucs:
adb reboot bootloader (past this if u are in BL)
choose 1 in 2 ways:
1.
fastboot flash recovery twrp.img (do it to install recovery cook replace recovery stock)
fastboot flash misc misc.bin (do this line if u use stock folder china - TWRP-3.2.3-1202-XIAOMI8UD-CN-wzsx150-fastboot.7z)
fastboot boot twrp.img (do it for reboot to recover cook)
2.
fastboot boot twrp.img (do it, u use recovery temporary recovery cook and very easy, find file recovery, install it)
(test again by to use temporary reovery, reboot to recovery again)
note: i like second way, very easy and fast with pro person (^o^)
i tested in all miui stock (china, global)
HAVE FUN \(^o^)/
this link for all
https://drive.google.com/open?id=1uT8g1oOOkD27P2fylNzlAlXrT8PbCJEs
do note use it if u scare virus, malware, etc........ \(^o^)/
reply me if u can not apply all or do not dowload my GG driver.
u can read and do all with this stock link in miui en (http://en.miui.com/thread-3671565-1-1.html)
Click to expand...
Click to collapse
Thanks for replying. However, this tells me how to flash TWRP, how to boot to TWRP - I have no problem doing that whatsoever. I can successfully do that again and again.
What I have not been able to do is flash Magisk v18 on v10 stock ROM and be able to boot successfully. It bootloops into TWRP.
My post help u to install twrp or flash twrp
I do not know your mean what is flash twrp !?
Reboot to recov cook by press volumn +/- and power button
Use magisk 17.1 stanle, u can find it in my gg driver or download in miui eu 's page
---------- Post added at 05:03 AM ---------- Previous post was at 05:02 AM ----------
nealed said:
Thanks for replying. However, this tells me how to flash TWRP, how to boot to TWRP - I have no problem doing that whatsoever. I can successfully do that again and again.
What I have not been able to do is flash Magisk v18 on v10 stock ROM and be able to boot successfully. It bootloops into TWRP.
Click to expand...
Click to collapse
1 in 2 ways is certainly successful
nealed said:
Thanks for replying. However, this tells me how to flash TWRP, how to boot to TWRP - I have no problem doing that whatsoever. I can successfully do that again and again.
What I have not been able to do is flash Magisk v18 on v10 stock ROM and be able to boot successfully. It bootloops into TWRP.
Click to expand...
Click to collapse
Hey, I'm success root my mi 8 pro (Android 9 V10.2.1.0.PECMIXM - MIUI 10)
If you know how to use TWRP, now just reboot your mi 8 pro to TWRP
and then choose Mount > check system & vendor.
Then flash the Latest Version of magisk (v18.1)
REMEMBER : TO MOUNT >> CHECK SYSTEM & VENDOR. AFTER THAT JUST FLASH MAGISK. ONLY MAGISK !!!
And then reboot to your system.
After that, download the latest versio of Magisk Manager, install it and open it.
And BOOOOM~
Your Mi 8 Pro just rooted.
nfadrizp said:
Hey, I'm success root my mi 8 pro (Android 9 V10.2.1.0.PECMIXM - MIUI 10)
If you know how to use TWRP, now just reboot your mi 8 pro to TWRP
and then choose Mount > check system & vendor.
Then flash the Latest Version of magisk (v18.1)
REMEMBER : TO MOUNT >> CHECK SYSTEM & VENDOR. AFTER THAT JUST FLASH MAGISK. ONLY MAGISK !!!
And then reboot to your system.
After that, download the latest versio of Magisk Manager, install it and open it.
And BOOOOM~
Your Mi 8 Pro just rooted.
Click to expand...
Click to collapse
I rooted firsr u
nd now i am using mi mix 3 ???
Ah, So You've rooted your 6.1 Plus/X6 but don't know how to Install stock or having troubles with it? I'm here to help!
*All of the instructions and procedures below requires an unlocked bootloader. If you do not have an unlocked bootloader, Please refrain from asking about it here.
*Not having an unlocked bootloader and following this will definitely brick your phone. You have been warned.
Installing Stock ROM - Method 1A(Nost) --
1. Get NOST from here - NOST
2. NOST ONLY SUPPORT OREO FIRMWARE, USE OST LA FOR PIE(Not sharing cause its a patched app, Search on Google and get it from TechMesto)
3. Download unpacked oreo firmware, You can get it from - Here
4. Extract the zip on your PC
5. Put your phone in bootloader mode, Power off - Press Volume Down+Power Button.
6. Now connect it to your PC
7. Open NOST, Select the .mlf file from the folder where you extracted the Firmware
8. Now select, Normal download and Erase User data option.
9. Now click on next and wait for NOST to flash the phone. (It takes 258 seconds or 2.3 - 2.5 minutes on my laptop)
Installing Stock ROM - Method 1B(OST LA) --
Same as NOST, It has the same UI.
Except You might have to change some values in the .mlf file.
An appropriate guide for the same - Here
Installing Stock ROM - Method 2(Hikary's Generic Flashing Script) --
I recommend this method more than NOST and OST LA.
1. Get Hikary's script from - Here
2. Get unpacked Firmware from - Here
3. Extract the Firmware
4. Put the .exe file you got from Github into the folder where you Extracted the firmware
5. Run the script
6. Follow instructions on screen
7. Profit!
Thanks alot to member - Hikary for this easy to use scipt!
You've installed Stock, Now let's add some magisk to it !
*Please disable Automatic System Updates through developer options to make taking OTA .zips easier.
Installing Magisk - Method 1A(Fastboot method) -
You will need Google's ADB drivers, Which you can get - Here/
1. Extract ADB to a Folder
2. Get Magisk patched boot images from - Here Don't worry, Boot images for Nokia 7 Plus will work on DRG(6.1 Plus/X6) and PL2(6.1)
3. Open adb(Type cmd in the address bar of the folder where you extracted adb)
4. Put your device on Download mode
5. type the command
Code:
fastboot boot 'nameofbootimage'.img
6. Now your phone will boot
7. Install Latest Magisk Manger from - [https://www.github.com/topjohnwu/magisk/releases]Here[/url]
8. Open Magisk Manger, You will see Magisk is installed, But there will also be an Install Button next to it. Tap on Install.
9. Let Magisk Install and re-boot the phone
10. Viola Magisk is now permenantly available
Installing Magisk - Method 1B(TWRP method) -
You will need Google's ADB drivers, Which you can get - Here/
1. Get the latest TWRP for 6.1 Plus
2. Get the Latest Magisk Installer from - [https://www.github.com/topjohnwu/magisk/releases]Here[/url]
3. Put the .zip file to your Internal Storage/SD Card
4. Open adb and pass the command
Code:
fastboot boot "nameofrecoveryfile.img"
5. Now TWRP will open on your phone
6. Install Magisk through TWRP
7. Wipe Dalvik
8. Reboot
9. Profit
Now you've got magisk. Follow the next post to see how to take an OTA update with Magisk Installed.
Nokia 6.1 Plus is an Android One certified device. Nokia is no slouch either when it comes to issuing updates. Learn how to take OTA without losing root.
1. Turn of Auto System updates through Developer options
2. Open Magisk Manager
3. Restore Stock Images but don't reboot.
4. Download and install, Let both the steps finish i.e applying update and apps, but don't reboot.
5. Go to magisk manager and select install to inactive slot option
6. Re-boot device.
7. You've not lost root, But have root access.
Done
CarbonGTR said:
Nokia 6.1 Plus is an Android One certified device. Nokia is no slouch either when it comes to issuing updates. Learn how to take OTA without losing root.
1. Turn of Auto System updates through Developer options
2. Open Magisk Manager
3. Restore Stock Images but don't reboot.
4. Download and install, Let both the steps finish i.e applying update and apps, but don't reboot.
5. Go to magisk manager and select install to inactive slot option
6. Re-boot device.
7. You've not lost root, But have root access.
Done
Click to expand...
Click to collapse
I don't see any option to restore stock images or install to inactive slot in Magisk. Am I missing something?
Hymix said:
I don't see any option to restore stock images or install to inactive slot in Magisk. Am I missing something?
Click to expand...
Click to collapse
Open Magisk Manager, Tap on Uninstall. You will see 2 options, Complete Uninstall and restore stock images.
*Nevar tap on the complete uninstall option, It will throw your phone into bootloop
To install to inactive slot, Tap on install, You will get 2 options, Release Notes and Install. Tap on Install again and select install to inactive slot, Reboot from within Magisk Manager.
The simplest way I've found to install Stock Rom is just using adb sideload.
Boot into TWRP and wipe as you would with any custom rom.
Go to advanced and adb sideload.
Send the adb sideload command from your computer with the relevant zip file.
Doesn't require any additional softward like NOST or OST....
Hymix said:
The simplest way I've found to install Stock Rom is just using adb sideload.
Boot into TWRP and wipe as you would with any custom rom.
Go to advanced and adb sideload.
Send the adb sideload command from your computer with the relevant zip file.
Doesn't require any additional softward like NOST or OST....
Click to expand...
Click to collapse
But does it also install the bootloader and stock recovery back? If yes then I'll add it to the post above.
CarbonGTR said:
But does it also install the bootloader and stock recovery back? If yes then I'll add it to the post above.
Click to expand...
Click to collapse
That's a good question. I've just been using stock and hadn't considered it. How would one check that?
Sent from my Nokia 6.1 Plus using Tapatalk
Bluebriz said:
That's a good question. I've just been using stock and hadn't considered it. How would one check that?
Sent from my Nokia 6.1 Plus using Tapatalk
Click to expand...
Click to collapse
It's easy. Get an OTA .zip file, Re-Boot to recovery and flash it. Or Use the ADB Sideload method.
Most likely installing the OTA would fail if the device is rooted because, Magisk will patch the boot.img.
Then I'll need to wait for another update, the September one, right? Because I installed it with ADB and have Magisk installed so I don't really want to mess with it until I have to.
Sent from my Nokia 6.1 Plus using Tapatalk
Bluebriz said:
Then I'll need to wait for another update, the September one, right? Because I installed it with ADB and have Magisk installed so I don't really want to mess with it until I have to.
Click to expand...
Click to collapse
I just took an OTA with Magisk installed it went fine. (September patch)
OK, then it doesn't seem to work. Trying to follow the steps, the system update gives an installation error. I'm guessing that somewhere along the road I've messed something up, so it seems stock rom and Magisk isn't an option for me.
Hymix said:
OK, then it doesn't seem to work. Trying to follow the steps, the system update gives an installation error. I'm guessing that somewhere along the road I've messed something up, so it seems stock rom and Magisk isn't an option for me.
Click to expand...
Click to collapse
Restore images before you do anything, If installation fails keep trying again. It happens to me to.
CarbonGTR said:
Restore images before you do anything, If installation fails keep trying again. It happens to me to.
Click to expand...
Click to collapse
Really? I did the restore via Magisk and that seemed fine, but then the update part didn't work. It downloaded then gave the error so I quit and started again with a fresh installation, minus Magisk.
Sent from my Nokia 6.1 Plus using Tapatalk
Have you guys modified the system/vendor partition in any way? If you did, Then it will obviously fail.
@Bluebriz and @Hymix I agree. It's the september security patch causing the installation issue.
It fails for me no matter what, Unless I completely un-root. But this method works perfectly fine on the August update.
Lets see for the October patch.
Okay, I can specifically narrow this down to way the September patch. The september patch requires the August security patch as a precondition to install. And that's where something funky is happening.
Guys a quick update. October update has been released but it also fails to install. This time I've managed to find the cause, Apparently some service that needs to be used for the update is being blocked/used by Magisk. (I could be wrong here)
The error code according to the recovery is 20(kDownloadStateInitializationError)
Is there any update to this issue?
Tried removing Magisk, didn't help.
Yesterday I got November security update ..iam using magisk...so it is showing installation problem...I tried in recovery and ADB method both didn't work.. finally I ended in bootloop ...so I again installed stock ROM...any solution is there without resetting each time how to install security updates..coz each time my data balance was wasted??
Last updated May 2020
Keeping it short. This is a simple way to root your device. You will need a computer and a data cable for this.
Objectives :
Have root using Magisk
Be able to install OTA from the settings without bootloops
Avoid boot loop
Very important :
This will work with ANY Xiaomi phone, and should work with ANY ANDROID phone as well. The difference between phones would be in where you can get your boot image from.
Your phone has to have an unlocked bootloader
Your phone has to have stock recovery. TWRP WILL cause bootloop for root and/or OTA updates from system.
I like to have root with magisk and don't want to install TWRP because I want to be able to install OTA from system without boot loops. This guide will help you achieve this with ease.
Steps:
Download the ROM full zip file. This could be the ROM ALREADY installed on your phone or you are updating your phone to it. Here is a video of one way to get your ROM file.
https://youtu.be/KsxHial1v1U
Open the file and extract "boot.img" on your phone or Computer.
Move the boot.img file to your phone
Download and install the latest Magisk official manager app from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
Open Magisk manager and click install then "select and patch a file" like in this video
https://youtu.be/USHcCMYlexM
Copy the Patched image from the download folder to your computer adb/fastboot folder
Reboot your phone into fastboot (press and hold power and vol down) and connect it to the computer
Flash that patches image file using fastboot
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
fastboot reboot
Click to expand...
Click to collapse
Open Magisk manager and complete the installation if needed. The app will prompt you for action.
Enjoy
Update May 2020
Hello again,
Sorry for being away for so long. Here are some of the things I have noticed people are confused with and need to make them clear:
This method works for ANY Android phone. As long as you have the Correct boot.img and can unlock the bootloader
MAKE SURE 100% you have the correct boot.img file for your CURRENT ROM
MAKE 100% SURE, the boot.img file you get from the FULL ROM zip file, not an OTA update zip file
Make sure you check the date and time of the "magisk_patched.img" file to make sure that is the one you made
Make sure you use the LATEST magisk manager
Make sure you open magisk after flashing the magisk_patched.img as boot image. Magisk manager will tell you if there is another step needed, just click yes and it will be done in seconds
Make sure to enable "Hide Magisk" to allow you to have your BANK apps working as well as security checks
If any app you use gives you an error "YOU ARE Rooted bla bla bla" Use magisk manager to hide the root for this specific app (in the settings)
That's all I can remember, good luck
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Kiwironic said:
Keeping it short. This is a simple way to root your device. You will need a computer and a data cable for this.
Steps:
Download the ROM full zip file. This could be the ROM ALREADY installed on your phone or you are updating your phone to it. Here is a video of one way to get your ROM file.
Open the file and extract "boot.img" on your phone or Computer.
Move the boot.img file to your phone
Download and install the latest Magisk official manager app from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
Open Magisk manager and click install then "select and patch a file" like in this video
Copy the Patched image from the download folder to your computer adb/fastboot folder
Reboot your phone into fastboot (press and hold power and vol down) and connect it to the computer
Flash that patches image file using fastboot
Open Magisk manager and complete the installation if needed. The app will prompt you for action.
Enjoy
Click to expand...
Click to collapse
After fastboot flash, reboot, open magisk manager, tap INSTALL beside "magisk is up to date". Then select direct install; reboot.
Works on MIUI 11.0.2; davinciin. ??
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
welder73 said:
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
Click to expand...
Click to collapse
People report different amounts of wait time, depends on the mi account I think
welder73 said:
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
Click to expand...
Click to collapse
Phone is reset when the bootloader is unlocked, not before/during the waiting time.
Can do with locked bootloader?
Micdu70 said:
Phone is reset when the bootloader is unlocked, not before/during the waiting time.
Click to expand...
Click to collapse
Thank you man :good:
Sent from my Xiaomi Mi 9T using XDA Labs
Cabeção-Flu said:
Can do with locked bootloader?
Click to expand...
Click to collapse
No, bootloader has to be unlocked.
@Kiwironic followed your guide and worked very well, although I had to wipe data through the stock recovery to get the phone to boot, I believe that's just how newer Xiaomi phones work. I do have one question though, now that I'm rooted with stock recovery, would I be able to install OTA updates? I'm assuming I would of course lose root and have to redo the process from scratch if that's the case.
Lazer Bear said:
@Kiwironic followed your guide and worked very well, although I had to wipe data through the stock recovery to get the phone to boot, I believe that's just how newer Xiaomi phones work. I do have one question though, now that I'm rooted with stock recovery, would I be able to install OTA updates? I'm assuming I would of course lose root and have to redo the process from scratch if that's the case.
Click to expand...
Click to collapse
I had root on MIUI10 and updated the ROM to MIUI11 then did my root again the way mentioned and did NOT have to wipe. You can get OTA anyway, it will try the update first, it will fail, then it download and install a full ROM zip automatically. You have to wait for it to do that twice, that's all. The first boot after the update takes some time.
@Kiwironic First, thank you so your simple guide!
Can this cause bootloop on my device? If yes, can I simply flash the original boot.img to boot without any data loss?
Also another question: my device is rootless and bootloader unlocked, so my Google Pay doesn't work. When installing Magisk it goes back to work immediately or I have to do something to work?
kryzeK said:
@Kiwironic First, thank you so your simple guide!
Can this cause bootloop on my device? If yes, can I simply flash the original boot.img to boot without any data loss?
Also another question: my device is rootless and bootloader unlocked, so my Google Pay doesn't work. When installing Magisk it goes back to work immediately or I have to do something to work?
Click to expand...
Click to collapse
If you flash the full rom, chances of bootloop is minimal. And should have stock experience except for being unlocked.
I got bootloop, using indian global V11.0.2.0.
After flashing patched boot, it gets bootloop recovery, only way is to wipe all data and reboot
After booting up and opeing magisk it shows a recommendation to install some ZIP
Accepting the recommendation results in bootloop,
Rejecting the recommendation and trying to Install > Direct Install results in bootloop as well
Posted a thread with this issue here
stone_henge said:
I got bootloop, using indian global V11.0.2.0.
After flashing patched boot, it gets bootloop recovery, only way is to wipe all data and reboot
After booting up and opeing magisk it shows a recommendation to install some ZIP
Accepting the recommendation results in bootloop,
Rejecting the recommendation and trying to Install > Direct Install results in bootloop as well
Posted a thread with this issue here
Click to expand...
Click to collapse
This
I got the exact same issue, every time it asked me to install additional zip files it went into recovery immediately after booting up.
Anyone know why this happened?
oblyvision said:
This
I got the exact same issue, every time it asked me to install additional zip files it went into recovery immediately after booting up.
Anyone know why this happened?
Click to expand...
Click to collapse
Do you have stock recovery or TWRP? Which version of Magisk are you using?
I have patched my boot stock image, installed full ROM, then flashed the patched boot image. Magisk did not show any recommendation installation.
There are a few guides online on how to deal with Magisk Bootloop without the need to wipe data.
Kiwironic said:
Do you have stock recovery or TWRP? Which version of Magisk are you using?
I have patched my boot stock image, installed full ROM, then flashed the patched boot image. Magisk did not show any recommendation installation.
There are a few guides online on how to deal with Magisk Bootloop without the need to wipe data.
Click to expand...
Click to collapse
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
oblyvision said:
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
Click to expand...
Click to collapse
On first installation MM asks to download what it needs e.g. to verify SafetyNet. Allow and there is no problem about. TWRP is generally not needed to install Magisk. Things are documented in Magisk guides
https://topjohnwu.github.io/Magisk/
https://www.didgeridoohan.com/magisk/HomePage
oblyvision said:
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
Click to expand...
Click to collapse
Yes, as the title suggests "without TWRP". The reason is, you cannot install OTA and magisk easily without using the stock recovery. Any attempt to update OTA or use any recovery script on the phone will result in a boot loop.
The solution to get out of the boot loop is simple. Actually a couple of solutions.
One, flash your stock recovery, or
Two, flash a full ROM that includes the stock recovery.
No need to wipe data
That's the only reason I made this post and the other about OTA on root. I don't like to use TWRP because I want OTA install without boot loop. At the same time I want root. Hence the solutions I provided
Kiwironic said:
Yes, as the title suggests "without TWRP". The reason is, you cannot install OTA and magisk easily without using the stock recovery. Any attempt to update OTA or use any recovery script on the phone will result in a boot loop.
The solution to get out of the boot loop is simple. Actually a couple of solutions.
One, flash your stock recovery, or
Two, flash a full ROM that includes the stock recovery.
No need to wipe data
That's the only reason I made this post and the other about OTA on root. I don't like to use TWRP because I want OTA install without boot loop. At the same time I want root. Hence the solutions I provided
Click to expand...
Click to collapse
I've tried flashing magisk via recovery and didn't work, the same bootloop. Here's the thread: https://forum.xda-developers.com/mi-9t/how-to/guide-miui-11-v11-0-1-0-pfjmixm-rooted-t3997299
I thought this might be a working alternative.
Gotta try installing magisk with stock recovery then, and if it still didn't work, well, more research for me..
oblyvision said:
I've tried flashing magisk via recovery and didn't work, the same bootloop. Here's the thread: https://forum.xda-developers.com/mi-9t/how-to/guide-miui-11-v11-0-1-0-pfjmixm-rooted-t3997299
I thought this might be a working alternative.
Gotta try installing magisk with stock recovery then, and if it still didn't work, well, more research for me..
Click to expand...
Click to collapse
You have to understand the requirements :
- stock recovery
- install magisk manager app
- patch the boot image for your stock ROM (same version on your phone)
- flash that Patched boot image.
- reboot
- done, that's magisk installed
The procedure is very simple. DFE or OFOX are NOT required. I myself flashed TWRP on an encrypted device and it boots and works as expected. Also twrp does not go away if you follow the steps correctly. No format needed either. Just remember your password.
0. First of all an unlocked bootloader is required. If this is your first time, go to miui.com/unlock. Backup your personal data before unlocking.
1. On windows install ADB DRIVERS and download PLATFORM-TOOLS and TWRP. Also download Magisk and move it to the phone, or to a type C usb stick if the device is encrypted.
2. In Developer Options Enable USB Debugging, then reboot to fastboot (Vol Down + PWR Button).
3. Connect the device to PC. Extract the platform tools folder and in it press Shift+Left Click and open a powershell window. Type
Code:
fastboot flash recovery [twrp version name]
4. Type fastboot reboot and hold Vol+ to go staight into TWRP.
5. From there flash magisk, wipe caches and reboot to system.
6. Come back here and hit that thanks button. :good:
It was always the trick to survive twrp is to boot into recovery and flash magisk. Anyway, good to have a clean thread.
Mi 9T Pro ll Tapatalk
Hasn't this been the preferred method since forever? And dfe just isn't needed at all encrypted unencrypted doesn't matter you can still flash magisk, and since when would twrp not work on stock miui roms?
It's just a update of a skinned Android, not a major android os update like android 11, really very little has changed to warrant making this thread, sorry.
hoopsnake said:
Hasn't this been the preferred method since forever? And dfe just isn't needed at all encrypted unencrypted doesn't matter you can still flash magisk, and since when would twrp not work on stock miui roms?
It's just a update of a skinned Android, not a major android os update like android 11, really very little has changed to warrant making this thread, sorry.
Click to expand...
Click to collapse
Preferred? I think it's the only one. But many people are asking about miui 12 and what's changed. Many things have changed with Android 10 and/or miui 12 in many other xiaomi devices and extra things are needed (especially on mediatek devices). Also there are some lies being spread about the need of DFE and alternative recoveries as "better".
Not everyone is familiar with the method of rooting and no one cared to create a straightforward how-to without spreading BS with idiotic recoveries and unnecessary things. Have a nice day.
Nothing changed regarding unlocking, flashing TWRP/Orangefox and rooting regarding the 9T Pro since it's release.
There is NO special method for Miui 12 and the method is overall as good as the same for all Xiaomi/Poco devices.
And the "many people" you mentioned is just 1 person who asked for it in the Questions/FAQ section so no need for unnecessary cluttering of threads.
It sometimes takes a while after flashing magisk for the phone to boot up. Make sure you double check that it was successful by using the Magisk Manager app!
trelokeeper said:
Preferred? I think it's the only one. But many people are asking about miui 12 and what's changed. Many things have changed with Android 10 and/or miui 12 in many other xiaomi devices and extra things are needed (especially on mediatek devices). Also there are some lies being spread about the need of DFE and alternative recoveries as "better".
Not everyone is familiar with the method of rooting and no one cared to create a straightforward how-to without spreading BS with idiotic recoveries and unnecessary things. Have a nice day.
Click to expand...
Click to collapse
Yes but is it really relevant to discuss changes on other devices on this forum? No
If those people can't do some simple basic research they shouldn't be rooting in the first place it's designed to be simple and easy and if people can't get that they should have never unlocked their bootloader in the first place. Nothing but clutter here. Give one example of someone speading as you say "lies" about dfe.
Is there a way to fix the "ctsProfile: false" ?
Tried a couple modules but they didn't work.
jugul said:
Is there a way to fix the "ctsProfile: false" ?
Tried a couple modules but they didn't work.
Click to expand...
Click to collapse
First of all, make sure that Magisk Hide option is enabled in Magisk Manager settings (reboot afterwards) - but if it's not enabled then Basic Integrity would also fail
Problem with CTS Profile failing started about month ago (it has been thoroughly discussed in the general Magisk thread) when Google enforced Hardware backed attestation for CTS Profile (for certain phones / stock firmwares). In that case Magisk Hide cannot hide that Bootloader is unlocked and therefore CTS Profile fails
If so, try how it works for Mi 9T, MIUI 11:
https://forum.xda-developers.com/showpost.php?p=83035713&postcount=40681
In short, install Magisk Hide Props Config module and use its option to delete ro.product.model and reboot afterwards.
The post above describes also how to get back Device is certified in Google Play settings, as well as about a sidefect with Settings/About that will no more properly display your phone model
There is a more 'generic' fix you will also find a link in the post above, to use a particular hardwareoff module for Magisk but that module redefines several ro.product.* props (not only ro.product.model), to cover for other phones like Samsung, etc - IMO, better not to redefine props whose redefinition is not needed for MIUI to pass CTS Profile
zgfg said:
First of all, make sure that Magisk Hide option is enabled in Magisk Manager settings (reboot afterwards) - but if it's not enabled then Basic Integrity would also fail
Problem with CTS Profile failing started about month ago (it has been thoroughly discussed in the general Magisk thread) when Google enforced Hardware backed attestation for CTS Profile (for certain phones / stock firmwares). In that case Magisk Hide cannot hide that Bootloader is unlocked and therefore CTS Profile fails
If so, try how it works for Mi 9T, MIUI 11:
https://forum.xda-developers.com/showpost.php?p=83035713&postcount=40681
In short, install Magisk Hide Props Config module and use its option to delete ro.product.model and reboot afterwards.
The post above describes also how to get back Device is certified in Google Play settings, as well as about a sidefect with Settings/About that will no more properly display your phone model
There is a more 'generic' fix you will also find a link in the post above, to use a particular hardwareoff module for Magisk but that module redefines several ro.product.* props (not only ro.product.model), to cover for other phones like Samsung, etc - IMO, better not to redefine props whose redefinition is not needed for MIUI to pass CTS Profile
Click to expand...
Click to collapse
That worked. Thanks!
trelokeeper said:
The procedure is very simple. DFE or OFOX are NOT required. I myself flashed TWRP on an encrypted device and it boots and works as expected. Also twrp does not go away if you follow the steps correctly. No format needed either. Just remember your password.
0. First of all an unlocked bootloader is required. If this is your first time, go to miui.com/unlock. Backup your personal data before unlocking.
1. On windows install ADB DRIVERS and download PLATFORM-TOOLS and TWRP. Also download Magisk and move it to the phone.
2. In Developer Options Enable USB Debugging, then reboot to fastboot (Vol Down + PWR Button).
3. Connect the device to PC. Extract the platform tools folder and in it press Shift+Left Click and open a powershell window. Type
4. Type fastboot reboot and hold Vol+ to go staight into TWRP.
5. From there flash magisk, wipe caches and reboot to system.
6. Come back here and hit that thanks button. :good:
Click to expand...
Click to collapse
Hey there I am a completely newbie in this thing, can you please guide me through dm's or anybody else there to help me . I am from India I bought k20 pro in alpha sale and it's warranty is now over so I wanted to root my phone.
I patched the b0ot file of my ROM with magisk and then I flashed it with fastboot. My devices is rooted but I have a issue with WiFi, suggestions?
I'm install twrp on powershell. I got information, is it succesful and when i want to go to recovery i see only miui recovery,. Not twrp. Where is a problem? Bootloader unlocked
Hi, through OrangeFox I tried to install the version miui_RAPHAEL_20.8.7_e721f66562_10.0.zip on my MI 9T Pro, starting from miui_RAPHAELEEAGlobal_V12.0.1.0.QFKEUXM_68e06ebeaa_10.0.zip.
Apparently everything went smoothly, but when the reboot starts again with OrangeFox.
Can someone help me?
Thank you
nigol
nigol said:
Hi, through OrangeFox I tried to install the version miui_RAPHAEL_20.8.7_e721f66562_10.0.zip on my MI 9T Pro, starting from miui_RAPHAELEEAGlobal_V12.0.1.0.QFKEUXM_68e06ebeaa_10.0.zip.
Apparently everything went smoothly, but when the reboot starts again with OrangeFox.
Can someone help me?
Thank you
nigol
Click to expand...
Click to collapse
Did you Format (not Wipe) Data?
if i just use rooted miui , do i still need to flash dfe? what are the benefits of decryption?
what are problems with leaving encrypted partition... pls help
mustali said:
if i just use rooted miui , do i still need to flash dfe? what are the benefits of decryption?
what are problems with leaving encrypted partition... pls help
Click to expand...
Click to collapse
Just for rooting you don't need DFE, nor to format (neither to wipe) Data.
You need it if you go to flash custom ROM
Btw, rooting can be done without TWRP, just by patching boot.img and flashing the patched image from Fastboot
zgfg said:
Did you Format (not Wipe) Data?
Click to expand...
Click to collapse
No, I just installed the zip with OrangeFox.
How can I fix it?
Orange restarts every time you restart ...
nigol
nigol said:
No, I just installed the zip with OrangeFox.
How can I fix it?
Orange restarts every time you restart ...
nigol
Click to expand...
Click to collapse
Try to Format Data from TWRP: Wipe, Advance, Format Data
ok thanks, I'll try
nigol
---------- Post added at 10:24 AM ---------- Previous post was at 10:11 AM ----------
On OrangeFox in the Wipe directory there are only these entries:
Dalvik / ART Cache, Cache, System, Vendor, Data, Internal Sorage, USB-Storage.
Which entries should I format?
Thank you
nigol