Database Info

How to Root J7 Prime (G610F) on Nougat?!

Hello Guys,
Updated my J7 Prime to Nougat today. Is there anyway to Root this device on Nougat?! Please replay.
Thank You.

vishnurmcf said:
Hello Guys,
Updated my J7 Prime to Nougat today. Is there anyway to Root this device on Nougat?! Please replay.
Thank You.
Click to expand...
Click to collapse
Not yet. Better wait for a couple of updates from Samsung & then try to root. I would recommend Magisk for rooting.

anubhab723 said:
Not yet. Better wait for a couple of updates from Samsung & then try to root. I would recommend Magisk for rooting.
Click to expand...
Click to collapse
man i need a working root i... tried by twrp by install the root latest version so now i am flashing a stock firmware hhhhhh ....will magist work 100 percent ?? i need the full confidence answer thanks a lot

lI also just updated, I tried using CF Auto Root but that didn't work and made my phone bricked (verification failed). Will Magisk work certainly because I don't want to have to reset again.

Get your device back to a fully stock state and then start fresh by installing TWRP. Next, I would suggest making a backup of your stock ROM in TWRP just in case something goes wrong and you need to restore your boot image. Then, I would attempt to root your device with an older version of Magisk, like V12.0, and see what happens. If you have root, great, if not, restore your stock boot image and flash the next newest version of Magisk. That would be my starting point. Good luck and happy flashing!
Sent from my SM-G955U using XDA-Developers Legacy app

fast69mopar said:
Get your device back to a fully stock state and then start fresh by installing TWRP. Next, I would suggest making a backup of your stock ROM in TWRP just in case something goes wrong and you need to restore your boot image. Then, I would attempt to root your device with an older version of Magisk, like V12.0, and see what happens. If you have root, great, if not, restore your stock boot image and flash the next newest version of Magisk. That would be my starting point. Good luck and happy flashing!
Click to expand...
Click to collapse
Will try that. Thanks!

wsty said:
Will try that. Thanks!
Click to expand...
Click to collapse
Sounds good. Let us know how it works out if you run into any trouble no hesitate to ask

fast69mopar said:
Sounds good. Let us know how it works out if you run into any trouble no hesitate to ask
Click to expand...
Click to collapse
I have some questions.
1. Do you need the specific Magisk file for your device or does Magisk work for all devices regardless of the variant?
2. Do you know where to get Magisk 12.0?

wsty said:
I have some questions.
1. Do you need the specific Magisk file for your device or does Magisk work for all devices regardless of the variant?
2. Do you know where to get Magisk 12.0?
Click to expand...
Click to collapse
Magisk works on almost all variants. The will need to flash the Magisk zip and then install the Magisk Manager apk.
Here is the link to the Magisk main thread. If you scroll down the the bottom of the OP, you will see the download link for the Magisk zip files. Also the Magisk Manager apk's are available in this thread too. If you need any help just ask.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Before you flash any root zip in TWRP, make a backup of your stock boot image. That was ifsomething goes wrong you can revert back and try again with a different version if Magisk.
Make sure you read the info that @topjonwu has made available for us for Magisk. The link below is full of information pertaining to Magisk.
There is one other thing that I forgot to put here. Magisk is a pretty universal root solution that patches the boot image just like Chainfire's SuperSU. There is not a device specific Magisk zip so you can flash any version if Magisk to attempt to gain root access in your device. Like I said before, I would start with flashing V12.0 and start from there. If V12.0 works and you have root, boot to TWRP and make a backup of your boot image to save it. That was if you flash, for instance, V13.0 and it doesn't work or fails to flash then you can boot back to recovery and restore your boot image and have working root.

fast69mopar said:
Magisk works on almost all variants. The will need to flash the Magisk zip and then install the Magisk Manager apk.
Here is the link to the Magisk main thread. If you scroll down the the bottom of the OP, you will see the download link for the Magisk zip files. Also the Magisk Manager apk's are available in this thread too. If you need any help just ask.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Thanks!

wsty said:
Thanks!
Click to expand...
Click to collapse
No problem

Any working Twrp for this?

Yes, I am having the same problem. I tried two different ROOT files, but it did not work.
What is Magisk? Someone can explain ...

