Hello!
So here's the deal: yesterday I decided to try out CM10.1 on my Nexus S. Being my first time rooting this phone all went well and I managed to flash the rom mostly without any problems. But my main concern is that after running root checker I got a message that my device isn't properly rooted... I did it just because I tried using ES file explorer in its root settings in order to delete a gallery2.apk file in system, which resulted in an error.
It's strange because I flashed the superuser zip before the rom and as far as I know CM10.1 comes with SU installed in it initially... Otherwise the ROM works perfect.
Do I need to flash everything from the beginning, doing another factory reset/wiping the cache? So far I've tried just to flash the superuser.zip from recovery (running 6.0.2.5 CWM recovery as far as I remember) and it didn't appear to root the device, although it said it installed successfully in the recovery. It may be something to do with the recovery or SU version? Any help is much appreciated!
Sent from my Nexus S using xda app-developers app
it's a problem about ES,
you should go to the settings and enable the root mode.
Jhyrachy said:
it's a problem about ES,
you should go to the settings and enable the root mode.
Click to expand...
Click to collapse
Yeah I know, tried that and ES said this feature cannot run on your phone... And the app doesn't appear in the superuser app either. Nothing does in fact. xD
Related
I followed the guide on General forum to flash ICS 4.0.3 stock but my ROM Manager Premium isn't working properly.
Flash ClockworkMod, Reboot into Recovery works fine. It seems like everything else works too........
BUT Fix Permission. When I try to run it, it says 'An error occured while attemping to run privileged commands!'
Titanium Back Pro has green check marks on everything including Root access.
SuperUser and other apps that needs root access seems to work fine.
I downloaded Root Checker Basic and it says that my Nexus S is rooted.
Voodoo OTA Rootkeeper has all check marked as well.
Fix permission works fine on CWM recovery and I see CWM recovery when I reboot in recovery, not stock recovery.
Could anyone help me out with this problem... Thank you!
Just tried and same thing....not sure rom manager might need to be updated
Sent from my Nexus S using xda premium
demo23019 said:
Just tried and same thing....not sure rom manager might need to be updated
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Hopefully that is the cause of the problem. I will try contact the developer.
I've followed a few guides here, but having no luck... Also I'm new to all this. Been on Android since Jan from iPhone.
I put on CWM and that seems to work. Then I tried loading Superuser from my SD card. After a few errors (warned and expected) it went through.
But them I couldn't install busybox or anything else like titanium. I finally gave up after a few things and recovered to right before I put superuser on. Now my phone wont power off. Thoughts?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Darbley said:
I've followed a few guides here, but having no luck... Also I'm new to all this. Been on Android since Jan from iPhone.
I put on CWM and that seems to work. Then I tried loading Superuser from my SD card. After a few errors (warned and expected) it went through.
But them I couldn't install busybox or anything else like titanium. I finally gave up after a few things and recovered to right before I put superuser on. Now my phone wont power off. Thoughts?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
sometimes the root wont stick, try it again or a couple more times yet.
you cant install tb? or does it say cant get root access?
no root access means no su binary were installed so install su again in your recovery keep doing this till it sticks.
do a battery pull then in your recovery wipe devlak catch, that should take care of the shutdown problem.
popcorn900 said:
sometimes the root wont stick, try it again or a couple more times yet.
you cant install tb? or does it say cant get root access?
no root access means no su binary were installed so install su again in your recovery keep doing this till it sticks.
do a battery pull then in your recovery wipe devlak catch, that should take care of the shutdown problem.
Click to expand...
Click to collapse
Thanks a lot! I'll keep messing around with it. Its the only way I'll learn.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Flash phone with CWM use this one
Clockworkmod Touch 5.8.1.3 Odin tar http://forum.xda-developers.com/show....php?t=1566613
Then wipe data/factory reset, format- system, data and cache, and clear the partition and dalvik caches, do that to all of them 3 times each, using touch cwm.
Then odin ICS download it from here http://www.sammobile.com/firmware/
(make sure only Auto Reboot is checked nothing else)
Once the phone loads go through the setup then leave it alone, let it sit for about 20min then flash back the CWM. Then download Superuser from here and put it on the root of your SD card then flash it in CWM if it fails just keep doing it until it works, it worked the second time for me.
Once superuser is installed install busybox from the market and everything will work.
This method worked perfect for me. The key is to wait about 20min after you flashed ICS before you do anything else.
Go into security and make sure "Unknown sources" is checked
Hope this helps you.
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.