Database Develop

I got TWRP and root on magisk here's how.

I have ABSOLUTELY no clue why this works, BUT. Giving credit where credit is due and also a discovery of my own.
@3DSammy listed 3 different ways to get TWRP on the 5. One of them was VERY VERY CLOSE. They suggested a seperate usb port which was close. What I did was i tried to install TWRP on my surface pro 3 where i originally unlocked my bootloader, but for some reason it refused to let me add TWRP on top. So I grabbed a secondary PC and tried every single USB port on it since the Surface pro 3 only has 1 usb. None of them worked. Tried restarting the pc. Nothing. Tried updating fastboot drivers and uninstalling and reinstalling fastboot drivers. STILL NOTHING
At this point I just got really pissed and force shut my laptop down by holding the power button. Tried it again on my surface to no avail. But once i went back to my other computer i forced down it worked for some reason.... O,o really spooky. So i guess if you want twrp then force shut down a windows PC and try again after it boots. Its just how i got it to work i REALLY hope this works for others because i was steamin. I got my 3t rooted in 2 seconds but this thing. MAAAAN a whole afternoon wasted on such an odd solution. I think it has something to do with the usb ports losing all power then resetting once they receive power again.
Take all this with a grain of salt, i dont know if this will work for you but lots of folks seem to be having issues with getting TWRP running.
Also yes, magisk does work normally and passes safetynet.

hey man, i'm wodering which version of magisk did you choose for oneplus 5?

ihead said:
hey man, i'm wodering which version of magisk did you choose for oneplus 5?
Click to expand...
Click to collapse
I recommend using the latest beta (v13)
---------- Post added at 07:22 AM ---------- Previous post was at 07:21 AM ----------
OcazPrime said:
I have ABSOLUTELY no clue why this works, BUT. Giving credit where credit is due and also a discovery of my own.
@3DSammy listed 3 different ways to get TWRP on the 5. One of them was VERY VERY CLOSE. They suggested a seperate usb port which was close. What I did was i tried to install TWRP on my surface pro 3 where i originally unlocked my bootloader, but for some reason it refused to let me add TWRP on top. So I grabbed a secondary PC and tried every single USB port on it since the Surface pro 3 only has 1 usb. None of them worked. Tried restarting the pc. Nothing. Tried updating fastboot drivers and uninstalling and reinstalling fastboot drivers. STILL NOTHING
At this point I just got really pissed and force shut my laptop down by holding the power button. Tried it again on my surface to no avail. But once i went back to my other computer i forced down it worked for some reason.... O,o really spooky. So i guess if you want twrp then force shut down a windows PC and try again after it boots. Its just how i got it to work i REALLY hope this works for others because i was steamin. I got my 3t rooted in 2 seconds but this thing. MAAAAN a whole afternoon wasted on such an odd solution. I think it has something to do with the usb ports losing all power then resetting once they receive power again.
Take all this with a grain of salt, i dont know if this will work for you but lots of folks seem to be having issues with getting TWRP running.
Also yes, magisk does work normally and passes safetynet.
Click to expand...
Click to collapse
Did you decrypt before installing Magisk?

Im using beta 13 and i dont know anything about the decryption so im guessing no im not. But i think i know wjat you mean. When i went into twrp the first time it asked for my pattern. So i drew that and it worked perfectly. I think maybe that decrypted it. Twrp and magisk work 100%

OcazPrime said:
Im using beta 13 and i dont know anything about the decryption so im guessing no im not. But i think i know wjat you mean. When i went into twrp the first time it asked for my pattern. So i drew that and it worked perfectly. I think maybe that decrypted it. Twrp and magisk work 100%
Click to expand...
Click to collapse
I just asked because it seems that Magisk can't work if your device is decrypted

Didn't know that. But, no it's working perfectly fine. I used the test twrp build on the stable twrp 3.1.1 thread. Everything went great, no reason to flash anything else. Stock is king.

i have tried to used magisk v12 and it didn't work perfectly, specificialy 3C System Tuner doesn't get the root permission correctly then i have to use supersu 2.8.2
so if you want to root you OP5 , magisk v13 or supersu is recommended

If I'm already rooted with SuperSU, would it be pretty easy to unroot and then root using the latest beta of Magisk?
It looks like this modified the boot image, would this cause problem when taking updates or would we simply just need to reflash Magisk after?

geoff5093 said:
If I'm already rooted with SuperSU, would it be pretty easy to unroot and then root using the latest beta of Magisk?
It looks like this modified the boot image, would this cause problem when taking updates or would we simply just need to reflash Magisk after?
Click to expand...
Click to collapse
You won't be able to update OTA because your stock recovery is gone. You'll need to download the full ROM and flash it in TWRP every time an update comes. You can uninstall SuperSU and put Magisk v13. I currently have it, works perfect and safety net passes.

geoff5093 said:
If I'm already rooted with SuperSU, would it be pretty easy to unroot and then root using the latest beta of Magisk?
It looks like this modified the boot image, would this cause problem when taking updates or would we simply just need to reflash Magisk after?
Click to expand...
Click to collapse
If you do the OTA through the official update method in the settings, it will say that you have a rooted device and the entire package will need to be flashed. Then TWRP will flash it and the phone will update correctly. However, you lose root, as well as TWRP. So then you have to fastboot flash recovery and then flash Magisk to get back to where you were.
I did it last night.

ArkAngel06 said:
If you do the OTA through the official update method in the settings, it will say that you have a rooted device and the entire package will need to be flashed. Then TWRP will flash it and the phone will update correctly. However, you lose root, as well as TWRP. So then you have to fastboot flash recovery and then flash Magisk to get back to where you were.
I did it last night.
Click to expand...
Click to collapse
Once you flash the full zip, flash magisk BEFORE you got into the phone, you will keep root and that also keeps the stock recovery from overwriting TWRP. So you keep root and TWRP. After flashing full zip.
This is for future reference so you do go through that again.