denizbay said:
Yes, I am having the same problem. I tried two different ROOT files, but it did not work.
What is Magisk? Someone can explain ...
Click to expand...
Click to collapse
Magisk can hide knox counter... using working twrp for Nougat... format data.. install magisk v14 & done. The only problem now, twrp cant read external storage, so cant flash anything thru sdcard, need to use OTG instead.
Sent from my SM-A910F using XDA-Developers Legacy app

Looking this: https://forum.xda-developers.com/ga...ared-root-file-j7-prime-g610f-nougat-t3678253

inamie said:
Magisk can hide knox counter... using working twrp for Nougat... format data.. install magisk v14 & done. The only problem now, twrp cant read external storage, so cant flash anything thru sdcard, need to use OTG instead.
Sent from my SM-A910F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Downloaded the TWRP from somewhere and follow the above step. Succesfully rooted my device..
Sent from my SM-A910F using XDA-Developers Legacy app

inamie said:
Downloaded the TWRP from somewhere and follow the above step. Succesfully rooted my device..
Sent from my SM-A910F using XDA-Developers Legacy app
Click to expand...
Click to collapse
What Magisk version, Version 14 tripped the verification error on my 610M

Try Magisk v14.0
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-sys

FINALLY !! I've rooted my J7 Prime on Nougat. Will post a thread on it very soon.

vishnurmcf said:
FINALLY !! I've rooted my J7 Prime on Nougat. Will post a thread on it very soon.
Click to expand...
Click to collapse
Looking forward to your instructions. Please release soon! Thank you!

【HELP!】Installed a module in Magisk Download manager and now i'm f*****

Sup guys, i had this problem with the SafetyNet Check that always kept failing, done some tutorials here at the forum but none of them worked, so i gave up... yesterday i was searching for some modules at the download page in the Magisk Manager app and found a module that was supposed to correct SafatyNet problema, after that installation my Magisk don't want to open anymore, all my modules still installed but i can't open the app anymore, i rooted my cellphone without TWRP so i can't use it to manage the dependencies of the app... any suggestion?
obs.: I'm not using TWRP cuz i just keep having a problem at the installation, i'm runnig the last version of the Android Pie OS (Beta 3)

You could temporarily boot into TWRP via ADB and a PC and flash the uninstaller.

DiGtal said:
You could temporarily boot into TWRP via ADB and a PC and flash the uninstaller.
Click to expand...
Click to collapse
He can boot it through fastboot, adb push the uninstaller and flash it.*
But isn't the safetynet fix just a build.prop tweak?
He can technically adb pull the build.prop, fix it and put it back in. Or just take a working build.prop from a fellow OB3 user ( me included ) and push it into the system through adb.

The Marionette said:
He can boot it through fastboot, adb push the uninstaller and flash it.*
But isn't the safetynet fix just a build.prop tweak?
He can technically adb pull the build.prop, fix it and put it back in. Or just take a working build.prop from a fellow OB3 user ( me included ) and push it into the system through adb.
Click to expand...
Click to collapse
I think the OP mentioned the problem they are having is from a Magisk module that is incompatible with the OP6. My recommendation, without TWRP on the phone, might be a Fastboot Rom to get your phone functional again.

tabletalker7 said:
I think the OP mentioned the problem they are having is from a Magisk module that is incompatible with the OP6. My recommendation, without TWRP on the phone, might be a Fastboot Rom to get your phone functional again.
Click to expand...
Click to collapse
I know that and the OP probably does too, but I guess they don't want to lose their current data?

The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
I don't know if that can be helped at this point. That bad Magisk module may have made that decision for him

The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
That's right, i know that i can fix this issue just installing the ROM again but i don't want to lose my data, i just want to delete a specific module from Magisk

s3nn4 said:
That's right, i know that i can fix this issue just installing the ROM again but i don't want to lose my data, i just want to delete a specific module from Magisk
Click to expand...
Click to collapse
restore stock boot.img. no root, no mods to load. fix it then reroot.

You don't need to restore. Follow this guide: https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366
It's called CoreOnlyMode4Magisk and it's flashed through TWRP. Magisk modules are systemless and this module will fix your problem.

mdl054 said:
You don't need to restore. Follow this guide: https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366
It's called CoreOnlyMode4Magisk and it's flashed through TWRP. Magisk modules are systemless and this module will fix your problem.
Click to expand...
Click to collapse
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3

MrSteelX said:
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3
Click to expand...
Click to collapse
Oh sorry I missed that part

You can use the modified boot.img with TWRP preinstalled from the OB3 thread:
https://forum.xda-developers.com/showpost.php?p=77390204&postcount=2

