Question Root or twrp recovery - OnePlus 10 Pro

Can I root this device without a computer? I looked and can't find a twrp recovery file for this device sorry if I'm asking a stupid question Im new to this before I had an I phone I have the ne2215 unlocked version

There is no TWRP currently and no, you cannot do it without PC because of fastboot etc.

kouzelnik3 said:
There is no TWRP currently and no, you cannot do it without PC because of fastboot etc.
Click to expand...
Click to collapse
Thank you so much... Can you link a tutorial or something to show how to root my phone? I wanna use substratum and I read Andromeda no longer works I've been on iPhone too long I forgot all the cool things android can do

s_nieto said:
Can I root this device without a computer? I looked and can't find a twrp recovery file for this device sorry if I'm asking a stupid question Im new to this before I had an I phone I have the ne2215 unlocked version
Click to expand...
Click to collapse
OnePlus 10 Pro NE2215 ***ROOTED*** (EX01 Update! READ BEFORE UPDATING)
This is for the NE2215 Rom. Step 1: Unlock your bootloader. Step 2: Download and install Magisk Stable or Canary. Your choice, but I used Canary. https://github.com/topjohnwu/Magisk Step 3: You can use either patch the stock boot or use my...
forum.xda-developers.com

s_nieto said:
Can I root this device without a computer? I looked and can't find a twrp recovery file for this device sorry if I'm asking a stupid question Im new to this before I had an I phone I have the ne2215 unlocked version
Click to expand...
Click to collapse
You really don't need TWRP.
There's also a bunch of threads on rooting now.
Here's my one:
(Guide) Rooting, payload dumper, magisk_patched guides NE2213
Hi all, Thought i'd share a guide on how to get these boot images yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself Please read the process before...
forum.xda-developers.com
It's based on the EU device so the images held here are for the NE2213 but the processes are valid for any OnePlus device.
All in thread if you need help

s_nieto said:
Can I root this device without a computer? I looked and can't find a twrp recovery file for this device sorry if I'm asking a stupid question Im new to this before I had an I phone I have the ne2215 unlocked version
Click to expand...
Click to collapse
You really don't need TWRP.
There's also a bunch of threads on rooting now.
Here's my one:
(Guide) Rooting, payload dumper, magisk_patched guides NE2213
Hi all, Thought i'd share a guide on how to get these boot images yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself Please read the process before...
forum.xda-developers.com
It's based on the EU device so the images held here are for the NE2213 but the processes are valid for any OnePlus device.
All in thread if you need help

Your first step will be to quickly set up the phone so your ready to handle the bootloader. Get past all set up, it doesn't matter what you do as your wipe the device anyway.
Second is going about the tackling the bootloader (oem unlocking) Plenty of guides however please use below Make sure your sat on the home screen (unlocked)
Bootloader link bro
(Once you have done this leave the terminal open, you need this again.)
Afterwards, do a quick setup, nothing major to this as your be wiping again anyway
g96818 was kind enough to post a quide here : Rooting​
I will refer to his links shared from now however in such a way you can stay here.
Assuming bootloader unlocked, device setup, now download and install the apk :Magisk root
You will also want his stock boot file being this here : Boot.img
With magisk open go to 'install' and select the boot image to patch it. Once it is patched up, connect back to the PC and copy the file to the same folder as the bootloader/ADB files . (rename the file to "patched_boot")
*terminal used before*
\To Reboot to bootloader - this also checks connection indirectly ( Copy from here and right click in CMD/terminal to paste it in)
Code in terminal:
adb reboot bootloader
(after a minute for two)Followed by:
fastboot boot patched_boot.img
After, reboot the phone so it powers up, maybe takes a tad longer but it should actually be very quick. (This is known as a temporary boot)
Then simply, "Open Magisk and perform a direct install". Afterwards i personally would reset the phone and set it up again properly (accounts, email, porn ect). The files you need remain.
Once set up, just be sure to reactivate developer options (OEM will now remain unlocked however re-enable USB debugging (if you have any issues this will save you!!!!!!!)) you cannot perm brick this phone unless you miss this one critical step up.
Reinstall magisk (I found my phone kept it however i also have it naturally on my play account so i may have missed it installing) Just check its there, any concerns you can now just directly flash again with no need for the PC now. Otherwise use a root checker off the play store however just get magisk anyway.
I then updated to A12 from the settings update and afterwards just for peace of mind, i redid a direct install via magisk incase the boot.img differed. I booted up perfectly fine after my update but for peace of mind i would recommend it.

Related

How to install MAGISC without TWRP and locked bootloader?

