[ISSUE] Trying to root Redmi 6, Miui 11, getting stuck installing Magisk - Xiaomi Redmi 6 Questions & Answers

I am unable to root my Redmi 6 Miui 11
I've followed youtube tutorials, read about this etc. but the thing is that I can't get this to wrok.
device model: redmi 6
miui global 11.0.3 | Stable 11.0.3.0 (PCGMIXM)
Android: 9 PPR1. 180610.011
ENABLED: USB debugging, USB debugging(Secutiry Settings), OEM unlocking
Unlocked the bootloader
tried latest and few older versions of TWRP for redmi 6 from the twrp.me - none of them worked as when I try to load into TWRP my screen goes all colors and depending on the version there might be a small light show of colors splashing.
Found this one to be working, from yt video - can't post link as a new user , (Although it says 6A) - never mind at least I've managed to load into TWRP.
When TWRP starts
it says: Mount Decrypt Data - since I do not have lock set I go to CANCEL
go to INSTALL -> says internal Storage (0MB), so I use SD card to install Magisk-v20.4.zip I confirm and see following errors:
Decrypt process ended with signal: 11
Failed to decrypt data.
Unable to decrypt with default password. You may need to preform Format Data.
then a bit later...
Unable to mount /data/media/TWRP/twrps_wzsx150
Is there any way I can bypass this issue? What should I do and what is the safest thing?
I am trying for 2 days to solve this issue but I am not sure what to do at this point.
If somebody know what should I do in order to root my device please tell me I will be grateful.

I've found the solution, the problem? I've not enough post to attach the boot img.
Go to the 4pda link of this post:
https://forum.xda-developers.com/showpost.php?p=80515805&postcount=2
Download the file "boot_11.0.3.0CN_R6_mgsk_202.img", flash the boot file with the command "fastboot flash boot boot_11.0.3.0CN_R6_mgsk_202.img", reboot, install the lastest magisk manager.
At this point you should have magisk 20.2 installed, only a problem, you can't update magisk

Don't do it!
Alex5532 said:
I've found the solution, the problem? I've not enough post to attach the boot img.
Go to the 4pda link of this post:
https://forum.xda-developers.com/showpost.php?p=80515805&postcount=2
Download the file "boot_11.0.3.0CN_R6_mgsk_202.img", flash the boot file with the command "fastboot flash boot boot_11.0.3.0CN_R6_mgsk_202.img", reboot, install the lastest magisk manager.
At this point you should have magisk 20.2 installed, only a problem, you can't update magisk
Click to expand...
Click to collapse
WARNING: Don't do it if you don't know what are you doing else your phone will be hard bricked and you need an authorized Xiaomi account to revive it.

Related

TWRP, Magisk, & Xposed for the NX619J

