Database Info

[HELP] Why is EZ Recovery not working

Ok so I'm stock rooted and I want to install CWM 6.0.1.0, so I downloaded Ez Recovery from the market and also the apk from the original post here on XDA. But it will not install CWM. I tried all the options. Recovery, Hybrid, and Stock, but when I flash them and it says it was installed successfully I press reboot it takes me to stock recovery every time.
Whats the problem???
Is it possible someone could provide me with a link to the recovery img file or tell me how to fix this problem?
Thanks

This may be obvious, but are you selecting reboot recovery from ez app menu?

Yes, when I flash my recovery I press reboot

Have you run the superuser app initially? I had similar behavior in which it said it flashed but still had stock recovery. The initial run of superuser got things going and when I ran ez recovery again it asked for root permissions and worked as expected...
Sent from my SCH-I535 using Tapatalk 2

I saw you post this in beans thread but I didn't have a fix but then I remembered how I fixed this on my phone. Uninstall ez recovery and reinstall from market. There was a problem with the version numbers or something and this fixed that problem for me
Sent from my SCH-I535 using xda app-developers app

codertimt said:
Have you run the superuser app initially? I had similar behavior in which it said it flashed but still had stock recovery. The initial run of superuser got things going and when I ran ez recovery again it asked for root permissions and worked as expected...
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I was having the same issue as the OP and your advice did it for me! I went back to stock about 2 days ago and I was already getting bored with it.

codertimt said:
Have you run the superuser app initially? I had similar behavior in which it said it flashed but still had stock recovery. The initial run of superuser got things going and when I ran ez recovery again it asked for root permissions and worked as expected...
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Yep, that did it. Thanks.

RAYOCOM said:
Yep, that did it. Thanks.
Click to expand...
Click to collapse
Wondering if any of you guys have had the problem where it flashes the recovery successfully and you can reboot in CWM / TWRP just fine. Then once you get back into the system and try reboot recovery again, it goes straight to the stock recovery.
Is this normal? Do I have to flash the recover everytime?

There is something you need to do in recovery to make it persist, some option you need to select. I'm still not clear on what it is, because its been a long time since I used CWM. I hope someone will chime in with exactly what needs to be done to make it stick so I can be clear on it as well.

apacseven said:
There is something you need to do in recovery to make it persist, some option you need to select. I'm still not clear on what it is, because its been a long time since I used CWM. I hope someone will chime in with exactly what needs to be done to make it stick so I can be clear on it as well.
Click to expand...
Click to collapse
When you select reboot, it will tell you that it is reverting back to stock recovery unless you fix it. You scroll down and select yes and you are good to go.
Sent from my SCH-I535 using xda premium

This happened to me as well when I first rooted. I had to reboot a few times until the proper recovery booted. Now that I have flashed a Rom, CWM recovery boots properly every time.
----
I typed this with my thumbs.

Horrible clarifying question

Ok everyone. Horrible question I know but here goes. I want to be right so please excuse a question I am sure has been asked many many times.
Situational info:
HTC one s s4 boot loader 1.06
No regular PC access.
Extensive knowledge and experience rooting and flashing G1 and G2X
Goal: unlock boot loader and open root access to enable flashing of roms via recovery while remaining PC independent
Steps I plan to execute:
1) unlock bootloader on htcdev site
2)grant root access following instructions(or all in one tool - your input here is appreciated)
3)instal CWM
4)download rom and kernel of choice
5) boot into boot loader, enter recovery, wipe, flash, boot
If I have any of this wrong please advise.
Again I apologize for the redundancy of this thread. Mods please delete after my process is verified to keep board clean. I only have one crack at this (PC access extremely limited) and I want to get it right.
Sent from my HTC VLE_U using xda app-developers app

Looks correct. First install HTC drivers & HTC Sync software (in order to unlock bootloader, I believe HTCdev site will instruct this).
I recommend (as well as many others, I believe) TWRP over CWM. ESPECIALLY if you do not have computer access. The 1S does not have S-OFF, which makes it very hard for us to flash kernels & radios. Well, not hard, but you need a PC if using CWM. Using TWRP, you can usually flash these things from your device. So definitely use TWRP for your situation.

You can't root without a PC. It's impossible. You are required to get a token that you can only get from a command prompt on the computer. Sorry, but you're out of luck. But when/if you get a PC the steps you wrote were mostly right
1) Correct
2) FLASH RECOVERY (use TWRP, CWM is not good on this device)
3) Then root by flashing a SuperSU zip in RECOVERY (that's why #2 and #2 are switched)
4) Yep
5) Always always always BACKUP YOUR ROM. Then wipe system, data, cache, and dalvik cache. then flash the ROM. If you have extra time you should fastboot your kernel if your hboot is below 1.13 (meaning 1.13 is NOT able to flash the kernel.)
Hope I helped. If I did press thanks