Just reflash OB3 from system updater and that will get rid of root and also keep your data. Then start over.
Sent from my OnePlus6 using XDA Labs

The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
MrSteelX said:
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3
Click to expand...
Click to collapse
Already fixed it, installed the last version of blu spark TWRP along with the Magisk 17.2, all perfect, had a problem with my OS at the beginning but just flashed again and did all the process to root, thanks for your help!

Next time don't be a twrp and use twrp

dgunn said:
Next time don't be a twrp and use twrp
Click to expand...
Click to collapse
The last update wouldn't let me install it, the Blu stuff made my day when I saw the compatible update

/Vendor won't unmount in recovery

Hi guys,
Just looking for some information, or maybe we could get a successful discussion on this matter to help others who might come across this issue.
I was getting a bootloop after flashing the latest Dolby Atmos build via Magisk Manager. I'm on Magisk 17.1
I could successfully reach recovery and I could successfully restore /system, /data and /boot from an earlier back up. But I couldn't restore /vendor, because TWRP could not unmount it.
I know that this is fixable via RUU (which is what I did in the end), though i'd like to understand what is happening and how to fix it without RUU (if it is even possible at all).
As mentioned in other posts, uninstalling Magisk is impossible without /Vendor being unmounted.
Any help and information is appreciated. I'll continue investigating to see if there's any further info for me to find.

Kyuubi10 said:
As mentioned in other posts, uninstalling Magisk is impossible without /Vendor being unmounted.
Click to expand...
Click to collapse
That's simply wrong. You should have installed Magisk using the Magisk Manager and a stock boot image in your internal SD card, by using the patch boot image method in Magisk Manager and flash it afterwards. Thus uninstalling Magisk would simply be to flash an unpatched stock boot image.
Sent from my HTC U12+ using XDA Labs

5m4r7ph0n36uru said:
That's simply wrong. You should have installed Magisk using the Magisk Manager and a stock boot image in your internal SD card, by using the patch boot image method in Magisk Manager and flash it afterwards. Thus uninstalling Magisk would simply be to flash an unpatched stock boot image.
Click to expand...
Click to collapse
No, that isn't an "uninstall"... What you described is an overwrite.
Flashing RUU does the exact same thing.
I'm talking about flashing the magisk uninstaller zip. - that is a true uninstall.
Maybe were getting semantics wrong, should we start defining the meaning of "uninstall" from now on?

Kyuubi10 said:
No, that isn't an "uninstall"... What you described is an overwrite.
Flashing RUU does the exact same thing.
I'm talking about flashing the magisk uninstaller zip. - that is a true uninstall.
Maybe were getting semantics wrong, should we start defining the meaning of "uninstall" from now on?
Click to expand...
Click to collapse
Man I'm not stupid and know exactly that it's "just" an overwrite.
But if you used the patch boot image method in Magisk Manager, and flashed the patched boot to "install" Magisk, you could uninstall all modules in Magisk Mananger and afterwards flash the stock boot and you'll be done uninstalling Magisk anyway. In this very case the uninstaller isn't needed at all.
Learn about the different ways on how to install and uninstall Magisk and you'll see that I'm right, as I clearly defined the installation method as well. Maybe you still didn't understand the different ways of how to install and uninstall Magisk.
If you flashed Magisk through TWRP yeah you're done and may have to flash a RUU. But anyone who read up on
this very topic and knew all basics of how Magisk and rooting on Treble A/B devices currently works would have known that one prior to rooting as well. It's stated in a lot of threads and happens on other devices as well, that Magisk isn't allowed to mount and alter vendor.
Sent from my HTC U12+ using XDA Labs

