Database Users

[POLL]Amon Ra or Clockwork

Was wondering which recovery everyone likes and why. Been using Ra since my G1 and I love it. (searched around for one of these and didnt see it. Mods delete if there was already one of these polls)

Amon all the way
Sent from my EVO using the Earths core to power my death ray

So...since this brought up...I see that some ROMs don't work with some recoveries? Is that correct? I swear it seems some ROMs only work with clockwork...but then I read all over that clockwork is buggy...or doesn't seem to work for everyone...or something.
I was thinking Amon Ra was the way to go.
I'll follow the answers to this one as well.

sablesurfer said:
So...since this brought up...I see that some ROMs don't work with some recoveries? Is that correct? I swear it seems some ROMs only work with clockwork...but then I read all over that clockwork is buggy...or doesn't seem to work for everyone...or something.
I was thinking Amon Ra was the way to go.
I'll follow the answers to this one as well.
Click to expand...
Click to collapse
Thats true. As far as I know, there have been issues with Clockwork not wiping correctly(I know someone like that)and causing bootloops after flashing. I dont know of any roms that dont work with Ra, but I believe Rom Manager will only work with Clockwork.

Clockwork since it is compatible with ROM Manager.

Clockwork since it has a back option in the menus. It's also updated frequently.

I've been running clock on the evo. I tried putting amon in but I guess I'm too stupid cause when I tried following the directions, I borked the phone good and it took me awhile to get everything back into working order. I could flash it now with rom manager but I'm kinda afraid after the last fiasco.
Sent from my PC36100 using XDA App

I've found that using both have worked for me the best. If I'm running Fresh Rom I will use Amon Ra's but I'll use clockwork for cm6. Its so easy to jump back and forth between recoveries using rom manager its never really an issue. Either way both developers are awesome and their recoveries both have good things to offer

anyway to switch back to Amon? not feelin the Clockwork im too use to it...

seriousblack25 said:
anyway to switch back to Amon? not feelin the Clockwork im too use to it...
Click to expand...
Click to collapse
Use ROM Manager to "flash alternate recovery."

another poll
dglowe343 said:
Was wondering which recovery everyone likes and why.
Click to expand...
Click to collapse
i was wondering the same thing exactly!! So a few days ago i asked the question on the Cyanogen forums... I got a lot of good responses and summarized the comments on the first post... check it out here: http://forum.cyanogenmod.com/topic/2562-best-recovery-for-evo-to-use-with-cm6/

I haven't had one single problem with clockwork recovery.

I like the recovery originally included with toastcfl's root found here. it's very similar to Armon's (don't know if things have to be signed or not), but you use the power button to go back instead of the double-press volume (which I find annoying to do).
I just don't like clockwork as much as the other two, that's just the way it is.

Using Amon Ra because I think it's the only recovery fully compatible with DamageControl.
Not sure of the actual "differences" between it and Clockwork - can anyone clarify?

oblivion0 said:
Using Amon Ra because I think it's the only recovery fully compatible with DamageControl.
Not sure of the actual "differences" between it and Clockwork - can anyone clarify?
Click to expand...
Click to collapse
I'm using clockwork with Damage Control I've had zero problems so far.

I hate Amon recovery... always have to move my ROM downloads to the root of the SD card... forget it 90% of the time and have to reboot to fix it... and that doesn't work so well if I borked my ROM.
I use Clockwork and have zero issues unless I'm trying to autoflash theme updates and such so I have to do those manually. Otherwise no complaints. And no signing issues with Clockwork either.

Amon_RA's recovery FTW!

Well, since rooting 24 hours ago, I've been using Clockwork via recovery boot (not through ROM Manager) and it's worked flawlessly so far. Backed up my rooted stock setup, flashed Fresh, DC, CM6, and then back to Fresh, wiped between every flash, and I've had no problems. Even flashed some Fresh Tweaks in the recovery boot. I actually flashed Amon Ra to see how I liked it . . . and I didn't. Mostly just navigating was a pain with the volume up+down thing, everything else seems like a wash. My only question is whether the Dalvik cache is really being wiped by Clockwork, since it takes half a second to complete when I select the option. I'm going to test it in a few minutes here.
Going to give Baked Snack a run for a while, we'll see how that holds up.

