I am currently running OOS Open Beta 17 on my OnePlus 3t (Android O) and I am unable to use Android Pay because it says my device is either rooted, running a custom ROM or has an unlocked bootloader. I really need to use Android Pay. Any help appreciated. Cheers!
TrollPirate said:
I am currently running OOS Open Beta 17 on my OnePlus 3t (Android O) and I am unable to use Android Pay because it says my device is either rooted, running a custom ROM or has an unlocked bootloader. I really need to use Android Pay. Any help appreciated. Cheers!
Click to expand...
Click to collapse
Well, maybe because your phone is either rooted or your bootloader is unlocked ?
If you are using SuperSU, I think you can't use Android Pay: you might need to use Magisk to bypass SafetyNet and use Android Pay.
As Magisk isn't compatible with Android Oreo for now, you can't use Android Pay while you are rooted.
casual_kikoo said:
Well, maybe because your phone is either rooted or your bootloader is unlocked ?
If you are using SuperSU, I think you can't use Android Pay: you might need to use Magisk to bypass SafetyNet and use Android Pay.
As Magisk isn't compatible with Android Oreo for now, you can't use Android Pay while you are rooted.
Click to expand...
Click to collapse
I haven't rooted my phone yet. But yes, my bootloader is unlocked. Can I get it working by locking my bootloader? And in case I do that, will future updates over OTA work?
TrollPirate said:
I haven't rooted my phone yet. But yes, my bootloader is unlocked. Can I get it working by locking my bootloader? And in case I do that, will future updates over OTA work?
Click to expand...
Click to collapse
I use Magisk on latest OOS, Android Pay does not give me this error.
TrollPirate said:
I haven't rooted my phone yet. But yes, my bootloader is unlocked. Can I get it working by locking my bootloader? And in case I do that, will future updates over OTA work?
Click to expand...
Click to collapse
You don't need an unlocked bootloader to run Open Beta. So there is no reason to think that OTA would be affected by locking it.
Be aware, I believe locking bootloader will wipe the phone.
Looks like Magisk is my only option. I just rooted my phone using superSU. Can anyone help me with a Magisk rooting guide (for OOS open beta Oreo)?
TrollPirate said:
Looks like Magisk is my only option. I just rooted my phone using superSU. Can anyone help me with a Magisk rooting guide (for OOS open beta Oreo)?
Click to expand...
Click to collapse
Here you go;
https://forum.xda-developers.com/oneplus-3t/how-to/magisk-oxygen-os-8-0-op3-3t-t3689901
I'm not exactly sure if the boot image comes from a verified source or if the changes are non malicious, but many users on that thread confirm that the Boot image is from a pre open beta package. Try this method at your own risk.
Cheers!
You can use SuperSu SR5 with suHide to pass safety net. SuHide - https://forum.xda-developers.com/apps/supersu/suhide-lite-t3653855/page64
SuHide doesn't work, checked yesterday. Even though it does hide root from Android Pay, it cannot hide bootloader's unlocked status.
thes3usa said:
Here you go;
https://forum.xda-developers.com/oneplus-3t/how-to/magisk-oxygen-os-8-0-op3-3t-t3689901
I'm not exactly sure if the boot image comes from a verified source or if the changes are non malicious, but many users on that thread confirm that the Boot image is from a pre open beta package. Try this method at your own risk.
Cheers!
Click to expand...
Click to collapse
Is there a risk associated with running on SElinux permissive mode 24/7, or is it not unusual for people to do so? Does a regular Magisk installation, on Android N for example, change your SElinux mode to permissive?
Thanks.
trAnwhiz said:
Is there a risk associated with running on SElinux permissive mode 24/7, or is it not unusual for people to do so? Does a regular Magisk installation, on Android N for example, change your SElinux mode to permissive?
Thanks.
Click to expand...
Click to collapse
There is a risk on running an system with Permissive SELinux, and it's considered a bug when it's Permissive in a ROM.
And nope, a normal installation via any custom recovery, or via ADB, of Magisk will not change your SELinux mode.
Related
Hello Gentlemen,
I've recently got a OP3T running OOS 4.1.6 and i've been wanting to unlock the bootloader and root it. I've done my bit of a research and i'm little confused on what version of TWRP and SuperSU should i be using ? Do i still need to do the DM-Vertity bit? I'm considering just flashing:
TWRP: twrp-3.1.1-2-oneplus3t.img
SuperSU: SuperSU-v2.82-201705271822.zip
Would anyone be kind enough to point me to the latest guide for OP3T for OOS 4.1.6 ? Apologies,if this has been asked before.
Thanks!
Unlock your bootloader with fastboot oem unlock, then flash this version of TWRP:
https://drive.google.com/file/d/0B0pr-ZA5b-1peEVyVmpsbGZTbnM/view
Then you can flash either SuperSU: https://download.chainfire.eu/1113/SuperSU/UPDATE-SuperSU-v2.82-20170528234214.zip
Or Magisk (which I'd personally reccomend): http://tiny.cc/latestmagisk
starsky135 said:
Unlock your bootloader with fastboot oem unlock, then flash this version of TWRP:
https://drive.google.com/file/d/0B0pr-ZA5b-1peEVyVmpsbGZTbnM/view
Then you can flash either SuperSU: https://download.chainfire.eu/1113/SuperSU/UPDATE-SuperSU-v2.82-20170528234214.zip
Or Magisk (which I'd personally reccomend): http://tiny.cc/latestmagisk
Click to expand...
Click to collapse
Thanks mate. How is that TWRP you mentioned different from the other one for OP3T ?
Do i also need to flash the dm-verity disabler or is it not required if i flash the latest TWRP/SuperSU ?
Fermats_theorem said:
Thanks mate. How is that TWRP you mentioned different from the other one for OP3T ?
Do i also need to flash the dm-verity disabler or is it not required if i flash the latest TWRP/SuperSU ?
Click to expand...
Click to collapse
Could you link me to the TWRP you found? And I didn't have to flash dm-verity disabler while flashing it on my 3T with 4.1.6. Just be aware that all personal data is lost when the bootloader is unlocked.
starsky135 said:
Could you link me to the TWRP you found? And I didn't have to flash dm-verity disabler while flashing it on my 3T with 4.1.6. Just be aware that all personal data is lost when the bootloader is unlocked.
Click to expand...
Click to collapse
Hello mate,
This is what i've downloaded for TWRP.
https://dl.twrp.me/oneplus3t/twrp-3.1.1-2-oneplus3t.img.html
Fermats_theorem said:
Thanks mate. How is that TWRP you mentioned different from the other one for OP3T ?
Do i also need to flash the dm-verity disabler or is it not required if i flash the latest TWRP/SuperSU ?
Click to expand...
Click to collapse
Fermats_theorem said:
Hello mate,
This is what i've downloaded for TWRP.
https://dl.twrp.me/oneplus3t/twrp-3.1.1-2-oneplus3t.img.html
Click to expand...
Click to collapse
I'm not sure of the exact differences, but I think the blu_spark one I sent you might have fixed the dm-verity issues. I know that the one I sent you has no problems with dm-verity, so I'd go with that one just to be safe. There seem to be a lot of people bricking their phones by flashing the wrong one and I know this one works because I just flashed it yesterday.
starsky135 said:
I'm not sure of the exact differences, but I think the blu_spark one I sent you might have fixed the dm-verity issues. I know that the one I sent you has no problems with dm-verity, so I'd go with that one just to be safe. There seem to be a lot of people bricking their phones by flashing the wrong one and I know this one works because I just flashed it yesterday.
Click to expand...
Click to collapse
Do you have One Plus 3 or 3T ?
Fermats_theorem said:
Hello Gentlemen,
I've recently got a OP3T running OOS 4.1.6 and i've been wanting to unlock the bootloader and root it. I've done my bit of a research and i'm little confused on what version of TWRP and SuperSU should i be using ? Do i still need to do the DM-Vertity bit? I'm considering just flashing:
TWRP: twrp-3.1.1-2-oneplus3t.img
SuperSU: SuperSU-v2.82-201705271822.zip
Would anyone be kind enough to point me to the latest guide for OP3T for OOS 4.1.6 ? Apologies,if this has been asked before.
Thanks!
Click to expand...
Click to collapse
I got my phone 1 week ago and I just followed the guide here.
https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.475142/
It seems quite straightforward.
Can't see what seems not clear for you.
Unleashed by ONEPLUS 3T rooted
Fermats_theorem said:
I've done my bit of a research and i'm little confused on what version of TWRP and SuperSU should i be using ?
Click to expand...
Click to collapse
Typically, you want to use the latest files available. So in this case, yes that would be TWRP 3.1.1-2 and SuperSU 2.82 (or alternately Magisk 13.3, totally a matter of preference SuperSU versus Magisk).
There are some cases, where a new version may have some bugs. But I haven't heard of any of these particular versions.
Using versions that are a little bit older may still work. But anything that is too old, will sometimes cause problems. Especially when Android versions have changed, root methods updated, etc.
Thanks folks, i've unlocked the bootloader and rooted it. After flashing the recovery it was asking me for the password and it couldn't access the internal storage. I flashed dm verity and Magisk via sideload though.
Now, I'm wondering what ROM do i try ? I'm looking at Freedom OS + Franco / ElementalX. I need a OOS based rom with a good battery backup. Any suggestions would be appreciated
I was wondering what sort of changes take place when you root the G5s Plus. I got several patch updates so far. Will the latest update stay once I root the device? I just want to root the device for now, not install any custom roms.
I received an OTA with an unlocked bootloader so I don't see any reason why you wouldn't with root. This only works with the stock recovery though, if you have TWRP installed I don't think it will work.
William1020000 said:
I received an OTA with an unlocked bootloader so I don't see any reason why you wouldn't with root. This only works with the stock recovery though, if you have TWRP installed I don't think it will work.
Click to expand...
Click to collapse
Rooting involves 3 steps. Unlock bootloader, install TWRP, and install Magisk patch. Just unlocked bootloader doesn't mean phone is rooted.
androidman2018 said:
Rooting involves 3 steps. Unlock bootloader, install TWRP, and install Magisk patch. Just unlocked bootloader doesn't mean phone is rooted.
Click to expand...
Click to collapse
Unlikely that the OTA will install if you have TWRP and Magisk... I wonder if we can still use Flashfire to flash the OTA and keep recovery and root?
I’m sure this is very simple and I’m just not getting it…
got new moto x4 XT1900-1 from b&h
unlocked boot loader with motorola code
using windows fast boot was able to follow the "How to : Moto X4 Root & TWRP Recovery" bu Munchy on youtube to install twrp using payton 3.2.1-1
then installed Magish 17.1 which seems to be what actually rooted the phone as per confirmation by Root Check app shows 8.1.0
now I am getting constant ota notices of a security update OPWS28.3.2 and I download it and it fails which is apparently normal for a rooted phone.
Can I disable the root and update???…can this be done by turning off magic…or uninstalling it…or is this done by tarp?
I believe I should back up the recover image using twrp…then what?…find and boot to a stock image?
???
any info appreciated
tia
PS…I just tried the "topjohnwu Update OTA tutorial for v17" method in tips and tricks on here and it also said update failed???
jojojones said:
I’m sure this is very simple and I’m just not getting it…
got new moto x4 XT1900-1 from b&h
unlocked boot loader with motorola code
using windows fast boot was able to follow the "How to : Moto X4 Root & TWRP Recovery" bu Munchy on youtube to install twrp using payton 3.2.1-1
then installed Magish 17.1 which seems to be what actually rooted the phone as per confirmation by Root Check app shows 8.1.0
now I am getting constant ota notices of a security update OPWS28.3.2 and I download it and it fails which is apparently normal for a rooted phone.
Can I disable the root and update???…can this be done by turning off magic…or uninstalling it…or is this done by tarp?
I believe I should back up the recover image using twrp…then what?…find and boot to a stock image?
???
any info appreciated
tia
PS…I just tried the "topjohnwu Update OTA tutorial for v17" method in tips and tricks on here and it also said update failed???
Click to expand...
Click to collapse
What I did (might be an easier way but this was fast and easy):
1) Uninstall/remove Magisk.
2) Re-flash firmware over current system but don't do 'fastboot erase userdata'
3) Boot into your system and take all the OTA's
4) Re-install Magisk via TWRP
Took about 10 minutes. Longest part was waiting for OTA's to install.
Sorry...I'm new to all this. How do I reflash firmware?....use twrp app that is installed?
Magisk 17 supposedly has the ability to do this.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
If you try this, please let us know. I have been waiting for an update to test this function.
jhedfors said:
Magisk 17 supposedly has the ability to do this.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
If you try this, please let us know. I have been waiting for an update to test this function.
Click to expand...
Click to collapse
Did not work for me. Nothing has so far.
jojojones said:
Sorry...I'm new to all this. How do I reflash firmware?....use twrp app that is installed?
Click to expand...
Click to collapse
Use this guide:
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
Remove command "fastboot erase userdata" from script flash-all.bat/flash-all.sh.
jhedfors said:
Magisk 17 supposedly has the ability to do this.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
If you try this, please let us know. I have been waiting for an update to test this function.
Click to expand...
Click to collapse
I've tried this, and it didn't work. Ended up having to boot into TWRP, uninstall Magisk, and then reboot. Haven't bothered trying to update since I attempted that.
jhedfors said:
Magisk 17 supposedly has the ability to do this.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
If you try this, please let us know. I have been waiting for an update to test this function.
Click to expand...
Click to collapse
I spent a little while trying to apply OTA with magisk. The only way I was able to do it was to flash the stock firmware like everyone says. I could only find 8.0, so I had to flash the firmware, install 3 OTA's, then reinstall twrp/magisk.
The only thing I didn't try was installing magisk without twrp, which I believe is supported but I'm not sure. I think that might be the secret sauce to fixing it, but I'm not sure, and I haven't wanted to reflash and go through the whole process again.
tjololo12 said:
I spent a little while trying to apply OTA with magisk. The only way I was able to do it was to flash the stock firmware like everyone says. I could only find 8.0, so I had to flash the firmware, install 3 OTA's, then reinstall twrp/magisk.
The only thing I didn't try was installing magisk without twrp, which I believe is supported but I'm not sure. I think that might be the secret sauce to fixing it, but I'm not sure, and I haven't wanted to reflash and go through the whole process again.
Click to expand...
Click to collapse
If you have the xt1900-1 retus you can flash the android one firmware which is 8.1 (currently on the Aug 2018 security patch).
ptn107 said:
If you have the xt1900-1 retus you can flash the android one firmware which is 8.1 (currently on the Aug 2018 security patch).
Click to expand...
Click to collapse
I have the android one variant. Do you know where I can get the firmware? There's a new security patch and I'd like to try installing it with stock bootloader + magisk (installed from a temporary twrp boot) to see if that works with the OTA. I'd like to get the method working since android 9 is coming at some point.
tjololo12 said:
I have the android one variant. Do you know where I can get the firmware? There's a new security patch and I'd like to try installing it with stock bootloader + magisk (installed from a temporary twrp boot) to see if that works with the OTA. I'd like to get the method working since android 9 is coming at some point.
Click to expand...
Click to collapse
September 2018 OTA for Android One (Oreo 8.1):
Blur_Version.28.251.17.payton_fi.google_fi.en.US
Click to "Download" and save as ZIP file.
Only way how to apply OTA update with magisk rooted X4 is flash ROM using fastboot (august 2018 ROM is on AFH), remove command 'fastboot erase userdata' from script 'flash-all.bat', install september OTA from adb sideload/SD card and root again.
Comby_sk said:
September 2018 OTA for Android One (Oreo 8.1):
Blur_Version.28.251.17.payton_fi.google_fi.en.US
Click to "Download" and save as ZIP file.
Only way how to apply OTA update with magisk rooted X4 is flash ROM using fastboot (august 2018 ROM is on AFH), remove command 'fastboot erase userdata' from script 'flash-all.bat', install september OTA from adb sideload/SD card and root again.
Click to expand...
Click to collapse
Thanks, the rom is exactly what I was looking for, I just wasn't sure which one to use. I'd hate to install the wrong rom and mess something up.
EDIT: I did get a chance to try it and you're correct, there is no way to install an OTA to this device without fully reflashing the stock rom, taking the OTA, then installing Magisk. I tried the following steps:
1. Flash ROM given from androidfilehost
2. Reboot, wait for OTA notification
3. Boot to bootloader
4. use fastboot to temporarily boot twrp
5. flash magisk 17.1 zipfile
6. reboot to system, verify that magisk/root is installed
7. Uninstall magisk using magisk manager "Restore Images" as given in the tips.md file
8. Take OTA
the OTA still failed, so even though TWRP wasn't installed and it was still the stock recovery, I was unable to install the OTA. Shame, it'd be nice if we could get this to work, but oh well.
I know that the tutorial says to be on firmware B164, does that mean that Magisk is unavailable for Oreo on this device?
Thanks!
XDA XILFY said:
I know that the tutorial says to be on firmware B164, does that mean that Magisk is unavailable for Oreo on this device?
Thanks!
Click to expand...
Click to collapse
I used magisk v16.0 to root my PRA-LX1 8.0.0.374(C432), which worked fine. However since the most recent update (PRA-LX1 8.0.0.374(C432Patch01)) I have not been able to use any version of magisk without my phone not booting up.
This is just a simple patched boot.img so you can re-do magisk after the update to 9.0.7 if you don't care for bothering with TWRP.
Instructions are the same as the others:
adb reboot bootloader
fastboot boot patched_boot-9.0.7.img
Open the Magisk Manager App and click install. When prompted, choose Direct Install.
Profit!
Download Link: Google Drive: https://drive.google.com/file/d/13RDdihjVwt1oXlaxasRXqu75_QlFJV2T/view?usp=sharing
If you Need Magisk Manager, you can grab it from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v6.0.1/MagiskManager-v6.0.1.apk
Thanks! Works like a charm
Thank you sir. Got me back rooted after the local upgrade to 9.0.7 on my tmo variant
Glad it helped!
Dameon87 said:
Glad it helped!
Click to expand...
Click to collapse
Yea seriously way easier than that root program. Done in under 5minutes. No fuss no muss
I'm completely unrooted and stock. Do I have to unlock bootloader to flash this to use Magisk?
Fade2 said:
I'm completely unrooted and stock. Do I have to unlock bootloader to flash this to use Magisk?
Click to expand...
Click to collapse
Yes
Any confirmation for this working on the T-Mo variant? I am bootloader unlocked with TWRP and Magisk root already.
Dameon87 said:
This is just a simple patched boot.img so you can re-do magisk after the update to 9.0.7 if you don't care for bothering with TWRP.
Instructions are the same as the others:
adb reboot bootloader
fastboot boot patched_boot-9.0.7.img
Open the Magisk Manager App and click install. When prompted, choose Direct Install.
Profit!
Download Link: Google Drive: https://drive.google.com/file/d/13RDdihjVwt1oXlaxasRXqu75_QlFJV2T/view?usp=sharing
If you Need Magisk Manager, you can grab it from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v6.0.1/MagiskManager-v6.0.1.apk
Click to expand...
Click to collapse
how do u get the stock boot.img for 9.0.7 6t international
tswb said:
how do u get the stock boot.img for 9.0.7 6t international
Click to expand...
Click to collapse
Can either grab it from the Payload.bin file after extraction, or use dd to pull it.
treetolber said:
Any confirmation for this working on the T-Mo variant? I am bootloader unlocked with TWRP and Magisk root already.
Click to expand...
Click to collapse
Post #3?
guspeed said:
Post #3?
Click to expand...
Click to collapse
It works fine on the T-Mobile or International.
In almost every case things will work on both unless otherwise noted.
@Dameon87 is there any way you could possibly throw an OOS 9.0.7 stock kernel zip together if it's not too much to ask?
Thanks!
I'll stick with the TWRP method.. after this messed up my phone with no internet at all in wifi or modem I had to go hunt down stock boot image.
Stock Boot Image are found here.. https://forums.oneplus.com/threads/...ta-oxygen-os-repo-of-oxygen-os-builds.941780/
strictlyphat said:
Thank you sir. Got me back rooted after the local upgrade to 9.0.7 on my tmo variant
Click to expand...
Click to collapse
So you had the t-mob variant.
then you unlocked bootloader and flashed 9.0.6 giving you the international variant.
How did you upgrade to 9.0.7?? Surely not OTA right?
CCJ22 said:
So you had the t-mob variant.
then you unlocked bootloader and flashed 9.0.6 giving you the international variant.
How did you upgrade to 9.0.7?? Surely not OTA right?
Click to expand...
Click to collapse
Local upgrade.
I have a question.. nothing to do with this thread. I tried making my own thread but the xda app won't let me.. however here is my question.. I just tried updating my greenify module for magisk and it said install fails.. reason is because my API is 28 and the max should be 27??? It also told me to downgrade to a different Android.... Anyone ever year such a thing?? And is there a fix for this???
anthony10126 said:
I have a question.. nothing to do with this thread. I tried making my own thread but the xda app won't let me.. however here is my question.. I just tried updating my greenify module for magisk and it said install fails.. reason is because my API is 28 and the max should be 27??? It also told me to downgrade to a different Android.... Anyone ever year such a thing?? And is there a fix for this???
Click to expand...
Click to collapse
You should address your issue on the greenify4magisk thread. The dev posted explaining the reason for the issue you encounter at the last page. I don't think greenify is needed for OnePlus 6T. 1+6T has a feature called Adaptive Battery which looks like it trying to do the same thing as greenify.
TheKnux said:
@Dameon87 is there any way you could possibly throw an OOS 9.0.7 stock kernel zip together if it's not too much to ask?
Click to expand...
Click to collapse
Dear,
I have created a stock kernel from 9.0.7 as per in the attachment.
Thanks.