5m4r7ph0n36uru said:
Man I'm not stupid and know exactly that it's "just" an overwrite.
But if you used the patch boot image method in Magisk Manager, and flashed the patched boot to "install" Magisk, you could uninstall all modules in Magisk Mananger and afterwards flash the stock boot and you'll be done uninstalling Magisk anyway. In this very case the uninstaller isn't needed at all.
Learn about the different ways on how to install and uninstall Magisk and you'll see that I'm right, as I clearly defined the installation method as well. Maybe you still didn't understand the different ways of how to install and uninstall Magisk.
If you flashed Magisk through TWRP yeah you're done and may have to flash a RUU. But anyone who read up on
this very topic and knew all basics of how Magisk and rooting on Treble A/B devices currently works would have known that one prior to rooting as well. It's stated in a lot of threads and happens on other devices as well, that Magisk isn't allowed to mount and alter vendor.
Click to expand...
Click to collapse
Brilliant! You should have started with this.
I'm looking for knowledge and information.
To be given a solution which I'm already aware of is useless to me. This thread was my way of asking for information... And telling me "i'm simply wrong" and then using wrong semantics for your explanation is a sure fire way of getting someone to call you stupid (though I never said it, and you simply implied it. Very good victim complex there).
In my daily job semantics are VERY important... So I absolutely WILL point out words used in the wrong context when I come across them.
It's just what I'm used to.
So next time choose your words very carefully not to confuse myself or others who come across this post.
Uninstall is a script designed to "uninstall" something... If I overwrite the entire partition manually, then it's not an uninstall.
Now that we have that out of the way, lets move on to building information that the community can make use of.
1. Magisk no longer can mess with a vendor partition. (Is this truly across the board? On all A/B devices? Can you post threads with more information please?)
2. You advise that the best way to install Magisk on A/B devices is via flashing patched boot... This is very interesting.
3. From your signature I noticed you've got different set ups in your A/B partitions.
I like that, do you have a guide where I can learn more?

5m4r7ph0n36uru said:
Man I'm not stupid and know exactly that it's "just" an overwrite.
But if you used the patch boot image method in Magisk Manager, and flashed the patched boot to "install" Magisk, you could uninstall all modules in Magisk Mananger and afterwards flash the stock boot and you'll be done uninstalling Magisk anyway. In this very case the uninstaller isn't needed at all.
Learn about the different ways on how to install and uninstall Magisk and you'll see that I'm right, as I clearly defined the installation method as well. Maybe you still didn't understand the different ways of how to install and uninstall Magisk.
If you flashed Magisk through TWRP yeah you're done and may have to flash a RUU. But anyone who read up on
this very topic and knew all basics of how Magisk and rooting on Treble A/B devices currently works would have known that one prior to rooting as well. It's stated in a lot of threads and happens on other devices as well, that Magisk isn't allowed to mount and alter vendor.
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
Also additionally, why can't TWRP mount/unmount Vendor?
Is that something that's already been discussed prior as well?
because that's the bigger problem I had.

Hi,
It would be nice to find how to format the partition 'vendor' and reinstall via TWRP? it's a problem for a complete custom rom that includes the 'vendor' part!
PS: With Super-R kitchen 'vendor' does not flash !!

Alan-B said:
Hi,
It would be nice to find how to format the partition 'vendor' and reinstall via TWRP? it's a problem for a complete custom rom that includes the 'vendor' part!
PS: With Super-R kitchen 'vendor' does not flash !!
Click to expand...
Click to collapse
As far as I've experienced after a fresh RUU i can flash vendor.
But not after the first boot.

OP6 after FULLROM Flash i lost the TWRP-Recovery

Hello Android community ....
I have a problem with my rooted OP6.
I always use my devices with root but since model OP6 I'm too stupid for that or have not found any suitable instructions?
I root and install the TWRP on the OP6
then I install the original FULLROM followed by the current and matching MAGISK to get root
and it boots perfectly including root and everything is great!
but the TWRP is always gone ...
that makes me totally crazy
What am I doing wrong or what can/must do differently so that the TWRP recovery stays on for the next time?
Does anyone have a tip for me?
Many Thanks
VG
Z.