This is a translation and rework of youyim2's executable. I've rewritten some of the batch file to make things more streamlined, as well as translated the whole thing into English. I am not the device maintainer. If you have questions, I'll help as best I can. This is only for getting TWRP, Magisk, and Xposed. You should be able to flash Open GAPPs if needed with no issue once you've got TWRP installed.
Download the zip file. Extract the contents. Run the *.bat file. Follow the instructions.
INSTRUCTIONS:
1) Unlock the bootloader first.
2) Unlock fastboot flashing.
3) Flash TWRP.
4) Reboot into recovery (TWRP)
5) Flash the version of Magisk that is included.
6) Reboot into the system
7) Install the included APK for Magisk. Official Magisk does not support this device.
8) If you want Xposed, reboot to recovery, and flash the included EdXposed zip and the riru-core zip.
9) Reboot back to the system
10) Install the included EdXposed apk
TWRP:
To get TWRP into English (or your language of choice), boot to TWRP recovery. When it shows up, slide the bar to the right to unlock it. After that, tap the button second from the bottom on the right column. This takes you to the Settings menu. In here, tap the globe icon in the top right tab. Choose your language from here.
NOTES:
1) The flashing unlock needs to be run EVERY TIME you reboot into bootloader, as it locks the flash mode every reboot. This type of unlock does not wipe data.
2) DO NOT WIPE /SYSTEM IN TWRP. It will brick your phone.
Download:
Link: Red Magic Mars-TWRP3.2.3.0-v1.1.zip
MD5: 84AB33312633B9AF91DD4E07478A059C
Size: 71.5 MB
Thanks, I can't flash twrp is fail
decscomputer said:
Thanks, I can't flash twrp is fail
Click to expand...
Click to collapse
Did you unlock the bootloader and do the flashing unlock? Both are required for TWRP to flash.
Yes, I did the process completely. I have the last Chinese Rom. The bootloader was unlocked, the fastboot Flash too but when I click the number 4 Is fail flashing twrp and there's a message saying Max limit exceded and too bootloader password Is error.
decscomputer said:
Yes, I did the process completely. I have the last Chinese Rom. The bootloader was unlocked, the fastboot Flash too but when I click the number 4 Is fail flashing twrp and there's a message saying Max limit exceded and too bootloader password Is error.
Click to expand...
Click to collapse
If you read Chinese, you could try the tool in this thread. It's what mine is based on, and may be better suited to the Chinese version.
Added options to reboot into recovery and bootloader as well as some more translation and other text adjustments.
decscomputer said:
Yes, I did the process completely. I have the last Chinese Rom. The bootloader was unlocked, the fastboot Flash too but when I click the number 4 Is fail flashing twrp and there's a message saying Max limit exceded and too bootloader password Is error.
Click to expand...
Click to collapse
OEM unlock has to be switched on in developer options do you have that switched on?
cajunflavoredbob said:
Did you unlock the bootloader and do the flashing unlock? Both are required for TWRP to flash.
Click to expand...
Click to collapse
Yes, I did the bootloader Is unlocked and I did the fastboot unlock but when I try to Flash twrp Is fail with a message exceded limit Max AND too password Is error or something like that. I try with the .exe AND directly with adb but it has the same result.
cajunflavoredbob said:
Hello friends. I have a problem and I can not find the solution .. in the magisk manager some modules are not shown when looking for them, like pix3lify, google framework, camera2api y more. The first time I rooted my nubia and installed magisk manager, the modules were shown and I could install them and they worked, but then I gave a full reset to red mars and since then I have not seen the modules never again. I have already reset the nubia more than 10 times, changed the language, installed other magisk manager apk, and nothing.
this magisk manager does not let me install modules from github and if I download and install a thirdparty zip from the web, magisk installs it but the module does not apply or is not installed for some reason.
Is the same in twrp:crying:
I do not ask for support, but if someone knows how to solve it or gives me any suggestions? please
Thanks
Click to expand...
Click to collapse
I have a problem with the bootloader
when i try to bootloader my nx619j , the bootloader failed and the message is "command write failed((too many links))" can u help me pls?
cajunflavoredbob said:
INSTRUCTIONS:
1) Unlock the bootloader first.
2) Unlock fastboot flashing.
3) Flash TWRP.
4) Reboot into recovery (TWRP)
5) Flash the version of Magisk that is included.
6) Reboot into the system
7) Install the included APK for Magisk. Official Magisk does not support this device.
8) If you want Xposed, reboot to recovery, and flash the included EdXposed zip and the riru-core zip.
9) Reboot back to the system
10) Install the included EdXposed apk
NOTES:
1) The flashing unlock needs to be run EVERY TIME you reboot into bootloader, as it locks the flash mode every reboot. This type of unlock does not wipe data.
2) DO NOT WIPE /SYSTEM IN TWRP. It will brick your phone.
Download:
Link: Red Magic Mars-TWRP3.2.3.0-v1.1.zip
MD5: 84AB33312633B9AF91DD4E07478A059C
Size: 71.5 MB
Click to expand...
Click to collapse
One thing that I have found rather disappointing with all of the "guides" (that can only be loosely called such) is that nobody has explicitly mentioned HOW you have to unlock the bootloader on Nubia devices without downloading something.
In fastboot mode, after toggling Bootloader Unlock in developer settings, one must type:
fastboot oem nubia_unlock NUBIA_NX619J
THEN you can do: fastboot flashing unlock
Flashing a boot image may require you to redo the bootloader flashing unlock to bypass the "This device is corrupt" screen.
Packed up Windows executables aren't exactly helpful for those of us using Linux or MacOS based systems. Even then, the Red Magic Mars packaged bat files/tools didn't install correct drivers for me on Win10. Could never get the device recognized within Fastboot on my Win10 Intel desktop after updating and reinstalling drivers.
There is also another quirk with the Nubia devices that I ran into that I have seen mentioned only once on another device's forum.
If you're running a Ryzen/AMD based system, you may have to issue the fastboot commands on an Intel based system instead.
Why? Beats me. It makes no sense, but after hours of pulling my hair out, I happened to come across a post suggesting it and gave it try.
Typing in the same commands with fastboot in the same OS (xUbuntu 20.04) with the same exact versions of every tool used... failed on my Ryzen desktop but worked fine on my Intel laptop. Had I known, it would have saved me several hours of swapping cables and reflashing software.
Also, for those (like me) who don't exactly like blindly trusting software found on forums.
You can download the official system images here:
REDMAGIC Mars
VERSIONS Europe & Asia: V207 North America: V111 LAST UPDATED 10/28/2019 DOWNLOAD V207: Download V111: Download Go to flash instructions UPDATED AND ADDED FEATURES Game Space: Call...
help.redmagic.gg
Pull boot.img from the update archive and use another device with Magisk installed to repackage the boot image for the Mars to flash yourself.
fastboot flash boot modified_boot_image.img
And done.
Due to the risk of bricking the Red Magic Mars within TWRP, I'd rather avoid using it entirely... so I only flashed a boot.img modified with Magisk instead.
One nice thing of note about the Red Magic Mars. It has an actual recovery partition and doesn't use the clusterfluck that is the A/B partition scheme.

