Develop Bugs

Update oxygen 3.2.6 removed my root. Please help. Also just joined xda.

My oneplus 3 was rooted (oxygen 3.2.5 maybe) but I installed the update 3.2.6 today from phone by going into settings. When the phone got updated my root does not work anymore. Please help.
I forgot how I rooted my phone before but it was still on android 6 when I rooted.
When I reboot I still get the black screen saying the device can't be trusted because xxxxxxxxxx Is unlocked, dont remember what.
Usb debugging is on as well as oem unlocked ( these options are still showing unlocked when i went to settings but don't know if they are ACTUALLY unlocked.
Xposed luck patcher, etc not working
Root checker says root not installed properly
Used twrp before.
Also is there any way that I can re-root my phone again without data loss?
Its my first post ever in any form so dont know about posting much.
You can mail me too at [email protected].
Thanks

Try flashing Super su manually from Recovery

Flash latest SuperSU (I think it is 2.78) in twrp. Flash xposed module in twrp too

If you did the official update from Settings > System Updates, then you are most likely back to stock recovery as well. You're going to have to re flash twrp before you can flash root and xposed. You will not lose data by performing any of these steps as your bootloader is still unlocked.

http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799

Download twrp
Boot to fastboot
fastboot boot sometwrp.img
Flash supersu from temporary twrp

Hw4ng3r said:
If you did the official update from Settings > System Updates, then you are most likely back to stock recovery as well. You're going to have to re flash twrp before you can flash root and xposed. You will not lose data by performing any of these steps as your bootloader is still unlocked.
Click to expand...
Click to collapse
If you had root and custom recovery (TWRP) then you couldn't have updated by this method as it wouldn't have worked. You need to reflash SuperSU in TWRP as others have stated.

Much simple: from recovery (hope you're having TWRP installed) flash latest SuperSU and Xposed zip file.
Then Wipe Cache/Dalvik, then reboot in System.
If you won't to lose root, you should consider a custom rom like FreedomOS, that provides SuperSU binary by itself (even Xposed, if I'm not wrong).

Android Pay and unlocked bootloader

I finally decided to get everything backed up so I could unlock my bootloader. Everything went as described that it would. Unfortunately Android now has their app check for not just root but also for unlocked bootloader and/or any custom recovery?? So essentially if you want android pay, your phone has to be completely stock? That's beyond ridiculous as our phones are not any less secure just because of these things we like to do. Are there any current flashable workarounds? I didn't even flash TWRP yet nor do I have SU installed... Just bootloader and that's enough to trip the app to say sorry you can't use.
Thanks all

DroidJay123 said:
I finally decided to get everything backed up so I could unlock my bootloader. Everything went as described that it would. Unfortunately Android now has their app check for not just root but also for unlocked bootloader and/or any custom recovery?? So essentially if you want android pay, your phone has to be completely stock? That's beyond ridiculous as our phones are not any less secure just because of these things we like to do. Are there any current flashable workarounds? I didn't even flash TWRP yet nor do I have SU installed... Just bootloader and that's enough to trip the app to say sorry you can't use.
Thanks all
Click to expand...
Click to collapse
This is the only solution at this moment. I'm using it and I can pay by phone withouth problems...
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

@BolintsMiki had a solution in a different thread:
You can use Android Pay with the latest Magisk. I think Xposed breaks Android Pay although.
The process to get Android Pay working with root is:
1. Flash the stock ROM again (or any custom ROM that doesn't come with root by default eg: LineageOS)
2. Flash your favorite kernel if you want to. (Any kernel, or none if you don't want to)
3. Delete /data/magisk.img and /data/su.img if you have them. (Just to give it a fresh start)
3. Flash Magisk. It will automatically install MagiskSU, which is the default (and recommended) root for Magisk.
4. Reboot.
5. Install Magisk Manager from the play store.
6. Go into the settings in Magisk Manager and enable Magisk Hide.
7. Reboot.
8. Android Pay should work.

AlvieOP said:
@BolintsMiki had a solution in a different thread:
You can use Android Pay with the latest Magisk. I think Xposed breaks Android Pay although.
The process to get Android Pay working with root is:
1. Flash the stock ROM again (or any custom ROM that doesn't come with root by default eg: LineageOS)
2. Flash your favorite kernel if you want to. (Any kernel, or none if you don't want to)
3. Delete /data/magisk.img and /data/su.img if you have them. (Just to give it a fresh start)
3. Flash Magisk. It will automatically install MagiskSU, which is the default (and recommended) root for Magisk.
4. Reboot.
5. Install Magisk Manager from the play store.
6. Go into the settings in Magisk Manager and enable Magisk Hide.
7. Reboot.
8. Android Pay should work.
Click to expand...
Click to collapse
May I ask how to flash Magisk without unlock bootloader?
It was failed to flash Magisk when I used stock recovery and I could not boot into TWRP without unlock bootloader
Thanks

You need an unlocked bootloader. Magisk just tricks SafetyNet (Android Pay) to think you have a locked bootloader and no root.

It does trick the Bootloader state? ORLY? For that to work I installed a custom kernel. My sig always shows the recent status of my phone. ^^

I had SuperSU + Magisk + ElementalX. Migrated to Magisk with MagiskSU + ElementalX. It's easy:
1. Download unSU script and flash it in TWRP.
2. Reflash OxygenOS ROM (to remove SuperSU from boot image).
3. Flash Magisk.
4.. Reboot system.
5. Flash ElementalX (it didn't work, when I flashed it just after Magisk) if desired.
In Magisk Manager settings you have to enable Magisk Hide and make sure that Android Pay and other apps, which require no root/locked bootloader, are selected. Reboot after that. Of course in really you have root and bootloader unlocked. Android Pay is working very well with such configuration.

[help] On Oreo, 8.1, latest, trying to install Magisk, and unable to install

I was following the guide at:
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279
I started with a Pixel XL 7.2, unlocked, magisk, etc. I uninstalled magisk, updated all OTA updates, and then began the thread above.
I followed 6 - Extract boot.img from Fcatory Image and fastboot boot.img
The continued with 7 - Root with Magisk
booted to twrp, flashed twrp, no issues.
Rebooted to recovery, flashed elementalX kernel 3.04, and added magisk v16.3
No errors
Rebooted phone, and upon boot, got a message:
"there's an internal problem with your device"
From what I've read, that is not really an issue and has something to do with some things not matching, so, an update to magisk in the future will resolve it. So no big deal.
However, I don't see magisk manager, and have no root.
I reboot back to recovery, uninstall magisk manager, and reboot phone.
Still get the internal problem message, but no big deal.
I reboot back to recovery, and try flashing magisk again.
Still no manager, still no root (from root checker).
I try installing the magisk manager app directly, but, the APK cannot install, and just gives a generic error message of "app not installed".
Reboot to recovery, uninstall magisk again, wipe cache. Reboot, still same internal problem message.
Try to flash magisk 16.0 instead, repeat the above, and still no root, and can't install APK.
So, just kind of stuck at this point. Phone tells me that elementalx installed without an issue though, so, just seems like magisk is the last step. Any help is greatly appreciated. Thank you.

The message you get upon boot is from the kernel, nothing to do with magisk. not that it matters, it doesnt affect anything.
According to EX thread and EX's official websites "How to install" guide, you are supposed to install magisk first. Thats how i do it.
what you need to do is......
Reflash the stock factory boot img and let it boot.
Reboot to bootloader flash or boot twrp, and install magisk.
Reboot let it boot all the way.
Then reboot to bootloader flash/boot twrp and install EX.
Reboot.
---------- Post added at 07:14 PM ---------- Previous post was at 07:12 PM ----------
Double post, sorry, butt.......
https://elementalx.org/how-to-install/
Read part one step three.
"3. Root your device (optional)
If you would like root access to your device, install SuperSU or Magisk. This should be done before installing ElementalX. Other root methods are NOT recommended. Root access will give you full control over your device and allow you to change kernel settings and tweak your device. To install SuperSU or Magisk, download to your device, reboot to recovery and install the zip you downloaded. Make sure you reboot into your system after the installation process completes. Ensure that root is correctly installed and working.
At this step, I usually make a backup of the stock rooted kernel. Now that you are rooted, you can do this very easily in EX Kernel Manager by selecting Tools->Kernel backup. This will save the boot.img."

Thank you for the help, will try it when I get a chance. The guide that I was following said for elementalx, flash kernel first. For exnoshadez, to do magisk first, for other kernels, do kernel first. I had read that some kernels need to go first, while others magisk needed to go first, and since that guide was specifically oreo, I thought kernel was first. But, thanks! Will try going back to factory boot image and progressing through.

So, I flashed back to stock boot.img, booted twrp, flashed twrp, and flashed magisk. But, Magisk still did not show up. I tried installing the magisk manager apk, but still get "App not installed" when trying that. At least the "there's an internal problem with your device" message went away.
Any other ideas on what to check when flashing, or why it's not "taking"?
Thanks again for the help.

Found out the problem:
Had to do:
adb uninstall com.topjohnwu.magisk
The key here was that I was upgrading from 7.2 to 8.1, and in the uninstall of magisk, I guess it left some remnant behind which prevented it from installing the new version.
The way I discovered this was trying to use adb to install the magisk manager apk, and that gave me the error:
adb: failed to install MagiskManager-v5.7.0.apk: Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE: Package com.topjohnwu.magisk signatures do not match the previously installed version; ignoring!]
Then, I simply uninstalled it, then flashed using twrp again, and it worked fine.

How to recover magisk root after uninstall

As the title says, I have uninstalled magisk root access on my SM-N975F and I now would like to know how to recover it. I have tried to flash the magisk zip through TWRP, which I still have. The installer did not return any error, but when rebooting magisk manager says that I don't have root access. I have tried holding Vol.UP+Power Button for the 2 boot screens and then releasing to make sure I don't boot into TWRP, but instead of booting into the system with magisk it just boots into TWRP. Is there any way to gain back root access without having to go through the intial procedure or rooting considering I have TWRP?

Magisk problems since most recent OTA

I have the xt-1952-4 variant. When I first got this phone and tried the various methods to flash and install Magisk, it worked then. Since then for whatever reason, whether it be to fix a soft brick or restore a backup, and having flashed the most recent (March 2020) stock ROM for this phone, never I repeat never have I gotten Magisk to take right. I don't know if it's Magisk or the security updates from Google or Motorola but it's made flashing root nonexistent, even yet while my bootloader is unlocked. Every thread here or on any Google search to install Magisk or root and install TWRP seems obsolete now. Anyone else have this problem And how to perhaps fix it? Am I the only one with such a problem? Thanks.

theburrus1 said:
I have the xt-1952-4 variant. When I first got this phone and tried the various methods to flash and install Magisk, it worked then. Since then for whatever reason, whether it be to fix a soft brick or restore a backup, and having flashed the most recent (March 2020) stock ROM for this phone, never I repeat never have I gotten Magisk to take right. I don't know if it's Magisk or the security updates from Google or Motorola but it's made flashing root nonexistent, even yet while my bootloader is unlocked. Every thread here or on any Google search to install Magisk or root and install TWRP seems obsolete now. Anyone else have this problem And how to perhaps fix it? Am I the only one with such a problem? Thanks.
Click to expand...
Click to collapse
It's only possible to install twrp if you also install a GSI. Twrp will not work on stock. Magisk is also incompatible with twrp, the two can never be installed together no matter what. This is a magisk problem. Magisk uses the recovery partition, so it can use mirrors to make changes (systemless root). Twrp also needs to occupy the same place, because twrp is a custom recovery. Because of this conflict, they can't coexist. Magisk needs you to boot into "recovery" to boot the normal OS with root, and twrp needs you to boot into recovery to operate normally. So it's one or the other.
Unless the developer of Magisk decides to use system root, all newer devices will continue to have this problem. I highly doubt that will change anytime soon. The foundation of Magisk is built on being systemless, and so are all the modules for it.
If you want to use magisk, install the app, and patch your boot.img with it as "recovery", then flash it with fastboot. You must always "reboot recovery" to keep root afterwards.