So I like to use Rom Manager to manage my backups. I downloaded it but now it says I don't have cwm installed. I flashed it with EZ recovery. Would I be okay to flash recovery again so RM acknowledges it and I can then manage backups or would that conflict.
Great Question - Thanks for asking it
tu3218 said:
So I like to use Rom Manager to manage my backups. I downloaded it but now it says I don't have cwm installed. I flashed it with EZ recovery. Would I be okay to flash recovery again so RM acknowledges it and I can then manage backups or would that conflict.
Click to expand...
Click to collapse
By now you've probably plotted the solution. But, I was wondering the same question. Which App is better and why?
I will continue working on this for myself. All I have come up with so far: Some ROM's install better with one or the other and it's best to have all-hands-on-deck, so to speak
Again thanks for starting this thread!
I have the same question.
Sent from my SCH-I535 using xda premium
rom manager has cwm 6.0.1.2 touch which has issues restoring backups on some roms from what I have read. cwm 6.0.1.1 non touch from ez recovery works flawless for everything and thats what I stick with. the only issue found with it is the nandroid dates are way off, but simply renaming them fixes that issue.
I thought the issue was with cwm touch 5 . something that ez recovery offers and not with the updated 6.0.1.2 through rom manager?
I'm running 6.0.1.2 without any issues, including multiple touchwiz and one aosp backup. Haven't noticed any problems other than never going back to the standard version cause touch is pure awesomeness
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises
Related
I have a rooted VZ GS3 with SU, ROM Manager, some Titanium frozen apps. Wanting to load a ROM but need to backup first. Whenever I attempt to backup with CWM (5.8.4.8) I get "Error while backing up boot image!". There is plenty of space so any idea what I am missing?
Bump. I'm having the same issue. My Cwm doesn't show my external sdcard either. It used to show internal sdcard and external sdcard but after soft bricking and using Odin to flash a Rom I lost that ability.
Sent from my SCH-I535 using xda app-developers app
same problem
i also have same problem
Is that a version of CWM Touch?
I believe this is a common issue, at least when I was having it and researched, and the accepted fix is to use a non-touch CWM. I'd recommend 6.0.1.0 as it has the ability for kexec and ensures you won't have an issue with flashing aftermarket kernels
Sent from my SCH-I535
Josolanes said:
Is that a version of CWM Touch?
I believe this is a common issue, at least when I was having it and researched, and the accepted fix is to use a non-touch CWM. I'd recommend 6.0.1.0 as it has the ability for kexec and ensures you won't have an issue with flashing aftermarket kernels
Sent from my SCH-I535
Click to expand...
Click to collapse
This!
Verified the issue is with CWM Touch. I reverted to the non-touch version, and I had no issues backing up.
Try using a different version of CWM touch. I have trouble backing up and restoring with touch too
I have no issues with K-exec CWM http://goo.im/devs/BeansTown106/SGS3vzw/cm9/d2vzw_recovery.img
Josolanes said:
Is that a version of CWM Touch?
I believe this is a common issue, at least when I was having it and researched, and the accepted fix is to use a non-touch CWM. I'd recommend 6.0.1.0 as it has the ability for kexec and ensures you won't have an issue with flashing aftermarket kernels
Sent from my SCH-I535
Click to expand...
Click to collapse
6.0.1.0 should do it. Also, make sure you are selecting the option to back up to the internal sdcard and not the external. That one took me a few minutes to realize as i don't have a 2nd sd card in my phone.
I just finished rooting my Verizon GS3 using the Easy root method ( http://www.youtube.com/watch?v=JVRjAiW7HdE&feature=plcp ) and everything went well, Installed Rom Manager, flashed Verizon GS3 CWM Recovery. Booted into Recovery, went to make a backup and it keeps giving me an error "Error while backing up boot image!" I've checked and it seems the the root took just fine, Superuser is working. I just can't make a backup in CWM. Please help
If you're using CWM Touch than that's the cause for not backing up. Use a non-touch CWM, preferably 6.0.1.0 so that you have the ability to use kexec and custom roms later to prevent potential issues later
Sent from my SCH-I535
You Da'man! Thanks so much
No problem, glad to help!
And meant to say custom kernels
Sent from my SCH-I535
What's a non-touch cwm?
Sent from my SCH-I535 using xda premium
when you go into Rom Manager and flash CWM it asked me if I want to purchase the "Touch". I did the first time I and was having an issue making a backup. When you are in CWM you usually have to use your volume up/down to toggle through it. If you add the "tough" you can use the screen and just tough what command you want to do. For some reason it didn't like it and wouldn't let me make a backup. So I flashed CWM again and it let me make the backup.
So I installed Clockwork mod touch via terminal emulator and the image on their site. It installs fine and works.....not really.
When I get into recovery and attempt to perform a backup of my current rom it simply says an error has a occured. this happens weather I boot into recovery to do it manually or i attempt to do it through rom manager.
Any ideas of what could be wrong?
Try installing EZ-Recovery from the market, then flash CWM Touch from there. It's a one click flash to recovery, no terminal commands.
Sent from my SCH-I535 using xda app-developers app
Vorfidus said:
Try installing EZ-Recovery from the market, then flash CWM Touch from there. It's a one click flash to recovery, no terminal commands.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
jesus that app made it so much simpler. too bad it's still not working correctly. Now I'm wordering if the img got corrupted somehow during download to the phone.
After redownloading and flashing it the error is still happening. Regular CWM Recovery works perfectly. Touch...still getting errors. Basically when I click backup it says "backing up boot image" then nothing happens and it goes right back the menu. When I click it again I get the erroer message "Error while backing up root image"
One thing I've noticed is, even with CWM Touch flashed, rom manager still sees it as CWM Recovery 5.8.4.9
Is it possible it just doesn't like synergy?
Yeah I had the same problem when I installed CWM touch using the adb push method. Wouldn't backup, backup was fine with the non-touch version. However, installing via ez-recovery worked.
jasondhsd said:
Yeah I had the same problem when I installed CWM touch using the adb push method. Wouldn't backup, backup was fine with the non-touch version. However, installing via ez-recovery worked.
Click to expand...
Click to collapse
even using ez-recovery didn't work for me.
Hitman3984 said:
even using ez-recovery didn't work for me.
Click to expand...
Click to collapse
Same issue for me. Looking for possible solutions.....
SiXandSeven8ths said:
Same issue for me. Looking for possible solutions.....
Click to expand...
Click to collapse
glad I'm not the only one.
Also noticed tonight smart alert isn't working after flashing to synergy. I thought maybe haptic feedback in power saving could be the cause but it isn't.
Edit: Tried again for the hell of it and this time I pointed to the cwm touch apart of ezrecovery and not the custom option by chossing the file and it now works.
All of that said rom manager and the cwm touch don't seem to work well together(im guessing unless you purchase
?) When you make a backup manually from going into recovery rom manager doesn't see it. CWM Touch also doesn't see the recovery made from non touch made in rom manager. Also Clockwork mod also still shows recovery as cwm 4.8.4.9
I'm relatively experienced in flashing roms but not ALL things root so this could be normal and just how things work.
Smart alert, still doesn't work.
I have been flashing (roms) for a while now devices including G2, HTC Hero, HTC Thunderbolt, Moto Razr, and now Galaxy S3. I don't typically post questions on any forums because I usually can find an answer with enough searching, it pains me to write this.
Problem: I can only flash certain roms on my Verizon SGS3.
I have no problem flashing unofficial aokp, unofficial cm10, and Synergy.
When I try to install different roms from xda and other websites i get the attached photo. These roms include paranoid android, miui, liquids jelly bean, and a few others.
My device is rooted, unlocked bootloader through ez unlock, running clockworkmod (touch) v5.8.4.5 via ez recovery.
Before I flash I always:
wipe data/factory reset
wipe cache partition
format system
wipe dalvik cache
Re-downloading has not fixed the issue. I'm sure im missing something simple any help would be warmly welcomed!
Thanks in advance all!
-Stumped S3 User
The problem is your running the wrong cwm recovery. 5 . something version causes problems with jb rom's. Surprising you got cm10 to run. Download cwm rom manager and install cwm touch 6.0.1.2 touch from in that application. EZ recovery does not offer that version of touch, but it does offer that version of regular. I don't see all the hype about ez recovery. That's definitely your issue.
Sent from my SCH-I535 using xda premium
annoyingduck said:
The problem is your running the wrong cwm recovery. 5 . something version causes problems with jb rom's. Surprising you got cm10 to run. Download cwm rom manager and install cwm touch 6.0.1.2 touch from in that application. EZ recovery does not offer that version of touch, but it does offer that version of regular. I don't see all the hype about ez recovery. That's definitely your issue.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Bingo!! Wrong version of CMW, just download e-z flasher from the play store and use it to flash either TWP or CMW. Easy peasy quick and easy.
I suggest you use twrp.
Twrp has bugs with jb rom's. Cwm regular or touch 6.0.1.2 is the most stable safe way to go. If your unsure at all, use cwm. Twrp on our devices at this time is NOT as stable as cwm, but does work effectively. If you use twrp, don't be surprised if you get a poor flash here and there.
Sent from my SCH-I535 using xda premium
annoyingduck said:
Twrp has bugs with jb rom's. Cwm regular or touch 6.0.1.2 is the most stable safe way to go. If your unsure at all, use cwm. Twrp on our devices at this time is NOT as stable as cwm, but does work effectively. If you use twrp, don't be surprised if you get a poor flash here and there.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Cwm 6.0.1.2 all day. Refuse to use anything else lol. Unless amon ra gets ported
Sent from my SCH-I535 using Tapatalk 2
Worked like a charm!
I downloaded rom manager, installed latest clock work, updated to touch, and it is working perfect! Thanks to all! The fun begins
what is the diffrence between twrp and clockworkmod? ever since i started rooting and flashing all ive known is clockworkmod....but it wont work with some of my apps like rom toolbox to flash roms....its telling me to use twrp......whats the diffrence though? i tried twrp touch once and it bricked my phone......so what is the diffrence? which one is better? should i get it? is there any risk on roms not being flashable with twrp? if so can i get the latest link and how to? i realize these might all be opinions but would really like to hear what you all have to say...thanks
I've never used an app to flash a Rom. I prefer to go to recovery myself, so I know what gets wiped. I've tried twrp a couple times before, but my phone didn't play nice with it, and it would refuse to boot, telling me there was no recovery or boot img loaded.
Sent from my ns4g using Tapatalk 2
p1gp3n said:
I've never used an app to flash a Rom. I prefer to go to recovery myself, so I know what gets wiped. I've tried twrp a couple times before, but my phone didn't play nice with it, and it would refuse to boot, telling me there was no recovery or boot img loaded.
Sent from my ns4g using Tapatalk 2
Click to expand...
Click to collapse
Crap Installed twrp and haven't used it but after what you said I'm scared to.....anyway to go back to cwm?
Sent from my Nexus S 4G using xda premium
Flash it thru fastboot or use the app "flash image gui" it is a paid app on the market, but has also been offered here on xda by the dev for free. I haven't used the app in awhile, but it worked for me back on ics when I used it last.
If you use fastboot it's fastboot flash recovery recovery.img just make sure to use the actual recovery img file name instead of "recovery.img" at the end
Sent from my ns4g using Tapatalk 2
mcluvin1065 said:
Crap Installed twrp and haven't used it but after what you said I'm scared to.....anyway to go back to cwm?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Use this guide
I use twrp and have for months. If your phone got bricked you probably did something wrong. Most likely flashed the wrong image. Use the goomanager app from the market to install the twrp. Open the app press menu and select install open recovery script option. Works like a charm.
Sent from my Nexus S using xda app-developers app
Yea i love twerps ui. It is slick. And all the features are awesome.
Sent from my SCH-I800 using Tapatalk 2
They are just both recoveries that you can use on your device. TWRP is based on the stock recovery and is all touch compatible whereas ClockWorkMod or CWM for short is a recovery where it does all the same features but some features of it are not available whereas in TWRP they are and vise versa. I use TWRP and I personally think that it is better than CWM any day. Yes like you I started of knowing only what CWM is but then I researched and found TWRP. I used TWRP ever since.
Although there are some disadvantages and Advantages of the both.
ClockworkMod:
The Advantages of CWM is that the backups are all in a way "linked" together. This means if you have the app swype for example and you backed that rom up that has Swype, and then made another backup of another ROM but with the same app Swype CWM recognizes that and uses the apk from the previous backup on the new one. So according to me it makes the backup faster.
Also there is a feature which is Fixing Permissions. TWRP has Fixing Permissions but it is not really that well made. With the Fixing Permissions it lets you fix apps that stop or like crash when you try and launch them. That helps when you flash a custom ROM and when you boot you get all these errors like "YouTube has stopped".
TWRP:
The advantages of TWRP is that it is all touch compatible and all "open source" in a way. I'm not sure about CWM but in TWRP you can customize it very easily if you know XML, with CWM I don't know. With TWRP it uses less data or memory on your SD card so it saves space on your internal storage which is a bonus.
Anything else I find about the advantages about the 2 I will post here in this post.
UselessSniper001 said:
They are just both recoveries that you can use on your device. TWRP is based on the stock recovery and is all touch compatible whereas ClockWorkMod or CWM for short is a recovery where it does all the same features but some features of it are not available whereas in TWRP they are and vise versa. I use TWRP and I personally think that it is better than CWM any day. Yes like you I started of knowing only what CWM is but then I researched and found TWRP. I used TWRP ever since.
Although there are some disadvantages and Advantages of the both.
ClockworkMod:
The Advantages of CWM is that the backups are all in a way "linked" together. This means if you have the app swype for example and you backed that rom up that has Swype, and then made another backup of another ROM but with the same app Swype CWM recognizes that and uses the apk from the previous backup on the new one. So according to me it makes the backup faster.
Also there is a feature which is Fixing Permissions. TWRP has Fixing Permissions but it is not really that well made. With the Fixing Permissions it lets you fix apps that stop or like crash when you try and launch them. That helps when you flash a custom ROM and when you boot you get all these errors like "YouTube has stopped".
TWRP:
The advantages of TWRP is that it is all touch compatible and all "open source" in a way. I'm not sure about CWM but in TWRP you can customize it very easily if you know XML, with CWM I don't know. With TWRP it uses less data or memory on your SD card so it saves space on your internal storage which is a bonus.
Anything else I find about the advantages about the 2 I will post here in this post.
Click to expand...
Click to collapse
Last CWMR touch 6.0.1.0 !
FULLY WORKING!
Flashable zip!
http://db.tt/vBx3A1UF