This is how you do it from twrp.
Flash rom (DON'T REBOOT)
Flash twrp (now reboot to recovery)
Flash magisk and boot = done.
Full roms will write over partitions.

whizeguy said:
This is how you do it from twrp.
Flash rom (DON'T REBOOT)
Flash twrp (now reboot to recovery)
Flash magisk and boot = done.
Full roms will write over partitions.
Click to expand...
Click to collapse
Thanks - maybe this also helps to resolve one of my confusions: will this now also work with Standard (not BluSpark) TWRP and Android Pie - there's all kinds of mixed statements online. Best

CoffeeMachineSwitch said:
Thanks - maybe this also helps to resolve one of my confusions: will this now also work with Standard (not BluSpark) TWRP and Android Pie - there's all kinds of mixed statements online. Best
Click to expand...
Click to collapse
I always use blu-spark. Always work

whizeguy said:
I always use blu-spark. Always work
Click to expand...
Click to collapse
thanks - but isn't that another source of complexity and error, as another party (bluSpark developer) is involved on top of TWRP team? And Magisk. Seems like many cooks throwing in ingredients to root, while the Android system itself keeps updating and changing....

People need to learn to READ

Best/most efficient root method OP7P

I am running 10.05, I can't decide whether to install twrp, dd root, or magdisk. Given that I have the most current version of oxygen os, what would be the best way to root my phone?
Don't misinterpret my ignorance for lazyness, a majority of guides I've seen aren't recent and don't go over pros & cons of the method.
Thank you, I'm willing to donate for help.

Edit: I'm stupid, I was in wrong forum. Please ignore this post and what I've said!

You only need a patched image if you don't want to install TWRP. If you install TWRP, I'd simply ADB sideload Magisk to get root.
That's what I've done and it works just fine.
This assumes that you're using a OnePlus 7 Pro, and not a 7T Pro. Not got a 7T, so can't comment on that.
Sent from my GM1913 using Tapatalk

Bagpuss said:
You only need a patched image if you don't want to install TWRP. If you install TWRP, I'd simply ADB sideload Magisk to get root.
That's what I've done and it works just fine.
This assumes that you're using a OnePlus 7 Pro, and not a 7T Pro. Not got a 7T, so can't comment on that.
Click to expand...
Click to collapse
Edit: I'm stupid, I was in wrong forum. Please ignore this post and what I've said!

Lossyx said:
TWRP doesn't work on devices launched with Android 10, which has been discussed many times.
My reply above stands true, a patched boot image is the only way as for right now.
(And we're on a 7T Pro forum)
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Are you positive? I see TWRP install guides everywhere. From what I've read TWRP with magdisk (not SuperSU, us it's not open source) is the best way to root with the most flexibility. What if I'm running 10.03.0GM21AA, and there is no patched image? Do I need to roll back?

Lossyx said:
There is only one way to root, and that is by using a patched image. Check the guides section, there's probably a patched image of your device, if not, you'll have to make your own.
And what's your version? AA or BA?
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
AA. So do I need to roll back? I bought the OP7P because I stupidly assumed it would be as easy/flexible to root as my past OP devices. It's ironic I switched from a Samsung devices to a OP for the ability for a stress-free rooting experience and I got the same problem lol. I might just return the phone for another, I'd prefer something with an SD card slot anyway.
What's the best phone with SD card feature that can run TWRP magdisk without issues like using banking apps and Netflix?
Forgive my ignorance, I am still in the learning process.

Lossyx said:
TWRP doesn't work on devices launched with Android 10, which has been discussed many times.
My reply above stands true, a patched boot image is the only way as for right now.
(And we're on a 7T Pro forum)
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
No we're on a 7 Pro forum. And TWRP works fine on the 7 Pro, but you need a patched version of some sort last time I checked.
sixisixsix said:
I am running 10.05, I can't decide whether to install twrp, dd root, or magdisk. Given that I have the most current version of oxygen os, what would be the best way to root my phone?
Don't misinterpret my ignorance for lazyness, a majority of guides I've seen aren't recent and don't go over pros & cons of the method.
Thank you, I'm willing to donate for help.
Click to expand...
Click to collapse
To root my phone, I didn't even use TWRP. I downloaded the lastest OOS version from OnePlus, extracted the boot image, copied that to my phone, Magisk patched that boot image file (you don't need root for that, you can use the Magisk manager). Then unlocked the phone, and installed the bootloader I just patched while the phone was in bootloader mode (fastboot flash boot boot.img or whatever).
Might not be the easiest, but I think it's clean, however back then I did not know about the option to properly use TWRP. Maybe I can find it, but I know it's possible to just unlock the 7 Pro, and then from the bootloader boot to TWRP once without flashing it, and install Magisk.

QUBiCA said:
No we're on a 7 Pro forum. And TWRP works fine on the 7 Pro, but you need a patched version of some sort last time I checked.
Click to expand...
Click to collapse
Oh damn, I'm actually stupid... How did I miss were on 7 Pro?!
@sixisixsix please ignore everything I've said! I will edit my posts.
Sorry once again
Sent from my OnePlus7TPro using XDA Labs

sixisixsix said:
AA. So do I need to roll back? I bought the OP7P because I stupidly assumed it would be as easy/flexible to root as my past OP devices. It's ironic I switched from a Samsung devices to a OP for the ability for a stress-free rooting experience and I got the same problem lol. I might just return the phone for another, I'd prefer something with an SD card slot anyway.
Click to expand...
Click to collapse
I've found OP devices (having owned two now) to be easy to root, and very friendly to the mod/root community such as XDA. Samsung is the opposite, in my experience (although each Sammy device is different, some better than others in this regard).
The main complexity with the 7 Pro is not that it is an OP device per se; but that it has something called A/B partitions, which are used for "seamless" OTA updates (Pixel devices use this scheme also - as well as a number of other phones).
The thing with A/B partition devices, is that they do NOT have a discrete recovery partition that you can just flash TWRP to. Therefore, you need to patch the boot.img partition (which on A/B devices contains both kernel and recovery, along with ramdisk). It is a little trickier, and somewhat more of a learning curve. But once you've learned that basic difference, it is not too bad.
It seems that the list A/B partitions devices is growing. So while I'm not an expert in the industry or anything, it appears that this is where Android is going (A/B is certainly not going away anytime soon, in any case).
So while the SD card feature is a legitimate difference (and a discriminator for some), I would say you should not make the A/B partition difference scare you away from OP devices. Maybe "too much information", but you can read more about the A/B partition scheme here: https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
---------- Post added at 10:13 AM ---------- Previous post was at 10:05 AM ----------
QUBiCA said:
To root my phone, I didn't even use TWRP. I downloaded the lastest OOS version from OnePlus, extracted the boot image, copied that to my phone, Magisk patched that boot image file (you don't need root for that, you can use the Magisk manager). Then unlocked the phone, and installed the bootloader I just patched while the phone was in bootloader mode (fastboot flash boot boot.img or whatever).
Might not be the easiest, but I think it's clean, however back then I did not know about the option to properly use TWRP. Maybe I can find it, but I know it's possible to just unlock the 7 Pro, and then from the bootloader boot to TWRP once without flashing it, and install Magisk.
Click to expand...
Click to collapse
Certainly a valid approach (fastboot flash a patched boot image). The "other" (TWRP) method works as well, and probably a little easier for most folks:
1) Unlock bootloader
2) fastboot boot twrp.img
Note that this is just remote booting a TWRP image, not installing it. It simply allows the next steps. You can't flash a TWRP image directly, for the reason I've noted above.
3) Once booted to TWRP, flash TWRP installer zip (OPTIONAL). This patched the boot.img so that TWRP is installed. You only need to do this if you want TWRP installed on the phone.
4) Also in "booted" TWRP, flash the Magisk zip.
The main fundamental difference, is that Magisk is patching the boot.img for you, instead of doing it yourself. Have the files (TWRP.zip and Magisk) on the phone before starting the process, and it is really pretty simple and fast.
The nice thing about the patched boot.img method, is that is worked even when TWRP method did not. This applied to when the phone was first released, and the command "fastboot boot" was broken (therefore not possible to fastboot boot TWRP). This happened again when the device was updated to Android 10. Although the developer got fastboot boot working fairly quickly in both circumstances.

