Develop Bugs

Chainfire Autoroot and COK1?

Hello friends,
Has Chainfire been updated to root the COK1 update? I am assuming it has, but...
I've tried a fresh download from his site and installation fails every time.
What could I be missing?
Thanks in advance for the help.
UPDATE: I figured out what I did wrong. It started with not reading the updates on how to root stock COK1 after updating. My bad. How do I recover now? After attempting to root the old way with CF_AutoRoot, I am now stuck in a bootloop with no access to Recovery. The only option I have is the Download tool for using ODIN.
Anyone have any ideas?

I think it's important to consider what Chainfire is offering with the recent update to CFAR. It's systemless root and the only purposeful use that applies, IMO, is for those that don't modify system, don't flash mods in recovery and would like to possibly utilize the full un-root option to take a future OTA update.
Chainfire warns that system has to be left alone and not even mounted. You might get away with installing busybox for systemless root but no guarantee that the OTA update will be possible with full un-root.
What makes this possible is the systemless root Chainfire uses. It's not compatible with system based root as we've long used in this forum. Flashing another system based root or system based SuperSU application may actually cause a boot loop. Flashing another kernel afterwards may also cause problems if not undoing the systemless root and flashing another system based SuperSU or su application.
If you didn't flash the stock tar and then latest CFAR to root, the only other method that it's prescribed for is stock ROM with stock kernel. And the fix for issues is to flash ROM with stock kernel and root again. Being that we don't have those around, the stock tar is the only way to get back to flash CFAR. Think of it as a root stock only tool with strict use prescribed. It's not intended for flashing sound mods, unofficial Xposed framework, or custom ROMs. All those will break the OTA update capability of the ROM and Xposed framework shouldn't be used on Odex ROM unless it's the finishing touch on a ROM.
Long post but systemless root requires consideration before using it. It's not for those that frequently flash, try other ROMs and mods and Xposed but for those content to sit at mostly stock updates and wait patiently for updates from Sprint.
I'm not sure why you're having an issue. Bad download or you've tried to flash another kernel or superuser application would be my guess. And the only solution I can think of is to start over with Odin, check your md5 where available and consider if CFAR systemless root fits you or not. You could just consider flashing recovery and custom ROM if you consider CFAR systemless root is not what you want.
If you continue having problems with boot loop, consider Philz CWM recovery and wipe everything but extSdCard and flash a ROM. Or Odin stock tar for stock recovery and factory reset. If using stock tar to recover, use latest Odin 3.10.7 and uncheck the option "auto reboot". When it finishes the flash and shows success, pull USB and battery and boot to recovery and wipe, power down, and Odin stock tar with Odin defaults, letting it auto boot this time.
IIRC, the symptom you describe occurred when flashing the old CFAR on recent updates. Maybe delete all CFAR copies and download again. Then start with the paragraph above.
Sent from my SM-N920P Note 4 via Tapatalk

samep said:
I think it's important to consider what Chainfire is offering with the recent update to CFAR. It's systemless root and the only purposeful use that applies, IMO, is for those that don't modify system, don't flash mods in recovery and would like to possibly utilize the full un-root option to take a future OTA update.
Chainfire warns that system has to be left alone and not even mounted. You might get away with installing busybox for systemless root but no guarantee that the OTA update will be possible with full un-root.
What makes this possible is the systemless root Chainfire uses. It's not compatible with system based root as we've long used in this forum. Flashing another system based root or system based SuperSU application may actually cause a boot loop. Flashing another kernel afterwards may also cause problems if not undoing the systemless root and flashing another system based SuperSU or su application.
If you didn't flash the stock tar and then latest CFAR to root, the only other method that it's prescribed for is stock ROM with stock kernel. And the fix for issues is to flash ROM with stock kernel and root again. Being that we don't have those around, the stock tar is the only way to get back to flash CFAR. Think of it as a root stock only tool with strict use prescribed. It's not intended for flashing sound mods, unofficial Xposed framework, or custom ROMs. All those will break the OTA update capability of the ROM and Xposed framework shouldn't be used on Odex ROM unless it's the finishing touch on a ROM.
Long post but systemless root requires consideration before using it. It's not for those that frequently flash, try other ROMs and mods and Xposed but for those content to sit at mostly stock updates and wait patiently for updates from Sprint.
I'm not sure why you're having an issue. Bad download or you've tried to flash another kernel or superuser application would be my guess. And the only solution I can think of is to start over with Odin, check your md5 where available and consider if CFAR systemless root fits you or not. You could just consider flashing recovery and custom ROM if you consider CFAR systemless root is not what you want.
If you continue having problems with boot loop, consider Philz CWM recovery and wipe everything but extSdCard and flash a ROM. Or Odin stock tar for stock recovery and factory reset. If using stock tar to recover, use latest Odin 3.10.7 and uncheck the option "auto reboot". When it finishes the flash and shows success, pull USB and battery and boot to recovery and wipe, power down, and Odin stock tar with Odin defaults, letting it auto boot this time.
IIRC, the symptom you describe occurred when flashing the old CFAR on recent updates. Maybe delete all CFAR copies and download again. Then start with the paragraph above.
Sent from my SM-N920P Note 4 via Tapatalk
Click to expand...
Click to collapse
This was very helpful information. Thank you for taking the time to write this up
I'm up and running again.

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).

