Database Info

[Q] ICS 4.0.3 ROM Manager Problem

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.

No root access

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

A small rooting dilema

Hello everyone, I'm completely new to androids and I recently rooted my phone with CF's Auto Root.
I've been scouring the forum for information on how to resolve my problem but none that really help me with my specific problem
I want to re root with clockwork but can't find anything on it
Can someone help me out here? Sorry for sounding really dumb, I just switched over from apple this stuff is a completely different world to me

Completly factory reset your phone n try rooting again . If it fails, you need to root using the same software as you did earlier
Sent from my HTC One S using xda app-developers app

sishirbaid said:
Completly factory reset your phone n try rooting again . If it fails, you need to root using the same software as you did earlier
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
So with my original method I've rerooted my phone. How do I install clockwork mod on a rooted phone if it wasn't installed in the rooting process?

Take a look at the "goo manager " app and TWRP instead of CWM.
But CWM also has an easy install app if your phone is supported. Just see if it is or not and go from there either way.
Sent from my SGH-T999 using xda app-developers app

Pennycake said:
Take a look at the "goo manager " app and TWRP instead of CWM.
But CWM also has an easy install app if your phone is supported. Just see if it is or not and go from there either way.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Thanks for answering Pennycake.
I'm on Rogers Carrier OEM firmware right now and I'd like to flash the international firmware as to rid bloatware to my Note 2.
Which app would you recommend me to backup my rom with?

I've successfully rerooted, I found the problem with my phone. After it had been unrooted it needed to be rebooted in order for some effects to take change. So through the original method of CF-Auto Root, I rerooted my phone. I've installed the standalone ClockWorkMod app but it doesn't seem to make back ups properly. Through the app I hit back up and it shows the time stamp I hit 'ok' and my phone shuts off and starts up in recovery mode only not in ClockWorkMod but Android system recovery <e3> or something along those lines with only options to: reboot, install updates from adb, wipe data, etc.
What am I doing wrong?

Try installing the recovert img using clockworkmod before backups, because its not an app error, it is a user error. Using chainfires root method means no cwm. Using odin or lemme guess, you have a gs3, unified tool kit you get cwm.
Sent from my SGH-T999 using xda app-developers app

What recovery do you have right now? If it's twrp (team win) do that go with clockwork mod. Twrp (goo manager) is by far (in my opinion) the best and user friendly. But it's your call. And you don't have to un root and re root to do it. You just have to flash the new recovery via bootloader and it will work. For rom choices I personally like jedi xpx and jellybam. With jedi xpx you can overclock the sh*t out of your note 2 to 1920 and it's still stable.
I've used many recoveries and twrp is my choice hands down. And yiu make back ups easier. So dont unroot again and re root. Just download the latest twrp and flash through bootloader. but to each their own
Sent from my SGH-I317 using xda app-developers app

iKoolkid said:
Try installing the recovert img using clockworkmod before backups, because its not an app error, it is a user error. Using chainfires root method means no cwm. Using odin or lemme guess, you have a gs3, unified tool kit you get cwm.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I'm on the Galaxy Note 2 i317m in Canada. Clockworkmod isn't letting me back up, everytime I get the box with the timestamp to create a back up I hit 'ok', my phone reboots into recovery mode and its the stock recovery, so no option to restore. Also when my phone's model isn't listed in the clockworkmod flashing menu within the app. Is my phone not supported? The N7100 is the one listed when it asks you do confirm a phone model.
markbencze said:
What recovery do you have right now? If it's twrp (team win) do that go with clockwork mod. Twrp (goo manager) is by far (in my opinion) the best and user friendly. But it's your call. And you don't have to un root and re root to do it. You just have to flash the new recovery via bootloader and it will work. For rom choices I personally like jedi xpx and jellybam. With jedi xpx you can overclock the sh*t out of your note 2 to 1920 and it's still stable.
I've used many recoveries and twrp is my choice hands down. And yiu make back ups easier. So dont unroot again and re root. Just download the latest twrp and flash through bootloader. but to each their own
Sent from my SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
When I boot into recovery it says is Android System Recovery <3e> and below are listed a few options, reboot, wipe cache, install from adb, etc

Then you dont have twrp installed. And by the sound of it you dont have cwm either
Sent from my SGH-I317 using xda app-developers app
---------- Post added at 10:32 AM ---------- Previous post was at 10:31 AM ----------
What ohone do you have?
Sent from my SGH-I317 using xda app-developers app

[Q] Stuck on TWRP 2.5.0.0

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.

No recovery anymore, Super SU problem

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.