Lossyx said:
Edit: I'm stupid, I was in wrong forum. Please ignore this post and what I've said!
Click to expand...
Click to collapse
redpoint73 said:
I've found OP devices (having owned two now) to be easy to root, and very friendly to the mod/root community such as XDA. Samsung is the opposite, in my experience (although each Sammy device is different, some better than others in this regard).
The main complexity with the 7 Pro is not that it is an OP device per se; but that it has something called A/B partitions, which are used for "seamless" OTA updates (Pixel devices use this scheme also - as well as a number of other phones).
The thing with A/B partition devices, is that they do NOT have a discrete recovery partition that you can just flash TWRP to. Therefore, you need to patch the boot.img partition (which on A/B devices contains both kernel and recovery, along with ramdisk). It is a little trickier, and somewhat more of a learning curve. But once you've learned that basic difference, it is not too bad.
It seems that the list A/B partitions devices is growing. So while I'm not an expert in the industry or anything, it appears that this is where Android is going (A/B is certainly not going away anytime soon, in any case).
So while the SD card feature is a legitimate difference (and a discriminator for some), I would say you should not make the A/B partition difference scare you away from OP devices. Maybe "too much information", but you can read more about the A/B partition scheme here: https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
---------- Post added at 10:13 AM ---------- Previous post was at 10:05 AM ----------
Certainly a valid approach (fastboot flash a patched boot image). The "other" (TWRP) method works as well, and probably a little easier for most folks:
1) Unlock bootloader
2) fastboot boot twrp.img
Note that this is just remote booting a TWRP image, not installing it. It simply allows the next steps. You can't flash a TWRP image directly, for the reason I've noted above.
3) Once booted to TWRP, flash TWRP installer zip (OPTIONAL). This patched the boot.img so that TWRP is installed. You only need to do this if you want TWRP installed on the phone.
4) Also in "booted" TWRP, flash the Magisk zip.
The main fundamental difference, is that Magisk is patching the boot.img for you, instead of doing it yourself. Have the files (TWRP.zip and Magisk) on the phone before starting the process, and it is really pretty simple and fast.
The nice thing about the patched boot.img method, is that is worked even when TWRP method did not. This applied to when the phone was first released, and the command "fastboot boot" was broken (therefore not possible to fastboot boot TWRP). This happened again when the device was updated to Android 10. Although the developer got fastboot boot working fairly quickly in both circumstances.
Click to expand...
Click to collapse
Thank you for taking the time to respond to my post in such detail! Wouldn't installing TWRP give me more flexibility for future updates? If I go the flashed image route won't I need erase my data on my phone every time I update?