Hi,
I used Magisc with several chinese brand phones and never had problems so far.
Now I got a new Moto Z, and I don't want to unlock the bootloader and install a custom recovery.
Is there another way to get Magisc working on my new device?
I understand the concept of systemless root and modification in general. The bootloader unlock and custom recovery installation do not fit in this concept, don't you think so?
Kind regards
Gesendet von meinem XT1650 mit Tapatalk
Not to hijack your thread, so consider this a free bump, but I am also curious. Galaxy S7 G920T here and looking for the same options.
JRapsky said:
Hi,
I used Magisc with several chinese brand phones and never had problems so far.
Now I got a new Moto Z, and I don't want to unlock the bootloader and install a custom recovery.
Is there another way to get Magisc working on my new device?
I understand the concept of systemless root and modification in general. The bootloader unlock and custom recovery installation do not fit in this concept, don't you think so?
Kind regards
Gesendet von meinem XT1650 mit Tapatalk
Click to expand...
Click to collapse
1 answer,,u can't..
Systemless mean that's it's doesn't messed with system partition so u can get the OTA update..
Or some app that detec change from system partition then refuse too work..
And to do that u need to flash TWRP and unlocked bootloader..
Sent from my Redmi 2 using Tapatalk
fake2die said:
1 answer,,u can't..
Systemless mean that's it's doesn't messed with system partition so u can get the OTA update..
Or some app that detec change from system partition then refuse too work..
And to do that u need to flash TWRP and unlocked bootloader..
Click to expand...
Click to collapse
Not completely accurate. Magisk modifies boot.img (boot partition) and to modify it, you need to have an unlocked bootloader.
veez21 said:
Not completely accurate. Magisk modifies boot.img (boot partition) and to modify it, you need to have an unlocked bootloader.
Click to expand...
Click to collapse
Right! So you can accomplish a Magisk install without a custom recovery for example using the Magisk Manager or Flashfire but as stated above, in order to boot a modified boot.img the bootloader needs to be unlocked or otherwise it will refuse to boot it.
There should be an option to install magisc like a systeme update with the stock recovery.
Gesendet von meinem XT1650 mit Tapatalk
JRapsky said:
There should be an option to install magisc like a systeme update with the stock recovery.
Click to expand...
Click to collapse
I don't think you understand how Android works, there are several stages to the system in which the actual /system rests. Basically everything is signed and validated to guarantee the installation of the official software and to protect the phone. Even if you can install Magisk via the stock recovery (which would require a phone specific Magisk which is the opposite of the universal interface that topjohnwu is targeting) you won't be able to boot the phone because the /boot partition is altered and the verity function won't allow an altered image to load in order to protect the phone. So in order to load the changes Magisk makes, the bootloader which checks and loads the boot.img (that's why it's called boot-loader) needs to be unlocked so it boots everything (the new boot.img needs to be compatible of course, you cannot boot the S8 img on the G6 for example). If I missed anything or something is wrong please correct me.
Sytis said:
I don't think you understand how Android works, there are several stages to the system in which the actual /system rests. Basically everything is signed and validated to guarantee the installation of the official software and to protect the phone. Even if you can install Magisk via the stock recovery (which would require a phone specific Magisk which is the opposite of the universal interface that topjohnwu is targeting) you won't be able to boot the phone because the /boot partition is altered and the verity function won't allow an altered image to load in order to protect the phone. So in order to load the changes Magisk makes, the bootloader which checks and loads the boot.img (that's why it's called boot-loader) needs to be unlocked so it boots everything (the new boot.img needs to be compatible of course, you cannot boot the S8 img on the G6 for example). If I missed anything or something is wrong please correct me.
Click to expand...
Click to collapse
but can we could not flash magisk file useing pc instead of custom recovery??(with unlock bootloder) if no then Y?
COOLPLAY6FAN said:
but can we could not flash magisk file useing pc instead of custom recovery??(with unlock bootloder) if no then Y?
Click to expand...
Click to collapse
Of course you can (with some possible limitations set by the OEM). With fastboot, for example. But you won't be using the recovery at all (stock or custom).
JRapsky said:
Hi,
I used Magisc with several chinese brand phones and never had problems so far.
Now I got a new Moto Z, and I don't want to unlock the bootloader and install a custom recovery.
Is there another way to get Magisc working on my new device?
I understand the concept of systemless root and modification in general. The bootloader unlock and custom recovery installation do not fit in this concept, don't you think so?
Kind regards
Gesendet von meinem XT1650 mit Tapatalk
Click to expand...
Click to collapse
Actually you can boot into twrp rather than install/flash twrp which means u must use cmd to boot twrp everytime for flashing something~ As for locked bootloader, just like others said, you must unlock it.
Didgeridoohan said:
Of course you can (with some possible limitations set by the OEM). With fastboot, for example. But you won't be using the recovery at all (stock or custom).
Click to expand...
Click to collapse
so can u gave proper guide to root useing magisc useing pc instead of custom recovery
(with unlock OEM)
Thanks in advance
COOLPLAY6FAN said:
so can u gave proper guide to root useing magisc useing pc instead of custom recovery
(with unlock OEM)
Thanks in advance
Click to expand...
Click to collapse
There are installation instructions on how to create the patched boot image with the Magisk Manager in the release thread.
When you have the patched_boot.img file, you'll need to flash it to your device. On most normal devices you can do this with fastboot. Check out your device's forums/DuckDuckGo/Google/Whatever-search-engine-you-use for instructions on that.
I'm also interested to install Magisk with as less impact as possible, so to summarize for newbies like myself:
* Unlocked bootloader is needed. Period.
* A custom recovery is needed to flash Magisk. TWRP for instance.
* That custom recovery prevent the built-in OTA update to work
* But TWRP can flash OTA updates that can be downloader from XDA for example
Am I correct?
Also,
* Magisk needs a patched boot image
* This image has no impact on the OTA process at all
* There are encryption matters to take care of (I don't understand them yet though).
Is everything correct?
Thanks.
Krystanos said:
I'm also interested to install Magisk with as less impact as possible, so to summarize for newbies like myself:
Click to expand...
Click to collapse
Let's see about answering those statements/questions.
* Unlocked bootloader is needed. Period.
Click to expand...
Click to collapse
Yes.
* A custom recovery is needed to flash Magisk. TWRP for instance.
Click to expand...
Click to collapse
Not necessarily. You can let the Magisk Manager patch your device's stock boot image and then flash it to your device with fastboot. See the installation instructions in the release thread.
* That custom recovery prevent the built-in OTA update to work
Click to expand...
Click to collapse
Yes.
* But TWRP can flash OTA updates that can be downloader from XDA for example
Click to expand...
Click to collapse
No. And yes. Official OTA files can (most of the time) not be flashed in TWRP. ROM zips and flashable firmware packages can.
* Magisk needs a patched boot image
Click to expand...
Click to collapse
Yes, that's all Magisk is about.
* This image has no impact on the OTA process at all
Click to expand...
Click to collapse
It definitely does. See the official docs
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips for more info on how to keep OTA capabilities for your device.
* There are encryption matters to take care of (I don't understand them yet though).
Click to expand...
Click to collapse
Possibly. Depends on what you're talking about.
Great answers. It's more clear for me now. Many thanks sir!
JRapsky said:
Hi,
I used Magisc with several chinese brand phones and never had problems so far.
Now I got a new Moto Z, and I don't want to unlock the bootloader and install a custom recovery.
Is there another way to get Magisc working on my new device?
I understand the concept of systemless root and modification in general. The bootloader unlock and custom recovery installation do not fit in this concept, don't you think so?
Kind regards
Gesendet von meinem XT1650 mit Tapatalk
Click to expand...
Click to collapse
Hi!
There are good news for you, rooting with magisk is very easy that way . No bootloader unlocking, custom recovery,
adb and fastboot command, no sdk no mtk tool . NOTHING but Sp flashtool - our best friend. This method really works with mtk phones android 5.0+ .
What U only need is
Sp flashtool and its drivers /scatter file with the ROM/ -I think not mtk devices with their own flashtool will work too
the ROM of your device
Magisc manager app on the phone
First of all you need clear up the device / after backup somewhere if needed/with sp flashtool - flash the whole ROM in format+download mode.
Install Magisc manager app , it will load for U a zip file in the map of the app
Put the boot img file of your rom in that map too
Run install option - it will create a patched boot img file within the app s map
Run again sp flashtool with download mode , mark only the boot section , and flash that patched boot img in phone
After reboot phone it is rooted
best regards
Forgive me and explain me something:
I read that "no custom recovery needed" and through the application it will create a patched boot img file.
I installed Magisk Manager 5.4.3, οpens and displays "not installed". I followed the steps that are described in the guide without anything being done.
One of the users they created patched recovery from the application menu in what order did they do it? 
 @Galaxtracker: you write "it will load for U a zip file in the map of the app" Where is the map of application ; I do not see any folder created ιn Android/Data or or somewhere else.
I have the Ulefone S8Pro with unlock bootloader (Android 7)
lefteriskmail said:
Forgive me and explain me something:
I read that "no custom recovery needed" and through the application it will create a patched boot img file.
I installed Magisk Manager 5.4.3, οpens and displays "not installed". I followed the steps that are described in the guide without anything being done.
One of the users they created patched recovery from the application menu in what order did they do it?
@Galaxtracker: you write "it will load for U a zip file in the map of the app" Where is the map of application ; I do not see any folder created ιn Android/Data or or somewhere else.
I have the Ulefone S8Pro with unlock bootloader (Android 7)
Click to expand...
Click to collapse
Install Magisk Manager.
Press install.
Select "Patch Boot Image File".
Select the stock boot image you've previously saved on your device.
Wait.
Flash the patched boot image to your device.
Done.
All of this is covered in the installation instructions...
The folder being mentioned above is MagiskManager on your internal storage (where the patched boot image is also stored).
Magisc
Hi!
Magisc works fine for me from the first time. Excuse me I won't do installation again to see how it goes. Really it causes some hesitation but in the end it's clear.
I use Total commander, and magisc folder is on the external SD card after installing magisc manager app. Factory reset later will not clear the root. After installing manager it says "not installed" till the end of the rooting process. Opening the app it begins to look after the downloadable zip file, you have to wait and download it. This zip and the stock boot img must be in the same place in a folder, and the app itself makes the patched boot img but I don't remember what was the name of the option. This is the flashable img file. In the end after flashing with flashtool and rebooting, magisc manager says "installed". Good luck
Hi, I am trying to centralise this sort of information and am compiling it in another topic for Magisk and android-based media centres too.
Trying to properly document things (full sentences with references, links, and examples) rather than just writing some brief summarised steps that most people will not understand - not just for myself but to share should it assist others learn and understand the preparation and steps involved, plus consequences and ramifications of their actions (which never seem to be stressed enough).
Here is what I have compiled. Hopefully it will help and prevent you going loopy!? :silly:
- - - - - - - - - - - - - - - - - - - -
*** EXTREMELY CLEAR MAGISK ROOT INSTRUCTIONS ***
(Work In Progress! To Be Verified & Critiqued By Others)​
Connect your WiFi so that all auxillary files can be downloaded during the rooting process.
Ensure you have a minimum of 2GB of free disk space. Allow for 1-2 hours to perform these steps. Do not rush!
Bootloaders come with every Android device, and give it all the instructions on how to boot and what to execute. If your Bootloader is locked, then you have not flashed anything like TWRP previously, or, you have re-flashed a stock Bootloader and Recovery, etc. The process is much easier when you have previously rooted the device using another method, and the Bootloader already unlocked.
To preserve your System partition, Magisk only modifies the unlocked Bootloader boot partition, which can easily* be restored and 'locked' later.
0. Before starting anything, always perform a FULL Backup (ADB) of your device, using a good quality USB cable and ADB FastBoot toolkit. Or on some devices you can use a Micro SD card with a TWRP recovery.img to boot into TWRP to perform a backup of partitions. Do both if you want! Make sure you search for the appropriate commands and usage of ADB FastBoot backup so that all data is backed up and included.
> ADB FastBoot: https://developer.android.com/studio/releases/platform-tools.html
> TWRP: https://dl.twrp.me/twrpapp/ \\ https://twrp.me/FAQ/
> Plus various other solutions...
1. Identify your device's firmware, build number, Bootloader, full unique model number, etc. Download any two of these apps:
a) AIDA64 ("System", "CPU" & "Android" tabs.)
b) Device Info HW ("General" & "System" tabs.)
c) DevCheck ("Hardware" & "System" tabs.)
2. Download the stock Bootloader, Recovery and Firmware (___.tar.md5) for your device model, variant and OS. (e.g. match your firmware, build number, bootloader, full unique module number, etc). Some sites will force you to pay to download - search around and you can get free download links, or sometimes from the manufacturer's site. From this firmware, we need to either extract or download the stock Bootloader.img image separately.
3. Install Magisk Manager v5.3-v5.6 as of 2017.02.22 ("Magisc" is typo by guy above).
4. Open Magisk and go to settings, adjust theme, change the language, enable notify for updates, change prompt timeout, etc.
5. On the home screen of the Magisk Manager app, click "Install" then in the pop-up select "Install" again.
a) If you have root access already, choose "Direct Method" - Select, wait, reboot and done (very easy!);
b) If you have stock recovery & locked bootloader, choose "Patch Boot Image File" - in the pop-up explorer, browse for the downloaded Bootloader Image.
c) ... I don't know about "Download ZIP Only" - I assume for flashing with Odin or ADB FastBoot from PC or existing root/unlocked user....?
NOTE: If you are being asked to browse and select a file, be aware that there is no confirmation! As soon as you click, that JPG or RAR archive will be used for patching (and result in an error if cannot be extracted!!!)
6. A file will likely be downloaded in the background (flashable ZIP), a black screen will pop-up processing etc. Wait.....
The processed Boot image will be processed and output to the /MagiskManager/ directory.
If you do NOT have root, or custom recovery, you will need to:
a) grab a PC, install the USB drivers for your device and confirm your device is fully recognised
b) then flash the "patched" Boot image from the Magisk Manager directory with ODIN for Windows or FastBoot on Windows via a good-quality USB cable.
7. ...
8. ...
I think that is it... I may have forgotten something. Please advise if something needs to be fixed or corrected. My Media Centre was already unlocked, so I did not have to unlock and flash the Bootloader.
9. Install free TWRP on your device, and choose to backup any partitions, should you wish to restore them later. Set an alarm to backup your device every few months! What are you prepared to lose if your device was lost/squashed/washed/crunched et al.???
Say thank you and donate to the amazing and all powerful Magisk developer 'TopJohnWu' and team!
Sweet! :fingers-crossed:

