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
I wanna flash Touch through Odin (unless there's an easier way) but will having regular clockwork installed hurt anything if I flash?
Sent from my SCH-I535 using xda app-developers app
Flash touch over regular cwm via ez recovery. It's fine. Don't use odin to flash recovery.
Thanks! Did that and it worked!
Sent from my SCH-I535 using xda app-developers app
FYI...it would be better if you ran CWM 6.0.1.0 instead of CWM Touch...ive had better results with the newer version, if you're interested in trying it out.
I actually used CMW to flash 6.0.1.2 over 6.0.1.0 as opposed to using EZ recovery. I used EZ Recovery to get 6.0.1.0 on the phone in the first place. I do this because the first S3 I tried to use the custom option in EZ Recovery on was soft bricked upon flash completion.
t h turkick
shangrila500 said:
I actually used CMW to flash 6.0.1.2 over 6.0.1.0 as opposed to using EZ recovery. I used EZ Recovery to get 6.0.1.0 on the phone in the first place. I do this because the first S3 I tried to use the custom option in EZ Recovery on was soft bricked upon flash completion.
Click to expand...
Click to collapse
Agreed, just use the CWM ROM Manager app to flash on the most current 6.0.1.2. You can also flash most recent touch recovery through the app as well, that option is at the bottom. I use the touch while I am using ICS roms, but when I start playing with JB developments, I flash back to 6.0.1.2 standard recovery. Though I have not experienced any issues with touch and JB, the developers warn in bold to not use it with JB roms. CWM is updated more frequently than the EZ recovery app, and why use an outside source to flash CWM anyways? EZ recovery is good to start out with because of its different recovery options, but ultimately is not better that the actual recovery source app CWM.
Hey there, I have a rooted HTC Sensation. I recently installed CM9 on my phone, before doing that however I made a backup of my stock ROM using Clockworkmod touch which I flashed using a fastboot command, I then wiped and installed CM9. I installed ROM manager after and pressed the button to install CMW to see if there was any updates, instead of updating it downgraded my CWM to a non touch version. I have made backups of CM9 using the non touch based CWM, my question is that will my older version of CWM restore a backup that was created from a newer CWM? Or... if I reflash a Clockworkmod touch recovery again, would I be able to access my original stock ROM and my CM9 ROM as well?
Many thanks
Jake
First of all, this is a question and therefore should be asked in the Q&A section. Regarding your question, I would go ahead and flash 4Ext touch. It is fully compatible with CWM backups, and touch-enabled.
I agree with above post, install 4ext recovery, it's a great recovery and very easy to use. It has many features! You won't regret installing it. You can get the download here on xda or even download it from the play store! It's the best recovery I've ever used! It will make things easier for you. Also I believe some roms require 4ext. Recovery. Hope this helps. Best wishes.
Sent from my HTC Sensation using xda premium
I have flashed many 4.3 Roms and can not get any of them to boot. I have followed all install instructions but can't get past gs3 screen. Any ideas?
Sent from my SCH-I535 using xda app-developers app
im having a similar problem to yours..i mean after i do a fresh install+gapps it works..but after i go back to recovery and install my other files it wont go past the gs3 logo no idea why.
Yep frustrating any other ROM is OK just 4.3 not working, sucks.
Sent from my SCH-I535 using xda app-developers app
I've flashed every 4.3 and all booted. Try just flashing ROM first. Let sit a few minutes then flash gapps. I also use the eclipse ROM gapps for all. No issues.
Sent from my SCH-I535 using xda app-developers app
I also have the same problem when I try to reboot on 4.3 Roms. First boot up is fine. But when I go into to recovery it won't boot back up unless I reflash the ROM from the start. If someone tries flashing ROM and gapps separately let us know if it fixes it.
Sent from my SCH-I535 using Tapatalk
Tried eclipse ROM and apps. No different. Initial boot works and ROM runs fine but reboot freezes up on gs3 screen. What is getting scrambled and is there a way to fix this.
Sent from my SCH-I535 using xda app-developers app
I've never had this issue. What I've done/used to flash all 4.3 roms was use the super wipe tool found in the general section(the one that wipes data, system and caches only) and then run it once and flash Rom+ gapps as instructed. I use twrp as well. Also, perhaps it's a stock 4.3 kernel and maybe flash a kernel straight after you flash the rom and gapps. Rom> gapps>kernel . Hope it helps
Sent from my SCH-I535 using Tapatalk
---------- Post added at 08:47 PM ---------- Previous post was at 08:41 PM ----------
http://forum.xda-developers.com/showthread.php?t=2097365
[Mod][Utility] Wiping Tools - Simple and Fast
Sent from my SCH-I535 using Tapatalk
I used ez recovery from the play store and used cwm touch recovery and I no longer have the reboot issues. Even if you're using cwm, I would just download ez recovery and try it.
Sent from my SCH-I535 using Tapatalk
Use ez recovery to flash the ROM or install cwm and then flash through that?
Sent from my SCH-I535 using xda app-developers app
I had a similar problem when I first tried 4.2 but I've found two ways that have always worked for me
Full wipe (I wipe everything 3 times, but I'm sure that's overkill)
Flash rom
Flash gapps
Reboot
If it gets stuck on any screen wipe the cache and dalvik cache
Reboot
The other method I've only used with Dirty Unicorns
Full wipe
Flash rom
Reboot
Once the rom reboots, reboot back into recovery
Flash gapps
Reboot
Wait 10 minutes
You can either reboot again or just use as is
But if nothing is working you can odin back to stock
Then use this tool to root, unlock the bootloader, and flash the custom recovery of your choice http://forum.xda-developers.com/showthread.php?t=2332825 (it even works on a mac)
(This is what I always use to root, unlock the bootloader, and flash recovery whenever I have to flash back to stock)
After I do that I always reboot and use Rom Manager to flash the latest recovery before flashing anything else.
These 2 roms have been 100% stable for me
http://forum.xda-developers.com/showthread.php?t=2484256 (4.3.1)
http://forum.xda-developers.com/showthread.php?t=2469789 (4.3 I've never tried the weeklies just the lastest stable build)
Hope it helps
It seems that most ROMs will boot up fine with the latest TWRP recovery. But there are a few that will only boot up with CWM. So download both recoveries and flash them using ez recovery when one of them isn't working.
So, I usually stick with TWRP 2.6 as my default. The great thing about ez is that it includes cwm in it. First off I'd make sure you're running the latest recovery available. Then if that doesn't work restore your backup, hopefully you made one, and flash cwm and try reflashing the ROM. Assuming you're wiping everything at least 3 times and flashing the correct ROM with the correct gapps, there's no reason why it shouldn't work. And another thing. It's never a good idea to restore data from any app, ever. Trust me, I know.
Sent from my SCH-I535 using Tapatalk
Juice3250 said:
It seems that most ROMs will boot up fine with the latest TWRP recovery. But there are a few that will only boot up with CWM. So download both recoveries and flash them using ez recovery when one of them isn't working.
So, I usually stick with TWRP 2.6 as my default. The great thing about ez is that it includes cwm in it. First off I'd make sure you're running the latest recovery available. Then if that doesn't work restore your backup, hopefully you made one, and flash cwm and try reflashing the ROM. Assuming you're wiping everything at least 3 times and flashing the correct ROM with the correct gapps, there's no reason why it shouldn't work. And another thing. It's never a good idea to restore data from any app, ever. Trust me, I know.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
You do realize that the recoveries built into ez recovery are over a year old. I wouldn't flash those under any circumstances. Only use ez recovery to flash from the custom slot.
Sent from my SCH-I535 using Tapatalk 2
Thanks for correcting me on that one. My bad.
Sent from my SCH-I535 using Tapatalk
Hi – I have a stubborn issue with my Blaze 4G not working on CM roms, I would appreciate any help you guys can provide. Below are the details:
I recently bought a T-Mobile Samsung Galaxy S Blaze 4G, and did the following:
- Rooted it using the following guide (it now has ICS)
- SIM Unlocked it using the following guide (now it works on other networks)
- Updated to CWM 6.0.3.8, since JB roms needs it
- Flashed the T769-UVLH5 modem, since CM support it
And now when I flash CM 10 stable or 10.2 nightly it gets stuck in booting and displaying the CM logo animation screen, after few minutes it reboots and does it all over again.
I remember when I upgraded to CM JB on my SGS3 I needed to flash a JB stock rom on it to get the new boot loaders for JB, but I saw no mention of this on this forum. What else am I missing?
Thanks.
TINGEA said:
Hi – I have a stubborn issue with my Blaze 4G not working on CM roms, I would appreciate any help you guys can provide. Below are the details:
I recently bought a T-Mobile Samsung Galaxy S Blaze 4G, and did the following:
-Rooted it using the following guide (it now has ICS)
-SIM Unlocked it using the following guide (now it works on other networks)
-Updated to CWM 6.0.3.8, since JB roms needs it
-Flashed the T769-UVLH5 modem, since CM support it
And now when I flash CM 10 stable or 10.2 nightly it gets stuck in booting and displaying the CM logo animation screen, after few minutes it reboots and does it all over again.
I remember when I upgraded to CM JB on my SGS3 I needed to flash a JB stock rom on it to get the new boot loaders for JB, but I saw no mention of this on this forum. What else am I missing?
Thanks.
Click to expand...
Click to collapse
You wiped data/cache/system? Reinstall it. Anyways use the new 6.0.4.4 recovery.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
You wiped data/cache/system? Reinstall it. Anyways use the new 6.0.4.4 recovery.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom. I have to admit that I forgot to do the wipes. but even after doing the wipes (data/system/ factory rest/ cach/devalk) and reinstalling the CM nightly, I still have the same issue.
as for recovery, I updated to the latest version using the rom manager, and according to the official site clockworkmod[dot]com[slash]rommanager (can't post links) I have the latest version for Blaze. how do you get the 6.0.4.4 on blaze?
I still feel it's a ICS vs JB bootloaders issue, but not sure how to proceed next.
Thanks!
TINGEA said:
Thanks Somcom. I have to admit that I forgot to do the wipes. but even after doing the wipes (data/system/ factory rest/ cach/devalk) and reinstalling the CM nightly, I still have the same issue.
as for recovery, I updated to the latest version using the rom manager, and according to the official site clockworkmod[dot]com[slash]rommanager (can't post links) I have the latest version for Blaze. how do you get the 6.0.4.4 on blaze?
I still feel it's a ICS vs JB bootloaders issue, but not sure how to proceed next.
Thanks!
Click to expand...
Click to collapse
No boot loaders man. This is before Samsung's complications.
Recovery is here.
http://d-h.st/AFu
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Thanks Somcom3X, but still didn't work. When installing the CM room in recovery 6.0.4.4 I get a bunch of getprop assert failures. This used to work on the previous version (6.0.3.8). Now the Rom won't install.
Also, I'm curious what did you mean by this is before Samsung's complications?
Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
Thanks Somcom3X, but still didn't work. When installing the CM room in recovery 6.0.4.4 I get a bunch of getprop assert failures. This used to work on the previous version (6.0.3.8). Now the Rom won't install.
Also, I'm curious what did you mean by this is before Samsung's complications?
Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
After 2011 samsung began installing software and counters to try and prevent people from rooting and installing custom firmwares.
knox is an example of this.
These devices don't have any of that complicated security.
You handy with odin? Your recovery is not right. Just to be clear, what is your model number?
If it is T 7 6 9, your good to go to odin. I'd recommend going back to stock, and then install a recovery and you should be good to go.
Somcom3X said:
After 2011 samsung began installing software and counters to try and prevent people from rooting and installing custom firmwares.
knox is an example of this.
These devices don't have any of that complicated security.
You handy with odin? Your recovery is not right. Just to be clear, what is your model number?
If it is T 7 6 9, your good to go to odin. I'd recommend going back to stock, and then install a recovery and you should be good to go.
Click to expand...
Click to collapse
Thanks again, I use the guide here to convert the image into a tar.md5 to flash using odin, but after flashing successfully I still have the same issue when installing the CM zip file in recovery, and yes it is the T-mobile Samsung Galaxy S Blaze 4G T769.
any other possible causes?
BTW - when I was flashing via Odin my upload phone screen was showing that I have a custom rom and the counter was 1.... do I need to fix that?
TINGEA said:
Thanks again, I use the guide here to convert the image into a tar.md5 to flash using odin, but after flashing successfully I still have the same issue when installing the CM zip file in recovery, and yes it is the T-mobile Samsung Galaxy S Blaze 4G T769.
any other possible causes?
Click to expand...
Click to collapse
SOLUTION:
The reason your stock recovery system keeps getting overwritten at Android startup is because of a script that is being run.* All you need to do is either rename this script or simply delete it.
Please keep in mind that if you restore your stock ROM, this script will be restored with it so you will have to rename or delete it again.* Do the following:*
1.
Make sure your device is powered on and running normally,
2.
Make sure you have rooted your device and that you have all of the necessary permissions in order to manipulate system files.*
3.
In the root file system go to \system\etc
4.
Find the file named install-recovery.sh and either rename it or, as I did, delete it.*
That’s all there is to it.*
Please keep in mind that you will need to flash your custom system recovery one more time after modifying the script file.* After that, reboot away and you will always be able to get back into your new system recovery.
Good Luck and Happy Tweaking.
Click to expand...
Click to collapse
Try that.
Found it here http://mark.candleshoreblog.com/201...-factory-stock-roms-at-android-system-reboot/
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
Try that.
Found it here http://mark.candleshoreblog.com/201...-factory-stock-roms-at-android-system-reboot/
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom3X - but I'm not sure this is needed for my case. I read the original blog post and my recovery does not get overwritten. I actually rebooted multiple times into CWM recovery and each time it is the same 6.0.4.4.
I also went into the /system/etc folder and there is no install_recovery.sh file.
to clarify, here is where I'm stuck now:
- when I use CWM 6.0.3.8 CM install completes successfully, but then CM will not boot, and will keep on cycling on the boot logo screen.
- when I use CWM 6.0.4.4 I can't start to install CM as it complained that my phone is not t769.
in all cases I'm using CM 10.2 nightly for T769.
Thanks for the help.
You should delete assert lines at the top of the zip's updater-script and it will let you flash it.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
I removed the assert lines from the updater script, and it was able to complete the install process afterwards, however when I booted the new CM 10.0 system it got stuck on the cyanogenmod boot logo. I made sure I do a system/data rest, cleared cash, and cleared devalk.
I do not think it's an issue with my recovery as I'm getting the same result as I did with the official 6.0.3.8.
Something else is going on.
Any ideas?
Thanks.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
I removed the assert lines from the updater script, and it was able to complete the install process afterwards, however when I booted the new CM 10.0 system it got stuck on the cyanogenmod boot logo. I made sure I do a system/data rest, cleared cash, and cleared devalk.
I do not think it's an issue with my recovery as I'm getting the same result as I did with the official 6.0.3.8.
Something else is going on.
Any ideas?
Thanks.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Tar back to stock GB. Upgrade to ICS. Then root and install cwm. Flash away
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
You should delete assert lines at the top of the zip's updater-script and it will let you flash it.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom3X - but this is more trouble than what I wanted to put in - I'll stick with the rooted stock ROM I have. I was hoping the process was a little more straight forward, similar to my SGS3.
thanks for all your help thus far!
Somcom3X said:
Tar back to stock GB. Upgrade to ICS. Then root and install cwm. Flash away
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Ok, my rooted ICS stock is acting up (random shutdowns and such), so I need to give this another try and get this phone to CM.
I tared back to stock GB, skipped the upgrade to ICS (was not able to upgrade via the ROM software update option), flashed CWMR (5.0.4.x) via Odin, upgraded to CWMR 6.0.4.5, installed CM 11 nightly, and then wiped data/factory rest and Dalvik .... and ....
it is still stuck on the boot screen....
I seriously would appreciate a silver bullet right now!
TINGEA said:
Ok, my rooted ICS stock is acting up (random shutdowns and such), so I need to give this another try and get this phone to CM.
I tared back to stock GB, skipped the upgrade to ICS (was not able to upgrade via the ROM software update option), flashed CWMR (5.0.4.x) via Odin, upgraded to CWMR 6.0.4.5, installed CM 11 nightly, and then wiped data/factory rest and Dalvik .... and ....
it is still stuck on the boot screen....
I seriously would appreciate a silver bullet right now!
Click to expand...
Click to collapse
Hmm. Go back to stock ics, flash a 10.2 recovery, then flash whatever you desire.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
What is a10.2 recovery? Is it a certain version of CWMR? And do I need to flash it via Odin? Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
What is a10.2 recovery? Is it a certain version of CWMR? And do I need to flash it via Odin? Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
It would be cwm 6.0.2.7
You can flash the img through a zip or by terminal on the phone.
Odin needs a tar'd recovery img
Sorry been very busy.
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2577265
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Thanks Somcom3X - I looked all over this forum and the internet, and could not find a link for a 6.0.2.7 CWM for Blaze - I found it for other phones but not Blaze. can you please point me to a link if you happen to know of one. the official site does not have an archived list of previous versions.
as for the provided link, I did follow it through, and downloaded the recovery Tar (it was CWM 5.5.04) but that yielded the same results after installing CM 10 and 10.2 - stuck at boot screen logo. I'm reasonably confident now that it is not a recovery issue, as I flashed half a dozen different versions and none worked with CM 10, 10.2, or 11.... it has to be something else!
Thanks.
TINGEA said:
Thanks Somcom3X - I looked all over this forum and the internet, and could not find a link for a 6.0.2.7 CWM for Blaze - I found it for other phones but not Blaze. can you please point me to a link if you happen to know of one. the official site does not have an archived list of previous versions.
as for the provided link, I did follow it through, and downloaded the recovery Tar (it was CWM 5.5.04) but that yielded the same results after installing CM 10 and 10.2 - stuck at boot screen logo. I'm reasonably confident now that it is not a recovery issue, as I flashed half a dozen different versions and none worked with CM 10, 10.2, or 11.... it has to be something else!
Thanks.
Click to expand...
Click to collapse
I'm very sorry for the delay. Been very very busy.
https://www.dropbox.com/s/awp1zy4u3x34a2v/CWM-cm-10.2-Recovery-t769.zip
That is my personal 10.2 recovery. Works fine for me.
The author is me, but I was too lazy to change the lines.
Sent from my SAMSUNG-SGH-T769 using Tapatalk