Lost TWRP and root after update to MIUI 10

Hello,
I have a Mi Mix 3, MIUI global 10.2 stable, 10.2.2.0 PEEMIXM.
I managed to root, install TWRP and gcam after a few days of trying.
* Two days ago I updated from phone settings (About phone, Check updates ...)
* I lost both root and TWRP.
* I tried exactly the previous methods to root and phone stuck at booting (three dots flicking on the screen) - via PC / adb / fastboot.
* After that, I reset phone to factory settings and try again - boot in fastboot, try to flash TWRP and I get this error message: error cannot load TWRP.img file (not available or missing).
I also mention:
1. Phone was already rooted by the same procedure
2. Phone is unlocked
3. Dev options / USB debugging check
4. I renamed TWRP.img with recovery.img
5. I even try "TWRP" without extension ".IMG" (last week before the update I succeeded this way - no .img in the name of the file)
Please help
I need something so that I can root phone again AND won't delete TWRP and root after next update.
Thx very very much.
Any software update on this phone will overwrite TWRP if it has a recovery partition image, which most Xiaomi updates do have. There is a way to block it from getting overwritten by booting the phone, which has been implemented in the latest versions of the Chinese TWRP image. I do not know if they have been implmented on the official TWRP for our device.
Based on what you posted, it sounds like you probably need to reboot into the bootloader and use fastboot flash recovery "TWRPIMAGE.IMG" to install TWRP, then hold VOL Down + Power and reboot into TWRP. Once that is done, you can root again using MAGISK or whatever you choose to use for root.
PWn3R said:
Any software update on this phone will overwrite TWRP if it has a recovery partition image, which most Xiaomi updates do have. There is a way to block it from getting overwritten by booting the phone, which has been implemented in the latest versions of the Chinese TWRP image. I do not know if they have been implmented on the official TWRP for our device.
Based on what you posted, it sounds like you probably need to reboot into the bootloader and use fastboot flash recovery "TWRPIMAGE.IMG" to install TWRP, then hold VOL Down + Power and reboot into TWRP. Once that is done, you can root again using MAGISK or whatever you choose to use for root.
Click to expand...
Click to collapse
Thank you very much for your time and information. I must add that I was able to flash TWRP according to the procedure explained above, but I couldn't enter/access TWRP recovery. Then, I tried to re-flash TWRP and I always get the message: "error cannot load 'twrp.img' no such file or directory"
And I've tried several methods, several TWRP, different USB cables - almost everything you can imagine. Still, I cannot load the TWRP.img - it's not found. I must say I follow exactly the procedure explained in every posts.
What options do I have?
If you are using adb to load twrp, try putting it in the c/ of your pc, and putting twrp image in the adb folder, and if that didnt work, try renaming the img file to pocorecovery