sixisixsix said:
Thank you for taking the time to respond to my post in such detail! Wouldn't installing TWRP give me more flexibility for future updates? If I go the flashed image route won't I need erase my data on my phone every time I update?
Click to expand...
Click to collapse
I don't think TWRP would give you more flexibility when it comes to updates, unless you are planning on switching ROMs often, but if this phone is your daily driver I would recommend against that.
If you unlock the phone your data will be wiped, but only once. After that it is completely up to you, if you switch ROMs and pick something that is completely different from stock, it is indeed recommended to wipe data to prevent weird issues. But for a regular system update (if you simply stick with the stock ROM and use Magisk for root, you can still receive normal updates from OnePlus), or an update of the same custom ROM, you do not need to wipe data. I wiped data only once, when I unlocked it, because I had to.
Flashing/installing TWRP generally is not necessary and like @redpoint73 explained, with the "new" A/B system, it is not advised to flash TWRP as it is combined with the boot image (which your phone needs to start up, and is updated after every update, so after every update you will lose TWRP again if I am correct). What @redpoint73 explained is that instead of installing (AKA flashing) TWRP, it is possible to just start it up (boot it) once without installing it. From there you can install Magisk on your stock OnePlus ROM and use the benefits of a rooted system.

QUBiCA said:
Flashing/installing TWRP generally is not necessary and like @redpoint73 explained, with the "new" A/B system, it is not advised to flash TWRP as it is combined with the boot image (which your phone needs to start up, and is updated after every update, so after every update you will lose TWRP again if I am correct).
Click to expand...
Click to collapse
It is correct that you lose the TWRP install when you update (as well as losing root). But it is just a simple matter of flashing the TWRP installer zip after the update (I do this the same time as re-flashing Magisk after OTA update), which takes about 10 seconds to accomplish. I wouldn't personally take that as a reason to "not" flash TWRP. But it is a personal preference whether to install TWRP or not. The reasons to have TWRP installed on the phone are much reduced from previous devices. In the past I would have said that being rooted without a custom recovery is asking for trouble. But now, with A/B partitions, along with the fastboot stock ROMs, the choice becomes much less clear. To the point that installing TWRP is purely optional.
I still personally believe that having TWRP installed gives you more recovery options. But again, it is a personal choice, and certainly not mandatory by any means.
---------- Post added at 09:11 AM ---------- Previous post was at 09:01 AM ----------
sixisixsix said:
Wouldn't installing TWRP give me more flexibility for future updates?
Click to expand...
Click to collapse
Actually, no (as QUBiCA touched on above).
Reason being, OTA updates will still come through on this device (even rooted). And you can still flash (or put OTA files on the phone to flash) using the built-in update engine in the phone's settings menu. Which gives you the option to update to either A/B partition slot. Plus, you can just re-flash TWRP (if desired) and Magisk after the update, straight from the Magisk Manager.
The trick is to make sure you do NOT reboot immediately after an OTA update (when rooted). Then simply open Magisk Manager, flash TWRP as if it were a Magisk module (optional, if you want TWRP installed again). Then install Magisk again through the Magisk Manager as well.. Now you can reboot, and you will be updated with root.
sixisixsix said:
If I go the flashed image route won't I need erase my data on my phone every time I update?
Click to expand...
Click to collapse
No (again, just backing up the answer already provided). There is not a big difference between the two methods. In either case, you are patching the boot.img partition to be rooted (whether you flash a patched boot.img, or you have Magisk patch it for you). And in both cases, you don't need to wipe your data.

