Hey guys,
I've just received my replacement phone and I'm trying to route it.
It came with 4.3 already installed.
I've unlocked the bootloader and installed CWM but want to s-off so I'm trying to root my stock (Three UK branding) ROM.
I've trying flashing superuser an superSU from recovery (CWM and TWRP) and they flash successfully and install onto my phone but don't actually give me root access!?
It also won't let me update the binaries in SuperSU
Any ideas?
Thanks in advance.
Edit - I'd somehow managed to download an outdated version on SuperSU. It's working now. Silly me.
I was wondering if there is root for the model VIE-L09C432B370 I already have the twrp installed I just want to know that root is indicated and if it is not too much to ask me to pass the link to install it properly
Can't you just flash SU in twrp?
Hi there.Anybody knows how to safty unroot EVA-L09 with stock b383rom.Thank you for the mountain:good:
there is 2 ways.
full unroot with root software you using.
flash boot.img from fastboot.
i gues, you using supersu root solution if need to unroot. best solution is dload firmware, will lose all data in phone, it will reset. and all you changed with root will be lost.. so, dop you realy want unroot? is pokemon go reason ?
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.
Hello guys. I have problem rooting my phone.
I can install TWRP but root doesn't work. I tried rooting with all methods and installing rooted ROMs. Right now I am on pixel experience ROM and it won't install rooted. BL is unlocked and I tried all methods to root. I have TWRP 3.4.0.0.
Any idea?
comnic5 said:
Hello guys. I have problem rooting my phone.
I can install TWRP but root doesn't work. I tried rooting with all methods and installing rooted ROMs. Right now I am on pixel experience ROM and it won't install rooted. BL is unlocked and I tried all methods to root. I have TWRP 3.4.0.0.
Any idea?
Click to expand...
Click to collapse
It is possible that it is rooted but Magisk Manager might not be showing up, I suggest downloading Magisk Manager APK and see what the manager says.