[Guide] Installing Blu_spark TWRP | Magisk 20.1 On Stable Oxygen OS 10

Hi there just incase someone else who had problems [like me]
who is hesitant or looking for a guide on how to install Blu_Spark TWRP and Root the device.
The guide below will work 99.9% of the time. just follow the instructions carefully
Necessary Files:
Install OnePlus 6 Driver
Install Fastboot Drivers
TWRP Image
Magisk 20.1
twrp-3.3.1-x_blu_spark_v9.107_op6
Stock boot image thanks [URL="https://forum.xda-developers.com/member.php?u=6994095" @Akhil701[/URL]
Step 1: [dont do this if you have installed ADB and Fastboot already]
Install Oneplus 6, ADB and Fastboot Drivers from the link above
* Reboot PC after installing
Step 2:
Put
Code:
Stock Boot Image [boot.img]
twrp-3.3.1-x_blu_spark_v9.107_op6.zip and
Magisk-v20.1.zip
on your internal storage
Also Put
Code:
twrp-3.3.1-11-enchilada-Q-mauronofrio.img
on your desktop
Step 3: Reboot device in fastboot/bootloader mode
Step 4: Connect Device to PC Via USB Cable
Step 5: On your desktop Press Shift Right Click then click the [Open Command Prompt Here]
Step 6: on the CMD Windows Type
Code:
fastboot devices
Press enter and see if your device shows up.
Step 7: type in the CMD Window
Code:
fastboot flash boot twrp-3.3.1-11-enchilada-Q-mauronofrio.img
press enter then after that on your phone screen use volume up or down button to reboot to recovery
Step 8:
Once you have the TWRP Screen
flash the stock boot image [boot.img] in boot partition [DO NOT Reboot!]
now go back and flash the Blu_Spark TWRP and then reboot to recovery
Step 9: Rooting
Flash Magisk 20.1.zip then reboot to system.
Thats it! no data will be wiped as long as your bootloader is already unlocked.
thanks to
@Funk Wizard for the initial instruction on how to install twrp and root
 @eng.stk for the Blu_Spark TWRP
 @mauronofrio for the initial TWRP Image
 @Akhil701 for the stock boot.img
 @remewer for inspiration to build this guide.​
Patched boot.img or why we need the boot image after flashing OOS10 via local update?
Sh0X31 said:
Patched boot.img or why we need the boot image after flashing OOS10 via local update?
Click to expand...
Click to collapse
im not sure about that also. im just hesitant to skip that step. it might break something. thats why i added that step on this guide
Thnx, this was a very easy walkthrough.
Only thing I want to say is that not everyone knows how to flash the 'boot.img' through TWRP. Maybe you can explain that in more detail.
no patched boot.img you need
1. connect your OP6 to PC
2. flash TWRP (from mauronofrio) by fastboot from PC
3. reboot from fastboot to recovery
4. in TWRP flash stock img OOS, don´t reboot
5. in TWRP flash TWRP (blu_spark 9.107)
6- reboot to TWRP to another slot
7. in TWRP flash Magisk 20.1
8. reboot to system
I have noticed this too, probably they have changed somehow the system, even fastboot boot doesn't work anymore....
I had to install magisk via boot.img patching
Functionally on OOS 10.0.1 OP6 ?
So I was unable to flash the new OTA through twrp running on my rooted OP6.
As such, I opted to install the new OTA through the "local install" option.
That worked great. Settings area all the same. Bootloader still unlocked (I double checked).
Drivers are all installed on my Windows 10 PC.
However, no matter what I attempt to flash from command prompt I always get:
FAILED (remote: unkown command)
Does anyone know of a solution yet?
I have been reinstalling drivers and rebooting my PC with no luck thus far.
Any ideas?
Thanks in advance.
Update:
Whelp now that it is upgraded to Android 10 (and was wiped of all data when I locked and then unlocked the bootloader again) it will not allow me to downgrade back to Andriod 9 through the local upgrade option and since I can not get fastboot to accept any commands I am stuck now in Andriod 10 without the ability to change anything at the moment.
Brisky86 said:
So I was unable to flash the new OTA through twrp running on my rooted OP6.
As such, I opted to install the new OTA through the "local install" option.
That worked great. Settings area all the same. Bootloader still unlocked (I double checked).
Drivers are all installed on my Windows 10 PC.
However, no matter what I attempt to flash from command prompt I always get:
FAILED (remote: unkown command)
Does anyone know of a solution yet?
I have been reinstalling drivers and rebooting my PC with no luck thus far.
Any ideas?
Thanks in advance.
Update:
Whelp now that it is upgraded to Android 10 (and was wiped of all data when I locked and then unlocked the bootloader again) it will not allow me to downgrade back to Andriod 9 through the local upgrade option and since I can not get fastboot to accept any commands I am stuck now in Andriod 10 without the ability to change anything at the moment.
Click to expand...
Click to collapse
i knew it while reading but thanks to the screenshot you provided you saved me from sounding "user error" once again and piss of so many who prefer to blame things and others LOL
in short, wrong command, it's fastboot flash boot <image name>
BTW and since i'm already at it, if anyone has a Mac runniing 10.15 "Catalina" and fastboot is working from terminal, i'd like to learn how he/she's done it
just came to my mind to ask here since i have to use windows 10 under parallels desktop to fastboot flash my android stuff at the moment and of course that's just an "Emergency" choice for me, everyone using both platforms will understand
magnamentis said:
i knew it while reading but thanks to the screenshot you provided you saved me from sounding "user error" once again and piss of so many who prefer to blame things and others LOL
in short, wrong command, it's fastboot flash boot <image name>
BTW and since i'm already at it, if anyone has a Mac runniing 10.15 "Catalina" and fastboot is working from terminal, i'd like to learn how he/she's done it
just came to my mind to ask here since i have to use windows 10 under parallels desktop to fastboot flash my android stuff at the moment and of course that's just an "Emergency" choice for me, everyone using both platforms will understand
Click to expand...
Click to collapse
Wow. Okay.
This is becoming a comedy of errors on my part.
Oh boy now I am getting Qualcom flashdump messages...
Huh now it is just booting normal but not letting me get into the new recovery flash...
I got it all fixed.
Thank you everyone for your help and patience with my posts.
Does 10.0.1 still have the ability to do screen-off gestures for music? I like 10 but on my wife's 7t, either she didn't turn them on, our it didn't have them so I'm curious if there same thing is happening with this? I also noticed on her 7t, constant data problems when's switching from WiFi to data. Sometimes data won't come back and only a reboot solves. I know it's a bug on OOS 10 on 7t but wondering if it's a device specific bug or an Android 10 bug? Anyone having op6 issues with data not coming back when switching from WiFi?
WIFI problem solved!
Below OOS 10.0.1 back inTWRP
Wipe: cache, system and vendor
Flash OOS 10
Flash boot img
Flash TWRP
Flash Magisk
Reboot system
Reboot recovery
Flash OOS 10.0.1
Flash boot img
Flash TWRP
Flash Magisk
Reboot system
Wifi works
After rooting 10.0.1 with magisk 20.1 mobile network is gone. no sim pin, no metwork. after unroot everything is fine
Hello Mates,
i updated my rooted oneplus 6 from 10 to 10.01 and after that use this method to root again. But there is a Problem now: My WiFi doesnt work? I cant activate it.
Do anybody know how i can fix that Problem?
Thank you in Advance
Best Regards
Coktail
As above. No wifi, no sound. What's going on?
Coktail said:
Hello Mates,
i updated my rooted oneplus 6 from 10 to 10.01 and after that use this method to root again. But there is a Problem now: My WiFi doesnt work? I cant activate it.
Do anybody know how i can fix that Problem?
Thank you in Advance
Best Regards
Coktail
Click to expand...
Click to collapse
cubic25 said:
As above. No wifi, no sound. What's going on?
Click to expand...
Click to collapse
Look 2 posts up...
ryanallaire said:
Look 2 posts up...
Click to expand...
Click to collapse
Unroot doesn't work for me. Still no wifi and audio.
Hi guys, sorry to resurrect this thread. I did everything in the correct order using 10.0.3.0 and after step 8 (reboot after flashing blu_spark) my phone gets stuck on blu_spark splash screen without any option to boot into twrp. Normal boot results in bootloop... Any ideas? Do I need to use different versions of twrp.img and .zip?
dynamode said:
Hi there just incase someone else who had problems [like me]
who is hesitant or looking for a guide on how to install Blu_Spark TWRP and Root the device.
The guide below will work 99.9% of the time. just follow the instructions carefully
@Funk Wizard for the initial instruction on how to install twrp and root
@eng.stk for the Blu_Spark TWRP
@mauronofrio for the initial TWRP Image
@Akhil701 for the stock boot.img
@remewer for inspiration to build this guide.​
Click to expand...
Click to collapse
Hello.
I´m on 10.3.0 op6, I followed all the steps and when i finish the step 8 and reboot, i stuck on the recovery message. I repeat all the steps flashing clean rom and always have the same problem.....
Can someone help me? Because i don´t know another way for installing magisc....
Thanks!!!
loggstar said:
Hi guys, sorry to resurrect this thread. I did everything in the correct order using 10.0.3.0 and after step 8 (reboot after flashing blu_spark) my phone gets stuck on blu_spark splash screen without any option to boot into twrp. Normal boot results in bootloop... Any ideas? Do I need to use different versions of twrp.img and .zip?
Click to expand...
Click to collapse
I am in exactly the same position here.
Followed all the steps and am now stuck on the blu_spark boot screen for the past 15 minutes

Failed root, stuck on unlocked bootloader warning message.

Hi everyone,
I have tried to get root priviledges following a guide from Droidwin.com to flash Magisk throught TWRP. At the very last step, after flashing Magisk 19.3 throught TWRP when I tried to reboot my phone, it gets stuck on the "unlocked bootloader warning message", which is supposed to disappear after a few seconds and move on to the boot animation.
It seems like I can go to the stock recovery, which shows fastboot and wipe actions. At this point, I can acces the fastboot screen, but the device is not listed using the ADB command "adb devices", nothing is find.
I'm wondering, what can I try to restore the phone ? I thank you in advance for any suggestions.
Here are some additionnal informations:
---Device---
Oneplus nord running OxygenOS 10.5.5, european version.
---What I've done to get in this situation---
Unlock bootloader using ADB
Launch an TWRP image file using ADB
"Try" to root using Magisk 19.3 zip throught TWRP
Power off from recovery (using TWRP touch interface), but the guide tells to click reboot at this step ...
Get stuck on the warning message, not having any boot animation.
Try to boot in Fastboot.
Turn the Nord Off and start it with plus minus and Power.
Boot TWRP with "Fastboot boot "TWRP File name.img" and flash magisk 20.4
Thank you @denndenn.
I'm able to launch TWRP using the ADB command "fastboot boot [twrpfile].img". But when TWRP starts, it asks me for my decryption password, I type it, brief lines of code says "unable to read system/apex" before showing the home page of TWRP. Someone knows what this means, and if that can be the cause ?
I've then tried to reflash Magisk 19.3, which lead to the same result. I couldn't figure out how load Magisk 20.4 to my internal storage in order to flash it trought recovery ... Do you know how to flash a file which is not on my phone ?
Search forum....
Msm tool oneplus nord wipes phone but fixes any issues
thibdur said:
Thank you @denndenn.
I'm able to launch TWRP using the ADB command "fastboot boot [twrpfile].img". But when TWRP starts, it asks me for my decryption password, I type it, brief lines of code says "unable to read system/apex" before showing the home page of TWRP. Someone knows what this means, and if that can be the cause ?
I've then tried to reflash Magisk 19.3, which lead to the same result. I couldn't figure out how load Magisk 20.4 to my internal storage in order to flash it trought recovery ... Do you know how to flash a file which is not on my phone ?
Click to expand...
Click to collapse
Plug your phone to your PC while in TWRP, then you can use adb to push files to your phone, for example with adb push magisk.zip /sdcard. Then, flash Magisk in TWRP.
How about flashing stock boot to see if your OPN boots to system again and then simply load Magisk zip to your internal storage and then flash via TWRP?
Thank you a lot for your suggestions !
Here is the solution in my case :
Because fastboot was working, I was able to flash stock oxygen rom, and get every working, but it needs to erase all your data.
You can find a guide on the XDA topic "[ROM][STOCK][FASTBOOT][OPN] Stock Fastboot ROMs for OnePlus Nord". The rom list have the lastest roms version (09/2020), and the process is super automated.
Have a good week-end XDA !

[Guide] TWRP+MAGISK ROOT Installed on OOS 10.3.5

Ok guys, I decided to write this up because the current state of finding good info on this is quite messy. I'm going to keep it short and to the point.
I'm not here to explain what TWRP or Magisk Root are. You can find that somewhere else.
Goal:
Install TWRP and Magisk Root on OOS 10.3.5, without losing data.
(This same method worked on earlier versions of OOS 10, and may also work on later versions.)
Requirements:
OnePlus 6 Unrooted and Unmodified Recovery
Computer/Laptop
Magisk (ZIP)
TWRP Blu_Spark (ZIP)
TWRP Q by Mauronofrio (IMG)
Important Notes:
If you have installed or upgraded to OOS 10.3.5, then your device should be returned to stock (unrooted and unmodified recovery), and you're ready to begin. Otherwise, I suggest you simply reinstall the system again (full system links here) and then you'll be ready.
To send commands from your computer to your phone, you will need Android ADB debug software and possibly OnePlus drivers.
OnePlus Drivers Installation Instructions
Download Links:
Magisk 20.4 ZIP
Magisk Uninstaller 20.4 ZIP
TWRP Blu_Spark 3.4.0-x v9.116 ZIP
TWRP Q by Mauronofrio 3.3.1-18 IMG
Begin
Step 1:
Disable all lock patterns and security on your phone.
Step 2:
Back up anything important on your phone. You accept responsibility for any lost data.
Step 3:
Copy/Save the ZIP files (Magisk + Magisk Uninstaller + TWRP Blu_Spark) to the storage in your phone. The IMG file (TWRP Q by Mauronofrio) should be saved on your Computer
Step 4:
Boot your phone to fastboot mode.
(Power off. Then press Power on + Volume Up)
Step 5:
Connect phone to computer with USB. (Don't use a crap/cheap USB cable or the connection may fail.)
Step 6:
On your Computer, Open the command line, and Run the command to fastboot the TWRP Q by Mauronofrio
fastboot boot twrp-3.3.1-18-enchilada-Q-mauronofrio.img
Step 7:
Your phone should boot into TWRP (this is a temporary boot and nothing yet has been modified on your device).
Step 8:
Use the TWRP menu to Install both ZIP files. Starting with TWRP Blu_Spark, then Magisk.
BEWARE, DO NOT REBOOT BETWEEN INSTALLS! READ CAREFULLY. TWRP MAY TRY TO REBOOT. INSTALL BOTH ZIP FILES BACK TO BACK WITHOUT REBOOT.
Step 9:
Reboot. Complete. Congratulations.
If someone could provide me a link to ADB, then I will gladly include it in the post. Thank you
BEWARE, DO NOT REBOOT BETWEEN INSTALLS! READ CAREFULLY. TWRP MAY TRY TO REBOOT. INSTALL BOTH ZIP FILES BACK TO BACK WITHOUT REBOOT.
With reboot works too. Install twrp then reboot system, then reboot recovery from system, and install magisk. Works. I tried several times.
Shyciii said:
With reboot works too. Install twrp then reboot system, then reboot recovery from system, and install magisk. Works. I tried several times.
Click to expand...
Click to collapse
I have had bad problems on an earlier version, where Blu_Spark would Not properly install Magisk, and ruined my Recovery. Let me ask, on reboot, Did you boot into TWRP Q Mauron or TWRP Blu_Spark to install Magisk?
Sepero said:
I have had bad problems on an earlier version, where Blu_Spark would Not properly install Magisk, and ruined my Recovery. Let me ask, on reboot, Did you boot into TWRP Q Mauron or TWRP Blu_Spark to install Magisk?
Click to expand...
Click to collapse
I always use Mauron-like TWRP, and never had a problem.
Shyciii said:
I always use Mauron-like TWRP, and never had a problem.
Click to expand...
Click to collapse
Well then, I should consider you luckier than me, as I've had lots of data lost due to the issues with TWRP and Magisk. According to Mauronofrio,
"after some tests i'm sure there is a compatibility problem between twrp and magisk, i was able to get only one of them, so actually i don't know how to proceed, i need to understand if it is a twrp problem or a magisk problem, TWRP is in stand-by for now."
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
If TWRP by Mauronofrio is now working with the latest Magisk, then he it appears he has not publicly stated so. Did you install Magisk 20.4?
Sepero said:
Well then, I should consider you luckier than me, as I've had lots of data lost due to the issues with TWRP and Magisk. According to Mauronofrio,
"after some tests i'm sure there is a compatibility problem between twrp and magisk, i was able to get only one of them, so actually i don't know how to proceed, i need to understand if it is a twrp problem or a magisk problem, TWRP is in stand-by for now."
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
If TWRP by Mauronofrio is now working with the latest Magisk, then he it appears he has not publicly stated so. Did you install Magisk 20.4?
Click to expand...
Click to collapse
Of coz. I always use the latest Magisk, so now 20.4
I've never rooted my device can i go from stock to root or.do i need to oem unlock? Tnq.
Hi, I need help.
On step 8 I can not find files I copied on step 4. How I should copy those files to find it when I need to install them in step 8?
Thank you
I got following message returned:
FAILED (remote: boot is not allowed in Lock State)
Do I have to unlock bootloader before? This would wipe all data ...
followed the second half of the guide being an idiot and just keep all security as is. workt like a charm actually.. Thanks:highfive:
We don't need to unlock the bootloader before doing this???
fastboot OEM unlock????
techstuff_18 said:
We don't need to unlock the bootloader before doing this???
fastboot OEM unlock????
Click to expand...
Click to collapse
No, first unlock bootloader because you can't run twrp in fastbot. I did this, mean installed magisk on latest oxygen.
erdock said:
I got following message returned:
FAILED (remote: boot is not allowed in Lock State)
Do I have to unlock bootloader before? This would wipe all data ...
Click to expand...
Click to collapse
i unlocked it then all worked. and yes all data wiped

Categories

Resources