redpoint73 said:
It is correct that you lose the TWRP install when you update (as well as losing root). But it is just a simple matter of flashing the TWRP installer zip after the update (I do this the same time as re-flashing Magisk after OTA update), which takes about 10 seconds to accomplish. I wouldn't personally take that as a reason to "not" flash TWRP. But it is a personal preference whether to install TWRP or not. The reasons to have TWRP installed on the phone are much reduced from previous devices. In the past I would have said that being rooted without a custom recovery is asking for trouble. But now, with A/B partitions, along with the fastboot stock ROMs, the choice becomes much less clear. To the point that installing TWRP is purely optional.
I still personally believe that having TWRP installed gives you more recovery options. But again, it is a personal choice, and certainly not mandatory by any means.
---------- Post added at 09:11 AM ---------- Previous post was at 09:01 AM ----------
Actually, no (as QUBiCA touched on above).
Reason being, OTA updates will still come through on this device (even rooted). And you can still flash (or put OTA files on the phone to flash) using the built-in update engine in the phone's settings menu. Which gives you the option to update to either A/B partition slot. Plus, you can just re-flash TWRP (if desired) and Magisk after the update, straight from the Magisk Manager.
The trick is to make sure you do NOT reboot immediately after an OTA update (when rooted). Then simply open Magisk Manager, flash TWRP as if it were a Magisk module (optional, if you want TWRP installed again). Then install Magisk again through the Magisk Manager as well.. Now you can reboot, and you will be updated with root.
No (again, just backing up the answer already provided). There is not a big difference between the two methods. In either case, you are patching the boot.img partition to be rooted (whether you flash a patched boot.img, or you have Magisk patch it for you). And in both cases, you don't need to wipe your data.
Click to expand...
Click to collapse
So if I used the patched version of 10.3.0 and another new version comes out I can just download it through settings and I will remained rooted?
Sent from my Redmi Note 8 Pro using Tapatalk

sixisixsix said:
So if I used the patched version of 10.3.0 and another new version comes out I can just download it through settings and I will remained rooted?
Sent from my Redmi Note 8 Pro using Tapatalk
Click to expand...
Click to collapse
NO.
You need to go through the process and flash Magisk from inside Magisk Manager.

tech_head said:
NO.
You need to go through the process and flash Magisk from inside Magisk Manager.
Click to expand...
Click to collapse
Okay so I downloaded magdisk manager, I flashed the patched version of 10.03, then when I rebooted I hit install update on magdisk and when the phone rebooted it was no longer rooted.
Even the guides for flashing aren't in depth enough for me. Can you help me out real quick?

sixisixsix said:
So if I used the patched version of 10.3.0 and another new version comes out I can just download it through settings and I will remained rooted?
Click to expand...
Click to collapse
You should get the OTA update and be able to download it through settings. BUT, after you install the update, you still need to do as I already said in order to remain rooted:
redpoint73 said:
The trick is to make sure you do NOT reboot immediately after an OTA update (when rooted). Then simply open Magisk Manager, flash TWRP as if it were a Magisk module (optional, if you want TWRP installed again). Then install Magisk again through the Magisk Manager as well.. Now you can reboot, and you will be updated with root.
Click to expand...
Click to collapse
---------- Post added at 09:28 AM ---------- Previous post was at 09:00 AM ----------
sixisixsix said:
Okay so I downloaded magdisk manager, I flashed the patched version of 10.03, then when I rebooted I hit install update on magdisk and when the phone rebooted it was no longer rooted.
Even the guides for flashing aren't in depth enough for me. Can you help me out real quick?
Click to expand...
Click to collapse
You seem to be mixing the two processes: Install update in Magisk is for when you update in the future. You shouldn't have to do this rooting the existing ROM with the patched boot.img method.
For the patched boot.img method, you should just be able to flash the patched boot.img, flash the Magisk apk, and open Magisk, and it should say rooted.
My recommendation is follow this guide: https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368
I can't possibly see how it can be any more in depth.