Database Develop

Android Pay on OOS Open Beta 17

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.

OTA updates with Magisk?

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.

[Help] Is it Possible For Me To Root (with Magisk) My PRA-LX1? [B269][Oreo]

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.

OTA update without losing Root?

Mi 9 has an update from 10.2.24 to 10.2.26. I would like to ask if there's a way to update my phone to the latest update without losing my root. Thanks!

just flash magisk after updating

mbc663 said:
just flash magisk after updating
Click to expand...
Click to collapse
I the patched boot img for 10.2.26 isnt yet available.

mbc663 said:
just flash magisk after updating
Click to expand...
Click to collapse
For me the update quit with mistake on my rooted phone, even via twrp and xiaomi updater.

How to install ota on rooted phone?

I just received an ota update for miui 12 on my ki 9t pro global version, can anyone tell me how to install this on a phone which has twrp and magisk?

jasoncalora said:
I just received an ota update for miui 12 on my ki 9t pro global version, can anyone tell me how to install this on a phone which has twrp and magisk?
Click to expand...
Click to collapse
You can do the OTA update, then reinstall TWRP and Magisk.
Or you can download the full MIUI 12 recovery ROM and install that in TWRP, but you'll still need to reinstall Magisk after.

thanks, just making sure it's safe for rooted and unlocked phones

Totally safe.
It seems I always have to download the update
twice, before it actually installs. Other than that
there are no problems. You lose root of course,
but that's fixed in a jiffy.
:good:

i also want to flash otà. should i flash fastboot rom or recovery rom by Twrp ??
Also can i flash higher version of android and miui by TWRP? For example : going from miui 10 android 9 to miui 11 android 10 ??? pls reply

Viper1000 said:
i also want to flash ot
Click to expand...
Click to collapse