Eric214 said:
Once you flash the full zip, flash magisk BEFORE you got into the phone, you will keep root and that also keeps the stock recovery from overwriting TWRP. So you keep root and TWRP. After flashing full zip.
This is for future reference so you do go through that again.
Click to expand...
Click to collapse
Hmm, I can't remember if it auto rebooted or not now, but thanks for the tip.

[Pie/Oreo/Nougat] How to root your Z2 [ALL]

Since no guide has been updated with information on official TWRP for root and backup reasons, I thought I'd create one.
DISCLAIMER:
To do this method requires you to unlock your bootloader. Your warranty is now void. This method assumes you have basic knowledge of ADB and Fastboot commands and know how to recover your device if you accidentally type a wrong command and now boot to TWRP and can't boot to system. If you cannot recover from this, Read up on guides to "return to stock" and familiarize yourself on how to recover your device should something go wrong.
There are two methods for root. You can flash TWRP to your boot image to be able to reboot to TWRP without a PC, or just a temp boot so you can just have root and not TWRP. I'll put in brackets the minor differences.
1: Get ready
Download latest build of TWRP img file from their website.(Previous link is to their instructions and device specific patches, download page is HERE.) {download the latest zip if you want to flash TWRP}
Download what you want on your phone (SU, Magisk, etc)
2:
Hook phone up to your PC, be sure you have latest adb/fastboot drivers. (I do not support windows related questions. If you have latest drivers, you'll have no issue with the below commands, Linux just works for this kind of thing)
3:
Navigate to your directory that has that img downloaded. (windows, shift right click and say "open command prompt here")
Type the below commands, and terminal output should be similar: (I.E. this is a copy/paste of terminal)
Main thing to remember is "Fastboot boot {filename}.img"
Code:
[email protected]:~$ adb reboot bootloader
[email protected]:~$ cd Downloads
[email protected]:~/Downloads$ fastboot boot twrp-3.2.1-1-nash.img
downloading 'boot.img'...
OKAY [ 0.841s]
booting...
OKAY [ 5.135s]
finished. total time: 5.976s
[email protected]:~/Downloads$
BE SURE TO DO BOOT AND NOT FLASH!!! (If you ask why you can no longer boot to system, I'll let you know you missed this line.)
5:
You're now in TWRP!
It will ask you for your password. This is your PIN or password to unlock your phone. Enter it.
TWRP has now decrypted your storage to read the zip file(s) you put on your phone!
Go to install and navigate to your directory where you put that file
Install Magisk/SU/TWRP/whatever you please.
(Note: some root zips require a factory reset)
6:
Reboot!
You're Done congratulations!
Attached are images if they help you see you're doing the right thing.
Special thanks @erfanoabdi @invisiblek @npjohnson @joemossjr @jbats
Without the above people a lot of what's above woudn't have been possible for this device specifically. Also, thanks to everyone who pitched in to get a device over to invisiblek. Leaps and bounds have been done since that donation. And thanks to the other devs who have invested in this phone and their time to help out.
(Quoted from Nathan Chance)
Quite a few people have asked to donate to me in the past and I have turned them down. I am not in this for the money, this is my hobby, something I truly enjoy. If you truly want to donate to something (it is not expected in the slightest), I recommend an entity like the Open Source Initiative, the Free Software Foundation, XDA, or any one of the people I have thanked in the OP. Additionally, you are free to copy any and all of my work; the only thing I request is that you not ask for donations as well (though I can't really enforce this lol). Thank you.

Random issues post:
SU does some wonky edits to the ramdisk. It is highly suggested to flash Magisk for root.
Some have reported needing to wipe data after flashing Magisk. If you can't boot after flashing Magisk, just go back into recovery (can be twrp or stock) and wipe data/factory reset to boot again.

Note: we do not have a recovery partition. Never flash the img file! Download the flashable zip if you want twrp on your phone and flash per OP instructions.

Awesome thanks

I get into a bootloop and right back into TWRP using this method. I got the failed to mount data invalid argument. I got rid of this by formating data in TWRP. Now I get failed to mount system device or resource busy when I attempt to flash Magisk.
Bootloop.
I am on TMO running the latest 27.1 Oreo

droidgreg said:
I get into a bootloop and right back into TWRP using this method. I got the failed to mount data invalid argument. I got rid of this by formating data in TWRP. Now I get failed to mount system device or resource busy when I attempt to flash Magisk.
Bootloop.
I am on TMO running the latest 27.1 Oreo
Click to expand...
Click to collapse
Be sure to mount system under the "mount" button

I need the OCX27.1 oreo. I did a return to stock flashall to OCX27 and now reflashed TWRP and Magisk and boots fine but I lost baseband and IMEI

Added warning to OP that some root zips require a data wipe.

I apologize in advance for asking a question that may have an obvious answer, but will this work for the Verizon variant of the Z2 Force? I'm not interested in trying out different ROMs just yet, but I would like to be able to remove adds, bloatware, and go back to using FoxFi the way it was meant to be used, specifically as a wireless hotspot. I can use the hotspot feature built into the phone, but it caps at 15 gigs & gets reduced to low, low speed after. Thanks in advance. Oh, and I should mention I'm currently running Oreo.

will4958 said:
I apologize in advance for asking a question that may have an obvious answer, but will this work for the Verizon variant of the Z2 Force? I'm not interested in trying out different ROMs just yet, but I would like to be able to remove adds, bloatware, and go back to using FoxFi the way it was meant to be used, specifically as a wireless hotspot. I can use the hotspot feature built into the phone, but it caps at 15 gigs & gets reduced to low, low speed after. Thanks in advance. Oh, and I should mention I'm currently running Oreo.
Click to expand...
Click to collapse
This guide assumes you can unlock your bootloader. Since Verizon and AT&T feel they have a right to lock down their devices, this guide won't work. That is why I voted with my wallet and left Vz after my M7 due to them putting phone OEM's privates in a vice and forced them to lock out those carrier variants.

Has this method been tested with OCX27.1 Oreo on TMO?

droidgreg said:
Has this method been tested with OCX27.1 Oreo on TMO?
Click to expand...
Click to collapse
It probably hasn't been tested, but it should work in theory.

Uzephi said:
It probably hasn't been tested, but it should work in theory.
Click to expand...
Click to collapse
I was on 27.1 when I attempted to root and got into a bootloop and lost my baseband when I flashall back to stock OCX27. I have a feeling 27.1 update isn't compatible with this method and cannot be downgraded to even OCX 27 Oreo

so no go on 27.1 twrp? I have root on 27.1 TMO obtained post update. Obtained by fastbooting the nash twrp and running magisk 16.zip. No needing to format data or anything
I was just wondering about the installable twrp zip. I am coming from samsung development so all this A/B partitioning and some of the other partitions are new to me.
As soon as I can get twrp on the phone and feel comfortable recovering. The kernels and roms will start coming.
Feels strange not having odin to save my ass

droidgreg said:
Has this method been tested with OCX27.1 Oreo on TMO?
Click to expand...
Click to collapse
tested and working

mattlowry said:
tested and working
Click to expand...
Click to collapse
Have you actually flashed installer.zip to install TWRP or just booted TWRP and only flash magisk or SU for root without installing TWRP?

I fastboot booted the twrp. I didn't try the installer. What is it?

Doesn't work for me, i've done every step whitout problems but after installing SU and reboot, it wont boot anymore, stays in Moto logo.

luponcooper said:
Doesn't work for me, i've done every step whitout problems but after installing SU and reboot, it wont boot anymore, stays in Moto logo.
Click to expand...
Click to collapse
I'll put a warning about SU then. It also causes other stuff to not flash right. Suggested root is magisk for our device. Reflash your boot.img from the flash all and reroot with magisk then wipe data (wiping might not be needed, I never had to but some people have needed to).

Uzephi said:
I'll put a warning about SU then. It also causes other stuff to not flash right. Suggested root is magisk for our device. Reflash your boot.img from the flash all and reroot with magisk then wipe data (wiping might not be needed, I never had to but some people have needed to).
Click to expand...
Click to collapse
Thanks a lot uzephi for answering.
I have the 6gb ram and 64gb model, XT1789-05. I try whit no succes to install Magisk (Error1) so i made a factory reset but still doesn't boot, stays in M logo.
Im super noob, can you guide me? i dont know how to recover the boot.img.
excuse my english.

Stock Owens XT1775, just got notice update is ready to install - root first or after?

Sorry if this seems like a dumb question - I'm a little green on the phone modding (last phone was a S3, rooted with oneclickroot I think) I have a bootloader unlockable XT1775 owens (bought from retail, no carrier lock) that I have been planning to bootloader unlock and root with TWRP & Magisk. I just got a notification that update "NPR26-58-45" is available. I downloaded it, but haven't installed yet - for fear that it might affect what I want to do for root.
What should I do? ie: - install it, and go forward with the root process? Root first, and then install?

jdsmn21 said:
Sorry if this seems like a dumb question - I'm a little green on the phone modding (last phone was a S3, rooted with oneclickroot I think) I have a bootloader unlockable XT1775 owens (bought from retail, no carrier lock) that I have been planning to bootloader unlock and root with TWRP & Magisk. I just got a notification that update "NPR26-58-45" is available. I downloaded it, but haven't installed yet - for fear that it might affect what I want to do for root.
What should I do? ie: - install it, and go forward with the root process? Root first, and then install?
Click to expand...
Click to collapse
Do NOT root first!
Edit: do me a favor and upload a system backup after you update, root and install twrp (if you do anyway), so I can make a twrp flashable ROM.
Edit-2: actually, if you could backup system before rooting or anything, that would be better.

You do not want to root first. Update then root as doing an ota while rooted may loose your root status or worse!

Goose03 said:
Do NOT root first!
Edit: do me a favor and upload a system backup after you update, root and install twrp (if you do anyway), so I can make a twrp flashable ROM.
Edit-2: actually, if you could backup system before rooting or anything, that would be better.
Click to expand...
Click to collapse
Thanks Goose. I will gladly upload that, but I will have to get back to you after the weekend - I apologize, heading out of town after work.
To clarify on the process, I would go through the step to unlock the bootloader (using the code I will get from Moto website and "fastboot oem unlock CODE"). After that is the TWRP step, right? If so, which command do I use: "fastboot boot recovery.img" or "fastboot flash recovery recovery.img" ??

jdsmn21 said:
Thanks Goose. I will gladly upload that, but I will have to get back to you after the weekend - I apologize, heading out of town after work.
To clarify on the process, I would go through the step to unlock the bootloader (using the code I will get from Moto website and "fastboot oem unlock CODE"). After that is the TWRP step, right? If so, which command do I use: "fastboot boot recovery.img" or "fastboot flash recovery recovery.img" ??
Click to expand...
Click to collapse
Np. Take your time. Thanks. Yes, that is what you do to unlock. Then for flashing twrp it's like you have but make sure to match the last part "recovery.img" to whatever the recovery is named. If your recovery is named twrp.img the command is:
fastboot flash recovery twrp.img

If it helps, I posted a step-by-step guide to unlocking, installing TWRP and rooting here: https://forum.xda-developers.com/moto-e4-plus/help/step-step-how-to-root-moto-e4-plus-t3752334

koop1955 said:
If it helps, I posted a step-by-step guide to unlocking, installing TWRP and rooting here: https://forum.xda-developers.com/moto-e4-plus/help/step-step-how-to-root-moto-e4-plus-t3752334
Click to expand...
Click to collapse
That's the one I had been following! I found that very helpful - that would make a good sticky post for guys like myself.
Since I have your attention too, I'd like to ask - is dmnoverity and phh's SU not needed at all? The only three files copied to the SD card (and then installed) are TWRP, Magisk zip, and Magiskmanager APK?

jdsmn21 said:
That's the one I had been following! I found that very helpful - that would make a good sticky post for guys like myself.
Since I have your attention too, I'd like to ask - is dmnoverity and phh's SU not needed at all? The only three files copied to the SD card (and then installed) are TWRP, Magisk zip, and Magiskmanager APK?
Click to expand...
Click to collapse
Phh SU is not needed since Magisk gives you all the necessary root and features. dmnoverity is not needed. I recommend you allow twrp system write access.

koop1955 said:
If it helps, I posted a step-by-step guide to unlocking, installing TWRP and rooting here: https://forum.xda-developers.com/moto-e4-plus/help/step-step-how-to-root-moto-e4-plus-t3752334
Click to expand...
Click to collapse
Well, I followed your instructions....with a minor tweak - and I'm having problems.
I unlocked the bootloader a couple days ago, but couldn't download the TWRP.bin file, so I used my phone through today. Formatted a 64gb card and loaded the magisk zip and apk on it. Flashed the TWRP on the phone, and used the wipe function to wipe data, cache, and dalvik, and then made a backup to my sd card. Flashed the magisk.zip, and then hit reboot "system". Now it just reboots to TWRP. I can reboot to bootloader, but hitting "start" goes to TWRP again.
What do I do? Where did I go wrong?

jdsmn21 said:
Well, I followed your instructions....with a minor tweak - and I'm having problems.
I unlocked the bootloader a couple days ago, but couldn't download the TWRP.bin file, so I used my phone through today. Formatted a 64gb card and loaded the magisk zip and apk on it. Flashed the TWRP on the phone, and used the wipe function to wipe data, cache, and dalvik, and then made a backup to my sd card. Flashed the magisk.zip, and then hit reboot "system". Now it just reboots to TWRP. I can reboot to bootloader, but hitting "start" goes to TWRP again.
What do I do? Where did I go wrong?
Click to expand...
Click to collapse
Try fastboot oem fb_mode_clear
Sent from my Moto E (4) Plus using XDA Labs

Goose03 said:
Try fastboot oem fb_mode_clear
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
Thank you. I tried the command, and it said OK, but it still boots to TWRP; i then reboot to bootloader, and select Start and it goes into the normal system. Is that how it is supposed to work?
Last night I was stuck in a TWRP loop, but i got it to go with formatting data and factory reset wipe in TWRP. After finally getting the system to boot, I installed the Magisk Manager and then Adaway. Now today I was playing with the Chase Pay app, which won't let me sign in due to being rooted. I then reverted my hosts file and uninstalled Adaway, and played with all the hide options in Magisk., to no avail. Root Checker app says that Safetynet is tripped.
Does Magisk effectively work for apps that look at Safetynet on this phone - apps like Chase Pay?

jdsmn21 said:
Thank you. I tried the command, and it said OK, but it still boots to TWRP; i then reboot to bootloader, and select Start and it goes into the normal system. Is that how it is supposed to work?
Last night I was stuck in a TWRP loop, but i got it to go with formatting data and factory reset wipe in TWRP. After finally getting the system to boot, I installed the Magisk Manager and then Adaway. Now today I was playing with the Chase Pay app, which won't let me sign in due to being rooted. I then reverted my hosts file and uninstalled Adaway, and played with all the hide options in Magisk., to no avail. Root Checker app says that Safetynet is tripped.
Does Magisk effectively work for apps that look at Safetynet on this phone - apps like Chase Pay?
Click to expand...
Click to collapse
It is not normal to have it boot straight to twrp or the bootloader rather than the rom unless you do so manually.
Have you triedbplaying with the settings in Magisk Manager? There is an option to hide Magisk from your choice of apps. There is also a couple other options in the settings to hide things as much as possible. If you have Xposed installed it won't pass a safteynet check.
Sent from my Moto E (4) Plus using XDA Labs

XT1775 rom's is possible install on XT1776 ?

almao11 said:
XT1775 rom's is possible install on XT1776 ?
Click to expand...
Click to collapse
You could. I've flashed xt1775 firmware to my xt1776 to get a backup of the system to make a twrp flashable from. I don't recommend it, but if you only flash the system and not the modem and oem it should provision data services. Why do you ask exactly?
Sent from my Moto E (4) Plus using XDA Labs

[Updated/All Versions & Models!] Root OnePlus 7T Pro

How to root any version of the OnePlus 7T Pro!
1. Make sure your bootloader is unlocked!
2. Once you're unlocked enter the following ADB commands to extract your current boot image (Your phone needs to be on)
adb shell dd if=/dev/block/bootdevice/by-name/boot_a of=/boot_a.img
adb pull /boot_a.img pathinyourpc
Click to expand...
Click to collapse
3. Download & install Magisk Manager on your phone
4. Put the boot_a.img file on your phone
5. Open the magisk manager app and click the "Advanced Settings" button, then enable "Prserve AVB 2.0/dm-verity & Preserve force encryption", then select the top "Install" button and select "Patch to boot image" and select the boot_a.img
6. Now magisk will create a magisk patched boot image file, put that on your computer
7. Now enter the following ADB command
adb reboot fastboot
fastboot --set-active=a
fastboot boot pathtomagiskpatched.img
Click to expand...
Click to collapse
8. Now you'll boot into the system, reopen the magisk app and click the top install button again and select "Direct install", then reboot
Congratulations you've now successfully rooted your phone!

EDIT: This guide is wrong.
Check these references for the proper guide to root. OP refuses to acknowledge it's wrong even when I pointed it out to him with proof.
https://forum.xda-developers.com/showpost.php?p=81023631&postcount=144
^^^
Mainly this one.
https://forum.xda-developers.com/showpost.php?p=81105485&postcount=171
https://forum.xda-developers.com/showpost.php?p=81106827&postcount=173
-----
Now I have something so do for the weekend, thanks
Just a question, have you tried Viper4Android (if your use it)?: Use 2.7.1.6 stable version.

hi,
tryed it out.. When i boot your patched image.. there is no install button in magisk. It tolds me that i am already on the newest version.
Second.. WLAN isnt working any more. Cant enable wlan. When i reboot with stock img. everything is fine.

Dukynuky said:
hi,
tryed it out.. When i boot your patched image.. there is no install button in magisk. It tolds me that i am already on the newest version.
Second.. WLAN isnt working any more. Cant enable wlan. When i reboot with stock img. everything is fine.
Click to expand...
Click to collapse
Yes it says its installed thats correct but you need to install it again in the magisk app so it stays after restarting the phone. I don't know about WLAN tho

Can you turn on Wifi ?
When i turn it on. It is disabled at the end.
There are similar problems in the 7t forums. Seems a problem with the used magisk version for the boot image.. did you use the canary magisk files ?
and yes.. I know why i need to install. But the linked version of magisk says only.. uninstall..
Edit: i have a european version of the oneplus 7t pro .. and can you provide the original boot image.

I can confirm I have successfully rooted using this method, and WIFI is working fine. Thank you very much, OP and everyone involved, no wits time to set up my device

Ah! Will do this immediately when I get home.

I tried magisk and now it loops to fastboot, does anyone know to recover from this? Does the msm tool for OP7T Pro?
edit: flashed the original boot img and boots fine, whever i try to boot magisk patched it bootlops because faulty drivers
to clear up, i tried installing viper4android driver directly from the app, so i guess theres residue left

Lossyx said:
I tried magisk and now it loops to fastboot, does anyone know to recover from this? Does the msm tool for OP7T Pro?
Click to expand...
Click to collapse
did you install modules ? try booting the patched boot image from here and then, uninstall the modules again...

Works like a charm!
Minor thing you may want to clarify (I know you know, but to prevent confusion for readers), you give a warning that this will wipe all data, but that is not exactly true. Unlocking the bootloader wipes all data, but that step is not part of your instructions. Just following your steps on an already unlocked phone does not wipe the phone.
Thanks to everyone who made this possible so soon!

Dukynuky said:
did you install modules ? try booting the patched boot image from here and then, uninstall the modules again...
Click to expand...
Click to collapse
please see my edited reply, i installed directry through viper4android app, no the module

Dukynuky said:
Can you turn on Wifi ?
When i turn it on. It is disabled at the end.
There are similar problems in the 7t forums. Seems a problem with the used magisk version for the boot image.. did you use the canary magisk files ?
and yes.. I know why i need to install. But the linked version of magisk says only.. uninstall..
Edit: i have a european version of the oneplus 7t pro .. and can you provide the original boot image.
Click to expand...
Click to collapse
got ist working.. layer 8 error.. didnt had the ota update installed.
Updated oxygen os.. then wifi is working. also used canary magisk files.. works perfekt.. thanks

Dukynuky said:
Can you turn on Wifi ?
When i turn it on. It is disabled at the end.
There are similar problems in the 7t forums. Seems a problem with the used magisk version for the boot image.. did you use the canary magisk files ?
and yes.. I know why i need to install. But the linked version of magisk says only.. uninstall..
Edit: i have a european version of the oneplus 7t pro .. and can you provide the original boot image.
Click to expand...
Click to collapse
my wifi works perfectly fine, I have the EU version too.
I attached screenshots of what to do with the installed, please select the direct install option and then reboot!

droidvark said:
Works like a charm!
Minor thing you may want to clarify (I know you know, but to prevent confusion for readers), you give a warning that this will wipe all data, but that is not exactly true. Unlocking the bootloader wipes all data, but that step is not part of your instructions. Just following your steps on an already unlocked phone does not wipe the phone.
Thanks to everyone who made this possible so soon!
Click to expand...
Click to collapse
I have a warning above the instructions already, I think you might have missed it

Lossyx said:
I tried magisk and now it loops to fastboot, does anyone know to recover from this? Does the msm tool for OP7T Pro?
edit: flashed the original boot img and boots fine, whever i try to boot magisk patched it bootlops because faulty drivers
to clear up, i tried installing viper4android driver directly from the app, so i guess theres residue left
Click to expand...
Click to collapse
I also bootlooped as well, I tried to install liveboot and i guess that didnt work lol
anyways, I fixed my bootloop by booting the unpatched boot img and then doing a factory reset in the settings, after that you can just boot to the magisk boot img again!

Lossyx said:
please see my edited reply, i installed directry through viper4android app, no the module
Click to expand...
Click to collapse
Use the module next time!

HolyChickenGuy said:
I have a warning above the instructions already, I think you might have missed it
Click to expand...
Click to collapse
I'm not sure where the misunderstanding is coming from, I know that you give that warning. What I mean is that strictly speaking following your steps does not wipe the phone, unlocking the bootloader wipes the phone. But you don't have that step in your instructions. See what I mean? .
When I read your steps, I was like "wipes my phone how?" Maybe booting your image would wipe my phone or something? I'm glad it didn't .
I just thought for clarity's sake it would be good to make that clear in the steps that's all!

droidvark said:
I'm not sure where the misunderstanding is coming from, I know that you give that warning. What I mean is that strictly speaking following your steps does not wipe the phone, unlocking the bootloader wipes the phone. But you don't have that step in your instructions. See what I mean? .
When I read your steps, I was like "wipes my phone how?" Maybe booting your image would wipe my phone or something? I'm glad it didn't .
I just thought for clarity's sake it would be good to make that clear in the steps that's all!
Click to expand...
Click to collapse
Oh sorry, yeah I rewrote it to make it clearer. Unlocking the bootloader will wipe your data
Sent from my HD1913 using Tapatalk

HolyChickenGuy said:
I also bootlooped as well, I tried to install liveboot and i guess that didnt work lol
anyways, I fixed my bootloop by booting the unpatched boot img and then doing a factory reset in the settings, after that you can just boot to the magisk boot img again!
Click to expand...
Click to collapse
Damn, you are my hero. Did a factory reset and followed the OP again, now everything is fine and I'm rooted. Thank you again.
edit: also, for safety precaution, disable automatic updates in Developer options
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation

Great, I'll check back in on this tomorrow and see how everyone is getting on before I try. Had a skim through here this morning before mine arrived and didn't see anything so set up as is.

[GUIDE] How to flash Lineage OS 16 Official + Gapps from OOS10 and pass SafetyNet

- In case some step fails, just make sure your bootloader is unlocked.
- I assume you have a working adb and fastboot. I used the official Google package: https://developer.android.com/studio/releases/platform-tools . It's possible you will still have an older version installed because some "pack" installed it and put it in your path. How to edit PATH? What is PATH?! https://www.howtogeek.com/118594/how-to-edit-your-system-path-for-easy-command-line-access/
- Advanced Reboot is an option so you can easily enter recovery/fastboot mode. Enable it in Developer Options. How to enable Developer Options? Tap Build Number several times.
I realize the guide is long but it's overly detailed. If you get stuck, have questions, just ask and I will also edit the OP to answer more questions / clarify on points I guess.
Let's go back to latest OOS9.
Make sure to back everything up. If you have Google One, you can do a backup there. If you have root, even better, you can do a full backup with TWRP. I would also copy every important files over to my PC as well - just in case.
Make sure you are unlocked. This can reset if you flashed a full system update or anything so just make sure. If not, unlock.
Grab the MSM toolkit - we will use this to flash back OOS9. See: https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
In my case I didn't have to mess with drivers or anything, just had to run the tool as admin. However, do read the steps, follow them in case you run into any trouble. Also, I just plug in the phone from a power off state with VOL buttons held down, start it, and I can start the flash process.
At this point you are locked, but does not matter for now. Thing is, now you are on a bit borked image. The stock image has broken fastboot, and might be AA or BA. Point is, you have to flash the correct update at this point. Grab the correct 9.5.11 for your device (AA = global; BA = EU): https://forum.xda-developers.com/oneplus-7-pro/how-to/oneplus-7-pro-global-repo-oxygen-os-t3930585
Just copy it up to your device and use System Update -> Local Update once again to flash it.
Now it's time to flash LineageOS 16.
Now it's time to bootloader unlock again. (Via Developer Options, enable oem unlock and advanced reboot, go into Bootloader, use fastboot oem unlock.)
Now download the latest LineageOS rom from the official site: https://download.lineageos.org/guacamole
Copy up the files to your phone. You can also use adb push at later step. I leave it to you. Copying up might be easier.
Use fastboot boot ...img to boot up the latest unofficial TWRP: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322 . You need the .img, but also grab the installer. Make sure you grab the Pie version, LOS16 == Android 9 (Pie).
Once you are in TWRP, go Install, and pick the Lineage zip. Then make sure to do a Wipe from the TWRP menu.
Reboot, let phone boot LineageOS. Shut down once it's booted. No need to set anything.
Press VOL_DOWN + Power to go into Lineage Recovery. Press Sideload here.
You need to grab "Mindthegapps" package from here: http://downloads.codefi.re/jdcteam/javelinanddart/gapps and you need to use adb sideload ...zip to load it onto the phone. It will cry about the zip being unverified, just tap proceed.
Now, once it's installed, wipe again from LineageOS Recovery again. At this point, you can also sideload TWRP. You need to use the .zip, and again - make sure you have the Pie version.
Phew, we are almost there! Reboot, log in to Google, do whatever. Set up your device.
Now, finally, let's finish up with SafetyNet.
Once everything is done, install the Magisk Manager APK and grab the ZIP from here. Since you have TWRP, you can just grab the zip to the phone itself.: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Enter TWRP by using Advanced Reboot, Install magisk ZIP.
Almost done!
Go into Magisk Manager, make sure all is green. Go into the left hamburger menu -> Downloads. Grab "MagiskHide Props Config", Install. Reboot.
Now you have to install "Busybox" from Play Store, and you need to install a Terminal Emulator from Play Store as well. Just grab any.
Go into BusyBox, grant root, Install.
Open Terminal, type "su", then type "props".
Just go through the menu system and pick your phone. Just type in a number, and enter. And so on. If you get stuck / afraid to do harm, just reboot the phone and install busybox again, open terminal again, try again. Or ask.
Upon rebooting as you go through the tool, SafetyNet should 100% pass upon reboot.

Thanks for this guide. I can' use MSM toolkit because I'm not on windows. Is there a linux version? Why can't I just dirtyflash 9.5.1.1 zip over installed OOS 10?

Great guide. I just have one question for you. I have a GM1910 Model of the phone with international rom. I'm currently on Oxygen OS 10.0.2, can I still follow your steps to downgrade to the 9.5.1.1 and then flash Lineage as per your instructions? I'm new to the OnePlus devices and I want to be sure before doing something that I'll end up regretting. I know that with my S10+ I was able to downgrade between builds easily, but don't know what to do with my OP7P.
Thanks for your time and help in advance.
Edit: How stupid of me, I didn't even read properly before commenting. My apologies. Your title clearly states how to install Lineage OS from OOS10. Disregard my question about downgrading. I just would like to know if my GM1910 model is supported with Lineage or other OOS ROMs. I would think yes, but better to make sure of course.

wp007 said:
Thanks for this guide. I can' use MSM toolkit because I'm not on windows. Is there a linux version? Why can't I just dirtyflash 9.5.1.1 zip over installed OOS 10?
Click to expand...
Click to collapse
Usually, you cannot dirty flash an older Build to downgrade. This will most likely cause an issue. You need to perform a clean install. I'm not entirely sure in OP7s case, but I do know this applies to Samsung devices and many others as well.

If one unlocks bootloader, flashes twrp and then installs LineageOS16 + openGapps only on guacamole, will they pass safetynet or do they need magisk?

Iolaum said:
If one unlocks bootloader, flashes twrp and then installs LineageOS16 + openGapps only on guacamole, will they pass safetynet or do they need magisk?
Click to expand...
Click to collapse
Magisk is most definitely required. Without it you cannot pass safetynet.

[*] Just go through the menu system and pick your phone. Just type in a number, and enter. And so on.
[/LIST]
Click to expand...
Click to collapse
I have followed all of your instructions and have successfully installed Lineage, TWRP, and Magisk. I've even downloaded the Magisk hide prop from downloads. The only thing I DO NOT understand is STEP 7. PLEASE explain what you have to exactly do here. I don't understand what you mean by: "Just go through the menu system and pick your phone. Just type in a number, and enter. And so on." After I type su, and then props, I get the following options:
1. Edit Device Fingerprint
2. Device Simulation(Disabled)
3. Edit MagiskHide props
4. Add/edit custom props
5. Delete prop values
6. Script settings
7. Collect logs
r. Reset all options/settings
b. Reboot Device
e. Exit
Where do I go to select my phone and number as you're mentioning? And when you say just type in a number and enter? What does that mean? What exactly do I type in? Any random number and enter? I don't understand this at all.
I'd appreciate some feedback here.
- Thanks
Edit: Turns out it only needs the fingerprint to be updated. (ro.build.version.security_patch) Do you have such a code. The developer says he has OP7P added to the list, but I for one, cannot seem to find it. What have you put for yours?
Edit #2: Issue has been resolved. Just did some digging of my own and figured it out. So all that needs to be done is you need to pick your device from the options of 1. Edit device fingerprint, follow the menu options until you see select from certified devices, and then you will see a list of certified devices.
Edit#3: Unfortunately, my devices model is not listed for the certified fingerprints. My model is GM1910, and I tried using the 1911 model, but it doesn't seem as though it worked. Because Google Play is still saying device not certified. Any other model numbers I can try for my model (GM1910)?
Edit #4: What a rough day it has been LOL. Finally found a working version. GM1913 works fine and I can confirm that my device has been indeed certified by Google Play Store. So for my model (GM1910) the GM1913 is the one that works. Ignore all of the above as I've explained it all here in case someone else is confused.

malimt said:
I....
Click to expand...
Click to collapse
Oh man, I am terribly sorry I wasn't really around. Sorry.
One major thing that I cannot figure out - I wasn't able to update.
For some reason after I updated LOS (via TWRP), my whole installation of LOS + Gapps broke.
Now, I needed my phone ASAP so I had to revert to OOS quickly because I needed my phone the next morning.
But, maybe it would work if you update from LineageOS itself.
I would VERY, VERY heavily recommend doing a TWRP full backup before attempting a LOS upgrade.
Shouldn't take long, for me it was like 10 minutes tops, I copied over the files to my PC and that was it. If something breaks, just copy the backups back and restore the backup.
If someone figures out a safe way to upgrade from LOS to LOS... let us know and I'll update the thread.
Ps.: In case your LOS breaks during an upgrade and your backup doesn't restore, you can install OpenGapps now via TWRP (you need the bigger package). This way you'll still have permission issues (like for some reason all Google apps will have bad permissions, so you have to give all perms to each one-by-one) BUT you will have a kinda working phone...

h8Aramex said:
Oh man, I am terribly sorry I wasn't really around. Sorry.
One major thing that I cannot figure out - I wasn't able to update.
For some reason after I updated LOS (via TWRP), my whole installation of LOS + Gapps broke.
Now, I needed my phone ASAP so I had to revert to OOS quickly because I needed my phone the next morning.
But, maybe it would work if you update from LineageOS itself.
I would VERY, VERY heavily recommend doing a TWRP full backup before attempting a LOS upgrade.
Shouldn't take long, for me it was like 10 minutes tops, I copied over the files to my PC and that was it. If something breaks, just copy the backups back and restore the backup.
If someone figures out a safe way to upgrade from LOS to LOS... let us know and I'll update the thread.
Ps.: In case your LOS breaks during an upgrade and your backup doesn't restore, you can install OpenGapps now via TWRP (you need the bigger package). This way you'll still have permission issues (like for some reason all Google apps will have bad permissions, so you have to give all perms to each one-by-one) BUT you will have a kinda working phone...
Click to expand...
Click to collapse
Thank you for your response. Never apologize, you have a great guide here. I understand you were busy and had to step away. Also, I'm not sure why you experienced that because I followed your guide every step of the way and everything went perfectly, aside for the safetycheck but I managed to figure that out so you're good! Furthermore, I used Dec. 3 build and right after I installed it, there was an update. I updated the phone in the settings of LOS itself and it worked flawlessly, I downloaded the OTA and updated, rebooted and it was great! No issues there. Did yours use the OTA update? If not, give that a try.
Thanks again for a such an easy guide! Its great! Really works!

I hate A/B partitioning. It only works in increments with your guide, outdated tools everywhere and a ****ty system, on top of not having an sd card. I loved my Samsung. Not for the Touchwiz, bloat etc, but they had sd cards an the old system, which just....worked. Either the gapps fails, the twrp gets overwritten or it boots, without actually loading magisk or gapps. It seems random if the lineage recovery wants to boot to a or b. This is horrible, but now I have to finish it....

You have not specified what you include in a "wipe". This is never the same for anyone, often not necessary and mostly something people do superstitiously - Therefore clarification would be nice. Still fighting with getting this ****ty system to work. Hope it will be restored with a OOS10 flash, if this keeps failing

malimt said:
Usually, you cannot dirty flash an older Build to downgrade. This will most likely cause an issue. You need to perform a clean install. I'm not entirely sure in OP7s case, but I do know this applies to Samsung devices and many others as well.
Click to expand...
Click to collapse
https://www.getdroidtips.com/how-to...d-10-q-to-android-9-0-pie-on-oneplus-7-7-pro/

h8Aramex said:
- In case some step fails, just make sure your bootloader is unlocked.
- I assume you have a working adb and fastboot. I used the official Google package: https://developer.android.com/studio/releases/platform-tools . It's possible you will still have an older version installed because some "pack" installed it and put it in your path. How to edit PATH? What is PATH?! https://www.howtogeek.com/118594/how-to-edit-your-system-path-for-easy-command-line-access/
- Advanced Reboot is an option so you can easily enter recovery/fastboot mode. Enable it in Developer Options. How to enable Developer Options? Tap Build Number several times.
I realize the guide is long but it's overly detailed. If you get stuck, have questions, just ask and I will also edit the OP to answer more questions / clarify on points I guess.
Let's go back to latest OOS9.
Make sure to back everything up. If you have Google One, you can do a backup there. If you have root, even better, you can do a full backup with TWRP. I would also copy every important files over to my PC as well - just in case.
Make sure you are unlocked. This can reset if you flashed a full system update or anything so just make sure. If not, unlock.
Grab the MSM toolkit - we will use this to flash back OOS9. See: https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
In my case I didn't have to mess with drivers or anything, just had to run the tool as admin. However, do read the steps, follow them in case you run into any trouble. Also, I just plug in the phone from a power off state with VOL buttons held down, start it, and I can start the flash process.
At this point you are locked, but does not matter for now. Thing is, now you are on a bit borked image. The stock image has broken fastboot, and might be AA or BA. Point is, you have to flash the correct update at this point. Grab the correct 9.5.11 for your device (AA = global; BA = EU): https://forum.xda-developers.com/oneplus-7-pro/how-to/oneplus-7-pro-global-repo-oxygen-os-t3930585
Just copy it up to your device and use System Update -> Local Update once again to flash it.
Now it's time to flash LineageOS 16.
Now it's time to bootloader unlock again. (Via Developer Options, enable oem unlock and advanced reboot, go into Bootloader, use fastboot oem unlock.)
Now download the latest LineageOS rom from the official site: https://download.lineageos.org/guacamole
Copy up the files to your phone. You can also use adb push at later step. I leave it to you. Copying up might be easier.
Use fastboot boot ...img to boot up the latest unofficial TWRP: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322 . You need the .img, but also grab the installer. Make sure you grab the Pie version, LOS16 == Android 9 (Pie).
Once you are in TWRP, go Install, and pick the Lineage zip. Then make sure to do a Wipe from the TWRP menu.
Reboot, let phone boot LineageOS. Shut down once it's booted. No need to set anything.
Press VOL_DOWN + Power to go into Lineage Recovery. Press Sideload here.
You need to grab "Mindthegapps" package from here: http://downloads.codefi.re/jdcteam/javelinanddart/gapps and you need to use adb sideload ...zip to load it onto the phone. It will cry about the zip being unverified, just tap proceed.
Now, once it's installed, wipe again from LineageOS Recovery again. At this point, you can also sideload TWRP. You need to use the .zip, and again - make sure you have the Pie version.
Phew, we are almost there! Reboot, log in to Google, do whatever. Set up your device.
Now, finally, let's finish up with SafetyNet.
Once everything is done, install the Magisk Manager APK and grab the ZIP from here. Since you have TWRP, you can just grab the zip to the phone itself.: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Enter TWRP by using Advanced Reboot, Install magisk ZIP.
Almost done!
Go into Magisk Manager, make sure all is green. Go into the left hamburger menu -> Downloads. Grab "MagiskHide Props Config", Install. Reboot.
Now you have to install "Busybox" from Play Store, and you need to install a Terminal Emulator from Play Store as well. Just grab any.
Go into BusyBox, grant root, Install.
Open Terminal, type "su", then type "props".
Just go through the menu system and pick your phone. Just type in a number, and enter. And so on. If you get stuck / afraid to do harm, just reboot the phone and install busybox again, open terminal again, try again. Or ask.
Upon rebooting as you go through the tool, SafetyNet should 100% pass upon reboot.
Click to expand...
Click to collapse
GeeAyeZee said:
https://www.getdroidtips.com/how-to...d-10-q-to-android-9-0-pie-on-oneplus-7-7-pro/
Click to expand...
Click to collapse
Awesome! Thanks. I guess I'm liking the OnePlus more than my S10+ now. Samsung makes much more difficult to rollback using Odin and such. But this is just great!