Hi- I got into recovery (twrp) and wiped as usual, and installed cm13's latest, and open gaps mini package. I had been on xenon xd 5.1, with full root access. Now, although I can still get into twrp, the apps that need root can't get access, and I have been unable to get SuperSU to update the binaries using either method. I would appreciate any help on this.
Sent from my 9020A using XDA Free mobile app
ccriffman said:
Hi- I got into recovery (twrp) and wiped as usual, and installed cm13's latest, and open gaps mini package. I had been on xenon xd 5.1, with full root access. Now, although I can still get into twrp, the apps that need root can't get access, and I have been unable to get SuperSU to update the binaries using either method. I would appreciate any help on this.
Sent from my 9020A using XDA Free mobile app
Click to expand...
Click to collapse
Well, I have achieved root access, but if I let SuperSU update the binaries, it never goes past the boot screen. I can dirty flash CM13 again, and I'm back to having root access and a working phone with all the apps. Just don't let SuperSU update.- cc
Sent from my LG-D850 using XDA-Developers mobile app
Related
Recently flashed Slimbean 4.3 built 1.
After that I observed that I lost my ROOT.
Then I went to download mode and tried to ROOT, but that failed and displays a problem with Supersu.
I tried to figure out, but haven't got any solution.
Need help.
My device: Tab 2 p3100
Sent from my GT-P3100 using XDA Premium 4 mobile app
Same Here
itsmepawan said:
Recently flashed Slimbean 4.3 built 1.
After that I observed that I lost my ROOT.
Then I went to download mode and tried to ROOT, but that failed and displays a problem with Supersu.
I tried to figure out, but haven't got any solution.
Need help.
My device: Tab 2 p3100
Sent from my GT-P3100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The same thing happened to me. I flashed Mokee 4.3 , but I just found carbon 4.3 for my gs3. flashed that on my phone, now I wanted to put carbon on my GT-P5113. No Root, tried using Odin to root my tab with the same file I auto rooted my tab with. It looks like it works. cycles through just like It should. on boot up, it says updating apps 1 of 112... until 112 of 112... then it boots up normally. Go to unlock screen, open Joey Krim Root Checker. No root access. It's just strange... It's like I can't Root it again, and I can't install TWRP or CM Recovery.
Revamp69 said:
The same thing happened to me. I flashed Mokee 4.3 , but I just found carbon 4.3 for my gs3. flashed that on my phone, now I wanted to put carbon on my GT-P5113. No Root, tried using Odin to root my tab with the same file I auto rooted my tab with. It looks like it works. cycles through just like It should. on boot up, it says updating apps 1 of 112... until 112 of 112... then it boots up normally. Go to unlock screen, open Joey Krim Root Checker. No root access. It's just strange... It's like I can't Root it again, and I can't install TWRP or CM Recovery.
Click to expand...
Click to collapse
My CMW recovery is working fine, I have problem with Root access and Supersu. So far tried few methods but not succeeded so far.
Sent from my GT-P3100 using XDA Premium 4 mobile app
*awesome title here*
Most ROM have a opting in the developers options . to get root access all you have to do is select apps and ADB
Issue Solved:
I tried to read about supersu little bit on forum and found that
Supersu.zip v1.60 is working fine on many custom Roms running 4.3
*So I download that zip file.
*Went to recovery
*Wiped data,cache and dalvik cache
*Installed that zip file of supersu and reebooted
After reboot I opened the supersu app and all was working fine.
Thanks !!
Sent from my GT-P3100 using XDA Premium 4 mobile app
I solved my issue too. Had to download and install TWRP. After that, I had no problems.
Sent from my GT-P5110 using xda app-developers app
I rooted my phone and installed jellyBAM rom, I later tried to install supersu from the app store and completely lost root access. Now i tried flashing supersu but i still cannot get root again. I removed supersu and tried flashing superuser but im still missing root. Is their any-way that I can regain my root access with your app because I would prefer to not have to do a factory reset. I know that jellyBAM has a built in superuser that's build into the settings.apk, Im assuming that this is the problem.
Demaier said:
I rooted my phone and installed jellyBAM rom, I later tried to install supersu from the app store and completely lost root access. Now i tried flashing supersu but i still cannot get root again. I removed supersu and tried flashing superuser but im still missing root. Is their any-way that I can regain my root access with your app because I would prefer to not have to do a factory reset. I know that jellyBAM has a built in superuser that's build into the settings.apk, Im assuming that this is the problem.
Click to expand...
Click to collapse
On some 4.3 ROMs superuser has to be enabled in the settings.. ??
Sent from my Full Android on Crespo using xda premium
Setting.Out said:
On some 4.3 ROMs superuser has to be enabled in the settings.. ??
Sent from my Full Android on Crespo using xda premium
Click to expand...
Click to collapse
It is in fact a 4.3 rom, do you have any ideas on where the setting may be?
It originally worked with its built in superuser. That superuser has practically no settings.
It just started working randomly.... I did not change anything so i do not understand it so thanks anyways, i guess we will never know what made it misbehave...
In setting -> developer option ->root access ->checked (Apps+Adb) then try again..
I hope this will help..
Sent from my Full Android on Crespo using xda app-developers app
My S3 is rooted with TWRP 2.5.0.0 installed and working fine. I want to upgrade to 2.6, but I'm having trouble. Stuck...
I tried GooManager using the "Install OpenRecoveryScript" menu item. It recognizes my device correctly, shows me the file it's going to download (openrecovery-twrp-2.6.3.1-d2vzw.imp) and proceeds to the download page. I get no progress or activity messages from here on until it's all over. After 5 seconds or so (less probably) a system message appears at the bottom that the recovery was installed. The message is in the same style as the hovering message that acknowledges an app attains root priv.
But when I boot into recovery, I'm still on 2.5.0.0. Anybody else have this problem?
(About me: I'm familiar and comfortable with most of the operations for flashing ROMs but I'm not deeply technical with Android...so I don't really know what needs to happen when you mess with a recovery image.)
Thanks,
David
Go to the official twrp website, search for our device (d2vzw), and download the latest img under "Download-Recovery Image Method (DD)," and download Flashify from the Play Store. Next, open Flashify, press "Recovery Image" and find the img file that you downloaded, and flash away.
Your advice worked. But I had to jump a few extra hoops that are probably worth documenting.
When I installed and ran Flashify, it told me I had lost root -- which would explain a lot. And YES, my SU app was gone.
So I researched how to get back root and found a post that recommended I confirm that I had really lost root. It recommended I install SuperSU app.
And they were right. SuperSUinstalled and obtained root. It could then grant root to Flashify AND I successfully flashed / upgraded TWRP to 2.6.3.1
I run SlimRom. I wonder what happened to their SU app...
Thanks again!
Sent from my SCH-I535 using xda app-developers app
davidb1835 said:
Your advice worked. But I had to jump a few extra hoops that are probably worth documenting.
When I installed and ran Flashify, it told me I had lost root -- which would explain a lot. And YES, my SU app was gone.
So I researched how to get back root and found a post that recommended I confirm that I had really lost root. It recommended I install SuperSU app.
And they were right. SuperSUinstalled and obtained root. It could then grant root to Flashify AND I successfully flashed / upgraded TWRP to 2.6.3.1
I run SlimRom. I wonder what happened to their SU app...
Thanks again!
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Cool! I'm using SlimKat and when I'm on AOSP, I don't usually have SuperSU since root is enabled in Developer Settings. I had to do the same on SlimBean as well. Of course, it doesn't matter now but it's there for future reference.
Sent from my SCH-I535 using Tapatalk 4
That's what is so weird. I had enabled Root in Dev Options a while ago. But the app or system process or whatever seems to have stopped fishing out root. Installing a new SU app has brought things back to normal.
Glad to hear you're playing with SlimKat. That was the main reason I wanted to upgrade TWRP. I read you should be on a 2.6 version to flash SlimKat.
Sent from my SCH-I535 using xda app-developers app
I meant "dishing" out root... Funny how a typo gives you the opposite sometimes...
Sent from my SCH-I535 using xda app-developers app
This phone can cause some weird bugs from time to time haha and yea, you need TWRP 2.6.3.1 to flash any KitKat rom. SlimKat is pretty smooth, just missing a lot of features while they make sure its stable.
Hello,
I have rooted my phone, flashed TWRP 2.6.0.0 and CM 10.2 with the All-in-One Toolkit. Everything worked fine.
Then I installed the SUPER SU App from Chainfire and updated the Binary on the "normal" way. After that I uninstalled the app.
Today I wanted to install a newer version of TWRP. I used the GooManager. The download worked fine and the device rebooted. I can use the phone and I get into Bootloader but when I want to go to Recovery the device reboots and reboots....
My first thought was, that I don't have Root anymore because I uninstalled the Super SU App from Chainfire and I don't get any notifications when I start a app that needs root and the built in Super SU in the settings doesn't make any logs since some days. But Root Checker says that my device is rooted and for example Titanium Backup works fine although it's not in the list of apps with Super SU.
What can I do? Maybe trying to install the recovery with the GooManager again or new Rooting and Recovery installing with the Toolkit?
Sincerely,
May be you should flash back twrp 2.6.0.0 which was working for your phone and reinstall super su
I tried to root without the toolkit. I followed all steps and everything worked fine. But when the device rebooted after rooting I stopped in the bootscreen. I'm able to get into CM and use the phone without problems, but now the root is completely gone!
Can anyone help? I really don't know what to do now.
Edit: So, after rooting I have a Super SU app installed, but it's not able to update and not working...
Can you try with the twrp from this link:
http://flemmard.net/recoveries/openrecovery-twrp-2.6.3.0-ville-selinux.img
and root again
Sent from my One S using xda app-developers app
Okay, thanks. Wich root shall I try? With flashing the SuperSu with the recovery or with getting rooted over PC?
Thanks again.
Hevy12 said:
Okay, thanks. Wich root shall I try? With flashing the SuperSu with the recovery or with getting rooted over PC?
Thanks again.
Click to expand...
Click to collapse
Try flashing the supersu from recovery
Sent from my One S using xda app-developers app
ka_55 said:
Try flashing the supersu from recovery
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
I flashed the Recovery and the SuperSU. The recovery is installed but there is no root. But I can't uninstall the installed SuperSU apk from the old try of rooting that went wrong. I only can deactivate it. Should I do this and try flashing the SuperSU.zip again?
Thanks!
Sincerely,
Edit: Problem solved with the newer SuperSU version.
So i used the toolkit to get my phone rooted and the bootloader unlocked, the weird thing is that I am able to get into TWRP recovery and once I have flashed the Superuser zip, but when i reboot the phone i dont have root access?! Any suggestions?
Which toolkit did you use
Sent from my A0001 using XDA Free mobile app
When it asks you to fix root when you rebooting recovery say no
Send from OnePlus One using Tapatalk
I used both, I think there's only 2, either way thanks guys I gave up and simply flashed stock everything and now I have the new update.
In SU settings uncheck " Respect CM Root Settings " and root will stick