I have wondered that for awhile, silver. It may sound stupid but at least a confirmation in the log messages below would be nice.
Sent from my PC36100 using XDA App

herbthehammer said:
I have wondered that for awhile, silver. It may sound stupid but at least a confirmation in the log messages below would be nice.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Okay, I decided to test. Fired up ADB and booted into recovery from Android. Mounted /data and looked inside /data/dalvik-cache. There was a long list of .dex files. Then I unmounted /data and used the Clockwork menu to wipe the Dalvik-cache (this option is located under the "advanced" menu, NOT just the "wipe cache" option). Re-mounted /data and looked inside . . . and the dalvik-cache directory was gone. It took *slightly* longer than normal when I actually hit the button to wipe it (more like .7 seconds instead of .5), but it does appear that my Clockwork v2.5.0.1 is wiping dalvik just fine. And, of course, when I rebooted back into Android (rooted .6 stock at the moment) it took a long time to boot at the 4G screen, as the cache was being rebuilt. Once I was back in, I checked the /data directory again and dalvik-cache was back and full of .dex files again.
So there. No more speculating, just science.
And if you're ever worried about it, you can just use ADB to wipe the dalvik-cache yourself:
Code:
adb shell
mount /data
rm -rf /data/dalvik-cache/*
Then you can use the Clockwork menu to wipe everything else and flash your ROM. These three commands actually just delete everything inside the dalvik-cache directory, whereas Clockwork appears to remove the directory entirely. Doesn't really matter either way, the system will replace the directory if it gets deleted.
Mmm . . . terminal code.

[Q] Can't boot... have been meticulous... Help please?

This may "wreak of non-search" and I am sorry if it does. While I have searched, the overall panic that one experiences when you suspect a brick and cannot afford to have a brick.... (that, plus a friend purchased this Glacier for me to help me get back on my feet with respect to career/employment, etc., so a good amount of guilt is thrown into this mix)... all prevents me from rationally and methodically searching thread after thread to figure out why I am having the problem I am having.
I will be as precise as possible.
1. Back in Feb., I perm rooted with visionary... then about 2 weeks later, I read that this root was not true radio s=off perm root, so I used adb and the scripts to perm root again--using the wiki as a guide. Saved a copy of the partition 7 bin on my laptop as an added precaution. Also, BTW, I never flashed the engineering HBOOT. It didn't seem essential to do so... PLUS, in almost every guide it warned that this was the most likely chance for one to f*ck up and brick, so in the interest of erring on the side of caution, I skipped that.
2. I kept stock ROM for several weeks after that... just enjoying root and freezing bloatware with Ti, and doing other root-enabled mods... nothing too involved.
3. About 1 week ago, I finally decided to flash my ROM. I had Rom Manager (paid version), and had flashed ClockworkMod Recovery 3.0.0.5. Further, as an FYI, I had/have numerous nandroid backups on the SD, plus several Ti backups of apps/data... even sync'd this with dropbox, so I can access those now (which are not of any help obviously).
4. I first flashed a CM7 nightly build--wiped data and cache, and as far as I know followed the guides precisely. All was well...new ROM worked alright... some bugs, but it was nice to have the new features, etc.. And of course the mental gratification of having 2.3.3 (GB) instead of 2.2.1 (boring old froyo). I updated the nightly maybe 2 times... in each case, I simply flashed without backing up those ROMS or wiping data/cache as they didn't seem necessary, plus I still had all my stock rom nandroid backups on the SD.
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Since I cannot get into the phone... I am of course panicked... I have ADB on my laptop if needed, but I really am at a loss as to why this happened, and what I can do at this point....
Please, please advise. My utmost appreciation and sincerest gratitude in advance for any assistance.
Thank you!!!
syntropic

syntropic said:
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Click to expand...
Click to collapse
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
should come up to a white screen.

take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Sent from my HTC Glacier using XDA App

Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
Click to expand...
Click to collapse
No... that is what I meant when I said tried to "boot into recovery". And I got the 3 vibrate alerts and a blank screen, and nothing........

take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Click to expand...
Click to collapse
Will do... Thank you. DO you have any idea of where I f*cked up here??

Could be a number of things. Like wipe didn't go through completely , bad download, or just random crap out like a few others. Even flashing with the wrong cwr version can less to your issues. Lol like I said could be a number of things. Sorry I couldn't be more helpful.
Sent from my HTC Glacier using XDA App

OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....

I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Sent from my HTC Glacier using XDA App

syntropic said:
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
Click to expand...
Click to collapse
What recovery are you using? 3.0.0.5? and you're trying to flash a 2.2 ROM. Thats where the problem lies. See my post regarding this. It's in my signature, the green one.

I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Click to expand...
Click to collapse
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
EDIT: MUSTKll20... Well, you were right... This is not ROM specific. I tried Re-Flashing RC3, which previously worked fine. Now, since I have CWModRec 3.0.0.5, I need to use a 2.3 ROM.... So I thought I would start with this idea. So, I guess, I need to get whatever is corrupt deleted... So my only question thus remains: How do I wipe everything except the SD from within CWR?
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!

syntropic said:
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
Click to expand...
Click to collapse
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
and android phone have a method of using a section of the SD card for their memory banks. I'm not really sure how it works either, but it does. You can wipe the internal w/o wiping the SDcard.
Wiping the phone from with in the recovery image will not touch the SDcard, it will only wipe the internal. You can format the SD card from the Recovery Image, but i'll leave that dog sleep so we do not it accidentally.

last little clean-up question.
Sorry to bump this... last LAST question...
Mustkll20: I realized that you were correct to suggest to wipe everything except the SD... Something is corrupt.
But I am not real sure exactly how to wipe EVERYTHING except the SD, from within CW recovery... Since that is the only mode I have available to me. Once I wipe, I will reinstall CM RC3, then update Clockworkmod Recovery to 3.0.0.6, and then try and download RC4 again using another method, and re-flashing.
I would trial and error this, but do not want to wipe the SD.
Thanks guys... seriously.

You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
Click to expand...
Click to collapse
I didn't see your reply... ummm. and I do need to wipe.. Because I have tried to re-flash both RC3 and RC4, and I get what must be a "bootloop": During the CM splash, it stops and then reboots---over and over. It never did that before.... so my problem is something else...
I don't know what else there is besides the SD and the ROM, but whatever it is, I need to delete it. So should I do a factory reset???

Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.

lowandbehold said:
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
Click to expand...
Click to collapse
Yep... I know the thread is not for thrillseekers (i.e., its boring), but I mention that I discovered this phenomenon... so I really wasn't in all that bad a spot to begin with.
I still need to figure out how to fix my current problem.... all CM RCs (I can only flash 2.3 ROMs because of CW 3.0.0.5) go into what I guess is a bootloop. In other words, they do not ever boot, just crash and restart. And the RC3 ROM I used worked fine before this... so something else is causing this problem. I need to wipe everything I guess, but I just don't know how... without touching the SD card and from within Clockwork Recovery.

Ok. Go into recovery.
1. Wipe data/factory reset
2. wipe cache partition
Both of these are on the main screen.
Go to advanced
3. Wipe Davlik Cache
Go back to main screen
Go into mounts and storage
4. format boot
5. format system
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.

lowandbehold said:
Ok. Go into recovery.
{...}
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
Click to expand...
Click to collapse
Thank you for the concise and thorough response!!!!!!! Id thank you, but have used up my allotment. get ya tommorow!!

And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?

syntropic said:
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
Click to expand...
Click to collapse
You can thank the Google c&d order for that. Go to cyanogenmod.com. there is a link there for the gapps zip.
Sent from my HTC Glacier using XDA App

OK... I thoght Gapps.zip was just Google Docs. Luckily, I had that on my SD card from one of my many ROM downloads. I see why they had to make it separate.
But I am installing it, and everything is great... And I learned a lot too... Which can only mean trouble.
Thanks!

More boot loops, not like the others

Ive got the following on the HBOOT screen
GLACIER PVT ENG S-OFF
HBOOT=0.85.2007 (PD1510000)
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Oct 11 2010, 12:44:14
Clockwork v3.0.0.6 (using this method http://forum.xda-dev...ad.php?t=944681 )
Okay so with that for reference, I'd like to find out why I can't flash CM7 without the blue Andy bootloop. I understand that a fresh install takes time to load, I gave it 30mins before a battery pull, I then returned the battery, hit the top power button and let that sit for another 20. Before I flashed the ROM (through recovery) I made the following wipes in this order; wipe data/factory reset and then wipe cache partition. I've flashed other ROMs that have flashed without issue (Ice Glacier 1.1.6 themed and Royal MIUI) but, lets face it CM owns. Any help would be appreciated. Thank you for reading this.

DHSdrone said:
Lets face it CM owns.
Click to expand...
Click to collapse
No, Sense owns.
With that out of the way, the only thing I can think of is a corrupt download. Try re-downloading the zip to your PC and copying it to your SD. My other thought was a bad recovery, but since you've successfully flashed other ROMs, that doesn't seem likely.

you didn't wipe dalvik in advanced, do that and bootloop will stop...

darinmc said:
you didn't wipe dalvik in advanced, do that and bootloop will stop...
Click to expand...
Click to collapse
Little known fact, if you wipe data, you already wiped dalvik.

option94 said:
Little known fact, if you wipe data, you already wiped dalvik.
Click to expand...
Click to collapse
Mmmhmm, the only thing it could be is bad download or some other mysterious gremlin lol
Sent from my HTC Glacier using XDA Premium App

option94 said:
Little known fact, if you wipe data, you already wiped dalvik.
Click to expand...
Click to collapse
Well then I retract my statement...

when you say bad or corrupted download I assume your talking about the recovery. I thought the same as well, Ive tried both versions of what was posted as the correct, best, and or easiest method of clockworkmod recovery. Im not sure if both versions were in fact the same recovery.img but they both worked for the roms Ive flashed except for cm (nightly 29, cm7-rc2, rc3,and rc4). The fact tjat I cant get this to work, only makes me want it more.

DHSdrone said:
when you say bad or corrupted download I assume your talking about the recovery.
Click to expand...
Click to collapse
No, I mean the CM7 download. The actual ZIP file that you flash.
As far as recovery versions, only 3.0.0.5 and 3.0.0.6 can flash CM7.

Ive tried flashing several different versions of cm7, starting with rc-2 through rom manager. When that gave me my first boot loop I went back to the method I was more familiar with. With trying the different versions I don't see how they were all currupt or broken downloads. I haven't tried any of the cm froyo roms yet.
As far as my earlier statement of "cm owns" I mean no disrespect of any of the other rom developers (including those that did work properly the first time). Ive just came from the G1 and cm is the only rom I ran. Sense may be the best way to go, it's not something Ive given much consideration or time.

I have had the same issue except mine seems to be all 2.3 (Gingerbread) based roms, they all go to bootloop. I have no problem however flashing any of the 2.2 based roms. I also have cwm 3.0.0.6

I had the same issue everytime with different nightly releases. After wiping everything and formatting boot and system still would do it. I found if you wipe then install cm7 only the phone boots fine then reboot setup wifi if your using it the go back into recovery install gapps and it works fine.
Sent from Teh retardarded duc using XDA Premium App

Im unable to get a full boot. After reading several similar sorties I've always turned off all wireless radios. Will post a logcat later today.

Ok so was able to get mine to Boot completely Finally!!! I am somewhat of anoob so sorry if it seems confusing.
1.From recovery wipe data/ factory
2. Wipe cache
3.Advanced > wipe dalvik
4.Mounts>format boot
5.Mounts>format system
6.Advanced> partion SD card (I believe I used 256) No swap partition(dont know if it matters)
7.Mount USB and transfer cm7 and Gapps
8.Flashed cm7 only not apps.
9.Reboot phone (should boot all the way up)
10.Go back to recovery and flash Gapps
11.Reboot phone
My phone booted up very quickly. I hope this helps anyone else out there with the same issue

no more loop da loops
After searching google, and then to various forums, and finally giving up and posting to 2 separate forums, Ive come to say THANK YOU !!! You are all evil geniuses of the highest degree and I bask in your greatness. Ive been overlooking one thing, that is the "if things go bad, try the sd-card format" well I did and it worked. Now that the derp has left my head, and the panic has subsided I can see now that my problem was in fact like many others, and the answers were right in front of me. Again thanks for being patient and coming together as a community to help me out.

Rom installations / flashing conformity.

This is probably just me but I'm starting to think we are over complicating the ROM installation process by having different versions of recovery and flashing. We already have KIES and odin, do we need different recovery installations too?, tegrak, CMR, chainfires etc? We are now seeing ROMS that can only be flashed with one type which cant be good as its causing fragmentation of development. I may also have contributed to two people who have bricked their phones recently.
Why on earth are we doing this?, wouldnt it be much better to use one type of recovery, that way anyone can flash any ROM with it without having to change root / kernels etc.
I am sure each different version has its own advantages but are these really worth the fragmentation it is causing, be nice if devs all decided to get together and come up with a one fits all CWR which is then used on all ROMS and all Phones.
I can dream cant I, feel free to put me straight on this if I am missing something here.

couldn't agree more. i rooted my phone the other day with a kernel change, but now i want to isntall a rom but cant even start to work out the way to get cwm on to flash a rom!!! annoyinh to say the least.... the x10 and sgs1 i had were a breeze

da.trute said:
This is probably just me but I'm starting to think we are over complicating the ROM installation process by having different versions of recovery and flashing. We already have KIES and odin, do we need different recovery installations too?, tegrak, CMR, chainfires etc? We are now seeing ROMS that can only be flashed with one type which cant be good as its causing fragmentation of development. I may also have contributed to two people who have bricked their phones recently.
Why on earth are we doing this?, wouldnt it be much better to use one type of recovery, that way anyone can flash any ROM with it without having to change root / kernels etc.
I am sure each different version has its own advantages but are these really worth the fragmentation it is causing, be nice if devs all decided to get together and come up with a one fits all CWR which is then used on all ROMS and all Phones.
I can dream cant I, feel free to put me straight on this if I am missing something here.
Click to expand...
Click to collapse
But everyone is using CWM anyway...
And the .zip is a standard way to flash a ROM. So in theory, you can use any recovery to flash your zip
So there's no need to come up with some one-size-fits-all, as the zip files used meet a standard

Freedom to choose is a great thing. I like having options.

pulser_g2 said:
But everyone is using CWM anyway...
And the .zip is a standard way to flash a ROM. So in theory, you can use any recovery to flash your zip
So there's no need to come up with some one-size-fits-all, as the zip files used meet a standard
Click to expand...
Click to collapse
I am currently using cognition ROM, are you suggesting I can download any ROM, say Villain and copy to my SD and install without doing anything else?, I dont think that is the case, it mentions a different root, as does extreme. Cog and mui have no mention of changing root.

Intratech said:
Freedom to choose is a great thing. I like having options.
Click to expand...
Click to collapse
It is yes, however you seem to have misunderstood the thread, having different methods being forced up you by different cooks is not choice, choice would be that all methods were compatible and interchangeable, they are not apparently. Some require different roots / kernels.
EDIT. not suggesting anything is really being forced on us, I appreciate all dev work, just hoping for a bit more conformity of installation process.

da.trute said:
I am currently using cognition ROM, are you suggesting I can download any ROM, say Villain and copy to my SD and install without doing anything else?, I dont think that is the case, it mentions a different root, as does extreme. Cog and mui have no mention of changing root.
Click to expand...
Click to collapse
You copy it to internal SD, pull your head out of your ass, turn phone off, turn phone on holding menu and volume up and choose to flash zip from SD card.
Just.
Like.
Every.
Other.
Rom.

seshmaru said:
You copy it to internal SD, pull your head out of your ass, turn phone off, turn phone on holding menu and volume up and choose to flash zip from SD card.
Just.
Like.
Every.
Other.
Rom.
Click to expand...
Click to collapse
Cognition uses CMR root, Villain uses CF-root, I am pretty sure you cannot flash Villain straight of the top of a non CF rooted phone, or I am wrong?

da.trute said:
Cognition uses CMR root, Villain uses CF-root, I am pretty sure you cannot flash Villain straight of the top of a non CF rooted phone, or I am wrong?
Click to expand...
Click to collapse
See, if you actually had developed the ability to read, you would know that all root is is the su script in the ROM and SuperUser.apk, nothing more.
You would also know root has nothing to do with flashing ROMs, since you can have CWM as recovery without having root.
Now if you're flashing an entirely different ROM you might want to select "wipe data/factory reset" before flashing but you can still flash using CWM.
Turn phone off, turn phone on holding volume up and center button, select wipe data/factory reset, and then flash zip from SD card.

Wow. He's just asking a question. Why belittle people for asking?

duuurp said:
Wow. He's just asking a question. Why belittle people for asking?
Click to expand...
Click to collapse
Because I see exactly 3 threads on the same page that could either answer his question or link him to the answer. But people are too lazy to read.
Due to people like this we have a thread here which isn't needed at all since there is conformity to flashing across all ROMs. All because people make claims about things when they don't even know how it works.

The big difference in swapping from one custom rom to another is not the method of flashing but do you need a clean phone to install a custom rom on top of another one .
My personal choice is a fully wiped phone before installing a new custom rom .
Methods CWM or Odin mostly CWM as thats the major choice for devs .Kies is not a rom flash tool .
Choice also gives a better recovery option .
Villain on top of or below Cognition both use same flash method via rooted CWM flash .
The problem on this forum is not three or four choices but a complete refusal by many to even bother reading any instructions .
jje

duuurp said:
Wow. He's just asking a question. Why belittle people for asking?
Click to expand...
Click to collapse
Hi, you get used to these ***** after a while

seshmaru said:
See, if you actually had developed the ability to read, you would know that all root is is the su script in the ROM and SuperUser.apk, nothing more.
You would also know root has nothing to do with flashing ROMs, since you can have CWM as recovery without having root.
Now if you're flashing an entirely different ROM you might want to select "wipe data/factory reset" before flashing but you can still flash using CWM.
Turn phone off, turn phone on holding volume up and center button, select wipe data/factory reset, and then flash zip from SD card.
Click to expand...
Click to collapse
You have to change kernel at the end of flash on Villain which I suppose isnt the same but is still a difference in installation process
what about touch extreme, whats this about then?
Make sure you got CF Root CWM (not the clockworkmod root) go into CWM, flash zip file, done! its that simple!
PS. some roms out there installs through clockworkmod, not the one by Chainfire, in those cases you must flash Chainfires Root with his version of CWM first!

da.trute said:
You have to change kernel at the end of flash on Villain which I suppose isnt the same but is still a difference in installation process
what about touch extreme, whats this about then?
Make sure you got CF Root CWM (not the clockworkmod root) go into CWM, flash zip file, done! its that simple!
PS. some roms out there installs through clockworkmod, not the one by Chainfire, in those cases you must flash Chainfires Root with his version of CWM first!
Click to expand...
Click to collapse
So let me see, it says flash the .zip with CWM.
So... Lets turn phone off, turn phone on holding volume up, center button and power button, wipe data/factory reset, and then flash .zip from SD card.
All of a sudden it magically works.
PROTIP: They're talking about the CWM app, which you don't need, every ROM still has clockworkmod recovery installed so rebooting with volume up, center button and power button will always let you flash the .zip file.
Kernel files should always be flashed with Odin if you are flashing them seperately since it gives better security. Even if they have a flashable .zip.

It may seem like there are a hundred different versions of CWM recovery but they're all based on the same thing; CWM. They all work on the same premise of copying the zip to the phone and then flashing. Some have integrated apps, some don't but the basic premise remains. The other option is Odin/Heimdall but as one is .tar based and the other is .zip there shouldn't be too much confusion here

seshmaru said:
So let me see, it says flash the .zip with CWM.
So... Lets turn phone off, turn phone on holding volume up, center button and power button, wipe data/factory reset, and then flash .zip from SD card.
All of a sudden it magically works.
PROTIP: They're talking about the CWM app, which you don't need, every ROM still has clockworkmod recovery installed so rebooting with volume up, center button and power button will always let you flash the .zip file.
Kernel files should always be flashed with Odin if you are flashing them seperately since it gives better security. Even if they have a flashable .zip.
Click to expand...
Click to collapse
what does this actually mean then?
"Make sure you got CF Root CWM (not the clockworkmod root)"

I have flashed all three roms using the exact same method .
Changed kernels four times this week using CWM .
Revived one bricked phone using Odin .
jje

Hollow.Droid said:
It may seem like there are a hundred different versions of CWM recovery but they're all based on the same thing; CWM. They all work on the same premise of copying the zip to the phone and then flashing. Some have integrated apps, some don't but the basic premise remains. The other option is Odin/Heimdall but as one is .tar based and the other is .zip there shouldn't be too much confusion here
Click to expand...
Click to collapse
which kind of proves my point really, if they all do the same thing then there is no need for them and no need to stipulate their usage, it just makes flashing more confusing for noobs.

da.trute said:
which kind of proves my point really, if they all do the same thing then there is no need for them and no need to stipulate their usage, it just makes flashing more confusing for noobs.
Click to expand...
Click to collapse
No, there is only 1 method for ROM flashing, CWM. Every ROM has CWM, CWM is the end all be all for you, no matter what different apps do, they all use 1 method CWM. CWM CWM CWM. Stop being dense and read up before posting dumb factually wrong claims.
Every single ROM can be flashed by holding volume up, center button and power, how difficult is it to grasp this concept?
Here this video should help you.
http://www.youtube.com/watch?v=JmvCpR45LKA

Best wiping script, and how to check current version of recovery?

Been out of the flashing business for awhile I need to get caught up with everything and get everything up to date.
I have seen like 4 or 5 scripts that you can flash before you root, what is the best one available?
How can I find out what my current recovery version is and update to the lastest? I have Amon_RA right now.

jhoffy22 said:
Been out of the flashing business for awhile I need to get caught up with everything and get everything up to date.
I have seen like 4 or 5 scripts that you can flash before you root, what is the best one available?
How can I find out what my current recovery version is and update to the lastest? I have Amon_RA right now.
Click to expand...
Click to collapse
Anyone? Calkulins?

I have used Calkulin's "Format All" ever since he released it ... never a hiccup. Also, if you will check your SD Card and look for the recovery image file, it should tell you which version you have. It will look something like "recovery-RA-supersonic-v2.3.img" ... which btw is the most current. You can also boot into recovery, and the version will be there.

One of the best ones is King's Format All.zip. Can get it from any of the King/eVoKings threads in development.
Just boot into recovery. Most AR recoveries show the version number upon loading. Version 2.3 works very good for about anything.

As said above check Recovery at bottom of screen. Load Amon Ra 2.3 if you don;t already have it. I like using CALKULIN'S Format All script. It will wipe everything, perfect if going to a different ROM. I tend to run it twice for good measure.

I use VR_Superwipe , ive never had issues.

open up the scripts in notepad and compare them. most are identical, almost word for word. most also comes from calk's format all.
if you use an ext partition, don't forget to wipe that manually.
Sent from my PC36100 using Tapatalk

If you have Amon Ra, you don't NEED a wiping script.
Just wipe everything in recovery, and it's fine.