Didn't realized and tried to install SuperSU on CM13. Got a bootloop which I fixed with unSU.zip (http://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459). Now I have no root even though root is enabled in developer options. Any suggestions?
Me too, just encountered this problem
Edit: Dirty flashed ROM from update, seems to be working now.
iammarrk said:
Didn't realized and tried to install SuperSU on CM13. Got a bootloop which I fixed with unSU.zip (http://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459). Now I have no root even though root is enabled in developer options. Any suggestions?
Click to expand...
Click to collapse
Wht did you flashed supersu when root was already available in developer options? :/
CM13 already have su binaries and to enable them you have to go in developer options -> root. If you flashed Sultan CM13 (which i really recommend) you have to install SU from here. Remember to keep the TWRP updated.
EDIT: i read again the first post. I guess unSU removes all the binaries, the ones from CM as well. Flash again the same ROM and gapps without wiping data and you should be good to go
Related
ive downloaded and installed the hammerhead omnirom nightly from their site and it works great except for the fact that my apps cant get root access. Anyone know why this is and how to get root access back.
ive also installed superuser, though when i go to install the latest binary through the app, the latest version of it (3.1.1) doesnt get installed, it stays with the default "legacy" version
TheAtheistOtaku said:
ive downloaded and installed the hammerhead omnirom nightly from their site and it works great except for the fact that my apps cant get root access. Anyone know why this is and how to get root access back.
ive also installed superuser, though when i go to install the latest binary through the app, the latest version of it (3.1.1) doesnt get installed, it stays with the default "legacy" version
Click to expand...
Click to collapse
Root has not been merged into OmniRom yet, so please flash the Super SU zip in recovery.
Super SU v1.80
ryukiri said:
Root has not been merged into OmniRom yet, so please flash the Super SU zip in recovery.
Super SU v1.80
Click to expand...
Click to collapse
ah, didnt know that, first time using omni. thanks
Just flashed the factory Rom and got everything set up. I flashed TWRP then tried to flash the latest SuperSu to get root and it installed it but when I went to open it it would say that I don't have any binaries installed and I can't uninstall SuperSU either. I tried to install CWM Recovery and refresh it through there but I still have the same issues... :/ What am I doing wrong or how can I get my phone rooted properly? Thanks for any help!
Nocturnal86 said:
Just flashed the factory Rom and got everything set up. I flashed TWRP then tried to flash the latest SuperSu to get root and it installed it but when I went to open it it would say that I don't have any binaries installed and I can't uninstall SuperSU either. I tried to install CWM Recovery and refresh it through there but I still have the same issues... :/ What am I doing wrong or how can I get my phone rooted properly? Thanks for any help!
Click to expand...
Click to collapse
You need to flash a kernel that is permissive and then flash SuperSU there are a few in the forums if you search you shall find them
Instead of a permissive kernel, simply use Chainfire's AutoRoot, which will flash a more secure kernel and SuperSU automatically. You don't even need TWRP for this. http://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip
Go to http://autoroot.chainfire.eu/ to get AutoRoot for other devices.
aalaap said:
Instead of a permissive kernel, simply use Chainfire's AutoRoot, which will flash a more secure kernel and SuperSU automatically. You don't even need TWRP for this. http://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip
Go to http://autoroot.chainfire.eu/ to get AutoRoot for other devices.
Click to expand...
Click to collapse
So I flash this in ADB? Is the secure kernel the same as stock? and if I were to flash a customer kernel like FK would I lose root? Sorry for all the questions just trying to clarify some stuff so I'm not completely ignorant to what I'm doing lol
There's a batch file that does it. You run it in the bootloader, not ADB.
FK has a Lollipop compatible kernel, but try and root stock first. Then flash FK's Lollipop version (it's different) and run CF AutoRoot again. Just to be sure things are working. Personally, I'm going to use stock for a while, understand the performance and then try FK or EX or whatever, so I'll be able to tell the difference.
I've looked at every tutorial I could find and none of them say what to do if flashing SuperSU doesn't work. I know my bootloader is unlocked , I'm running TWRP v2.8.5.1 and trying to flash SuperSU v2.02 but v2.01 does not work either. I am running CM12 as well. Any help would be much appreciated, thanks in advance.
Maybe you are flashing some old supersu binaries!Search for SuperSU V.2.46
del
Also update TWRP to latest (2.8.6.0) and indeed flash SuperSU designed for Lollipop (2.01 and 2.02 are old ones).
TWRP 2.8.6.0 Link:
https://dl.twrp.me/bacon/twrp-2.8.6.0-bacon.img.html
SuperSU 2.4.6 Link:
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Twrp should give you the option to root the phone after you flash the rom. Are you sure you don't need to enable it in the developer options?
Sent from my Oneplus One using Tapatalk
SuperSU setting -> Uncheck Respect CM Root settings
Enable SuperSu
Dev. Options -> turn OFF Update Cyanogen recovery
Been having an issue with rooting my OPO with SultanXDA's CM13.
The phone keeps getting stuck in boot. I have used a few types. Was wondering if anybody had any ideas? Or versions of SuperSU that actually work on CM13 ROMS
Jamesr1292 said:
Been having an issue with rooting my OPO with SultanXDA's CM13.
The phone keeps getting stuck in boot. I have used a few types. Was wondering if anybody had any ideas? Or versions of SuperSU that actually work on CM13 ROMS
Click to expand...
Click to collapse
use the build in root in sultanxda's cm13. go to the developer option. enable the root access. Don't flash superSU.
b0l0t4n said:
use the build in root in sultanxda's cm13. go to the developer option. enable the root access. Don't flash superSU.
Click to expand...
Click to collapse
i feel really stupid for not spotting that. Thank you very much
Have you installed official Xposed for Nougat?
Does it work fine on your MotoZ?
Any performance issues/lags?
Please add details on your ROM version, root method and if you have Magisk installed too or not...
Thank you.
I have this rom
Android Nougat on Moto Z (All Unlocked Versions) and rooted in the way that post says.
Installed xposed OK via TWRP, modules are correctly checked and enabled but didn't work, for example greenify didn't recognize that xposed is installed so didn't show the option.
Now I have missed data connection so am going to reinstall the same rom on the dirty way to not lose data and reinstall everything.
lilloscar said:
I have this rom
Android Nougat on Moto Z (All Unlocked Versions) and rooted in the way that post says.
Installed xposed OK via TWRP, modules are correctly checked and enabled but didn't work, for example greenify didn't recognize that xposed is installed so didn't show the option.
Now I have missed data connection so am going to reinstall the same rom on the dirty way to not lose data and reinstall everything.
Click to expand...
Click to collapse
Two things...
- Greenify needs to fix its compatibility with Nougat, it's a known bug
- It is *needed* to use new official Xposed apk v.3.1.2 to manage modules activation. I've seen that unofficial or old version aren't able to enable them properly...
Thanks I have just read that about greenify, the list of compatible modules with nougat is short at this time guess so
Sent from my XT1650 using Tapatalk
Mine doesn't boot with xposed installed.
Stock 7.1.1 with turboZ and magisk
I remember that installing magisk caused a bootloop on my stock 7.0
I had forgotten what modifications I did to my 7.0 stock (retus), trying to flash Xposed on it prevented it from booting (probably because of verity-dm) so I restarted from scratch.
1) Downloaded 7.1.1 stock from here and flashed it. Downloaded and installed 2 OTAs from system updates then.
2) Flashed latest TWRP (3.1.1-0).
3) I've read various reports of latest Magisk not working on Moto Z. Gave it a try though. Flashed Magisk v14.0, everything went well and I got back root access.
4) Tried installing systemless Xposed, however install failed from Magisk Manager, flashing the zip succeeded in recovery but Xposed wasn't recognized after reboot.
5) So I flashed classic Xposed (arm64) following these instructions, everything went fine (after one very long reboot).
Hi my fried. How long time this reboot in minuts?
Thanks
Ano59 said:
I had forgotten what modifications I did to my 7.0 stock (retus), trying to flash Xposed on it prevented it from booting (probably because of verity-dm) so I restarted from scratch.
1) Downloaded 7.1.1 stock from here and flashed it. Downloaded and installed 2 OTAs from system updates then.
2) Flashed latest TWRP (3.1.1-0).
3) I've read various reports of latest Magisk not working on Moto Z. Gave it a try though. Flashed Magisk v14.0, everything went well and I got back root access.
4) Tried installing systemless Xposed, however install failed from Magisk Manager, flashing the zip succeeded in recovery but Xposed wasn't recognized after reboot.
5) So I flashed classic Xposed (arm64) following these instructions, everything went fine (after one very long reboot).
Click to expand...
Click to collapse
josenilsantana said:
Hi my fried. How long time this reboot in minuts?
Thanks
Click to expand...
Click to collapse
It took maybe 15-20 minutes for the first reboot.
For me systemless Xposed install e worked properly too.
Ano59 said:
It took maybe 15-20 minutes for the first reboot.
Click to expand...
Click to collapse