OP did mention that he will have limited PC access to perform the unlock process, so he will be able to do it initially.
Here's the link for TWRP: http://forum.xda-developers.com/showthread.php?t=1677670 (make sure to use this one, the other link in the forums is for the S3 processor)

Ok so I can flash recovery as soon as I unlock boot loader and use twrp check.
The supersu, that's just a zip to flash in recovery to grant root access?
What is fasbooting kernel?
Thanks guys, appreciate the help. Will be performing this within the next two hours. Just trying to be ready so it goes off smooth. Once I get this done I need to do my friend's G2(condition for PC time lol)
Sent from my HTC VLE_U using xda app-developers app

TWRP is a recovery. You will use that instead of CWM, not in addition to.
If you're going to flash a custom rom then you don't have to worry about rooting first. The rom will be rooted already.
Fastbooting kernel is a method of using a pc + command prompt to flash the kernel on your phone. Because HTC hasn't completely "unlocked" the 1S, we need workarounds like that to do certain things. However. TWRP will allow you to flash most things, including most kernels. If you use TWRP and yout hboot is low (which yours is) you shouldn't have too many issues.

Brief note here, I won't have adb access on this pc....will I be able to flash twrp without adb? I see there is an app in the market for it but seems to require root first. Thanks again for the input
Also, downloaded roms and kernels will need to reside on my SD card. This will become an issue if pre install format/wipe kills my SD card. Please advise. Roms and kernels will need to always be installed from SD card via recovery
Sent from my HTC VLE_U using xda app-developers app

briandresstoyota said:
Brief note here, I won't have adb access on this pc....will I be able to flash twrp without adb? I see there is an app in the market for it but seems to require root first. Thanks again for the input
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
You need adb access. That's how you flash recovery, using command prompt on the PC.
Not sure about this app, what's the name of it? To my knowledge you need adb to flash recovery on this phone.
If this isn't possible, you will still be able to root, just not have a custom recovery or flash roms. I don't believe you need to unlock the bootloader to root...not 100% sure but I believe you can root without it, which should be pretty simple.

On twrp website there is an option to install recovery via an app called goomanager. In the app store goo manager states root required. Should I revise my steps to this:
1)unlock bl
2) root using supersu img
3)goomanager install twrp
4)use twrp to flash roms and kernels
I would really love to avoid flashing radios btw. I just feel like it might be safer to let it be. Radios always made me nervous on previous devices
Sent from my HTC VLE_U using xda app-developers app

You could download goo manager from the play store then install open recovery script from menu..then flash the SuperSU zip. You wouldn't require ADB then.

invasion2 said:
You could download goo manager from the play store then install open recovery script from menu..then flash the SuperSU zip. You wouldn't require ADB then.
Click to expand...
Click to collapse
This is correct. I forgot about goomanager.
As for the radios, there isn't really too much risk on the 1S. I remember it was always a scary issue on the HD2 because of EU vs. US radios, which could cause a brick. On the 1S you can flash EU radios with no prob. Actually, some people report better performance in the US with EU radio. So yeah, don't be worried about it, it's pretty safe on this device - with normal precautions and proper flashing of course.
HOWEVER:
Make sure to only use S4 radios/roms on S4 processor. There is an S3 version of the 1S as well, and you cannot switch any roms/kernels/radios between the two.

Hey hey!!! Made it work. Flashed aokp. Running sooooo amazing. Anyone know how to make home screen and app store rotate?
Sent from my HTC One S using xda app-developers app

Can't make home screen. But turn on auto-rotate in settings and it should rotate the store.

So I am a happy rooted owner. No sound in music apps or YouTube.
Sent from my HTC One S using xda app-developers app

Soo started with aokp then cm10. No sound on either except in power amp. So weird
Sent from my HTC One S using xda app-developers app

Try flashing official CM10
http://get.cm/?device=ville
If you prefer a stock look try TrickDroid or Viper
Sent from my HTC One S using xda app-developers app

Actually flashed most recent cm10 nightly after my go with AOKP. Still no dice. I've posted the issue on both ROM dev forums so hopefully it will get resolved. I feel like it is operator error but I have flashed each ROM twice with a full wipe before each install. I understand the process for flashing so I hope its something small I missed.
Sent from my HTC One S using xda app-developers app

briandresstoyota said:
Actually flashed most recent cm10 nightly after my go with AOKP. Still no dice. I've posted the issue on both ROM dev forums so hopefully it will get resolved. I feel like it is operator error but I have flashed each ROM twice with a full wipe before each install. I understand the process for flashing so I hope its something small I missed.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Do you have no sound from the speaker or do you have headphones or something plugged in?

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

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.

*Root Access Possibly Lost Fix Root?

When ever I am about to exit Cwm I get this error*Root Access Possibly Lost Fix Root?. There are two options yes and no. I tried both but still I get d same error.
P. S- my root is fine all root apps work perfectly
Sent from my Nexus 5 using Tapatalk