[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.

So has anyone figured out how to root the phone?

I've tried multiple rooting programs to try to root the phone, but none of them seem to work. So my question is, has anyone figured out a working method to get root? (I've unlocked the boot loader already)
TheRedPandaSSN said:
I've tried multiple rooting programs to try to root the phone, but none of them seem to work. So my question is, has anyone figured out a working method to get root? (I've unlocked the boot loader already)
Click to expand...
Click to collapse
I haven't been able to root it either. How'd u unlock the bootloader ?
greeneyez15o said:
I haven't been able to root it either. How'd u unlock the bootloader ?
Click to expand...
Click to collapse
If you go into developer options it allows you to unlock the bootloader.
TheRedPandaSSN said:
If you go into developer options it allows you to unlock the bootloader.
Click to expand...
Click to collapse
I don't think that completely unlocks the bootloader
TheRedPandaSSN said:
If you go into developer options it allows you to unlock the bootloader.
Click to expand...
Click to collapse
All that does is ALLOW the bootloader to be unlocked - it doesn't unlock it.
I just unlocked the bootloader
Used adb
"Fastboot flashing unlock"
Next im gonna try to apply root
Wish me luck
I have just ordered this phone. Will hopefully be able to share backup copies of ramdisk(boot) to be used with magisk to give root
Well if anyone is Interested in trying out mtk-su to get system-less, boot-less root it should work. It worked with my umidigi phone that also has mtk p70 soc. And running pie.
https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213
Here is device back up script project I had done based on that mtk-su.
https://github.com/mrmazakblu/Root-Backup-Helper
My test of using mtk-su did not work out.
But i do have backup copy of the stock boot.img , install magisk manager (currently i used V 7.3.4, after magisk update, V20 caused device trouble. Recommend stay with mahisk v19.3) and patch the boot.img from link below, then flash with "fastboot flash boot /file.name" to have full root.
here is stock boot file
https://androidfilehost.com/?fid=1899786940962604580
:::UPDATE::10-27
Successfully flashed magisk with twrp. But because the current twrp has no working touchscreen. It was done with ADB commands.
mrmazak said:
My test of using mtk-su did not work out.
But i do have backup copy of the stock boot.img , install magisk manager (use most recent version, currently i used V 7.3.4) and patch the boot.img from link below, then flash with "fastboot flash boot /file.name" to have full root.
here is stock boot file
https://androidfilehost.com/?fid=1899786940962604580
Click to expand...
Click to collapse
How'd u patch the boot.img ?
Thanks !!!
greeneyez15o said:
How'd u patch the boot.img ?
Thanks !!!
Click to expand...
Click to collapse
You can follow full guide found on magisk thread.
Here is general steps.
1. Install magisk manager app
2. Select install. Choose option to patch local file.
3. When complete, copy that patched_boot.img to PC
4. Fastboot flash boot patched_boot.img
I did not share the patched boot.img. you need to do this step on your own. Is better that way.
mrmazak said:
You can follow full guide found on magisk thread.
Here is general steps.
1. Install magisk manager app
2. Select install. Choose option to patch local file.
3. When complete, copy that patched_boot.img to PC
4. Fastboot flash boot patched_boot.img
I did not share the patched boot.img. you need to do this step on your own. Is better that way.
Click to expand...
Click to collapse
Sorry for the question, but wheres the option to patch local file?
---------- Post added at 01:25 PM ---------- Previous post was at 01:01 PM ----------
greeneyez15o said:
Sorry for the question, but wheres the option to patch local file?
Click to expand...
Click to collapse
I followed instructions, I keep getting error cannnot load 'patched_boot.img'
greeneyez15o said:
Sorry for the question, but wheres the option to patch local file?
---------- Post added at 01:25 PM ---------- Previous post was at 01:01 PM ----------
I followed instructions, I keep getting error cannnot load 'patched_boot.img'
Click to expand...
Click to collapse
I feel maybe I was too general in the steps. (not enough detail) sorry.
If you got to the part when it is loading patched_boot
then you got past the patching part.
so, you need to find the patched_boot.img . It should be in the download folder on device
copy this to your PC.
reboot phone to bootloader mode.
then open terminal in same window as the copied patched_boot.img file, or use the full path name in the command.
In the following example, the patched_boot.img file is saved in c:\adb
Code:
adb pull /sdcard/Download/patched_boot.img c:\adb\
adb reboot bootloader
fastboot flash boot c:\adb\patched_boot.img
fastboot reboot
mrmazak said:
I feel maybe I was too general in the steps. (not enough detail) sorry.
If you got to the part when it is loading patched_boot
then you got past the patching part.
so, you need to find the patched_boot.img . It should be in the download folder on device
copy this to your PC.
reboot phone to bootloader mode.
then open terminal in same window as the copied patched_boot.img file, or use the full path name in the command.
In the following example, the patched_boot.img file is saved in c:\adb
Click to expand...
Click to collapse
Got it !!! Had to reboot my computer ?
mrmazak said:
You can follow full guide found on magisk thread.
Here is general steps.
1. Install magisk manager app
2. Select install. Choose option to patch local file.
3. When complete, copy that patched_boot.img to PC
4. Fastboot flash boot patched_boot.img
I did not share the patched boot.img. you need to do this step on your own. Is better that way.
Click to expand...
Click to collapse
Does anyone manage to change the system file? when you try the phone freezes helps reboot
fafanakatr said:
Does anyone manage to change the system file? when you try the phone freezes helps reboot
Click to expand...
Click to collapse
Do you mean, flashing gsi image, or editing things on stock system. I have been focussed on tarp, and my tried either case.
I can do that soon and confirm if system is freeze.
OK, first time i tried to flash GSI here it is failed.
used fastboot flash system **gsi.img**
(phh v119)
it flashed without error, but will not go past bootloader splash screen. --ODD
will try again later
mrmazak said:
Do you mean, flashing gsi image, or editing things on stock system. I have been focussed on tarp, and my tried either case.
I can do that soon and confirm if system is freeze.
OK, first time i tried to flash GSI here it is failed.
used fastboot flash system **gsi.img**
(phh v119)
it flashed without error, but will not go past bootloader splash screen. --ODD
will try again later
Click to expand...
Click to collapse
I did everything according to the instructions that you suggested, and everything worked out for me, I got a root, but when I try to change the system files, the phone freezes, maybe the root is not full? Thanks for your work)
fafanakatr said:
I did everything according to the instructions that you suggested, and everything worked out for me, I got a root, but when I try to change the system files, the phone freezes, maybe the root is not full? Thanks for your work)
Click to expand...
Click to collapse
Well all depends on what system files you have changed.
I was able to delete the system private-app file "blu-ignite" (an unauthorized app installed program) without freezing system.
I was on magisk 19.3. when I try to update to magisk v20 then I have issues. Freezes, wifi not turn on, ect. So try to restore stock, and Will have to use custom update Chanel with magisk to force it to use the older version.
I am also trying to see if twrp can be used tethered, to install magisk. By using "adb shell twrp sideload" command. And sideloading the magisk file.
If, when I see it works I can write the the whole process.
mrmazak said:
Well all depends on what system files you have changed.
I was able to delete the system private-app file "blu-ignite" (an unauthorized app installed program) without freezing system.
I was on magisk 19.3. when I try to update to magisk v20 then I have issues. Freezes, wifi not turn on, ect. So try to restore stock, and Will have to use custom update Chanel with magisk to force it to use the older version.
I am also trying to see if twrp can be used tethered, to install magisk. By using "adb shell twrp sideload" command. And sideloading the magisk file.
If, when I see it works I can write the the whole process.
Click to expand...
Click to collapse
I will try to do as you suggested and let you know) I will be well waiting for your success
mrmazak said:
Well all depends on what system files you have changed.
I was able to delete the system private-app file "blu-ignite" (an unauthorized app installed program) without freezing system.
I was on magisk 19.3. when I try to update to magisk v20 then I have issues. Freezes, wifi not turn on, ect. So try to restore stock, and Will have to use custom update Chanel with magisk to force it to use the older version.
I am also trying to see if twrp can be used tethered, to install magisk. By using "adb shell twrp sideload" command. And sideloading the magisk file.
If, when I see it works I can write the the whole process.
Click to expand...
Click to collapse
thank you very much I did everything according to the instructions and everything worked out for me,I tried to turn on the camera2api but so far without success,
can you understand this?

