Hello,
I am having issues with the new recovery mode 6.0.14, how do I roll back to the recovery mode before this?
I updated my recovery using rom manager, it does not give me the option to roll back
thanks
Which one you want? I have 6.0.1.3 by sk8r and its touch. I can upload it but other than that you gotta download the one you want and flash it in recovery..
I used ROM manager and went back to 5.xxx
noodles2224 said:
Which one you want? I have 6.0.1.3 by sk8r and its touch. I can upload it but other than that you gotta download the one you want and flash it in recovery..
Click to expand...
Click to collapse
I can not remember what exactly was the version# it was before it got updated, I know it was version# 5 something.
I haven't been able to do any nandroid backup ever since it was updated to version 6.0.1.4
I want to stay away from touch, I haven't had any good luck with it
tomasitoc said:
I can not remember what exactly was the version# it was before it got updated, I know it was version# 5 something.
I haven't been able to do any nandroid backup ever since it was updated to version 6.0.1.4
I want to stay away from touch, I haven't had any good luck with it
Click to expand...
Click to collapse
TWRP FTW!! 2.22 has no issues what so ever!!
Sent from my SGH-T989 using xda premium
tomasitoc said:
I can not remember what exactly was the version# it was before it got updated, I know it was version# 5 something.
I haven't been able to do any nandroid backup ever since it was updated to version 6.0.1.4
I want to stay away from touch, I haven't had any good luck with it
Click to expand...
Click to collapse
I had the same issue, this is what i did...
open ROM manager, scroll to the bottom you will see a option that says something about all recoveries, click that it shows 5.0.2.6 and 5.0.2.7, the .7 is the one you want, hit that and it will install that for you..
worked for me
Hit thanks if i helped you!
Thank you
Related
Does anyone know if there was a change made to ROM Manager/Clockworkmod Recovery yesterday?? I had V2.6.0.1 installed and yesterday afternoon I got a notice that Clockworkmod Recovery had been upgrade and to download the new release. It was 3.0.0.5 (RomManager Version 3.0.0.7) so I updated my recovery.
This morning I tried to install a ROM that I have installed dozens of times before using v2.6.0.1 but this time it wouldn't run because of the scripting issues within V3. I tried to find & reload V2.6.0.1 but RomManager does not list it as an alternate install at the bottom of RomManager's setting page.
Anyone else receive the update notice?
I got the update message yesterday too! I chose not to update because I knew about the issues you talked about. You can flash RA recovery, flash ROM, then go back if you need to. Or I can get you the zip if clockwork that does both versions of scripting..... Wait can't do that from the xda app....okay ill post it up when I get to my work computer...unless someone else throws it up before I do.
Sent from my PC36100 using XDA App
gzibell said:
I got the update message yesterday too! I chose not to update because I knew about the issues you talked about. You can flash RA recovery, flash ROM, then go back if you need to. Or I can get you the zip if clockwork that does both versions of scripting..... Wait can't do that from the xda app....okay ill post it up when I get to my work computer...unless someone else throws it up before I do.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Thanks. I couldn't find a .zip version of 2.6.0.1 on XDA. only the _img version.
ChadH42 said:
Thanks. I couldn't find a .zip version of 2.6.0.1 on XDA. only the _img version.
Click to expand...
Click to collapse
Just great!..I should have never upgraded!
http://mirror1.kanged.net/recoveries/
Guess I got beat to it but here is the zip file anyways.
CM still has an option to go to 2.5.0.7
I did not know this Sh%^t and could not restore any nands and was forced to unroot and start over. Seemed easier (for me) than pushing a recovery. I was not able to boot into anything to make the change... one would think that clockwork would play nice with older clockworks
apfrost said:
http://mirror1.kanged.net/recoveries/
Click to expand...
Click to collapse
gzibell said:
Guess I got beat to it but here is the zip file anyways.
Click to expand...
Click to collapse
thanks!! I'm keeping this so if It happens again...
How do I install the .zip file? Installing via recovery is only temporary. Next reboot it's back to 3.0.0.5
Sent from my PC36100 using Tapatalk
I only use it as a temp. I think to actually install you have to use a .img file....???? Not sure on that one. Someone has the answer.
Sent from my PC36100 using XDA App
gzibell said:
I only use it as a temp. I think to actually install you have to use a .img file....???? Not sure on that one. Someone has the answer.
Click to expand...
Click to collapse
gzibell, I know this is an old thread, and I don't even have an Evo (I have a lowly Sprint Hero), I was just looking for an earlier version of clockwork than the 3.0.0.5 I'm currently using and I ran across this thread, and your post made me aware that I could flash 2.5.0.7 strictly as a temp, without losing the embedded 3.0.0.5 that I'm currently using...what an awesome idea!
So I tried it, and it works great!
Just want to say thanks for that post, friend!
I rooted my phone using Unrevoked3. Of course by doing this, an outdated version of CWM Recovery was flashed to my phone. Can I flash a newer version of CWM Recovery from CWM or will that mess up my phone?
VisualPerfection said:
I rooted my phone using Unrevoked3. Of course by doing this, an outdated version of CWM Recovery was flashed to my phone. Can I flash a newer version of CWM Recovery from CWM or will that mess up my phone?
Click to expand...
Click to collapse
Flashing a new version won't hurt a thing. An easy way is to install ROM manager from market, open ROM manager and select the first option to flash cwm. After that you can uninstall ROM manager if you wish. Or you can dl the version you want and install it from your SD card.
Sent from my ADR6350 using xda premium
CondemnedSoul said:
Flashing a new version won't hurt a thing. An easy way is to install ROM manager from market, open ROM manager and select the first option to flash cwm. After that you can uninstall ROM manager if you wish. Or you can dl the version you want and install it from your SD card.
Sent from my ADR6350 using xda premium
Click to expand...
Click to collapse
Thanks, that's what I was thinking... Just wanted to be sure! And hey, I gotta also say thanks for helping me bring life to my dad's Eris. I flashed your ROM on it and he's really noticed a difference. Ha ha, it's actually usable now!
VisualPerfection said:
Thanks, that's what I was thinking... Just wanted to be sure! And hey, I gotta also say thanks for helping me bring life to my dad's Eris. I flashed your ROM on it and he's really noticed a difference. Ha ha, it's actually usable now!
Click to expand...
Click to collapse
Any time glad people are still enjoying it. I'll be updating the Eris ROM with the R.I.P. release soon. Working on getting cm fully synced back up now for that, updating my inc cm ROM and starting the condemned cm series for inc2. Also have a new inc ROM in testing now. Just have a few things to work out with it yet.
Sent from my ADR6350 using xda premium
Ever since flashing the new touch recovery I cannot create a back up of my current rom in CWM. Any suggestions or theories as to what I might have screwed up.
I really want to flash some of that tasty ics but I dont want to do anything without a backup first.
blkbltwrestler said:
Ever since flashing the new touch recovery I cannot create a back up of my current rom in CWM. Any suggestions or theories as to what I might have screwed up.
I really want to flash some of that tasty ics but I dont want to do anything without a backup first.
Click to expand...
Click to collapse
id suggest reverting back to good ol button recovery
touch recovery seems to be buggy.
Sent from my Galaxy S II
jordanishere said:
id suggest reverting back to good ol button recovery
touch recovery seems to be buggy.
Sent from my Galaxy S II
Click to expand...
Click to collapse
Thats what I have been reading do you know where I can find the old CWM recovery?
If anybody has an old CWM recover can you pm me or post a link all the old links seem to be dead
rom manager should have an option for you to revert to an old version of cwm.
Sent from my Galaxy S II
Yes, you should download rom manager from Google Play and downgrade CWM.
When I try to flash a different recovery through the app it says no legacy recoveries found
blkbltwrestler said:
When I try to flash a different recovery through the app it says no legacy recoveries found
Click to expand...
Click to collapse
can you chose the 1st option that allows you to get the most up to date recovery?
Sent from my Galaxy S II
jordanishere said:
can you chose the 1st option that allows you to get the most up to date recovery?
Sent from my Galaxy S II
Click to expand...
Click to collapse
No. When I touch the first option nothing happens.
nevermind I found the old recovery on rootwiki. I am gonna keep this one jic
Been looking around and still not sure of how to. I want to update my recovery (non-touch) for CM10.
On their website theres a link for recovery 6011.
I am runing on 5.0.2.6 (think so, my phone is on the 10 min reboot time now)
Do I really need to update ? And how is it suposed to be done.
Thank you.
NLPUNITED said:
Been looking around and still not sure of how to. I want to update my recovery (non-touch) for CM10.
On their website theres a link for recovery 6011.
I am runing on 5.0.2.6 (think so, my phone is on the 10 min reboot time now)
Do I really need to update ? And how is it suposed to be done.
Thank you.
Click to expand...
Click to collapse
While, its not necessary to update your recovery, its nice to have the latest versions of any software, including recoveries. Bug fixes are typically ironed out in the latest version. In the case of CWM, Darkside scripts are no longer required. To update your recovery, download the zip, and flash it in your current recovery. Then reboot your recovery, or your phone. When you go back to your recovery, the new one will be there.
Make sure the recovery is for our phone
Sent from my SGH-T989 using xda app-developers app
Thank you. I grabbed the recovery file on the cm10 post. So im prety sure its legit!
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
NLPUNITED said:
Thank you. I grabbed the recovery file on the cm10 post. So im prety sure its legit!
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Just to be sure, should i REwipe and REinstal my rom or flashing a recovery doesnt need a fresh rom start ?
NLPUNITED said:
Just to be sure, should i REwipe and REinstal my rom or flashing a recovery doesnt need a fresh rom start ?
Click to expand...
Click to collapse
Yup just had to go into Odin because 6.0.1.1 messed up my phone big time..couldnt instal any zips in recovery it froze..Scared the heck outa me.
NLPUNITED said:
Yup just had to go into Odin because 6.0.1.1 messed up my phone big time..couldnt instal any zips in recovery it froze..Scared the heck outa me.
Click to expand...
Click to collapse
Try TWRP. Absolutely no issues. Flashed repeatally with no problems. Here is a flashable zip.
http://db.tt/og1sjTKo
Sent from JMT Goodness
LoopDoGG79 said:
Try TWRP. Absolutely no issues. Flashed repeatally with no problems. Here is a flashable zip.
http://db.tt/og1sjTKo
Sent from JMT Goodness
Click to expand...
Click to collapse
Whats the diff between touch and hard recovery ? Beside the fact that i guess you can use the touch screen
Hello,
So I've been rooted for a while now, i was going to install a custom rom but decided not to a few months ago. Tonight, i decided to install aokp, however my phone would not go into cwm, only stock recover. I could have sworn it was installed, but fine, so i installed it once again with auto reboot in odin checked, and it still wouldnt enter cwm. I then tried to install it again with auto reboot checked off so i could see if i could enter it without the reboot. I ended up getting into it, but then when i was taking a NANDROID, it just froze on one of the first steps. Fine, reboot, try to enter cwm again. Nope, just stock android recovery. I am sure im installing it correctly and pressing the right button combos. I am at a total loss for what is stopping me from being able to enter cwm. I hope you guys know/help me find whats going on.
Thanks!!!
Zay
maybe you didn't actually "root" your phone to begin with lol
are you sure you have "superuser" or "superSU" app?
anyways to get CWM or TWRP recovery you need
find a up-to-date CWM or TWRP (if i spell teamwin recovery correctly)
download it
put your phone in ODIN Mode (download mode) by power + vol down + home
flash the recovery
i personally think twrp is better
they just released a new version which support ExFat
and all you need is just use terminal on your phone to install it.
pcshano said:
maybe you didn't actually "root" your phone to begin with lol
are you sure you have "superuser" or "superSU" app?
anyways to get CWM or TWRP recovery you need
find a up-to-date CWM or TWRP (if i spell teamwin recovery correctly)
download it
put your phone in ODIN Mode (download mode) by power + vol down + home
flash the recovery
i personally think twrp is better
they just released a new version which support ExFat
and all you need is just use terminal on your phone to install it.
Click to expand...
Click to collapse
Yes my phones rooted.
If you actually read my post, you'd know that that is EXACTLY what I am doing.
Thanks anyways though..
Zay48 said:
If you actually read my post, you'd know that that is EXACTLY what I am doing.
Thanks anyways though..
Click to expand...
Click to collapse
i have no idea how i missed that odin part on your part... i read everything but somehow i just missed that part alone 0_0
anyways
try install twrp recovery instead then
by using terminal emulator
can get it here https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
latest twrp can be found here http://forum.xda-developers.com/showthread.php?t=2074951
pcshano said:
i have no idea how i missed that odin part on your part... i read everything but somehow i just missed that part alone 0_0
anyways
try install twrp recovery instead then
by using terminal emulator
can get it here https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
latest twrp can be found here http://forum.xda-developers.com/showthread.php?t=2074951
Click to expand...
Click to collapse
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks
Zay48 said:
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks
Click to expand...
Click to collapse
if you still want cwm then i guess you can try flash stock rom and root it again and see
since you're going to flash a custom rom which will delete all your data anyways
Zay48 said:
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks
Click to expand...
Click to collapse
Stock ROM has a built in script that reloads standard android recovery when it boots. The only way to keep it is to keep Odin auto reboot unchecked, boot directly in and make your nandroid/flash custom. Once you are on a custom ROM CWM will stick.
On a side note TWRP is a very nice recovery and many people find it much easier to use. If you insist on CWM, make sure you have the latest version. You might need to flash CWM again if you had a bad flash. It shouldn't freeze up on a nandroid.
Many people never experienced this because they flashed during early ICS when the device was released. The change was an update just before JB was released which caused this little annoying script to appear.
Sent from my SGH-I747 using xda app-developers app
RPelham said:
Stock ROM has a built in script that reloads standard android recovery when it boots. The only way to keep it is to keep Odin auto reboot unchecked, boot directly in and make your nandroid/flash custom. Once you are on a custom ROM CWM will stick.
On a side note TWRP is a very nice recovery and many people find it much easier to use. If you insist on CWM, make sure you have the latest version. You might need to flash CWM again if you had a bad flash. It shouldn't freeze up on a nandroid.
Many people never experienced this because they flashed during early ICS when the device was released. The change was an update just before JB was released which caused this little annoying script to appear.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thankyou!! That makes sense ;p. When I did get to start making a nandroid last night but it froze, right before it froze it said the free space on my sdcard was 1612 mb (or something like that) This is wrong, I have the 16gb i747 so I have 11.95 gb of usable storage for apps and such, after deleting some big apps I have 4.93 gb available, my sdcard is a 16 gb sdcard which has 12.06 gb available. Do the math and I have enough room on my sdcard for a nandroid, so what could be causing cwm to freeze and report false information?
Zay48 said:
Thankyou!! That makes sense ;p. When I did get to start making a nandroid last night but it froze, right before it froze it said the free space on my sdcard was 1612 mb (or something like that) This is wrong, I have the 16gb i747 so I have 11.95 gb of usable storage for apps and such, after deleting some big apps I have 4.93 gb available, my sdcard is a 16 gb sdcard which has 12.06 gb available. Do the math and I have enough room on my sdcard for a nandroid, so what could be causing cwm to freeze and report false information?
Click to expand...
Click to collapse
Bump
what version of CWM are you currently running?
you could always try to download GooManager or ROM Manager from the Play Store.
then from one of those, install the custom recovery, GooManager for TWRP or ROM Manager for CWM.
xBeerdroiDx said:
what version of CWM are you currently running?
Click to expand...
Click to collapse
3.0.7
Zay48 said:
3.0.7
Click to expand...
Click to collapse
That is a very out dated version as they are now up to version 6.0.2.3. I would try getting an updated CWM. that could very well fix your freezing/reporting problems...
Sent from my SGH-I747 using xda app-developers app
CWM is very very funny and one of the reasons I switched to TWRP was for stability
In my experience errors come up on restoring images when 1) you don't use the same version you backed up the image with 2) you don't get to CWM through the same method you used while making the image (ie through ROM manager with your phone on).
zetsui said:
CWM is very very funny and one of the reasons I switched to TWRP was for stability
In my experience errors come up on restoring images when 1) you don't use the same version you backed up the image with 2) you don't get to CWM through the same method you used while making the image (ie through ROM manager with your phone on).
Click to expand...
Click to collapse
He's not having a problem restoring images, he's having a problem making his first nandroid.
Sent from my SGH-I747 using xda app-developers app
Zay48 said:
3.0.7
Click to expand...
Click to collapse
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
RPelham said:
That is a very out dated version as they are now up to version 6.0.2.3. I would try getting an updated CWM. that could very well fix your freezing/reporting problems...
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.
Download rom manager and update your cwm and then try making a nandroid again.
Sent from my SGH-I747 using xda app-developers app
CrackerTeg said:
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.
Click to expand...
Click to collapse
I was also a CWM user, but after I got my s3 and my first flash of CWM on the s3 hard bricked my phone, I decided to use TWRP. Little did I know I was missing out on what TWRP had to offer. I won't ever turn back to CWM again lol.
That said... If you insist in CWM, this is the guide I followed to get a successful CWM flash. (This was the CWM I was running successfully for the brief time TWRP disbanded.)
http://wiki.cyanogenmod.org/w/Install_CM_for_d2att
The above is for the ATT variant only. If you have a different variant and can't find the link, post back and I'll find it for you
Sent from my SGH-I747 using xda app-developers app
CrackerTeg said:
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.
Click to expand...
Click to collapse
apparently it's still around because new android users who want to root use those guides with outdated files
RPelham said:
I was also a CWM user, but after I got my s3 and my first flash of CWM on the s3 hard bricked my phone, I decided to use TWRP. Little did I know I was missing out on what TWRP had to offer. I won't ever turn back to CWM again lol.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Preach brother!