I fixed my own problem:
The full wipe will not remove root.
If you lose root, you can re-root with this tutorial: http://theunlockr.com/2014/04/13/root-samsung-galaxy-s4-t-mobile/
The CHRoot method still works; I just rooted another device last night so I figured I'd post that here as well.
Updated
Root can be achieved by flashing TWRP and then CF's supersu.zip from TWRP too.
Link to CF's website: https://autoroot.chainfire.eu/
Related
Hello, (sorry for my bad english)
I lost my root after I updated the cm 11 for safestrap. I got super su pro with the survival mode activated, how can I regain root?
Thanks.
Survival mode can be helpful when using OTA / dirty flash updates (from various ROMs in general) but if you flash an entire partition, that's a liiittle bit different.
Just flash the SuperSU ZIP from Chainfire: enter safestrap recovery and install it from there.
You should have root access again, reply if not (ofc. you will ^^).
Hi!
So my HTC was rooted and all fun, but I couldn't install the OTA update due to TWRP recovery. So I unrooted and uninstalled TWRP. And then I received the official OTA update from HTC. Now my phones runs marshmallow and its smooth AF! I'm happy with it, but my QUESTION IS, How to root it again? I did try to root it and looked up for Youtube videos to figure it out, but I failed! Can someone help?
P.S: I couldn't find and videos on Youtube for rooting HTC one M8 on marshmallow.
1) Flash TWRP.
2) Flash SuperSU 2.67 BETA. It will flash superuser in systemless mode by patching the boot image. No other method as of now if you want root in system.
PS : AND REMEMBER, if TWRP shows you with an option to flash SuperSU after you're done flashing and/or later on whenever accessing your recovery, PRESS "DO NOT INSTALL" as flashing it using this option will mess up your system. Root will be present by flashing 2.67, it's just that TWRP isn't able to detect it.
Patched boot image is for "traditional" root (which modifies the system). The new "systemless" root method does not install the patched boot image.
Good morning...
I've had my S6 with 6.0.1 "CDP2" "rooted and with twrp 3 for about one week.
However late last nite I noticed I lost root. "There is no SU binary installed and Supersu cannot install it".
Recovery was updated and default was installed..
I tried to root again, successfully "stated by ODIN" re-boots and goes through the phase as establishing TWRP, then default recovery is re-installed...
Any ideas ?
Thanks..
I have run into the exact same issue. Lost root with latest security update yesterday and can't seem to get it back
I was able to regain root. My mistake was trying to flash an older SuperSU. When I flashed the 2.71 version everything went fine. I did loose root after the OTA just needed to flash the right SuperSU to regain it.
Sent from my SM-G920P using XDA-Developers mobile app
I also need to flash new Super SU. But my recovery is not TWRP. It's Android recovery and has 3 options for Install update : Through ADB, External storage or Cashe. Which option to choose?
IronMaidenBG said:
I also need to flash new Super SU. But my recovery is not TWRP. It's Android recovery and has 3 options for Install update : Through ADB, External storage or Cashe. Which option to choose?
Click to expand...
Click to collapse
Flash the latest CF-Auto root, then flash TWRP. CF-AUTO root will knock out the kernels protections and allow you to flash TWRP.
kbless60 said:
I was able to regain root. My mistake was trying to flash an older SuperSU. When I flashed the 2.71 version everything went fine. I did loose root after the OTA just needed to flash the right SuperSU to regain it.
Sent from my SM-G920P using XDA-Developers mobile app
Click to expand...
Click to collapse
Same thing happened to me. I had an OTA security update, lost root, but reflashed 2.71 SuperSu using TWRP to regain root.
Tutorial Available
There is a tutorial, including links, available here: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862
Specific instructions for rooting after PD3 are here: http://forum.xda-developers.com/showpost.php?p=66978384&postcount=41
I'm trying to install TWRP on my 10 since it's working for Nougat now. Problem is, the flash failed due to S-ON. The instructions for Sunshine state that after S-OFF, you need TWRP to remove encryption from the device, by wiping data and performing a factory reset. That's a bit of a dilemma, whole reason I'm doing this is to install TWRP.
If it makes any difference, I'm rooted using Chainfire's SuperSU method which bypasses TWRP. The recovery is "stock" but tweaked by CF to load SuperSU binaries and such.
Can I use my "stock" recovery to remove encryption after S-OFF, or am I in a bit of a bind?
veer10 said:
I'm trying to install TWRP on my 10 since it's working for Nougat now. Problem is, the flash failed due to S-ON. The instructions for Sunshine state that after S-OFF, you need TWRP to remove encryption from the device, by wiping data and performing a factory reset. That's a bit of a dilemma, whole reason I'm doing this is to install TWRP.
If it makes any difference, I'm rooted using Chainfire's SuperSU method which bypasses TWRP. The recovery is "stock" but tweaked by CF to load SuperSU binaries and such.
Can I use my "stock" recovery to remove encryption after S-OFF, or am I in a bit of a bind?
Click to expand...
Click to collapse
As I posted in your other thread, you don't need S-off to flash twrp, just need an unlocked bootloader which you said you already have. Just follow the instructions from the twrp thread.
I would like to get to the point where I'm able to OTAs instead of manually flashing factory images but I'm not passing safety net when I uninstall magisk and reinstall it when the update reaches step 2. I'm not sure what is causing the update to fail. I recently switched from system root via supersu (obviously wouldn't pass safety net) to systemless root with magisk. I'm running 8.1 feb. security update with the following apps installed: adaway, busybox, CF. Lumen, greenify, magisk manager, & titanium backup. (rootless substratum & andromeda as well).
I do not have TWRP installed, I only boot to it to flash magisk and kept TWRP systemless. The purpose for this post I guess is to try understand which of the installed apps listed may affect the /system files. I was under the impression that since i now root systemlessly I would be able to accept OTAs. What am I missing here?
As far as I know you cannot be rooted and/or have a custom recovery. You can have a unlocked bootloader but you have to be stock in order to receive OTAs.
I really don't get the problem. Just flash full ota file via TWRP and then flash again magisk and twrp again.
With TWRP, flashing full OTA files is a breeze... I think incremental otas can be done in the same way, but better to flash full ota files...
onesolo said:
I really don't get the problem. Just flash full ota file via TWRP and then flash again magisk and twrp again.
With TWRP, flashing full OTA files is a breeze... I think incremental otas can be done in the same way, but better to flash full ota files...
Click to expand...
Click to collapse
......... you can flash full OTAs from TWRP?? I knew I was missing something.
So download the full OTA to internal storage. flash in TWRP. then magisk and if i choose not to install TWRP (i usually only boot to it), I'm done?
onesolo said:
I really don't get the problem. Just flash full ota file via TWRP and then flash again magisk and twrp again.
With TWRP, flashing full OTA files is a breeze... I think incremental otas can be done in the same way, but better to flash full ota files...
Click to expand...
Click to collapse
Wait, doesn't flashing the full OTA get rid of TWRP?
Do you have instructions how to install full images without TWRP being uninstalled?
Also... How do you get ota to install if the original bootloader is replaced by twrp? I thought installing twrp permanently voids the possibility to install ota...!