THE root method. (any android version. yes 10 stable)

Alot of people still dont seem to understand or know how to root their devices and the help ppl find online can be misleading and sketchy. I just want to share this easy method to hopefully save some ppl from trying to do this or that and having bad results. This IS the common sense duh way to root. Use magisk to root it. Long as you got adb and fastboot on ur pc and the phone's bootloader is unlocked you can root like this...
1)download the magisk manager.
2)get the ota .zip file for the android version you are running.
3)get payload-dumperwin64.zip and unzip it.
4)unzip the ota.
5)put the payload.bin file from the ota into the input folder for payload dumper.
6)run payload dumper.
7)get the boot.img from the output folder of the payload dumper.
8)copy the boot.img to your phone.
9)open magisk manager.
10)press install, then install, then 'select and patch a file'.
11)select the boot.img
12)once the boot.img is patched it will be renamed magisk_patched.img, copy the magisk_patched.img to your computer.
13)start your phone in fastboot mode
14)on your computer open a command prompt and type 'fastboot flash boot (and the magisk_patched.img file location)'
15)once successful type 'fastboot reboot'
ROoT! Super easy right? And yes, it works with 10 stable. Just make sure to use magisk manager 20.1.
As far as twrp goes, you can try flashing it with magisk if you like, but I can't say whether or not it will work on 10 because I didnt bother. Twrp hasnt been very helpful to me on my 6T.
I know to a lot of us this is pretty common sense, but it looks like there are still a lot of ppl needing help getting rooted on 10 stable for some reason... Thats why I posted this. Don't hate. Help.
<Mod edit>
To install TWRP,
download - android Q twrp img and the installer zip. Place the TWRP installer zip in your phone storage.
download magisk installer zip into your phone storage.
1. boot in fastboot, open command line in your PC.
2. flash twrp img - fastboot flash boot <your twrp>.img. You lose root and custom kernel here.
(fastboot boot <your twrp>.img for android 9.)
3. Reboot to recovery from phone's fastboot menu
4. install the <TWRP installer>.zip file in TWRP.
5. Reboot TWRP to flash magisk.
6. Flash <magisk installer>.zip in TWRP
7. Reboot system. Exit your command line on PC.
The end.
Can't we just flash Magisk on TWRP?
yot2703 said:
Can't we just flash Magisk on TWRP?
Click to expand...
Click to collapse
Yea, but you tend to lose twrp upgrading to 10. I've seen ppl report having problems when they try the twrp q img. This way, there is no need for twrp. But if you successfully got twrp workin w/ 10, by all means go that route. I decided not to bother with twrp for now after one of my backups failed to be recoverable. The last straw. Lol.
e5p10nage said:
Yea, but you tend to lose twrp upgrading to 10. I've seen ppl report having problems when they try the twrp q img. This way, there is no need for twrp. But if you successfully got twrp workin w/ 10, by all means go that route. I decided not to bother with twrp for now after one of my backups failed to be recoverable. The last straw. Lol.
Click to expand...
Click to collapse
Seeing as how I haven't made a reliable backup in TWRP/custom recoveries in like two years, I appreciate this route. Swift Backup and frequent OTG backups are enough for me, I just want root.
There is a new version of twrp, build .27 that is meant to fix backup / restore issues
Striatum_bdr said:
There is a new version of twrp, build .27 that is meant to fix backup / restore issues
Click to expand...
Click to collapse
Gud to know. Does 'fastboot boot twrp.img' work with android 10 now with .27? Cuz it wasn't lettin me do it after the updgrade.
e5p10nage said:
Gud to know. Does 'fastboot boot twrp.img' work with android 10 now with .27? Cuz it wasn't lettin me do it after the updgrade.
Click to expand...
Click to collapse
No it doesn't work at all forever. Fastboot is modified in 10 you must write 'fastboot flash boot file.img'
Is losing WiFi one of the bugs on Q? I had WiFi, but it won't stay on after I used this to root.
Doesn't work. Made image with latest Magisk Manager. I suspect it might be existing Magisk modules that make my phone boot loop, but without root and TWRP I can't get rid of them without a factory reset, which is what is recommended in the first place when using this method on A10. So this does not work.
UberFiend said:
Is losing WiFi one of the bugs on Q? I had WiFi, but it won't stay on after I used this to root.
Click to expand...
Click to collapse
I have heard of that being a bug with Q. Just look it up on google. Lots of pixel owners havin that same issue. I didnt have this problem, so I am not sure what caused it or how to fix it. You FOR SURE used the boot.img from the ota you currently have installed? Anyway, I think I saw someone say something about the throttling in the developer settings.. IDK if that really has anything to do with it though.. Im sorry that happened though.
greentag said:
Doesn't work. Made image with latest Magisk Manager. I suspect it might be existing Magisk modules that make my phone boot loop, but without root and TWRP I can't get rid of them without a factory reset, which is what is recommended in the first place when using this method on A10. So this does not work.
Click to expand...
Click to collapse
If you dont have root how or why do you have modules? This wasnt meant for upgrading.. This is meant for AFTER you have upgraded. Im not sure I understand what you are saying. Oh, and make sure to use the same ota you upgraded with btw.
e5p10nage said:
If you dont have root how or why do you have modules? This wasnt meant for upgrading.. This is meant for AFTER you have upgraded. Im not sure I understand what you are saying. Oh, and make sure to use the same ota you upgraded with btw.
Click to expand...
Click to collapse
I upgraded from 9.17 to 10. I lost root and ability to flash Magisk, as I am not willing to factory reset, currently. When I was on 9, I had TWRP and root along with Magisk Modules. Just because you flash a stock boot image, doesn't mean that the folder Magisk modules are stored in doesn't exist. So when I upgraded, I had all those modules still stored.
When you try to patch and flash the stock boot image on 10, you're going to see allot of people complaining about boot loops. The current method to gain TWRP and root on 10 require you to factory reset, and my assumption is that it clears Magisk modules out. So if you use the method you posted, you're going to get boot loops, unless you factory reset beforehand. I tried the method posted before you made a post about it, and it is the same as now, boot loops, and being forced to flash stock 10 boot image.
greentag said:
I upgraded from 9.17 to 10. I lost root and ability to flash Magisk, as I am not willing to factory reset, currently. When I was on 9, I had TWRP and root along with Magisk Modules. Just because you flash a stock boot image, doesn't mean that the folder Magisk modules are stored in doesn't exist. So when I upgraded, I had all those modules still stored.
When you try to patch and flash the stock boot image on 10, you're going to see allot of people complaining about boot loops. The current method to gain TWRP and root on 10 require you to factory reset, and my assumption is that it clears Magisk modules out. So if you use the method you posted, you're going to get boot loops, unless you factory reset beforehand. I tried the method posted before you made a post about it, and it is the same as now, boot loops, and being forced to flash stock 10 boot image.
Click to expand...
Click to collapse
This method I am talking about.. Should only be done after already successfully upgrading. Not as a method OF upgrading. What I mean is.. If youre tryin to do this on 10.. Then you need to upgrade to ten via the system update local upgrade method.. THEN patch the boot.img from the SAME exact ota.zip you used to local upgrade. If youre on 9.0.17 and you patch and flash a boot.img for 10, I would expect a boot loop. Maybe I am misunderstanding you.. IDK But for me, I HAD to factory reset to upgrade to 10. Im not sure why. I local upgraded with the ota, then my phone wouldnt boot up except into recovery mode. I hit factory reset, and it booted up fine. A couple days later I used the same ota to patch a boot.img and I fastboot flashed it, and it was smooth as butter. Root, no need to reset, no loss of data, no wifi issue... I am not sure what it is that is going wrong for some of you, but I wanna make sure you understand, this is not a way to keep root through the upgrade.. This is just a way to root without having twrp AFTER the upgrade. Or am I completely not getting what youre saying?
Tl;dr: this is not THE root method IMHO.
I would advise everyone to stay away from this payload-dumperwin64.zip as it produces following Virustotal results (7 detections). Even if they are false positives, it's a needlessly complex method considering the alternatives out there. In comparison, Magisk is 100% clean while that is essentially one major hack. Let's not forget that the recent update of this TWRP recovery has tackled the decryption issue and grants us back all access to system manipulation and troubleshooting root problems. If you ask me, that still is the root method.
Wrapped with delicious Fajita [emoji896]
Timmmmaaahh said:
Tl;dr: this is notTHE root method IMHO.
I would advise everyone to stay away from this payload-dumperwin64.zip as it produces following Virustotal results (7 detections). Even if they are false positives, it's a needlessly complex method considering the alternatives out there. In comparison, Magisk is 100% clean while that is essentially one major hack. Let's not forget that the recent update of this TWRP recovery has tackled the decryption issue and grants us back all access to system manipulation and troubleshooting root problems. If you ask me, that still is the root method.
Wrapped with delicious Fajita [emoji896]
Click to expand...
Click to collapse
Not everyone wants to have to deal with twrp. Especially after being screwed over by it before the new .27 or whatever. Also, it doesnt have to be that specific payload dumper. Any payload dumper you decide to use is fine. Thats just the one I used. And actually I went and looked and found these instructions from the magisk gitHub:
https://github.com/topjohnwu/Magisk/blob/master/docs/install.md#boot-image-patching
e5p10nage said:
Not everyone wants to have to deal with twrp. Especially after being screwed over by it before the new .27 or whatever. Also, it doesnt have to be that specific payload dumper. Any payload dumper you decide to use is fine. Thats just the one I used. And actually I went and looked and found these instructions from the magisk gitHub:
https://github.com/topjohnwu/Magisk/blob/master/docs/install.md#boot-image-patching
Click to expand...
Click to collapse
Heres what it says:
"Boot Image Patching
You would want to choose this method if either your device does not have custom recoveries, your device is A/B and you don't want to mix recovery and boot images, or your device is using system-as-root without A/B partitions.
To use this method, you are required to obtain a copy of the stock boot/recovery image, which can be found by extracting OEM provided factory images or extracting from OTA update zips. If you are unable to obtain one yourself, you might be able to find it somewhere on the internet."
e5p10nage said:
Heres what it says:
"Boot Image Patching
You would want to choose this method if either your device does not have custom recoveries, your device is A/B and you don't want to mix recovery and boot images, or your device is using system-as-root without A/B partitions.
To use this method, you are required to obtain a copy of the stock boot/recovery image, which can be found by extracting OEM provided factory images or extracting from OTA update zips. If you are unable to obtain one yourself, you might be able to find it somewhere on the internet."
Click to expand...
Click to collapse
The payload dumper thing I was talking about is a method of obtaining the boot.img from the ota on your own instead of looking for one on the web. Doesnt matter what payload dumper you use, that was just the one I found. Hopefully this makes it a lil more clear.
e5p10nage said:
This method I am talking about.. Should only be done after already successfully upgrading. Not as a method OF upgrading. What I mean is.. If youre tryin to do this on 10.. Then you need to upgrade to ten via the system update local upgrade method.. THEN patch the boot.img from the SAME exact ota.zip you used to local upgrade. If youre on 9.0.17 and you patch and flash a boot.img for 10, I would expect a boot loop. Maybe I am misunderstanding you.. IDK But for me, I HAD to factory reset to upgrade to 10. Im not sure why. I local upgraded with the ota, then my phone wouldnt boot up except into recovery mode. I hit factory reset, and it booted up fine. A couple days later I used the same ota to patch a boot.img and I fastboot flashed it, and it was smooth as butter. Root, no need to reset, no loss of data, no wifi issue... I am not sure what it is that is going wrong for some of you, but I wanna make sure you understand, this is not a way to keep root through the upgrade.. This is just a way to root without having twrp AFTER the upgrade. Or am I completely not getting what youre saying?
Click to expand...
Click to collapse
I said I upgraded. It's literally the first thing I said.
I upgraded the same way everyone else did. Using Oxygen Updater from the Playstore, then local upgrade. I did not factory reset, however, like you did.
The method you posted only works if you factory reset after the OS 10 upgrade.
There's already a method to upgrade and keep data, while also keeping TWRP and root, but there are a number of hoops to jump through.
greentag said:
I said I upgraded. It's literally the first thing I said.
I upgraded the same way everyone else did. Using Oxygen Updater from the Playstore, then local upgrade. I did not factory reset, however, like you did.
The method you posted only works if you factory reset after the OS 10 upgrade.
There's already a method to upgrade and keep data, while also keeping TWRP and root, but there are a number of hoops to jump through.
Click to expand...
Click to collapse
I see. Well I am glad you pointed this out cuz I wasnt aware of the need to factory reset. The only reason I did is because after the local upgrade my phone wouldnt boot to anything but recovery UNLESS I reset it. So I didnt have an option not to really. I was rooted with twrp on 9.0.17, got the ota from oxy updater, local updated, just like ya said you did. Not sure why it wouldnt boot after that without the reset. Im not entirely sure that it is 100% needed to factory reset to root this way though. Ive talked to other people who tried this and said they had no problem. Then Ive also talked to other people who have. I feel like there are some variables we arent considering at work here. But thank you for pointing this out. The only goal I have here is to be helpful, so all problems with this method also need to be part of the conversation. So I appreciate it.

[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!

Categories

Resources