Magisk/TWRP Recovery and Upgrading

It's been awhile since I've used a custom recovery. Since I've had this phone I've used systemless root and flashfire to install OTA's and that has worked fairly well. Recently my phone bootlooped and google sent me a new one.
I just unlocked it, installed TWRP and Magisk, but was wondering what the best way to upgrade the phone would be.
1I've heard flashfire works with Magisk, but I never had much luck with custom recovery's and updating with flashfire.
If flashfire doesn't work, what would be the best way to update?
When 7.1.2 is released, could I just flash the system, radios, etc. from fastboot and then reflash magisk from TWRP and be upgraded?

I had to uninstall magisk, reboot, download the ota via the system menu and install it, then re-flash twrp, then boot recovery and flash magisk, then re-add my modules and re-enable systemless adblock

Best way to upgrade to O from current state? Stock 7.1.1 rooted.

So I have a Play Store Pixel XL running stock 7.1.1, rooted, with TWRP 3.0.2-0-RC1 recovery.
Most upgrade guides I've read seem to assume stock recovery, or no root to start, or some such.
What do I need to do to get to Stock Android O, rooted? If I need to wipe the phone I can, but I'd prefer not to if I can avoid it.
Thanks!

If you don't want to wipe just update through factory image, just open the factory zip, open flash-all file and remove "-w" from last line, then execute it (update without wipe)
But I suggest to flash the stock factory image with the "-w" to make a clean install, flashing major release like 7.x -> 8.x is always better wipe to avoid potential issues.
But yes, you can first give a try without wipe and only if you find bugs try wiping. Your choice.

simply flash the OTA, then re-root

xraystyle said:
So I have a Play Store Pixel XL running stock 7.1.1, rooted, with TWRP 3.0.2-0-RC1 recovery.
Most upgrade guides I've read seem to assume stock recovery, or no root to start, or some such.
What do I need to do to get to Stock Android O, rooted? If I need to wipe the phone I can, but I'd prefer not to if I can avoid it.
Thanks!
Click to expand...
Click to collapse
Use full unroot in supersu. Then take ota. Then root again after upgrading to O

Thanks for the help everyone, you pointed be in the right direction.
In the event that it might help someone else, here's what I ended up doing:
1. I downloaded the OTA, booted into the TWRP I had currently installed, and then sideloaded the OTA.
2. I used ADB to push the newest TWRP flashable zip, the latest SuperSU, and the latest SU-Hide to /sdcard on the device.
3. I then used the most recent TWRP bootable img, booted into it with fastboot, and used it to flash the TWRP zip I had previously pushed to the phone storage. I then had the OTA with the latest TWRP installed on the phone.
4. Finally, I rebooted to recovery on the phone (latest TWRP now instead of stock), and flashed SuperSU and SU-Hide.
I'm now stock, rooted, on O. No wipe necessary, kept all my apps and data. So far the OS itself has been entirely stable. I had an issue or two with a few apps after the upgrade, but those were fixed with a quick re-install. Except for Better Terminal Emulator Pro, seems it doesn't want to work on Oreo and it's no longer under active development. It's fine though, there's other terminal emulators out there.
Thanks again for the help!

xraystyle said:
3. I then used the most recent TWRP bootable img, booted into it with fastboot, and used it to flash the TWRP zip I had previously pushed to the phone storage. I then had the OTA with the latest TWRP installed on the phone.
Click to expand...
Click to collapse
Which version of TWRP do you have TWRP working with Oreo 8.0?
I can boot into the modded TWRP 3.1 (fastboot boot twrp-3-1-pixel-bootable-mod.img) but AFAIK there is no working flashable recovery for 8.0 yet.

quick question, are the steps the same for stock root 7.1.2? I've never installed twrp. I've fastbooted to it to root and that's it. I'm familiar with that as I've sideloaded all the ota security updates and the re-rooted.
my main question is su-hide required? I have never done it and have no reason to that I'm aware of. Seems all the guides I see involve su-hide and flashing kernels etc. I've never changed kernels since having the pixel. Really just want root for adaway.
I plan to do a clean install of O and then hope to root with fastboot twrp to flash supersu.

gordonlw said:
quick question, are the steps the same for stock root 7.1.2? I've never installed twrp. I've fastbooted to it to root and that's it. I'm familiar with that as I've sideloaded all the ota security updates and the re-rooted.
my main question is su-hide required? I have never done it and have no reason to that I'm aware of. Seems all the guides I see involve su-hide and flashing kernels etc. I've never changed kernels since having the pixel. Really just want root for adaway.
I plan to do a clean install of O and then hope to root with fastboot twrp to flash supersu.
Click to expand...
Click to collapse
That's how I did it. I don't use suhide.

Does the -w in the .bat file format or wipe the data? I want a clean clean , o-fresh in the morning feeling kind of wipe

toknitup420 said:
That's how I did it. I don't use suhide.
Click to expand...
Click to collapse
Thanks! What I ended up doing:
Decided to try and unroot and take the ota. super-su full unroot would not work. so I fastbooted to the mod twrp and flashed UPDATE-unSU. I then took the ota. then fastbooted to mod twrp and flashed super-su. worked perfect!

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.