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!
Oh, CWM, how MUCH I can't stand thee:
Anyway, here's a long version:
I can't stand using CWM for recovery.
(I initially had an OG Evo, and it was nothing but a headache, so I always used AmonRa, successfully, and use that or TWRP on my ALL my other devices, where I can...
I'very made other posts about its issues, and have gotten into it with Koush online before about all the problems with it, and how he just let's so many versions out into the wild that aren't working for different phones...
With the ET4G, I kinda had to use it, and was able to flash a working version thru Odin.
Whatever, I was able to use it.
Lately, Koush releases a touchscreen version, there are stories about it all over the web: so I go into Rom Manager to check it out:
It tells me that it's not yet compatible with the ET4G, but that my version of CWM is outdated, so I should flash a newer CWM....
LIKE AN IDIOT, I agreed.
Now, just when I finally have a chance to flash CM9 on my ET4G, after waiting SOOOOO long?
I can't.
Because now, my recovery's totally borked.
I can't even get my phone to do anything but bootloop the CM7 animation, and download mode is the only thing I can get into.
Now, I'm gonna have to spend all this time today fixing what shouldn't be messed up in the first place instead of enjoying CM9 like I should be doing.
(BTW: Koush, if you're listening: this will be the last time for sure I ever fall for that again.)
Yeah, I'm mad, Bro.
Sent from my PG86100 using xda premium
I never use ROM manager but doesn't cwm have to be packaged with a kernel in order for it to work? ie. we can't just flash a recovery like we could in the evo 4G days. Methinks if you just use odin to flash a kernel+cwm package you'll be back up and running in no time.
_MetalHead_ said:
Methinks if you just use odin to flash a kernel+cwm package you'll be back up and running in no time.
Click to expand...
Click to collapse
Methinks you are a wise and gracious man with your help......
_MetalHead_ said:
I never use ROM manager but doesn't cwm have to be packaged with a kernel in order for it to work? ie. we can't just flash a recovery like we could in the evo 4G days. Methinks if you just use odin to flash a kernel+cwm package you'll be back up and running in no time.
Click to expand...
Click to collapse
Oh, yeah: I can fix it, but my wife has my laptop till like 7pm, and I really don't wanna mess with drivers, Odin, all, that stuff on my desktop. I keep all my Android stuff on one PC (laptop) and I like having ADB, drivers, all that stuff, in one place...Just kinda threw a rock into my chain, on today of all days...
Sent from my PG86100 using xda premium
Edit: And, yeah, I knew that used to be the case with CWM (needed kernel flash), but when a known high-level dev is telling me basically, that "this updated version will work for that very specific Android device that you have", and that "I can use his app to flash it", I guess I wanted to believe him...
Eff that guy: He needs to spend less time stacking his money, and more time having some accountability for what he releases to the public.
/End rant.
So, this has nothing to do with Clockworkmod, you are really pissed that samsung requires recovery and kernels on the same partition.
Koush can only do so much magic.
Bielinsk said:
So, this has nothing to do with Clockworkmod, you are really pissed that samsung requires recovery and kernels on the same partition.
Koush can only do so much magic.
Click to expand...
Click to collapse
?
How much magic does it take to remove the ET4G from Rom Manager's compatability list?
I'd bet not too much: In fact, I'd bet I could learn that trick in one short weekend.
Sent from my PG86100 using xda premium
If you're still rooted Mobil odin
Nandroid hardly ever works for me, it usually fails during the restore.
just uninstall rom manager its about worthless for our phone.
drksilenc said:
just uninstall rom manager its about worthless for our phone.
Click to expand...
Click to collapse
I know it sux but I have to agree the real problem and question is if you know your way around your phone then honestly why in the hell would you use Rom Manager, Not getting on you but I too hated CWM on OG Evo, I used Amon but the one thing we all learned early is do it yourself so you dont need Rom Manager...
I love the new clockwork mod touch recovery. I actually like it better than twrp2.0. Only thing I like about twrp is you can compress the backups. The new cwm touch was just released for the ns4g.
Sent from my Nexus S 4G using xda premium
I agree ROM manager is useless in the galaxy s4g forums its ROM Mangler.
Sent from my SPH-D710 using xda premium
playya said:
I know it sux but I have to agree the real problem and question is if you know your way around your phone then honestly why in the hell would you use Rom Manager, Not getting on you but I too hated CWM on OG Evo, I used Amon but the one thing we all learned early is do it yourself so you dont need Rom Manager...
Click to expand...
Click to collapse
I know, I know...
(And I'm back up with CM9 on my ET4G: used my desktop, couldn't wait all day), and believe me: there's probably no one who's more outspoken about their anti-cwm/rommanagerness than I am: I'm just mad at myself for believing that the new update would work..
Oh well, lesson (re)learned....
Sent from my SPH-D710 using xda premium
This is why i no longer use that pos rom manager. When i first started out with android that biatch messed up my og epic a few times. I learned my lesson after a few odins
Sent from my SPH-D710 using xda premium
eao1991 said:
This is why i no longer use that pos rom manager. When i first started out with android that biatch messed up my og epic a few times. I learned my lesson after a few odins
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I use it all the time to boot into recovery and that is it
Sent from my SPH-D710 using xda premium
Originally Posted by eao1991
This is why i no longer use that pos rom manager. When i first started out with android that biatch messed up my og epic a few times. I learned my lesson after a few odins
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I use it all the time to boot into recovery and that is it
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I use the extended power options for that...but obviously the rom needs to include it which most do now. I'm still kicking myself in the ass for ever buying rom manager but I guess it was the noob in me.
Sent from my SPH-D710 using xda premium
Same thing happened to me when I first rooted my phone. I rooted the stock rom then installed rom manager and installed the recovery that way. Then when I booted into recovery, the only option I had was to reboot.
Don't ever use Rom Manager. Ever.
CBowley said:
Same thing happened to me when I first rooted my phone. I rooted the stock rom then installed rom manager and installed the recovery that way. Then when I booted into recovery, the only option I had was to reboot.
Don't ever use Rom Manager. Ever.
Click to expand...
Click to collapse
For our phone.
There's definitely nothing wrong with CWM. Blame rom manager if you must place the blame anywhere besides yourself.
I bought rom manager to support clockworkmod and have access to the latest clockworkmod versions. I think they have provided a wonderful tool. Anyway, I actually never used it except to check for roms and latest clockworkmod.
I've flashed the touch version of clockworkmod (downloaded the .img file from the clockrkmod web site) on my ns4g using adb and fastboot (thanks to Paul627 for the tutorial).
Sent from my Nexus S 4G using Tapatalk
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!
I just got this new SG3 and was using Rootbox on my last one which I really liked. I noticed they use TWRP in their update options so I figured I would try with this new g3. First time trying TWRP downloaded the latest from their blog openrecovery-twrp-2.4.3.0-d2att.tar. I really like the looks & feel but am having nothing but trouble with flashing roms. Can some one tell me why I should not go back to CWM?
lectron8 said:
I just got this new SG3 and was using Rootbox on my last one which I really liked. I noticed they use TWRP in their update options so I figured I would try with this new g3. First time trying TWRP downloaded the latest from their blog openrecovery-twrp-2.4.3.0-d2att.tar. I really like the looks & feel but am having nothing but trouble with flashing roms. Can some one tell me why I should not go back to CWM?
Click to expand...
Click to collapse
OK so I went back to CWM flashed task650 AOKP, and gapps, not one problem, smooth as can be and now running new rom. Thanks CWM
lectron8 said:
I just got this new SG3 and was using Rootbox on my last one which I really liked. I noticed they use TWRP in their update options so I figured I would try with this new g3. First time trying TWRP downloaded the latest from their blog openrecovery-twrp-2.4.3.0-d2att.tar. I really like the looks & feel but am having nothing but trouble with flashing roms. Can some one tell me why I should not go back to CWM?
Click to expand...
Click to collapse
Umm what kinda problems did you encounter trying to flash anyway?
Sent from my SAMSUNG-SGH-I747 using xda premium
Not sure why your having issues with it. No problems here with TWRP
Wayne Tech S-III
zelendel said:
Not sure why your having issues with it. No problems here with TWRP
Wayne Tech S-III
Click to expand...
Click to collapse
+1 always used TWRP.. Like always
Sent from my SAMSUNG-SGH-I747 using xda premium
Probably me
metalhead2791 said:
Umm what kinda problems did you encounter trying to flash anyway?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Its probably me but I just couldn't get it to work. I tried to flash from goomanager the right rom & gapps and I also tried from recovery. I didn't think it worked, I didn't see any confirmation of install, so I got scared and restored.
I have since done it with CWM and am ok. Thanks for the response anyway.
How did you end up flashing CWM back over TWRP? I too am having issue and would like to flash back CWM, but can't find a way how to. No flashable .tar file as far as I can find, and ROM manager doesn't list me the option to flash CWM.