Related
Guys which recovery is better- Amon RA or Clockwork? What is the difference b/w the two?
both are good at getting the job done. but clockwork is much better overall since it integrates with ROM manager and automates everything for you. definitely try out clockwork.
i've had issues with clockwork recently, personally I use Amon_Ra, but both are VERY similar almost identical
Blueman101 said:
i've had issues with clockwork recently, personally I use Amon_Ra, but both are VERY similar almost identical
Click to expand...
Click to collapse
What type of issues?
Only reason I dont use Clockwork is because it works well with ROM Manager it auto updates my ROM and that is just annoying But really I cant seem to find any major differences between the two
Keshav_CoolDude said:
What type of issues?
Click to expand...
Click to collapse
It didn't wipe a previous rom correctly.
Amon 's recovery gives me a feeling that it was designed for Nexus One
clockwerk's recovery gives me the opposite feeling, it was designed for all devices.
amon's recovery is easier to use, yet powerful enough for doing everything
clockwerk's recovery provides more options and detailed functionalities, but we usually don't use them all.
amon's UI is more easy and obvious to use than clockwerk's
if you don't rely on rom manager, I personal suggest using Amon's
houzuoguo said:
Amon 's recovery gives me a feeling that it was designed for Nexus One
clockwerk's recovery gives me the opposite feeling, it was designed for all devices.
amon's recovery is easier to use, yet powerful enough for doing everything
clockwerk's recovery provides more options and detailed functionalities, but we usually don't use them all.
amon's UI is more easy and obvious to use than clockwerk's
if you don't rely on rom manager, I personal suggest using Amon's
Click to expand...
Click to collapse
+1
(charac)
Personally I think that the strong point of clockworth is the integration with ROM manager. In the other hand, I think Amon`s RA is more clear and has enough power to complete any task. The two are good, but I prefer Amon`s.
It`s your choice. Try both and decide.
I started using clockwork for some time. I gotta say I love the ROM Manager integration and the ability to go through folders so you don't have to always have what you're trying to flash on the root of your sd card. just recently though while restoring a backup clockwork just froze. I let it sit thinking it was just taking a while but after a good while I just pulled the battery. I went back to restore and it flew by quickly, restoring the rom just fine. this has happened twice already and it never happened with amon's recovery. I agree with houzuoguo when he said it feels like amon's was built for the nexus and clockwork was built for multiple devices.
I like clockwork for 1 reason. I love the comfirmation window he uses. A buch of no's then a yes are u sure.
Example:
No
No
No
No
No
No
No
Yes - This action can not be reversed
No
No
No
It amuses me.
What rom is the best?
What flavor ice cream is the best?
Try them both for a bit and make up your own damn mind.
codesplice said:
What rom is the best?
CM6 Nightly
What flavor ice cream is the best?
Mint Chocolate Chip by far.
Try them both for a bit and make up your own damn mind.
Click to expand...
Click to collapse
I win! lol. But he does has a point.
Amon Ra is more stable/reliable; clockwork has the integration with ROM manager.
Personally, it annoys me that I can't even do the simple things like "check for updates" and "download ROM" without having clockwork flashed first. I don't get why, those are not functions needing the recovery; let me at least check updates and download them. I can do the flashing manually with my recovery of choice. I guess its an effort to get market share and reliance on the app, leading to more sales for the more feature rich paid app. So I avoid clockwork on principal. Not that I don't want to support dev's, I do, but this seems underhanded to me. Gimping every feature, whether they depend on recovery functionality or not.
Ok thnx everybody..
I think I should stick with Amon only..
A lot of roms say that they require clockwork recovery 3.0.0.6 to flash them. I know there's a way to flash it manually, but I personally want to wait until rom manager supports it. Is it absolutely necessary that 3.0.0.6 is there? I have 3.0.0.5, and i'm fine with switching between that and 2.5.1.2 in order to flash roms. Namely, i want to flash royalmint as it looks quite sick. quite sick indeed.
If you're willing to use 3.0.0.5 to flash Gingerbread ROMs and 2.5.x.x to flash Froyo ROMs, then it's not necessary. It's a whole lot easier to have one recovery though, obviously. ROM Manager does support 3.0.0.6 as far as managing backups, if that matters to you.
If your fine with re-flashing then not really. There are some fixes and code improvements but for the most part its up to you. but i'd suggest the 3.0.0.6 just for the convenience and i haven't heard of anyone reporting issues related to it. So as far as being safe id say its as safe and flashing back and forth to begin with. but don't do anything your uneasy about cuz if something does happen you are solely responsible.
If nothing else you could flash the newest version of 3.0.0.6 just so you don't have to flash "stock" recovery when you need/want to recondition/retrain your battery.
http://forum.xda-developers.com/showthread.php?t=1014554
Isn't there a problem with backup in 3.0.0.5? Either way, the maker of Rom Manager works with the CM team, so there are literally 20 phones out that they are trying to provide support for. It's not that they guy has seen the fixes/updates in 3.0.0.6 and decided they were wrong, he just has a lot on his plate. The improvement is worth it, for compatibility, if nothing else. Add in the ability to charge while off in the newest 3.0.0.6 and it is literally a one-stop recovery. Do what you like, you don't NEED it, then again you don't NEED custom ROMs, or cell phones, or forums. So I guess it's all relative, but it IS important for flashing and ensuring a calibrated battery.
kimbernator said:
A lot of roms say that they require clockwork recovery 3.0.0.6 to flash them. I know there's a way to flash it manually, but I personally want to wait until rom manager supports it. Is it absolutely necessary that 3.0.0.6 is there? I have 3.0.0.5, and i'm fine with switching between that and 2.5.1.2 in order to flash roms. Namely, i want to flash royalmint as it looks quite sick. quite sick indeed.
Click to expand...
Click to collapse
You do not NEED the 3.0.0.6 but it does make life easier. If you don't mind re-flashing the images then more power to you.
3.0.0.6 makes life easy. Trust me. I flash backup and restore alot through diff builds.
Sent from my HTC Glacier using XDA Premium App
I love 3.0.0.6 and has made life a lot easier, but don't believe it is necessary. Have heard that some of the bootloop issues are from using 3.0.0.5, but don't know if that holds any salt. Some of the mods are not compatible with 3.0.0.6 though.
Sent from my HTC Glacier using XDA App
ptran said:
I love 3.0.0.6 and has made life a lot easier, but don't believe it is necessary. Have heard that some of the bootloop issues are from using 3.0.0.5, but don't know if that holds any salt. Some of the mods are not compatible with 3.0.0.6 though.
Click to expand...
Click to collapse
You're giving out bad information. As has been said over and over, 3.0.0.6 is absolutely necessary to flash both Froyo and Gingerbread ROMs, and there is NOTHING that it is not compatible with. With 3.0.0.6 installed, you can flash ANYTHING, which is why it's so highly recommended.
Not true. Some of the older mod scripts are not compatible with the newer clockwork recoveries (see faves to anything post by trueblue_drew) and thus will get a script error if you don't flash back prior to flashing it. Most mods will work, but NOT all.
Sent from my HTC Glacier using XDA App
ptran said:
Not true. Some of the older mod scripts are not compatible with the newer clockwork recoveries (see faves to anything post by trueblue_drew) and thus will get a script error if you don't flash back prior to flashing it. Most mods will work, but NOT all.
Click to expand...
Click to collapse
Please link to those mods so people are aware. So you're saying they work when flashed on 2.5.x.x but not 3.0.0.x?
Yes. I thought the same thing as you until I tried flashing an anything to mms favorites button this morning and then got the script error. Read through the post and found out why. Will post a link to the thread.
Sent from my HTC Glacier using XDA App
forum.xda-developers.com/showthread.php?t=885967&page=12
Sent from my HTC Glacier using XDA App
ptran said:
forum.xda-developers.com/showthread.php?t=885967&page=12
Click to expand...
Click to collapse
For those that might want that, that's good to know, thanks. I still think that considering all factors, 3.0.0.6 is still the best overall recovery solution, but it's good to know that it doesn't work for 100% of flashable items.
Agreed. Flashing back and forth seems like a waste of time overall.
Sent from my HTC Glacier using XDA App
ptran said:
Not true. Some of the older mod scripts are not compatible with the newer clockwork recoveries (see faves to anything post by trueblue_drew) and thus will get a script error if you don't flash back prior to flashing it. Most mods will work, but NOT all.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
And the devs for those mods only have to change the update script to an updater script. Its fairly easy to do, and is technically the right way to do things.
3.0.0.6 does not support flashing amend scripts. Google has moved to using Edify scripts, or updater-scripts. That is the only type of script that 3.0.0.6 will support.
and for those mods (that are not full ROMs and simply minor add-ons) you can select all clockwork recoveries, switch to 2.5.1.2, flash your amend script, reboot, all clockwork recoveries, 3.0.0.5, and you're back on 3.0.0.6. They are not (for the most part) game-changing situations where you find yourself in a bootloop and it is important to have a versatile recovery like 3.0.0.6. Most of the flashable fonts on XDA are amend scripts as well, so using that method is an easy workaround for cosmetic upgrades and other framework tweaks. You can make a mistake and put yourself in a bootloop flashing these things, but first timers and people struggling to understand what is important about the different recoveries are dealing with ROMs for the most part. If you are getting to the details with other mods, you should at least take the time to get to the details about ROM Manager and the differences in the available recoveries.
I had no clue that this forum had gotten bigger than an answer or two 0.o
Anyways, i have a couple of reasons for not flashing 3.0.0.6 manually. I'm still a bit of a noobie, i got my very first android phone on christmas and i have managed to flash multiple release candidates of cm7 since then. I haven't gained 100 percent confidence in my abilities yet. Also, the instructions say that flashing 3.0.0.5 in rom manager will flash 3.0.0.6, and 2.5.1.2 will flash stock recovery. It seems like if any newer recoveries were released it would be impossible to use rom manager to update it with the slightly different set up.
Also, i heard another guy say that having the phone boot in to recovery when plugged in to power could be a failsafe if the phone won't boot normally, so i'll stick with 3.0.0.5 until rom manager officially flashes 3.0.0.6 the easy way.
kimbernator said:
Also, i heard another guy say that having the phone boot in to recovery when plugged in to power could be a failsafe if the phone won't boot normally, so i'll stick with 3.0.0.5 until rom manager officially flashes 3.0.0.6 the easy way.
Click to expand...
Click to collapse
The original version of 3.0.0.6 in option94's thread also boots into recovery when plugged in.
Now available for the Evo Shift, go try it out and let us know what ya think about it!
If it aint broke, don't fix it.
VICODAN said:
If it aint broke, don't fix it.
Click to expand...
Click to collapse
I don't care I would still like a ICS touch recovery for the shift that works with rom manager.
I saw this a couple of days ago. I wouldn't mind getting it.
Sent from my PG06100 using Tapatalk
Been using it on the EVO. It's good, but not quite as responsive as TWRP was. It's basically just an enlarged CWM that's touchable, not quite designed for touch yet. On the otherhand its still nice and can't wait to see future progressions with it
Sent from my EVO 4G
notsointeresting said:
Been using it on the EVO. It's good, but not quite as responsive as TWRP was. It's basically just an enlarged CWM that's touchable, not quite designed for touch yet. On the otherhand its still nice and can't wait to see future progressions with it
Sent from my EVO 4G
Click to expand...
Click to collapse
Yeah according to koush's twitter he just "hacked" touch into cwm recovery so I'm sure he'll work on it more. Twrp is a nice recovery and koush is a really good recovery developer so I'm sure he'll make it better if possible. It's funny after finding out about twrp 2.0 being in development before it was even released I asked koush if it was possible to have touch in cwm. Now we're getting it lol.
notsointeresting said:
Been using it on the EVO. It's good, but not quite as responsive as TWRP was. It's basically just an enlarged CWM that's touchable, not quite designed for touch yet. On the otherhand its still nice and can't wait to see future progressions with it
Sent from my EVO 4G
Click to expand...
Click to collapse
Using it on my NS4G and honestly I like it better than TWRP. Everything being larger is reassuring, in TWRP I was always nervous because there was such a small area to select. With the items being so close in TWRP I always wanted my volume keys to work so I could make fine maneuvers and in CWM Touch they do. So you can use it just like regular CWM or with touch. Nice if you mess up your touch screen. And of course it also works with ROM Manager. I downloaded it from the site but I may actually donate the $2 for it too.
Touch recovery has just become available on my SHIFT!!! CHECKIN' IT OUT NOW, VERY COOL!
Let Me Put My Shift In U
letmeputdatipin said:
Touch recovery has just become available on my SHIFT!!! CHECKIN' IT OUT NOW, VERY COOL!
Let Me Put My Shift In U
Click to expand...
Click to collapse
I know I tested it for him last night but it's not stable. I wouldn't purchase it quite yet. Download it from the site and test it out. It will boot into recovery for about 5-10 secs format your cache then reboot to system/rom. Strange bug. It would be nice if someone else could confirm this.
sparksco said:
I know I tested it for him last night but it's not stable. I wouldn't purchase it quite yet. Download it from the site and test it out. It will boot into recovery for about 5-10 secs format your cache then reboot to system/rom. Strange bug. It would be nice if someone else could confirm this.
Click to expand...
Click to collapse
I just flashed it through fastboot and haven't seen that issue. I'm actually in the process of making a backup
Edit: Weird thing.. made a backup and rebooted, everything was gone. It brought my ROM completely back to barebones.. even gapps were gone. Restoring with Touch now to see what happens.
Sent from my Android powered Tenderloin
crump84 said:
I just flashed it through fastboot and haven't seen that issue. I'm actually in the process of making a backup
Edit: Weird thing.. made a backup and rebooted, everything was gone. It brought my ROM completely back to barebones.. even gapps were gone. Restoring with Touch now to see what happens.
Sent from my Android powered Tenderloin
Click to expand...
Click to collapse
Hmm, well I did fastboot erase recovery before flashing, not sure if that has anything to do with it. What recovery did you flash this on top of, just the previous cwm recovery? You can also report bugs to him on irc freenode #koush
sparksco said:
Hmm, well I did fastboot erase recovery before flashing, not sure if that has anything to do with it. What recovery did you flash this on top of, just the previous cwm recovery? You can also report bugs to him on irc freenode #koush
Click to expand...
Click to collapse
Yeah I was coming from the previous version of cwm. I just did a restore and everything is fine. Ill probably mess with it a little later when I have some free time.
Sent from my Android powered Tenderloin
I'm not at my pc to try fastboot again but I did flash the previous cwm recovery and it works fine. Then I flashed the new touch recovery with the flash_image command in terminal emulator and I'm getting the same results as before. This is really annoying me because I would like to get this recovery working and I don't know WTH is going wrong here. Maybe it's the new firmware update? I doubt it. Anyways hope to here from more people that try this out.
Edit: when I get a chance later I'll flash with fastboot without running the fastboot erase recovery command and see how it goes.
I must have got lucky... I used joey krim's GUI Flash App and flashed it over the top of the prior clockwork mod recovery... I'll spend a little time tonight trying to replicate...
Sent from my PG06100 using Tapatalk
Well just used the touch recovery to flash my first ROM and had no issues. Maybe my first experience was fluke.
Anyway, liking this recovery so far.
I'm gonna be using GUI flash like Drob since its just easier for me
question for the pro's, if I understand all this I just rename the recovery-clockwork-touch-5.8.1.6-speedy.img to PG06100.img , boot into fastboot and flash ?
jrny99 said:
question for the pro's, if I understand all this I just rename the recovery-clockwork-touch-5.8.1.6-speedy.img to PG06100.img , boot into fastboot and flash ?
Click to expand...
Click to collapse
I'm nit sure about that (although I feel it should be .zip but probably wrong), but you could use Flash Image GUI from the Market or use fastboot from your PC. You'd just stick the .img file in the same folder as fastboot, cd there and type "fastboot flash recovery whateveryounamedit.img". Personally I like Flash Image, works well for flashing kernels too.
jrny99 said:
question for the pro's, if I understand all this I just rename the recovery-clockwork-touch-5.8.1.6-speedy.img to PG06100.img , boot into fastboot and flash ?
Click to expand...
Click to collapse
Yeah, just to reiterate what J-Ice already said... don't rename the img, just flash through fastboot.
I can confirm this is not working for at least one other person on the latest firmware update via twitter messaging...I've tried GUI, fastboot, flash_image, all same results.
TWRP Recovery is officially dead. I just tried to use it with the latest Kindle version and it is not working for me at all.
However I was able to use Custom CWM Beta 2 http://forum.xda-developers.com/showthread.php?t=1454241.
I was able to fast boot to its recovery mode and make a backup of my Kindle. Thank goodness! Now I feel confident trying out something else besides Amazon's underwhelming Android.
While development on TWRP 2.0 has been halted it still works just fine. I have it on my Wife's fire. There is no functional reason for it to stop working.
I have CWM-Touch modified by DooMLoRD on mine and it works as well.
From the OP's message it is not clear if he had problems loading it, or using it, though I can't think of why if it was loaded it wouldn't work.
I guess my point is ...
Its not worth using something that is dead and that the Custom CWM-Based Touch Recovery 5.0.2.7 for Kindle Fire works just fine and is in active development. I'd rather spend my energy testing and using CWM Touch than TWRP at this point.
Its install process was easier and actually worked for me while the TWRP install did not work for me at all. TWRP never showed an install or reboot screen like it was supposed to.
TWRP works fine. Just a matter of preference.
misleading subject line.
I think it a little misleading to say twrp is dead.
I've never used cwm, I suspect it works just as good.
If it ain't broke don't fix it. If you can give me a valid reason why I
should switch I will. And it being actively developed isn't good enough.
I was on 6.2.2, installed Burritoroot 3 via adb, downloaded twrp 2.0 manually and put it into the kindle utility folder (check the batch-file for correct name) and pressed "install twrp" in kindle utility.
For a "officially dead and not working software" it was pretty easy to install and works like a charm.
twrp works fine as long as you never "reboot to recovery". twrp never fixed the bootmode during system reboot.
I switched, because of no support. I love cwm, and I'm familiar with it. plus, reboot system properly sets the boot mode. which to me. is what's supposed to happen.
Sent from my HTC Glacier using XDA App
Sambena said:
I think it a little misleading to say twrp is dead.
I've never used cwm, I suspect it works just as good.
If it ain't broke don't fix it. If you can give me a valid reason why I
should switch I will. And it being actively developed isn't good enough.
Click to expand...
Click to collapse
Only it isn't misleading. TWRP is dead. It is no longer being developed.
See here http://teamw.in/blog/15 where they say "We will be abandoning twrp". They also state that they will be putting their efforts directly into ClockworkMod. Which I think is commendable and will actually help improve CWM Touch in the long run.
We should support and use active projects. As TWRP being abandoned is relatively new news I thought I would post about it because I only found out about it after researching how to get it installed properly. I abandoned trying to make it work when I realized it was no longer being developed and CWM Touch seemed to be the place to go given the news.
I am real new to the KindleFire community but so far loving my Kfire. I see in slot of posts they say to use TWRP to install or update a ROM. Since I have CWM installed can I use it instead are they interchangeable for installing files?
Hope that make sense.
Thanks
Rod
most people are taking about twrp because it was the first recovery for the kf
cwm is quite new for the kf
you can use both to install roms ...
Cwm is able to be updated by current developers. Twrp looks cool, but just needs to be updated. If someone updates the reboot wrappers it'd be a winner. But I do like and prefer cwm
Sent from my Kindle Fire using xda premium
yeah twrp is dead for our device. cwm is still alive though
paranoid android85 said:
yeah twrp is dead for our device. cwm is still alive though
Click to expand...
Click to collapse
Is there or link or how-to to swtich from TWRP to CWM? Does CWM have all the features as TWRP? I have been using TWRP since I rooted the KF, have used it to back up, flash new roms to try out, flash back to my backup. CWM does all this, just dosn't have the nice CWM interface?
ontwowheels said:
Is there or link or how-to to swtich from TWRP to CWM? Does CWM have all the features as TWRP? I have been using TWRP since I rooted the KF, have used it to back up, flash new roms to try out, flash back to my backup. CWM does all this, just dosn't have the nice CWM interface?
Click to expand...
Click to collapse
The easiest way is to use THIS method, just be sure to unzip the file on your Kindle rather than on a computer or it may not work correctly. The only difference I've noticed between CWM and TWRP is that CWM does not compress the backup so the file is a lot bigger, my backups used to be in the low 500mb range and now they are in the low 800's.
Any particular reason to migrate to CWM? I have TWRP from the first day ant it doing a job very well. So, did CWM have any new features?
gett said:
Any particular reason to migrate to CWM? I have TWRP from the first day ant it doing a job very well. So, did CWM have any new features?
Click to expand...
Click to collapse
Development should be the main reason imo I think the interface looks way better. I got annoyed by the flickering backlight with twrp. It does all the same things, but cwm looks better. Plus before I switched, twrp wouldn't flash roms or gapps all the time, it would get stuck and I would have to reboot
Sent from my SPH-D710 using Tapatalk
gett said:
Any particular reason to migrate to CWM? I have TWRP from the first day ant it doing a job very well. So, did CWM have any new features?
Click to expand...
Click to collapse
For me there was not a reason to use TWRP as I have been using CWM for the last several years on smartphones and was more comfortable with it. I also read several articles where people had issues with TWRP so with as much problems as I was having trying to root my kindle because of USB driver I wanted to stick with something I know. So I thought it best to stick with and old friend I was used too. Not saying one is better than the other I just like CWM better for me and think it gives me more options to perform operations on my phone and kindle.
Rod
How have the pros and cons changed with the intro of TWRP 2.1? I am currently using CWM touch but prefer the TWRP interface, but don't want to sacrifice any features.
phantom9x said:
How have the pros and cons changed with the intro of TWRP 2.1? I am currently using CWM touch but prefer the TWRP interface, but don't want to sacrifice any features.
Click to expand...
Click to collapse
all the reboot option in twrp are still broken so Cwm is still the way to go and mabe im ocd but i like haveing Cwm on my phone and tablet plus you dont have to worry about accidenty hiting reboot to recovery and being in a boot loop
different versions of CWM touch?
I just switched from CWM touch (DooMLorD) v1.0 Final to v5.0.2.7-kf1.5 I was wondering what the differences are? I tried the Change UI color feature, but it doesn't seem to work, just stays red. is there something I'm missing? and what else was changed?
its just cleaned up. not sure why it wont change colors, works fine on my device I tested all the colors when I posted the screen shots.
Sent from my HTC Glacier using xda premium
smirkis said:
its just cleaned up. not sure why it wont change colors, works fine on my device I tested all the colors when I posted the screen shots.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I installed it and changed it to cyan with no problem! Thanks!
PS, not to resurrect a dead issue, make sure you use Root Browser (if you used Root Explorer it may not have updated check the version).
smirkis said:
its just cleaned up. not sure why it wont change colors, works fine on my device I tested all the colors when I posted the screen shots.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Hmmm....I followed the instructions to the letter, even retried it, then rebooted, no luck, installed TWRP, rebooted, reinstalled CWMT 1.5 still no luck with colors. It's not really a big deal, I'm just Being kinda OCD! Everything else about it work perfect though....
P.S. I realize this probably belongs in the DEV thread, but I can't post there yet YAY For Noobs!!