Hello, I recently dug out my nook hd+ that has cm12.1 build from 20151018 it was turned off for a while but it had twrp as recovery and was rooted but now when I go to root checker it says the Superuser binary isn't installed and when I try to reboot to recovery it just reboots into the main menu. How can I get back root?
Did you flash/install SuperSU (e.g., https://download.chainfire.eu/696/SuperSU) after you installed CM12.1?
Unlike previous CM versions, CM12.x does not come "Rooted".
I installed CM12.1 and it didn't have root, so I went into TWRP and flashed it.
Related
so I installed the latest CM12 Droid 4, and for some reason it's telling me I'm not rooted.
I was rooted in 4.1.2 using the razr utility for the XT894.
I first flashed original firmware
then did step 3 (root)
then installed safestrap using a 3.75 download link.
booted into recovery, installed latest CM12 nightly...
... but i can't get root access?
How do I restore root access now that I'm on 5.0.x?
Yes, I ENABLED root access in developer options. Still won't give root access.
Root Checker says:
Root access: no access
Su Found: system/xbin, system/bin
Hi,
After flashing CM12.1 you need to flash SuperSU:
http://forum.xda-developers.com/showthread.php?t=1538053
Actually, I didn't have to do that. I just started over again. I did try flashing SuperSU by downloading the APK they have linked on the playstore page, through SafeStrap Install ZIP function, but it didn't work.
I went with the Razr Utility and installed 4.1 with wipe. then reinstalled root. then I went and installed safestrap 3.75, followed by lollipop.
all is well now.
I think the cable extension i was using was causing packet loss issues of somesort, as i can touch the cable end and it cuts in and out. But the root process said it was completed successfully. I think it just didn't go through the cleaning process and left files over that caused a root loss of some sort.
It seems to be fine now.
Cm12 has it's own root, and is different from stock rom.
When device is in twrp recovery, it doesn't matter if Rom is Rooted or not.
Guessing it was a bad cm12 install, you didn't need to reflash firmware, just reboot to twrp, reinstall the Rom.
May need to redownload the Rom, and verify the md5 checksum.
To root Rom in twrp use
SuperSu flashable zip (UPDATE-SuperSU-v2.45.zip - 28 Jan 2015)
Sent from my XT907 using Tapatalk
sd_shadow said:
Cm12 has it's own root, and is different from stock rom.
When device is in twrp recovery, it doesn't matter if Rom is Rooted or not.
Guessing it was a bad cm12 install, you didn't need to reflash firmware, just reboot to twrp, reinstall the Rom.
May need to redownload the Rom, and verify the md5 checksum.
To root Rom in twrp use
SuperSu flashable zip (UPDATE-SuperSU-v2.45.zip - 28 Jan 2015)
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
if you look at my second post, I said I tried to install the SuperSU binary using recovery, and it did not do anything.
I just reinstalled the rom after wiping the partition to avoid any issues.
I'm running CM 12.1 on an ODROID XU3-Lite.
When I install SuperSU and let it update the binary automatically, the root gets lost after one reboot.
I have no way to boot into recovery on the XU3-Lite.
How can I install the latest SuperSU?
Hello all,
I have recently been asked to use email on my work phone (instead of my preferred web-app option). My device (S4 i9505 running a Cyanogenmod 12.1 nightly) was/is rooted but after the (standard) encryption process the phone was stuck on a black screen/bootloop/problem.
This was resolved by re-flashing the CM 12.1 rom using TWRP which booted and the device was encrypted with my work email on the phone. SuperSU is installed but the binary needs to be updated and the phone is saying it's not rooted when checking the root using Root Checker.
I want to reinstall/reinstate SuperSU, but I am wondering if this will freeze the phone again, as it is encrypted. What are the known problems with rooted phones/SuperSU and encryption?
Cheers
Solved
Hi all,
Solved it by simply flashing the latest SuperSU zip via TWRP in recovery. It seems that you can use a rooted phone with encryption enabled. However, when I encrypted it (via the standard way) it was stuck in some kind of bootloop problem where the screen was black but the phone was on. To solve this, I presume the problem was with SuperSU. I would first make a backup of your ROM before encrypting then I would temporarily disable SuperSU, or uninstall it, then encrypt the device. Afterwards re-enable or re-flash SuperSU from recovery. If you do get a boot problem, you can flash a ROM or recover your old one and start again.
My steps were: encrytp, then got the boot problem so I flashed a new CM 12.1 nightly. Afterwhich the phone booted normally and the phone was encrypted, but "not" rooted. I then downloaded the latest SuperSU zip and flashed it from the recovery leaving me with an encrypted, rooted phone.
By the way, encryption is annoying as you must enter a pin everytime you use the phone, after it is locked. My S4 only lets you use a pin, no pattern allowed. However, it is preferred by employers/IT.
I'm running CM 13 nightly with TWRP recovery, trying to get root access.
When I enable root through developer options in the rom, it doesn't work, according to root check.
When I flash Super SU Beta 2.68 through recovery is says partway through installation it says "decompressing ramdisk; failure, aborting"
Flashing v. 2.46 causes a bootloop.
Anyone have any ideas why I can't get root?
Thanks!
Deivore said:
I'm running CM 13 nightly with TWRP recovery, trying to get root access.
When I enable root through developer options in the rom, it doesn't work, according to root check.
When I flash Super SU Beta 2.68 through recovery is says partway through installation it says "decompressing ramdisk; failure, aborting"
Flashing v. 2.46 causes a bootloop.
Anyone have any ideas why I can't get root?
Thanks!
Click to expand...
Click to collapse
Never flash supersu on CM! You should reinstall CM just incase flashing supersu messed something up.
You should never flash supersu on a custom rom, they usually come pre-rooted.
Sent from my XT1095 using Tapatalk
I've tried asking this question on other threads but no one is replying.
I have installed the official OOS4.0 through TWRP. I was on a CM13 ROM so I flashed the full 3.5.4 zip and then the 4.0 OTA directly after. Then I flashed SuperSU but I guess it didn't work because I don't have root access.
Now I lost access to TWRP as well. So I tried to reflash TWRP through my Mac and though the process runs smoothly, whenever I boot into recovery, it's still stock.
Is there anything I can do to regain TWRP access through a MacBook?