Related
Has anyone received Google Assistant on their phones yet? Just curious.
Yep. You can force it with a build.prop edit. It worked for me, but I think there are mixed reports. Root required.
https://forum.xda-developers.com/showpost.php?p=71272192&postcount=1520
I'm surprised to hear some people still don't have GA natively. I'm a long time HTC user, but I just bought my 10 last Fri. it's pretty sweet. although, I must say, I still REALLY like my One M8.
SilverZero said:
Yep. You can force it with a build.prop edit. It worked for me, but I think there are mixed reports. Root required.
https://forum.xda-developers.com/showpost.php?p=71272192&postcount=1520
Click to expand...
Click to collapse
I unlocked my bootloader Saturday but I'm reluctant to root because I don't want to lose Android Pay. If I can modify some the build.prop for Google Assistant and get wi-fi hotspot then reboot so I can use Android pay then I might.
misfiremind said:
I unlocked my bootloader Saturday but I'm reluctant to root because I don't want to lose Android Pay. If I can modify some the build.prop for Google Assistant and get wi-fi hotspot then reboot so I can use Android pay then I might.
Click to expand...
Click to collapse
I'm S-ON, unlocked bootloader, newest N firmware and latest Bad Boyz ROM (full version with MagiskSU, not SuperSU) and I have Android Pay working just fine. No reboot necessary, just use Magisk Manager to hide Magisk from Android Pay.
SilverZero said:
I'm S-ON, unlocked bootloader, newest N firmware and latest Bad Boyz ROM (full version with MagiskSU, not SuperSU) and I have Android Pay working just fine. No reboot necessary, just use Magisk Manager to hide Magisk from Android Pay.
Click to expand...
Click to collapse
I know, but I've rooted and messed with custom ROMs on every phone I've had and I'm kind of tired of messing with that stuff. Really I think the best thing I could do is buy a Pixel. I'm tired of the different phone manufacturers and their bloated ROMs and the constant problems that custom ROMs have. At least for right now. Thanks though. I'll keep it in mind if I ever feel like jacking with that stuff again.
"OK Google" Always on!!??
So has anyone else noticed this?
The attached screenshot shows the settings for the "ok google" always listening feature. I know this feature is useful to launch google from any screen or even when the screen is off but I do not want this on for privacy reasons. I was always able to disable it on Marshmallow but now with N even when i turn it off it turns back on.
How to try to reproduce:
Turn off the feature
Exit the settings menu
Go back to the Ok google settings and see if its enabled again.
Is this happening to anyone else!?
misfiremind said:
I unlocked my bootloader Saturday but I'm reluctant to root because I don't want to lose Android Pay. If I can modify some the build.prop for Google Assistant and get wi-fi hotspot then reboot so I can use Android pay then I might.
Click to expand...
Click to collapse
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
misfiremind said:
I know, but I've rooted and messed with custom ROMs on every phone I've had and I'm kind of tired of messing with that stuff. Really I think the best thing I could do is buy a Pixel. I'm tired of the different phone manufacturers and their bloated ROMs and the constant problems that custom ROMs have. At least for right now. Thanks though. I'll keep it in mind if I ever feel like jacking with that stuff again.
Click to expand...
Click to collapse
you must not be familar w/ Magisk....the "magic" of magisk can modify the phone w/o actually modifying /system, so technically u have a stock device but custom at the same time...plus magisk hide allows AP to work & pass SafetyNet
my Magisk ROM has all the mods & bloatware removed just like my custom ROM...
deakelem said:
So has anyone else noticed this?
The attached screenshot shows the settings for the "ok google" always listening feature. I know this feature is useful to launch google from any screen or even when the screen is off but I do not want this on for privacy reasons. I was always able to disable it on Marshmallow but now with N even when i turn it off it turns back on.
How to try to reproduce:
Turn off the feature
Exit the settings menu
Go back to the Ok google settings and see if its enabled again.
Is this happening to anyone else!?
Click to expand...
Click to collapse
this is from my Bolt, so it may be different, but I can disable just fine...
OMJ said:
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
you must not be familar w/ Magisk....the "magic" of magisk can modify the phone w/o actually modifying /system, so technically u have a stock device but custom at the same time...plus magisk hide allows AP to work & pass SafetyNet
my Magisk ROM has all the mods & bloatware removed just like my custom ROM...
Click to expand...
Click to collapse
I didn't even try after unlocking because I'm still waiting for my bank to support Android Pay, but I just checked and your right. I'm blocked from Android Pay. Might as well figure out how to root and install a ROM this weekend. ? And no, I have no idea what Magisk is, but I guess I'll have to figure it out.
deakelem said:
So has anyone else noticed this?
The attached screenshot shows the settings for the "ok google" always listening feature. I know this feature is useful to launch google from any screen or even when the screen is off but I do not want this on for privacy reasons. I was always able to disable it on Marshmallow but now with N even when i turn it off it turns back on.
How to try to reproduce:
Turn off the feature
Exit the settings menu
Go back to the Ok google settings and see if its enabled again.
Is this happening to anyone else!?
Click to expand...
Click to collapse
Mine seems to work fine. Have you tried clearing the Google App data? I had an issue with a couple of apps after the Nougat update and had to clear the data and uninstall then reinstall the apps to get them working correctly.
misfiremind said:
Mine seems to work fine. Have you tried clearing the Google App data? I had an issue with a couple of apps after the Nougat update and had to clear the data and uninstall then reinstall the apps to get them working correctly.
Click to expand...
Click to collapse
Ill try that but I flashed N using the RUU and then clean installed OMJ's badboys rom so no app data would have been there during M to N
---------- Post added at 02:16 PM ---------- Previous post was at 02:14 PM ----------
OMJ said:
this is from my Bolt, so it may be different, but I can disable just fine...
Click to expand...
Click to collapse
Thats strange, i dont have all those menu entries... could be cause I have work email on my phone via activesync which restricts certain security and lockscreen options.
OMJ said:
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
Click to expand...
Click to collapse
I'm confused . . . My bootloader is unlocked, has been since I got my 10 last summer, and I just used Android Pay this weekend, and Magisk Manager says I'm currently passing SafetyNet. Android Pay is checked in Magisk Hide.
Are you saying that unlocking the bootloader alone will cause SafetyNet to fail, but Magisk Hide will then allow it again?
SilverZero said:
I'm confused . . . My bootloader is unlocked, has been since I got my 10 last summer, and I just used Android Pay this weekend, and Magisk Manager says I'm currently passing SafetyNet. Android Pay is checked in Magisk Hide.
Are you saying that unlocking the bootloader alone will cause SafetyNet to fail, but Magisk Hide will then allow it again?
Click to expand...
Click to collapse
yes, merely having the bootloader unlocked even w/ 100% stock ROM, safetynet will fail....the beauty of magisk is that it hides it
I think at this point I'd rather relock my bootloader and go back to using my Galaxy S4 while I try to sell my HTC 10 and then put that money towards a Pixel. Anybody wanna buy a phone? ?
It's here! I literally just this minute got Google Assistant!
OMJ said:
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
you must not be familar w/ Magisk....the "magic" of magisk can modify the phone w/o actually modifying /system, so technically u have a stock device but custom at the same time...plus magisk hide allows AP to work & pass SafetyNet
my Magisk ROM has all the mods & bloatware removed just like my custom ROM...
Click to expand...
Click to collapse
I think I am going to give this a shot. I am running your stock rooted with TWRP while S-on. Can I just install your Magisk Full Rom and go from there or is that too easy to believe? Thanks OMJ!
OMJ said:
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
you must not be familar w/ Magisk....the "magic" of magisk can modify the phone w/o actually modifying /system, so technically u have a stock device but custom at the same time...plus magisk hide allows AP to work & pass SafetyNet
my Magisk ROM has all the mods & bloatware removed just like my custom ROM...
Click to expand...
Click to collapse
Is magisk a ROM or more of a mod? And what is magisk su? I'm going to try and get my phone rooted this weekend but I can't find a tutorial thread, it seems to be scattered everywhere. It seems like I fastboot TWRP, flash SuperSU, flash magisk then install magisk manager from Google Play?
misfiremind said:
I didn't even try after unlocking because I'm still waiting for my bank to support Android Pay, but I just checked and your right. I'm blocked from Android Pay. Might as well figure out how to root and install a ROM this weekend. ? And no, I have no idea what Magisk is, but I guess I'll have to figure it out.
Click to expand...
Click to collapse
im running viper due to lack of cm/aosp st the moment.. so i have magisk but i have no idea what it is or how to use it. very little instruction out there.
Has anyone been successful in editing their build.prop file to activate (or deactivate) Google Assistant? I actually want to deactivate Google Assistant but I can't seem save changes to my build.prop file.
I have root on stock ROM.
Set SE Linux to permissive.
Tried using Root Explorer and build.prop Editor. Both give me an error message stating it can't save the build.prop file.
Suggestions?
I just received the OP5 yesterday and unlocked the bootloader. I got the "Android Pay can't be used on this device" message when I try to add a credit card on android pay. Does anyone know if I need twrp and magisk installed in order for android pay to work?
dslreports said:
I just received the OP5 yesterday and unlocked the bootloader. I got the "Android Pay can't be used on this device" message when I try to add a credit card on android pay. Does anyone know if I need twrp and magisk installed in order for android pay to work?
Click to expand...
Click to collapse
in theory according to posts ive seen for other devices you need magisks latest beta version.
dslreports said:
I just received the OP5 yesterday and unlocked the bootloader. I got the "Android Pay can't be used on this device" message when I try to add a credit card on android pay. Does anyone know if I need twrp and magisk installed in order for android pay to work?
Click to expand...
Click to collapse
Check by Playstore>settings... you're probably uncertified...
EDIT: You need magisk to pass the safetynet...
Correct. It says uncerified for me. The only thing i did was unlock bootloader. Sigh. I guess i have to twrp and magisk. Thanks.
dslreports said:
Correct. It says uncerified for me. The only thing i did was unlock bootloader. Sigh. I guess i have to twrp and magisk. Thanks.
Click to expand...
Click to collapse
Usually deleting Play Store data and cache fixes the "uncertified" issue. It did with my OnePlus 3/3T. It didn't work for me with the OnePlus 5 however.
EVR_PR said:
Usually deleting Play Store data and cache fixes the "uncertified" issue. It did with my OnePlus 3/3T. It didn't work for me with the OnePlus 5 however.
Click to expand...
Click to collapse
It won't unless you either 1) Use magisk as mentioned or 2) use a custom kernel with SafeyNet patches.
When you unlock your bootloader, the prop (which you can read using a terminal emulator and typing getprop) has a flag called verifiedbootstate. If it returns anything but green SafeyNet will fail.
Sent from my OnePlus 3T using XDA Labs
U need to flash latest magisk and pass the safetynet to make Androidpay to work.
this is probably a stupid question but it's been a while since ive used android ... can you use android pay if you don't unlock the boot loader?
gameofdroness said:
this is probably a stupid question but it's been a while since ive used android ... can you use android pay if you don't unlock the boot loader?
Click to expand...
Click to collapse
Of course..why not...
HatRiGt said:
U need to flash latest magisk and pass the safetynet to make Androidpay to work.
Click to expand...
Click to collapse
I've flashed v. 13 (https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589) and worked as a charm!
I have both the newest version of Magisk and the manager, but I'm still failing safetynet, do I need to manually hide something else in magisk hide? Any help is greatly appreciated
oowaymike said:
I have both the newest version of Magisk and the manager, but I'm still failing safetynet, do I need to manually hide something else in magisk hide? Any help is greatly appreciated
Click to expand...
Click to collapse
Try the latest stable version of Magisk. It worked for me a few days ago while the beta wasn't (beta is working for me lately though).
You might want to reflash stock boot partition before flashing Magisk, I don't know if it will make a difference...
yubimusubi said:
Try the latest stable version of Magisk. It worked for me a few days ago while the beta wasn't (beta is working for me lately though).
You might want to reflash stock boot partition before flashing Magisk, I don't know if it will make a difference...
Click to expand...
Click to collapse
Thanks for the suggestions. I tried the stable version with no luck as well. I'll wait for the next beta version, and if that doesn't do the trick ill try reflashing the stock partition. If anyone finds a custom kernel that gets around safety net I'd really appreciate it.
dslreports said:
Correct. It says uncerified for me. The only thing i did was unlock bootloader. Sigh. I guess i have to twrp and magisk. Thanks.
Click to expand...
Click to collapse
I'm curious to know why one would unlock the bootloader if not at least to install custom recovery and root.
Eric214 said:
I'm curious to know why one would unlock the bootloader if not at least to install custom recovery and root.
Click to expand...
Click to collapse
I don't know if this is OP'S reason, but you can boot TWRP without actually installing it... So you can take nandroid backups of an otherwise stock device.
Also, unlocking bootloader wipes your phone, so if you want it stock for now but think you might root in the future you won't have to deal with that...
TBH though, SafetyNet is working as advertised by failing an unlocked bootloader. We like to have our cake and eat it too.
I'm wanting to only unlock bootloader, but otherwise keep everything stock. Will just unlocking bootloader invalidate CTS checks and deny things like Android Pay?
I also want to keep getting OTAs, keep stock recovery and remain rootless. I just know I'll eventually want to root, but i don't want to be forced to wipe when I do
NOTE: I get my 6T in a few hours
I use Android Pay all the time with my unlocked and rooted 6T. If you end up installing things that mess with the system partition and SafetyNet like Xposed then Android Pay will not work.
So just the act of unlocking the bootloader will not disable Android Pay in my experience with my 5T and 6T now.
It was basically the same for me. I just tested it for you and Google Pay seemed to work fine. I do know from the DRM Info app that my security level went from L1 to L3, which I guess means no HD video on sites like Netflix or whatever, which I don't use on my phone anyway. That's about all I know so far
Thanks guys! Super appreciate it! I remember seeing posts about people just unlocking bootloaders on other devices causing issues, I didn't think it would. Gives me a great peace of mind before I do something silly!
Magisk will keep SafetyNet valid.
If you're unlocked but NOT rooted, you'll need to use a custom kernel.
If you have an unlocked bootloader without Magisk and without a custom Kernel, you will fail CTS and in turn fail SafetyNet.
Oh no. Unlocked bootloader, ran an update and got the attached images.
Looks like unlocking the bootloader kills off Google Pay and CTS
@hartleyshc seems to be correct. Might have to lock it again
mattisdada said:
Oh no. Unlocked bootloader, ran an update and got the attached images.
Looks like unlocking the bootloader kills off Google Pay and CTS
@hartleyshc seems to be correct. Might have to lock it again
Click to expand...
Click to collapse
I'm not currently rooted on any device,but,shouldn't using Magisk fix what you're concerned about? (At least in relation to this particular phone).
The one reported thing w/unlocking the b/l is Widevine Level 1 is downgraded to Level 3,preventing video playback at HD quality on some streaming content.
AFAIK,there is no Magisk or Xposed module that fixes DRM on b/l unlocked phones.
That's been shown to be the case with this phone,YMMV if this is an issue to you:
https://android.gadgethacks.com/how...ix-amazon-prime-video-other-services-0181603/
Here's the app to check/verify:
https://android.gadgethacks.com/how...ix-amazon-prime-video-other-services-0181603/
KOLIOSIS said:
I'm not currently rooted on any device,but,shouldn't using Magisk fix what you're concerned about? (At least in relation to this particular phone).
The one reported thing w/unlocking the b/l is Widevine Level 1 is downgraded to Level 3,preventing video playback at HD quality on some streaming content.
AFAIK,there is no Magisk or Xposed module that fixes DRM on b/l unlocked phones.
That's been shown to be the case with this phone,YMMV if this is an issue to you:
https://android.gadgethacks.com/how...ix-amazon-prime-video-other-services-0181603/
Here's the app to check/verify:
https://android.gadgethacks.com/how...ix-amazon-prime-video-other-services-0181603/
Click to expand...
Click to collapse
Main thing I want is just Google Pay and certain games, Widevine I'm not terribly fussed about. Right now Google Pay is complaining after just unlocking bootloader, no other modifications
Magisk does fix it, but I'm trying to be more hands off now, I don't want to have to install something after each ota, do manual updates, etc
mattisdada said:
Main thing I want is just Google Pay and certain games, Widevine I'm not terribly fussed about. Right now Google Pay is complaining after just unlocking bootloader, no other modifications
Click to expand...
Click to collapse
Install and stay on the latest version of Magisk. If there's any apps that complain about being rooted, you can use Magisk to hide itself from that app. (Pokemon Go and banking apps seem to implement this most frequently).
Especially if you don't care about widevine, I'd suggest just rooting. It will be easier to install some sort of mod in the future than having to unlock your bootloader again.
Go into Magisk settings and toggle the options to download and install the latest beta of Magisk. That way you can always stay current and always pass SafetyNet.
I was rooted on my Nexus 6p and I can't remember the last time Magisk failed SafetyNet for me except when I wasn't current and I'm a very frequent Google Pay user.
hartleyshc said:
Magisk will keep SafetyNet valid.
If you're unlocked but NOT rooted, you'll need to use a custom kernel.
If you have an unlocked bootloader without Magisk and without a custom Kernel, you will fail CTS and in turn fail SafetyNet.
Click to expand...
Click to collapse
From what I understand if he has Magisk his device should be rooted. Since I have valid SafetyNet check with stock kernal. I would share my Magisk hide.
P.S. Make sure that "Logger buffer sizes" under "Development tools" is not "Off" otherwise Magisk hide will not be triggered.
Sent from my ONEPLUS A6013 using Tapatalk
vichao.s said:
From what I understand if he has Magisk his device should be rooted. Since I have valid SafetyNet check with stock kernal. I would share my Magisk hide.
P.S. Make sure that "Logger buffer sizes" under "Development tools" is not "Off" otherwise Magisk hide will not be triggered. View attachment 4671491View attachment 4671492View attachment 4671493View attachment 4671494
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
SafetyNet check result.
Sent from my ONEPLUS A6013 using Tapatalk
vichao.s said:
From what I understand if he has Magisk his device should be rooted. Since I have valid SafetyNet check with stock kernal. I would share my Magisk hide.
P.S. Make sure that "Logger buffer sizes" under "Development tools" is not "Off" otherwise Magisk hide will not be triggered.
Click to expand...
Click to collapse
But that's not what they asked. They said they only wanted to unlock the bootloader. You will fail safetynet that way.
Safetynet checks against unlocked bootloaders. There's currently two ways to bypass this check. With magisk, or with a custom kernel.
Also this thread was almost 2 months old. No need to bring it back up. Their question was answered.
Hi XDA community,
I will receive my new OnePlus Pro 8 tomorrow.
This will be my first OnePlus phone and it will likely be the North American version.
Primarily, I would like to unlock the bootloader and root the phone, additionally also have the Dual-sim functionality enabled.
I don't have a lot of experience with rooting, but can follow steps and instructions
1) Should I start the new phone let it update all the way to oxygen OS 11 and than follow steps to unlock the bootloader and root the phone and than transfer my data? - Will this process be more complicated than doing it with Oxygen OS 10.?
2) Once the phone is rooted, can I transfer data from my old phone through the USB/Phone/data transfer apps so it gets setup automagically ?
3) Does TWRP work with OS 11 ? if not is there an update schedule for it?
4) Does Dual Sim for NA phones work with Oxygen OS 10 or is it enabled only at Oxygen OS 11 ?
Any things else that I should be aware of? (this process or the phone in general as well?)
Thank you all
DV
Peace.
dvartak said:
Hi XDA community,
I will receive my new OnePlus Pro 8 tomorrow.
This will be my first OnePlus phone and it will likely be the North American version.
Primarily, I would like to unlock the bootloader and root the phone, additionally also have the Dual-sim functionality enabled.
I don't have a lot of experience with rooting, but can follow steps and instructions
1) Should I start the new phone let it update all the way to oxygen OS 11 and than follow steps to unlock the bootloader and root the phone and than transfer my data? - Will this process be more complicated than doing it with Oxygen OS 10.?
2) Once the phone is rooted, can I transfer data from my old phone through the USB/Phone/data transfer apps so it gets setup automagically ?
3) Does TWRP work with OS 11 ? if not is there an update schedule for it?
4) Does Dual Sim for NA phones work with Oxygen OS 10 or is it enabled only at Oxygen OS 11 ?
Any things else that I should be aware of? (this process or the phone in general as well?)
Thank you all
DV
Peace.
Click to expand...
Click to collapse
1. I would prefer to unlock the phone first and than boot twrp and flash magisk. After you got root update the system and install magisk to inactiv slot.
2. I don't know.
3. Nope.
4. Should also work with OOS 10.
Thank you for your reply..
Kollachi said:
1. I would prefer to unlock the phone first and than boot twrp and flash magisk. After you got root update the system and install magisk to inactiv slot.
2. I don't know.
3. Nope.
4. Should also work with OOS 10.
Click to expand...
Click to collapse
Thanks for your reply
Is there a forum thread for how I can unlock the bootloader and to perform root, the XDA forum threads while very resourceful are a bit overwhelming as there seem to be multiple methods of achieving root.
I am not planning on installing customROMS as yet, just want the phone to be unlocked and so I can enable the colour filter, installing gcam etc for now.
Cheers,
DV
dvartak said:
Thanks for your reply
Is there a forum thread for how I can unlock the bootloader and to perform root, the XDA forum threads while very resourceful are a bit overwhelming as there seem to be multiple methods of achieving root.
I am not planning on installing customROMS as yet, just want the phone to be unlocked and so I can enable the colour filter, installing gcam etc for now.
Cheers,
DV
Click to expand...
Click to collapse
I have a couple in the guides section..have a look. So long as you follow it correctly you should be fine.
One for the bootloader.
One for updating, rooting and payload dumper.
A few more questions...
dladz said:
I have a couple in the guides section...have a look. So long as you follow it correctly you should be fine.
One for the bootloader.
One for updating, rooting and payload dumper.
Click to expand...
Click to collapse
Do you mind pasting the links here, I have managed to get the bootloader unlocked using fastboot.
(NVM, I think I found your threads oneplus-8-pro/how-to/root-uk-eu-patched-magisk-boot-img-t4175033 & )
My model is IN2025
OS: 10.5.10.IN11AA
I wanted to know,
1) OxyOS updater is prompting that there is an update to Oxygen OS 11.IN11AA
Can I update to OxyOS 11 and still keep the bootloader unlocked ?
"It displays that OEM unlock is detected, system will download the full upgrade package, please backup data...etc."
2) Should I root my phone now and later will I be able to upgrade / flash to Oxygen OS 11 ? -North-American market requires OS 11 for dual sim
Where can I find the appropriate files to get make a 'patch' using payload for this version (10.5.10.IN11AA) ?
Thank you
dvartak said:
Do you mind pasting the links here, I have managed to get the bootloader unlocked using fastboot.
(NVM, I think I found your threads oneplus-8-pro/how-to/root-uk-eu-patched-magisk-boot-img-t4175033 & )
My model is IN2025
OS: 10.5.10.IN11AA
I wanted to know,
1) OxyOS updater is prompting that there is an update to Oxygen OS 11.IN11AA
Can I update to OxyOS 11 and still keep the bootloader unlocked ?
"It displays that OEM unlock is detected, system will download the full upgrade package, please backup data...etc."
2) Should I root my phone now and later will I be able to upgrade / flash to Oxygen OS 11 ? -North-American market requires OS 11 for dual sim
Where can I find the appropriate files to get make a 'patch' using payload for this version (10.5.10.IN11AA) ?
Thank you
Click to expand...
Click to collapse
Yes you can
Yes that's fine
Easiest way is whatever you like .
You can either root now then take the update and then OTA install magisk patched or just boot the magisk patched after and then directly install
Sorry, I still have some more questions..
dladz said:
Yes you can
Yes that's fine
Easiest way is whatever you like .
You can either root now then take the update and then OTA install magisk patched or just boot the magisk patched after and then directly install
Click to expand...
Click to collapse
I updated to OS11.IN11AA to enable Dual Sim first.
I guess I can try rooting now. Sorry I still have a few queries:
1)
In your instructions you suggest extracting 'your own' boot.img using the payload_dumper.
My phone (thanks to the OEM unlock) has downloaded a large 2GB+ zip file on the phone, should I use that payload.bin to extract the boot.img
or
the one on the oneplus website will work as well? - They appear to be the same but would like to know if there is a difference.
From the oneplus Website: OnePlus8ProOxygen_15.O.30_OTA_0300_all_2010031617_2198430880804411.zip
From the phone: OnePlus8ProOxygen_15.O.30_OTA_0300_all_2010031617_f9ca0bfd1b.zip
2)
I installed MagiskManager from the link in your thread (Preferred magisk manager- https://mega.nz/file/LU9U3aSC#EFJTOK...ejzi-VyUa3nQq8)
There weren't any updates till I selected the stable channel and than canary again. I have installed the whatever updates, it showed:
It now reads:
Magisk (latest): 1469b82a
Installed: N/A <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Why does it show N/A ?, will this change after the rooting process ?
Ramdisk: Yes
A/B: yes
SAR: yes
Crypto: File
Manager (latest) 1469b82a(315)(14)
installed: 1469b82a(315)
Does this seem correct?
You have been really awesome !
Cheers,
DV
dvartak said:
I updated to OS11.IN11AA to enable Dual Sim first.
I guess I can try rooting now. Sorry I still have a few queries:
1)
In your instructions you suggest extracting 'your own' boot.img using the payload_dumper.
My phone (thanks to the OEM unlock) has downloaded a large 2GB+ zip file on the phone, should I use that payload.bin to extract the boot.img
or
the one on the oneplus website will work as well? - They appear to be the same but would like to know if there is a difference.
From the oneplus Website: OnePlus8ProOxygen_15.O.30_OTA_0300_all_2010031617_2198430880804411.zip
From the phone: OnePlus8ProOxygen_15.O.30_OTA_0300_all_2010031617_f9ca0bfd1b.zip
2)
I installed MagiskManager from the link in your thread (Preferred magisk manager- https://mega.nz/file/LU9U3aSC#EFJTOK...ejzi-VyUa3nQq8)
There weren't any updates till I selected the stable channel and than canary again. I have installed the whatever updates, it showed:
It now reads:
Magisk (latest): 1469b82a
Installed: N/A <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Why does it show N/A ?, will this change after the rooting process ?
Ramdisk: Yes
A/B: yes
SAR: yes
Crypto: File
Manager (latest) 1469b82a(315)(14)
installed: 1469b82a(315)
Does this seem correct?
You have been really awesome !
Cheers,
DV
Click to expand...
Click to collapse
Hey,
1.) Yep that's absolutely fine, I tend to use oxygen updater as it's been absolutely flawless up until now and it won't allow you to download a firmware not compatible with your device.
Wherever you choose the numbers you've shown seem good to me, but id I had to choose I'd go with oxygen updater.
2.) Some people have had a lot more luck with the beta channel, so long as you have the install/update buttons then you're ready to patch the boot.img and go ahead and boot it using Fastboot.
Don't worry about N/A that just states that magisk_patched isn't there yet, which is normal.
So at this point, you're welcome to stick with stable but I couldn't recommend it as I've not done this myself, I've only had luck with canary but others have had luck with beta.. I'd recommend one of them channels, changing back to canary may now show the buttons that were missing..
If not then beta.
There are some troubleshooting steps at the end of the guides at the bottom. As well as all the files which I used.
Let me know how you get on
dladz said:
Hey,
2.) Some people have had a lot more luck with the beta channel, so long as you have the install/update buttons then you're ready to patch the boot.img and go ahead and boot it using Fastboot.
Don't worry about N/A that just states that magisk_patched isn't there yet, which is normal.
So at this point, you're welcome to stick with stable but I couldn't recommend it as I've not done this myself, I've only had luck with canary but others have had luck with beta.. I'd recommend one of them channels, changing back to canary may now show the buttons that were missing..
If not then beta.
There are some troubleshooting steps at the end of the guides at the bottom. As well as all the files which I used.
Let me know how you get on
Click to expand...
Click to collapse
Thanks again for all your help!
So I believe, the channel display when first opened did not show any install / update buttons but the settings showed channel: Canary.
I believe I switched to stable and the buttons showed up (i did not install than), after which I switched channels to canary and than installed.
When I search for the "1469b82a" and magisk it shows this as a Update to Canary channel (3days ago) https://github.com/topjohnwu/magisk_files/blob/canary/notes.md
I hope I am on the right track..
-------------------------------
UPDATE: So I think it has worked,
It seems I am rooted now, I have installed Titanium and bunch of other stuff that needs root.
(but I think I may have goofed up and ended up mixing your two solutions)
It was installed in 'b - drive/section'.
fastboot flash boot magisk_patched.img <(This is different from your step 4, where you do fastboot boot magisk_patched)
(I am hoping this did not goof things up, I misread )
It flashed just on 'b' - drive.
I did not flash in both 'a' and 'b'.
I also did'
"
5. Open magisk manager and click install/update, if you are missing the install/ update buttons, change magisk version to beta in magisk settings.
6. Select Direct install (recommended)
"
When I open Magisk Manager now, I see installed 1469b82a (21101) < same as the latest
I also have the "Uninstall Magisk button" showing which wasn't before. and settings shows me many more options (super user, magisk hide etc.)
2) Also what does Magisk hide do?,
> I have read many bank apps wont install due to rooting, will that help?
Thanks for being so patient and answering all questions !
dvartak said:
Thanks again for all your help!
So I believe, the channel display when first opened did not show any install / update buttons but the settings showed channel: Canary.
I believe I switched to stable and the buttons showed up (i did not install than), after which I switched channels to canary and than installed.
When I search for the "1469b82a" and magisk it shows this as a Update to Canary channel (3days ago) https://github.com/topjohnwu/magisk_files/blob/canary/notes.md
I hope I am on the right track..
-------------------------------
UPDATE: So I think it has worked,
It seems I am rooted now, I have installed Titanium and bunch of other stuff that needs root.
(but I think I may have goofed up and ended up mixing your two solutions)
It was installed in 'b - drive/section'.
fastboot flash boot magisk_patched.img <(This is different from your step 4, where you do fastboot boot magisk_patched)
(I am hoping this did not goof things up, I misread )
It flashed just on 'b' - drive.
I did not flash in both 'a' and 'b'.
I also did'
"
5. Open magisk manager and click install/update, if you are missing the install/ update buttons, change magisk version to beta in magisk settings.
6. Select Direct install (recommended)
"
When I open Magisk Manager now, I see installed 1469b82a (21101) < same as the latest
I also have the "Uninstall Magisk button" showing which wasn't before. and settings shows me many more options (super user, magisk hide etc.)
2) Also what does Magisk hide do?,
> I have read many bank apps wont install due to rooting, will that help?
Thanks for being so patient and answering all questions !
Click to expand...
Click to collapse
That's ok you just flashed it twice.
Reason for the boot and not flash is due to the fact that boot images can always go wrong,, bad copy or just corruption. But if you're rooted then you're all good
Magisk hide attempts to hide itself from apps that works otherwise detect it, meaning you can go ahead and use Google pay our your banking apps.
In theory anyway, but some apps have other ways of detecting root and thus it won't work.
Up until now I've been ok.
I see..
Ah I see, Thanks again. Google pay complains about root, but my other Bank apps seem fine so far. I'll try my luck with hide magisk.
I suppose next time the phone updates, I will lose root as the active partition will switch ?
The only odd thing that has happened is the I have an extra/duplicate icon for the Android Files App. I don't know how to get rid of it...but it's not a big issue.
Thanks again for your help!
Cheers,
DV
dvartak said:
Ah I see, Thanks again. Google pay complains about root, but my other Bank apps seem fine so far. I'll try my luck with hide magisk.
I suppose next time the phone updates, I will lose root as the active partition will switch ?
The only odd thing that has happened is the I have an extra/duplicate icon for the Android Files App. I don't know how to get rid of it...but it's not a big issue.
Thanks again for your help!
Cheers,
DV
Click to expand...
Click to collapse
Change to systemless and turn on magisk hide
dladz said:
Change to systemless and turn on magisk hide
Click to expand...
Click to collapse
remember to backup persist partition. i just got my oneplus 8 pro as well. it has a great deal for Black Friday in US.
dlhxr said:
remember to backup persist partition. i just got my oneplus 8 pro as well. it has a great deal for Black Friday in US.
Click to expand...
Click to collapse
How do I backup persist partition?, Will Titanium backup help or something else ?
I am new to the whole rooting thing.
dlhxr said:
remember to backup persist partition. i just got my oneplus 8 pro as well. it has a great deal for Black Friday in US.
Click to expand...
Click to collapse
Me? I have pal
I need it to root with Magisk--I'm not having luck any other way.
pbergonzi said:
I need it to root with Magisk--I'm not having luck any other way.
Click to expand...
Click to collapse
Looks like the was posted in the root thread
[GUIDE] ROOT OnePlus 7T Pro McLaren 5G (T-Mobile version HD1925)
Hi. So I wanted to put together a little write-up on how to root the T-Mobile McLaren 5G variant, at least how I rooted mine, as there doesn't seem to be anything about this yet. I was actually able to root my device last night successfully, so I...
forum.xda-developers.com
Artimis said:
Looks like the was posted in the root thread
[GUIDE] ROOT OnePlus 7T Pro McLaren 5G (T-Mobile version HD1925)
Hi. So I wanted to put together a little write-up on how to root the T-Mobile McLaren 5G variant, at least how I rooted mine, as there doesn't seem to be anything about this yet. I was actually able to root my device last night successfully, so I...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you!
How cool is that! I was just about to go at it with the MSM Tool, per the instructions here:
[GUIDE] Root and keeping root options
Update 230526: Correct numbering of "B.1.1 Simple" to "B.1.2 Simple", use "OOS 13+" instead of "OOS 13" as OOS 13.1 is now available A. First time rooting This process is common across all options A.1 Flashing Magisk patched boot image There...
forum.xda-developers.com
Artimis said:
Looks like the was posted in the root thread
[GUIDE] ROOT OnePlus 7T Pro McLaren 5G (T-Mobile version HD1925)
Hi. So I wanted to put together a little write-up on how to root the T-Mobile McLaren 5G variant, at least how I rooted mine, as there doesn't seem to be anything about this yet. I was actually able to root my device last night successfully, so I...
forum.xda-developers.com
Click to expand...
Click to collapse
Intriguingly, I have root, superuser access for apps, but none of my modules are working. Could be I did something wrong, flashed the wrong something the wrong way..., whatever.
Gonna clean up the show and start over.
pbergonzi said:
Intriguingly, I have root, superuser access for apps, but none of my modules are working. Could be I did something wrong, flashed the wrong something the wrong way..., whatever.
Gonna clean up the show and start over.
Click to expand...
Click to collapse
It could depend on the specific module and compatibility with Android 12. Which modules specifically?
Depending on files the module is overriding, some will work regardless of Android version, others may be very specific to the version or even the phone/oem framework
Ohhh..., thank you. Things that used to work on 11.
Ad Away, Vanced, Replace T-Mo Boot Anim With McLaren Anim; Disable T-Mo Shutdown Anim.
(Ad Away is not a mod, it's a root app that says there's no room for it now.)
I see what you mean--some of these things could have different names internally now.
I'll fiddle around some and report back, and Artimis--thank you for your ongoing help.
Methinks I can be perfectly happy with 12 when I get the most important things working, else I'll just revert to 11.
Artimis said:
It could depend on the specific module and compatibility with Android 12. Which modules specifically?
Depending on files the module is overriding, some will work regardless of Android version, others may be very specific to the version or even the phone/oem framework
Click to expand...
Click to collapse
Issue with Ad Away was corrected by simply enabling "Systemless Hosts" in Magisk.
Issue with Vanced was a matter of my accidentally updating my YouTube and YouTube Music, when prior to that I had been using an older version that Vanced could manage properly. I am looking into the new Revanced.net to see if that will be a viable solution for me.
Haven't looked at the boot and shutdown anims, but that is probably just an animation renamed from what the earlier versions of those modules changed, which is no big deal, but probably correctible, possibly via console command.
Oddly, the bootloader unlock warning doesn't show, but I think that's because the T-Mo 12 ROM was written in such a way as to cover it up--maybe it was overlooked(?)--the phone still seems to take as much time to boot as it would if the warning was showing.
Now that I'm comfortable with the process (and with @Chueppo boot images, and your sparkling assistance), it may just be time for me to a complete cleanup via factory reset, and start with a super-fresh phone, 'cause this sure is one nice phone.
Thanks again.