dsjd said:
When ever I am about to exit Cwm I get this error*Root Access Possibly Lost Fix Root?. There are two options yes and no. I tried both but still I get d same error.
P. S- my root is fine all root apps work perfectly
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Do you use SuperSU rather than Superuser? I think CWM recovery only look for Superuser, so if you have SuperSU installed it will think you aren't rooted.

Official CWM doesn't recognize the SuperSU binary. This is one of the reasons I don't recommend it, but rather PhilZ Touch CWM or TWRP.

Thanks

It helped me too, thanks

what did you guys do to fix this?
New cwm? Or Download superuser from the store and uninstall SuperSU? Can you guys please provide more details as this is driving me nuts to have to click on yes or no to fix root every time I go into Recovery. Or Should I use Twrp?
And, I'm surprised there aren't more people with this problem. Are we the only ones?

VOLTAGEROCK said:
New cwm? Or Download superuser from the store and uninstall SuperSU? Can you guys please provide more details as this is driving me nuts to have to click on yes or no to fix root every time I go into Recovery. Or Should I use Twrp?
And, I'm surprised there aren't more people with this problem. Are we the only ones?
Click to expand...
Click to collapse
Flash another recovery
or
Use Superuser

Lethargy said:
Flash another recovery
or
Stop using Superuser
Click to expand...
Click to collapse
Obviously this topic is a little more difficult for me to figure out on my own and your response even though you're trying to help me does not help. I don't know what it means to just stop using super user when I'm using supersu? Am I supposed to uninstall supersu and then install superuser? Are these the same apps? And if I do flash another recovery like team win, do I have to uninstall ClockworkMod first? I have tried to look online for an answer to this and this thread is the only one with this problem which is mind boggling the amount of Nexus 5 users compared to the five people here who are experiencing this problem. So if you can direct me to another link that has more information, that would be great otherwise I'm not quite sure how to fix this when you guys said you did it so easily.
Sent from my wondrous Nexus numeral 5

VOLTAGEROCK said:
Obviously this topic is a little more difficult for me to figure out on my own and your response even though you're trying to help me does not help. I don't know what it means to just stop using super user when I'm using supersu? Am I supposed to uninstall supersu and then install superuser? Are these the same apps? And if I do flash another recovery like team win, do I have to uninstall ClockworkMod first? I have tried to look online for an answer to this and this thread is the only one with this problem which is mind boggling the amount of Nexus 5 users compared to the five people here who are experiencing this problem. So if you can direct me to another link that has more information, that would be great otherwise I'm not quite sure how to fix this when you guys said you did it so easily.
Sent from my wondrous Nexus numeral 5
Click to expand...
Click to collapse
You replied to be as I was editing my post lol.
It only happens when you're using CWM + SuperSU, because CWM doesn't look for SuperSU, only for Superuser.
Just flash TWRP, CWM is horrible anyways. Or you could just ignore it and just press no every time. Makes no difference.
And you don't "uninstall" CWM then install TWRP. You flash it over (overwrite) CWM.

VOLTAGEROCK said:
Obviously this topic is a little more difficult for me to figure out on my own and your response even though you're trying to help me does not help. I don't know what it means to just stop using super user when I'm using supersu? Am I supposed to uninstall supersu and then install superuser? Are these the same apps? And if I do flash another recovery like team win, do I have to uninstall ClockworkMod first? I have tried to look online for an answer to this and this thread is the only one with this problem which is mind boggling the amount of Nexus 5 users compared to the five people here who are experiencing this problem. So if you can direct me to another link that has more information, that would be great otherwise I'm not quite sure how to fix this when you guys said you did it so easily.
Sent from my wondrous Nexus numeral 5
Click to expand...
Click to collapse
If your using super su, good. To change to twrp, which I recommend, just flash a twrp zip file in your current recovery. Google recovery zip collection xda.
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app

SuperSU
Superuser
Two different things, both are root. Think Honda/Toyota (horrible analogy)
Pick your side. I think that's what's confusing you.
Sent from my Nexus 5

Lethargy said:
You replied to be as I was editing my post lol.
It only happens when you're using CWM + SuperSU, because CWM doesn't look for SuperSU, only for Superuser.
Just flash TWRP, CWM is horrible anyways. Or you could just ignore it and just press no every time. Makes no difference.
And you don't "uninstall" CWM then install TWRP. You flash it over (overwrite) CWM.
Click to expand...
Click to collapse
I just flashed twrp and it installed fine. Thank you.
Another question, yesterday when I had CWM on my phone, I did a NAND backup which I just deleted from Root Exlporer after installing TWRP, but do I need to also delete the Clockwork folders from Root Explorer as well now?

VOLTAGEROCK said:
I just flashed twrp and it installed fine. Thank you.
Another question, yesterday when I had CWM on my phone, I did a NAND backup which I just deleted from Root Exlporer after installing TWRP, but do I need to also delete the Clockwork folders from Root Explorer as well now?
Click to expand...
Click to collapse
Yeah, you can't share backups between them as they do them differently.